Opened 10 years ago

Closed 10 years ago

Last modified 5 years ago

#4407 closed Bug report (rejected)

After successfull connection attempt the server fails to send the list of files

Reported by: Martin Owned by:
Priority: normal Component: FileZilla Server
Keywords: client doesn't receive the filelist Cc:
Component version: Operating system type: Windows
Operating system version: Windows XP Prof SP 3

Description

First, the problem does seem to occur randomly, but often since the version 0.9.26 or so. I'm using the version 0.9.31. The server gets the connection attempt by the client, seems to reply correctly, until the client requests the filelist. The client never receives the list, and a timeout is the consequence.

Heres a short log of a client who encountered the problem:

answer: 150 Connection accepted
answer: 226 Transfer OK
command: MDTM fenster.png
error: connection timed out
error: directory could not be received

On my side (the server):
(000001) 24.03.2009 17:17:42 - (not logged in) (93.212.190.161)> Connected, sending welcome message...
(000001) 24.03.2009 17:17:42 - (not logged in) (93.212.190.161)> USER Armin
(000001) 24.03.2009 17:17:42 - (not logged in) (93.212.190.161)> 331 Password required for armin
(000001) 24.03.2009 17:17:42 - (not logged in) (93.212.190.161)> PASS *
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> 230 Logged on
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> SYST
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> 215 UNIX emulated by FileZilla
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> FEAT
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> 211-Features:
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> MDTM
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> REST STREAM
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> SIZE
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> MODE Z
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> MLST type*;size*;modify*;
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> MLSD
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> UTF8
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> CLNT
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> MFMT
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> 211 End
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> PWD
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> 257 "/" is current directory.
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> TYPE I
(000001) 24.03.2009 17:17:42 - armin (93.212.190.161)> 200 Type set to I
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> PASV
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> 227 Entering Passive Mode (192,168,0,2,9,96)
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> LIST
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> 150 Connection accepted
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> 226 Transfer OK
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> MDTM fenster.png
(000001) 24.03.2009 17:17:43 - armin (93.212.190.161)> 213 20090321171339
(000002) 24.03.2009 17:18:09 - (not logged in) (93.212.190.161)> Connected, sending welcome message...

[Now the person tried again, but the result was the same...]

The problem doesn't occur every time, and it doesn't seem to be about specific files, as the files change, with which the problem happens. It also doesn't seem to be related to specific FTP clients, as we tried it with several, including the FileZilla Client. Sometimes it works quite well, so I suppose it has nothing to do with my personal firewall on my computer, or the NAT/firewall of my router (port 21 TCP is configured, and as I said, sometimes it works really well). In earlier versions this problem never occured, but I don't know the exact version with which I the issue began.

Change History (2)

comment:1 Changed 10 years ago by Tim Kosse

Resolution: rejected
Status: newclosed

Incorrect server configuration and in addition a broken router and/or firewall actively sabotaging the connection.

Read http://wiki.filezilla-project.org/Network_Configuration

Note: See TracTickets for help on using tickets.