FTP Script Causing Problems

[DBCox]

Hello everyone,

I have been using an Excel file with a VBA macro to save and upload multiple files to three different FTP sites daily. It has been working for a few months, but I recently hit a snag with 1 of my 3 FTP servers. It seems to be freezing after the "put" command. The prompt reads:

ftp> put file.txt
200 PORT command successful.
150 Opening ASCII mode data connection

If I press cntrl+C, I get:

ftp> put file.txt
200 PORT command successful.
150 Opening ASCII mode data connection
Aborting any active data connections...
Connection close by remote host.

It is working fine for the other two FTP sites. I have tried adding the "quote pasv" command to switch to passive mode. It did not seem to help.

Filezilla works just fine when I input the credentials there.

Any help will be greatly appreciated!

Thanks,

David!

 

[xenou]

It seems very hard to debug this as it is dependent on the state of the server you are uploading the file to. That said, I have always used as the "base" a test of the procedure without VBA. Meaning, if you can put the file from the command prompt yourself, "manually", without VBA, then you should probably also be able to script it "automatically", with VBA. As the first, step, then, you should test whether you can put the file "manually" using the command prompt.

Note:

Filezilla works just fine when I input the credentials there.

This begs the question what credentials are required ...

 

[DBCox]

Xenou,

Thanks for the info. Good call on trying to connect and upload manually. It will not work. I tried uploading and downloading, and it would not work. I tried switching to passive mode manually, and it still would not work. Is there anything else I can try on my end? If not, is there something specific I can request be changed on the server end?

Thanks,

David

 

[xenou]

Usually if FTP doesn't work either it's a matter of permissions, or the network isn't allowing traffic on the FTP port. I'm not very good with that kind of stuff - ideally you can contact an admin for the network on the remote server. Possibly you can try pinging the server using the port to see if it is even listening on that port.