your server is behind a (dumb, or else SSL-blocked) firewall and is trying to use Passive-mode FTP.your client is behind a (dumb, or else SSL-blocked) firewall and is trying to use Active-mode FTP.Theres a good site on FTP with example logs here. To get real information on why the connection is stuck, you're going to have to use a client that logs all of the protocol commands to see what's really happening. Ive used Network Monitoring tools to try and see what ports it is calling but I cant figure that out. I believe my FTP client is using some long range port number(s) that are potentially blocked by one of my two firewalls. I have also opened those ports on my AWS (Amazon) firewall.

I have ports 20, 21 open on my Windows firewall. This leads me to believe its a Firewall issue, (or even an IIS7 issue?) but I am unsure what ports I need to open? If I specify the 'localhost' URL, I do not get the error. If I specify my full FTP URL, I get the hanging error. Here is what bothers me.if I use DOS FTP commands, I can login and use the 'DIR' command only if I use 'localhost' as my address. I can remote desktop on to the server and through DOS commands I can login rather easily.īut if I issue a command like 'DIR', it hangs with:Įverything I have researched and read points to Firewall ports and/or Passive/Active mode settings. I am setting up an FTP server on my Windows 2008 server (R2).Įverything appears to be installed correctly but I am having trouble using an FTP Client to login to my FTP server.

Umn filezilla connection timed out