12-13-2004 12:35 PM - edited 03-02-2019 08:34 PM
If an FTP put works, but get is failing, where should I start in the troubleshooting process? Do you think it's s TCP issue and how can I check?
12-13-2004 12:49 PM
Could you start with the error message you receive when the get command fails. It could be related to the MTU size issue in the downstream direction. Is there a FW or ACLs between your workstations and the server.
Thanks,
12-13-2004 08:15 PM
Could be standard / passsive mode, depending on the firewall(s) involved.
If it's a graphical client, click (unclick) the "Passive Mode" checkbox.
If it's a command line client, try "PASSV" at the "ftp>" prompt.
If it was a mode issue, you would not get a flakey connection, you usually wouldn't get a connection at all. However, you may be able to connect to one host, but not another.
How is it that it's "failed?"
-Scott
12-14-2004 05:30 AM
Scott,
If it was a simple case of standard vs passive FTP, the problem would happen with both get and put.
My 2 cents,
12-14-2004 05:44 AM
A couple of pretty obvious things, but frequently turn out to be problems when FTP GET fails:
- be sure that you are correctly specifying the directory and the file name.
- be sure that the file you are attempting to get has permissions that allow remote accessing.
- be sure that the account you are using on the FTP server allows for remote gets.
HTH
Rick
12-14-2004 06:18 AM
The 20 TCP port is closed? If yes, could you open this port and try again?
12-14-2004 06:43 PM
Brett, run a trace from ethereal http://www.ethereal.com/
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide