Today I had the same problem on a system in the office when trying to connect to a new server. However, this time I was running a different ftp server (vsftpd) that gave me a helpful error message:
200 PORT command successful. Consider using PASV.
I tried the obvious, which was to restart ftp from the command prompt and then type PASV, but this gave the error "Invalid command." I found several posts that said that the ftp client built-in to Windows doesn't support passive mode. The good news is that
With Windows 7, enter this command to enter passive mode:
QUOTE PASV
With vsftpd, I was rewarded with this response, and everything started working:
227 Entering Passive Mode
As other have noted in the comments, this does not work on Windows XP.
Thanks.. That was helpful!
ReplyDeleteThis is true, the QUOTE PASV only puts the server into passive mode. While the built in version of windows FTP.exe won't use passive ftp. It always uses active.
ReplyDeleteto get around this you need to use a different ftp client such as http://www.passive-ftp.com
hope that helps someone!
Thanks dude! QUOTE PASV works and resolved an issue I was having downloading a file using the command line ftp in XP. I'll try to remember this in the future.
ReplyDelete@Anonymous: this won't help you. You cannot use it with the command-line ftp in XP, because it will only set the FTP-Server to passive mode. The Client still does not support passive mode.
ReplyDeleteon my win 7 32 bit QUOTE PASV or quote pasv doesn't work. After issuing the command it does say
ReplyDelete227 Entering Passive Mode
but tcpdump showed that the server is trying to connect back with its port 20 (TCP SYN packet seen) which is how active ftp works.
So, quote pasv is not actually setting the connection to passive but only showed it on command prompt.
Agree- pasv appears to work, then a subsequent Get command is replied to by PORT successful - boom, back to active.
ReplyDelete