5 replies to this topic

[Moskus]

I'm porting a FTP client class I have lying around (it's actually from Microsoft in 2003) to the .NETMF and VB.net. However, after the port the code halts as it can't receive more than 256 bytes from the FTP server, regardless the size of the buffer.

Just for fun, I copied the class to a regular Console application. It works without problems.

Here's the code.

Do While (True)
            Array.Clear(m_aBuffer, 0, BLOCK_SIZE)
            m_iBytes = m_objClientSocket.Receive(m_aBuffer, m_aBuffer.Length, 0)
            Debug.Print("m_iBytes: " & m_iBytes)
            m_sMes += Encoding.UTF8.GetChars(m_aBuffer, 0, m_iBytes)
            Debug.Print("m_sMes in loop: " & m_sMes)
            If (m_iBytes < m_aBuffer.Length) Then
                Debug.Print("m_iBytes is less than the buffer")
                Exit Do
            End If
        Loop

The BLOCK_SIZE is set to 512. m_objClientSocket.Receive stops after reading 256 bytes. I tried to change the size to 128 just to test it. The loop continues until .Receive has read a TOTAL of 256 bytes.


I am lost. Any pointers?

[Moskus]

I forgot to add the Class. See the ReadLine() function:

Attached Files

•  FtpClient.zip   4.7KB   8 downloads

[Moskus]

Anybody? Is it a bug with either the VB implementation or Sockets?

[erich]

Does it run in the Emulator? I am also having socket.Connect issues in C#(different config). It hangs before the stage you are at, but works OK in the emulator.

[Moskus]

I haven't tested with the emulator yet, but I will.

I sometimes have issues when Creating the socket:

m_objClientSocket = New Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp)

and... resolving the DNS seldom works. I have to use the direct IP.

Dim ip As System.Net.IPAddress = Dns.GetHostEntry(m_sRemoteHost).AddressList(0)
Dim ep As New IPEndPoint(ip, m_iRemotePort)

There seems to be some issues with Sockets in the 4.2 RC...

EDIT: You're right. In the emulator it works without hickups.

[Moskus]

Hmmmm! I believe the network connection for the Netduino is deemed "unstable" at best... I'll open a new thread on that.