Opened 10 years ago

Closed 10 years ago

#4787 closed Bug report (rejected)

Cannot retrieve contents of remote directories, regardless of size

Reported by: Dan Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: Vista SP2

Description

After upgrading to 3.2.7.1, I am unable to retrieve the file listing of remote directories. This happens on three different FTP servers (two hosted by GoDaddy.com - one Linux, one Windows, and another Linux server hosted by EHostPros.com).

No matter which server I try connecting to, the progress always hangs and eventually times out (I've extended the T/O length to 180 seconds) with the following as the last comm
Response: 227 Entering Passive Mode (IP, p1, p2)
Command: MLSD

I've always run in Passive mode, and the only other time I've had a similar problem was when trying to connect to a very large directory, which is not the case here. Just in case, I even tried setting my default remote directory on one server to the cgi-bin, which only has a few files in it. It times out, regardless. My router/firewall shows no messages in its security log, and I have no reason to believe my local configuration is the primary cause.

I've downgraded to 3.2.6.1, and it connects without problem or delay. Logfile is attached. Forgive me if this is a repeat of something already posted.

Thanks for your attention and for your hard work on this tremendous product.

Dan Sprehe,
Chicago, IL

Attachments (1)

filezilla.log (10.1 KB) - added by Dan 10 years ago.

Download all attachments as: .zip

Change History (2)

Changed 10 years ago by Dan

Attachment: filezilla.log added

comment:1 Changed 10 years ago by Tim Kosse

Resolution: rejected
Status: newclosed

Looks like there's some router and/firewall blocking FileZilla.

Check your firewall configuration. After the update to 3.2.7.1 the executable of FileZilla obviously has changed. Some Firewalls (and virus scanners) tend to block changed programs.

Note: See TracTickets for help on using tickets.