Opened 14 years ago

Last modified 13 years ago

#3126 closed Bug report

Limit number of simultaneous connections doesn't work

Reported by: symzo Owned by:
Priority: normal Component: Other
Keywords: Cc: symzo, Alexander Schuch, sire404, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

I use Free.fr's ftp server (ftpperso.free.fr). It limits the number of connections a user can have to 2. Though I limited to 1 the number of connections in my settings, I still receive (sometimes) a message from the server warning me that I already have two connections, and cannot connect once more (See the end of the log : "Response: 421 Vous ne pouvez avoir que 2 connexions simultannees").

(you might see directory listing problems as well in the log file attached, but they are unrelated : they started to happen latter than this bug).

OS : Ubuntu Feisty Fawn (but I already had the problem in Edgy Eft and windows XP)

In case it can help you : I used to be an FTPexpert ( http://software.visicommedia.com/fr/products/ftpexpert/ ) user, and never experienced this bug with that program.

Attachments (1)

filezilla-log-cropped.txt (6.6 KB ) - added by symzo 14 years ago.
filezilla detailed log

Download all attachments as: .zip

Change History (4)

by symzo, 14 years ago

Attachment: filezilla-log-cropped.txt added

filezilla detailed log

comment:1 by Alexander Schuch, 14 years ago

This might be a problem with FileZilla.

FileZilla creates a secondary control connection when transferring files so that it is still possible to browse the FTP server while files are being transferred.

There is no schedule on when the problem will be solved. But as it is know, it will be implemented as soon as there is time for it.

comment:2 by sire404, 13 years ago

I can verify that this bug exists. Even after setting the threads to one below the max nr of connections, and restarting FileZilla, I still get warnings from the server that I'm trying to do more connects than the allowed.

comment:3 by Tim Kosse, 13 years ago

Thanks for reporting. This issue has been fixed in the CVS
repository and will be available with the next version.

Note: See TracTickets for help on using tickets.