ftp client hangs after successful Port Command

I use FTP at the WINDOWS 8 command prompt. After successful connection to the host any command (like DIR, mput etc) hang.

Message: 200 Port Command Successful and just hangs right there.

I have Windows 7 PC and Windows XP PC and they both work properly!!!


  • Edited by asapozh Sunday, October 26, 2014 7:40 PM
October 26th, 2014 7:38pm

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.

Free Windows Admin Tool Kit Click here and download it now
October 26th, 2014 8:04pm

I was running into the same issue. However, both of my machines were behind the same firewall and one of the FTP sites used to run on IIS v6. However, when I changed it over to a new server running IIS v8 that is when it hanged... However, if I use ftp.exe using the actual ip address of the site then it works just fine. So, it is not a fix but a work around. I do not want to give my clients direct IP access to through ny firewall. 
March 31st, 2015 10:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics