Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#4885 closed Bug report (rejected)


Reported by: Leon McCalla Owned by:
Priority: normal Component: FileZilla Server
Keywords: PASV Cc:
Component version: Operating system type: Windows
Operating system version: 2003 server R2


in server beta 0.9.33 under passive settings, when i specify the server IP, if the client sends PASV, the server responds incorrectly..

Oct 12 18:48:17.684: FTP: ---> PASV
Oct 12 18:48:19.148: FTP: 200 Type set to I.

If i select default somehow the server sends the external IP address correctly. (possibly using the IP from the Server IP box)

Oct 12 19:10:49.735: FTP: ---> PASV
Oct 12 19:10:49.815: FTP: 227 Entering Passive Mode (65,15,36,65,7,228)

Attachments (2)

FileZilla Server.log (2.8 KB ) - added by Leon McCalla 14 years ago.
cisco log.rtf (1.4 KB ) - added by Leon McCalla 14 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by Tim Kosse, 14 years ago

Status: newmoreinfo

Please attach a complete and unmodified server log.

by Leon McCalla, 14 years ago

Attachment: FileZilla Server.log added

by Leon McCalla, 14 years ago

Attachment: cisco log.rtf added

comment:2 by Leon McCalla, 14 years ago

Status: moreinfonew

Both log files show debugs of two passive file transfer attempts between a cisco router and a windows server behind NAT. In the first attempt "use the following IP" is selected in the passive settings of the server and while the server logs appear to be normal, the cisco router logs indicate an abnormal response.

In the second attempt i selected the "default" button in the passive settings and while the filezilla logs appear identical to the first, the cisco logs depict the proper response after the "PASV" keyword is used.

nothing changed on the cisco yet the file transfer was successful once the default button was selected on the server.


comment:3 by Tim Kosse, 14 years ago

Resolution: rejected
Status: newclosed

Not the fault of FileZilla Server.

Your cisco router or perhaps some firewall on your computer is broken. According to the log FileZilla Server sends the correct IP in the first case. Your router and/or firewall cannot handle the proper case and bails out in the worst way possible by disrupting the connection.

In the second case FileZilla Server sends the wrong IP yet it miraculously gets modified by your router and/or firewall.

Please read, it explains why routers and firewalls that modify FTP are inherently broken and considered harmful.

comment:4 by Leon McCalla, 14 years ago

you are absoloutely correct.....


Note: See TracTickets for help on using tickets.