Filezilla works at home but not at worksite

[Joshua Zev Levin, Ph.D.]

The computer is an HP laptop using Windows Vista Sp-2 last updated to version KB980248 on April 29.

It works fine over the wireless connection at home, but not at the boss's home office. We have an 11b wireless connection at home, backed by a cable (Comcast) connection. The boss has, I beleive, 11g backed by DSL.

The connection log at the boss's office is:

Status: Connecting to 97.74.215.115:21...
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 10 of 75 allowed.
Response: 220-Local time is now 23:10. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220 You will be disconnected after 3 minutes of inactivity.
Command: USER drzev49
Response: 331 User drzev49 OK. Password required
Command: PASS
Response: 230-User drzev49 has group access to: 450
Response: 230 OK. Current directory is /
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Extensions supported:
Response: EPRT
Response: IDLE
Response: MDTM
Response: SIZE
Response: REST STREAM
Response: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response: MLSD
Response: ESTP
Response: PASV
Response: EPSV
Response: SPSV
Response: ESTA
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: 211 End.
Status: Connected
Status: Retrieving directory listing...
Command: CWD /Label-Maker
Response: 250 OK. Current directory is /Label-Maker
Command: PWD
Response: 257 "/Label-Maker" is your current location
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PORT 71,125,141,252,239,124
Response: 200 PORT command successful
Command: MLSD
Response: 425 Could not open data connection to port 50510: Connection refused
Error: Failed to retrieve directory listing
Error: Connection closed by server

At home, the log is:

Status: Connecting to 97.74.215.115:21...
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response: 220-You are user number 6 of 75 allowed.
Response: 220-Local time is now 09:52. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220 You will be disconnected after 3 minutes of inactivity.
Command: USER drzev49
Response: 331 User drzev49 OK. Password required
Command: PASS
Response: 230-User drzev49 has group access to: 450
Response: 230 OK. Current directory is /
Status: Connected
Status: Retrieving directory listing...
Command: CWD /Label-Maker
Response: 250 OK. Current directory is /Label-Maker
Command: TYPE I
Response: 200 TYPE is now 8-bit binary
Command: PORT 71,125,141,252,246,43
Response: 200 PORT command successful
Command: MLSD
Response: 150 Connecting to port 63019
Response: 226-ASCII
Response: 226-Options: -a -l
Response: 226 4 matches total
Status: Directory listing successful

The attached file shows the logs in their original colors, first page at the boss's place, and the second page from home. The horizontal rules divide the log into sections that are either identical or different between the two situations.

[Joshua Zev Levin, Ph.D.]

Comparison of the two log files

[Joshua Zev Levin, Ph.D.]

I am now at a hospital, using their guest service. Sill cannot connect, except this time, after the "MLSD" command, the connection times out.

I heard there might be a firewall problem -- that is, the firewall in the wireless modem.

I've also tried WinSCP, and that connect much more consistently than Filezilla. Maybe it's time for a change.

[Tim Kosse]

Please don't attach .doc files, nobody can open those. For log files use .txt, for screenshots use .png

There is something wrong with your configuration, unless both the computer in your bosses office as well as that one at your home are one and the same. Pleas read ​http://wiki.filezilla-project.org/Network_Configuration for configuration instructions.

[Joshua Zev Levin, Ph.D.]

I have a better solution -- use WinSCP instead, because it doesn't give me these problems, and, in general, has a less-confusing interface.

Bye-bye.