FileZilla Forums

Well. The FTP support in WinSCP is based on FileZilla. The shell extension of FileZilla is based on WinSCP's shell extension.

Other than that, both projects use entirely different toolchains for development. Sharing code between the projects thus involves a heavy amount of porting and is not generally worth it as rewriting from scratch will often be faster.

I had this same problem... it was the router. I rebooted it and it immediately worked.

Kudos to this article for pointing me (finally) in the right direction...

http://www.dougv.com/2009/02/10/ftp-err ... and-modem/

I have this problem BUT only when I try to log in on certain networks. So far I have:

AT&T cellphone (via local hotspot): works fine (albeit rather slowly).
Office wifi: Failed to retrieve directory listing
Hotels (various Hilton, Staybridge, Mariott): works fine
Finnair lounge: Failed to retrieve directory listing
BA lounge: works fine
Home wifi (local): works fine
Home wifi (remote, different location): works fine.

So I'm guessing that this is something to do with the use of different ports. But which ports? Is there anyway to find out which ports are being used or to select which port is used?

The server is Ubuntu 10.10 running proftpd.

Status: Connecting to a.b.c.d:21...
Status: Connection established, waiting for welcome message...
Response: 220 My FTP Server
Command: USER <user>
Response: 331 Password required for <user>
Command: PASS
Response: 230 User <user> logged in
Command: OPTS UTF8 ON
Response: 200 UTF8 set to on
Status: Connected
Status: Retrieving directory listing...
Command: CWD /Directory/xxx
Response: 250 CWD command successful
Command: PWD
Response: 257 "/Directory/xxx" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (a,b,c,d,228,144).
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing


Rob.

Response: 227 Entering Passive Mode (a,b,c,d,228,144).

This.

228*256+144=58512

Take the second-to-last number times 256 and add the last. This is the data port the server wants to use.

So, I had this for a couple of days, then figured out the problem. Everything had worked fine previously, then I had some issues with my router and replaced it. Initially I could not connect at all, until I remembered to set up the port forwarding. Being lazy, I chose the built-in FTP port forwarding on the router. However, that was forwarding everything to port 21. On attempting to connect, I would be able to connect, but I would get this error. I realized that the problem was the built in port forwarding was forwarding me to the active (21) port rather than the passive ports that filezilla was looking for. Dunno if this helps, but it might be worth taking a peek.

So I was having the same problem, been working for over a year and suddenly stopped working. Tried many of the recommendations in this thread with no luck.

One interesting thing I noticed, is I have two accounts I upload to comcast, one was working and one would get the error.

In the end I deleted a couple of files in the root directory using comcasts web interface and suddenly it's not a problem any more.

Is there a limit on the number of files that can be retrieved?

There's no limit in FileZilla. However, there could be very well a limit on the number or the size of files you are allowed to store on their servers. That limit would be enforced by them, though.