Are all three machines on the exact same network using the same network connection? Are you also using command line FTP on the other two?
The most common cause for getting that result I've seen is where the client machine is using NAT and the destination server is also behind a firewall/router using NAT (eg neither end have a direct public IP address). In that instance the client often needs
to use Passive FTP in order to connect to the server, but passive FTP isn't available via command line FTP to it doesn't work. It will connect and allow you to login since those parts of the process use standard FTP, but after that when the connection will
start using passive FTP it locks up.
That said, if that's what is causing this then you should see the same effect using command line FTP from all three client machines is they're using the same connection.
-
Marked as answer by
Michael ShaoMicrosoft contingent staff, Moderator
Friday, November 07, 2014 8:29 AM