Implementing FTP client on W5200
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: Implementing FTP client on W5200
by Ricky ·
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,
RE: Implementing FTP client on W5200
by Eugeny ·
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.