Implementing FTP client on W5200

TCP/IP Chip W5200
1

My company is implementing FTP on the W5200, but we are having a problem in that everything works well with just socket 0 open on the command port, but when we open socket 1 for use as the data channel, we run into the problems noted below.

For example, when we issue the USER and PASS commands to get logged in, then issue a QUIT all is well; we get the proper responses from the server.

The problem becomes when we open the data port. We don’t any longer get all the proper messages back via the command port. Worse yet, we are getting a 425 error code from the server, which means it is not happy with the port we are trying to send the data to, even though we are using the port that the server passed to us as a result of us having sent the PASV command.

We have spent many man-hours trying to resolve this problem. It becomes even more burdensome in that we have over 80 of the W820io modules in the field that require an important upgrade once this problem is solved.Once this problem has been resolved, our customer plans on purchasing 500 more modules.

Your early attention to this would be greatly appreciated. If you need more information or if we can answer any questions, please do not hesitate to let us know.

Kind Regards,

Craig Thomas
VP R&D
CNC International LLC
Loveland Colorado USA
970-988-1103

2

Hi. cthomas

I’m sorry to hear that your problem.

First, look out the firewall(Turn off the firewall).

Second, Try see the below information.

Have you looked at our ioLibraries([url]https://github.com/Wiznet/ioLibrary_Driver[/url])?

We provied /Internet/FTPClient application. it is tested al ftp (Now it has been upgraded. it has been provided by the al drive.[url]http://www.altools.co.kr/Download/ALDrive.aspx[/url]).

Third, try make a data connection to the Active mode.

Kind Regards,

3

Craig, hopefully you resolved the issue. Please refer here http://ipswitchft.force.com/kb/articles/FAQ/Error-425-Can-t-open-data-connection-1307565974920 - in general the same what Ricky says, but it also lists SSL implementation as possible issue. The issue actually may be (a) client can not reach server and server informs client that it does not get any client’s reaction within specified time (check ports on the network), or (b) client tries to access using wrong way (e.g. SSL issue). IMHO you can distinguish one case from another by assessing timeout you get 425 response back from the server: for case (a) will be “standard” timeout, for case “b” response should follow immediately.