FileZilla Forums

hello there,
Using the latest version of Filezilla (just downloaded now), however both this version and the prior version I had show the "error: Failed to retreive directory listing" when I try to connect. Both with windows and vista. I have checked my firewall and it is set to allow filezilla.

Here is the log. Help is appreciated as I'm trying desperately to update my website. Thanks in advance!

Status: Resolving address of ftp.scratchpadsecretaries.com
Status: Connecting to 72.15.144.248:21...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.3.1 Server (ProFTPD) [72.15.144.248]
Command: USER slee1970
Response: 331 Password required for slee1970
Command: PASS ********
Response: 230 User slee1970 logged in
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: 211 End
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (72,15,144,248,234,218).
Command: LIST
Error: Connection timed out
Error: Failed to retrieve directory listing

See if you can change the transfer type under the transfer menu. If it is set to auto, change it to binary, and try that. If that doesn't work, try it in ascii.

The data type has no influence on such things.

Instead, read the Network Configuration guide.

I have the same problem, but in a weirder way. My laptop (Running version 2 of FileZilla) worked fine at the office and at home. I upgraded to 3.1.5 on the laptop. It works at the office just fine. At home (same ISP) I get the "Failed to Retrieve Directory Listing".

Here is the even weider part. At the office we have two NAT routers back to back. At home we have a single NAT router. The office works fine with double NAT routing and home fails with single NAT routing.

I have read the Network Configuration Guide and nothing in there helped at all.

Same Problem here since update to 3.1.4.1. And the problem still remains with 3.1.5
With FileZilla 2.2.32 (on the same computer / Windows XP SP3) everything works fine without "Failed to Retrieve Directory Listing"

Regards,
Bjoern

Thanks, Bjoern,

That's all I need to know. I'm going back to FileZilla 2.2.32. Hopefully all will be well then.

-O. D.-

I got the solution

Go to your site manager, click on Transfer Settings Tab.
Select the Transfer mode as "Active"

Initially i was also facing the same issue, finally the above setting solved my problem.
I am using File zilla 3.1.5

No solution, just a workaround. Active mode is a lot more firewall-unfriendly.

Hi, Using v3.1.6 and i also get



then i tried the active mode

settings -> connection -> ftp
ticked active and ticked Allow fall back to other transfer mode failure

under settings -> connection ftp -> active mode
ticked limit local ports used by filezilla
ticked get external ip from the following url (http://ip.filezilla-project.org/ip.php)
ticked don't use external ip address on local connections.

and... i get this...



help anyone?

Broken server, xxx,xxx,xxx,xxx is not a valid IP Address.

LOL, many people still think they can hide their IP from the webz...

hello all....

apparently i'm not the only one with this issue. i just got a Dell PowerEdge server for my home and i'm trying to get filezilla configured on it. i was able to get filezilla up and running on 2 occassions. but then, it would simply error out. i was even able to create a directory while it was working. i'm getting the same old "LIST" issue and then the "Failure to retrieve directory listing" error. I am able to ftp through the local ip address, but not from an outside network.


Status: Resolving address of mystripedshirt.kicks-ass.net
Status: Connecting to 71.141.254.170:17340...
Status: Connection established, waiting for welcome message...
Response: 220-FileZilla Server version 0.9.29 beta
Response: 220 Now don't go giving me viruses, BIYATCH! Good music only!
Command: USER joeyjoe021
Response: 331 Password required for joeyjoe021
Command: PASS *******
Response: 230 Logged on
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (71,141,254,170,0,44)
Command: LIST
Response: 425 Can't open data connection.
Error: Failed to retrieve directory listing
Response: 421 Connection timed out.
Error: Connection closed by server

i've read the Network Configuration guide and was still unable to figure it out. I'm using a d-link DIR-655 and and instead of using the Port Forwarding, i'm using the Virtual Server tool. Is there anything that i'm missing when setting up FZ server on the Server 2003 machine? since i'm getting a welcome message, i assume that i'm getting passed the router. maybe i'm totally wrong. any ideas?

The listening port is correctly configured. But there are problems with the FTP data connections. They are on different ports which

-must be known by the server,
-correctly forwarded, and
-opened in the firewall (all of them).


If it works only sometimes not all ports have been opened/forwarded. If you get one that is, it works, fails otherwise.

The problems people here are having are similar to the ones I am having. I investigated it a lot more and have described them at

viewtopic.php?f=2&t=9266

Could you please try to access your ftp site through the MS-DOS FTP. Start up an ms-dos prompt and type

ftp yourservername.com

it asks for username and password.

type help for commands

use dos or unix type commands

cd directoryname
for change directory to directoryname

try listing out directories by typing dir
dir for current directory and dir directoryname for listing directoryname

If a directory doesn't list with dir then try using ls instead of dir

I'm finding that the listing problem only occurs when listing with dir and only with directories with a larger number of files. The dir is the equivalent to the LIST (ls -l) used by filezilla.

I would like to know if this is the same with anybody else.

The resolution to this problem has been mentioned above. You must make sure that the port 990 is available through your firewall (port 990 is for logging in purposes and commands only, not to transfer data). You will have to open up some other un-used ports on your firewall (like 40000 to 40003, and I use these because I want 4 connections to transfer data. This will also have to be setup correctly on the server so you use all of them otherwise you are opening ports for no reason and exposing your network) in order to transfer data. Once these ports have been setup on the firewall, the server side of the firewall must also have these ports setup (like in Windows 2003 firewall) to allow data transfer. Then the FileZilla server settings need to be setup under Passive Mode Settings with: 1.) the external IP Address that your server has been "mapped" with on the firewall. Obviously, you cannot have a 192.168 or a 172.16 or a 10.x address used because these are not routable addresses outside of your router/firewall. This would be provided by your ISP. 2.) you must check the box "Use Custom Port Range" to setup up the same ports that you used on the firewall (40000 to 40003). You can keep the "Don't use external IP for local connections" checked if you are inside the firewall/router.

Don't know if this helps anyone but it should be what you need in order to setup the server for FTP (or FTPS in this case).