|I suggest that you perform the steps manually, recording all your typed responses, then put that material into a test script. The hitch seems to be in the logon sequence. If you can successfully log in to the ftp server "manually", then put that same sequence into a text file, f/e: login.ftp, then try:|
I believe that Ftp sites run different server applications, and they vary in how they want the login information presented. You need to determine exactly what your FTP server wants by running a manual login. Then your script should simply re-iterate those manual entries. F/E, my server login ftp-script looks like this:
Until you get the "230 login successful" you will get no-where else.
With that material in a ftp script-file, I have no trouble logging in using the commandline: FTP -S:login.ftp
If/when you achieve login, the rest is fairly straightforward using the content that M2go offered.
message edited by nbrane