Windows explorer uses pasv, command line does not. On 17/10/2013 3:10 PM, "Greg Keogh" <g...@mira.net> wrote:
> I haven't tried FileZilla yet, but in Wireshark I have a trace of FTP > failing from the command prompt and a trace working from Windows Explorer. > As I expected, the results are so different that I can't compare them. The > Windows Explorer trace is much longer and contains dozens of lines that are > gibberish to me as I'm not a networking guy. > > So I now have traces of one working and one failing, but I'm unable to > interpret or compare the results and I've learned nothing. > > Greg K > > > On 17 October 2013 15:01, David Connors <da...@connors.com> wrote: > >> On Thu, Oct 17, 2013 at 1:47 PM, Greg Keogh <g...@mira.net> wrote: >> >>> Chaps, FileZilla or Wireshark! The former I haven't used and I won't >>> learn anything if works or nor, unless it has some tracing facility. >>> >> >> You will learn exactly what the problem is. >> >> If it works with FileZilla using passive FTP then the problem is your >> firewall. Windows command-line FTP is active by default. >> >> With active FTP the server opens the data connection to you which is >> blocked unless you have a firewall that does stateful inspection. >> >> WIth passive FTP the client opens the data connection and that will work >> by default in most NAT/firewalls even without stateful inspection. >> >> David. >> > >
