Opened 12 years ago

Last modified 12 years ago

#1241 closed Bug report

Failure to select available local port

Reported by: legolas558 Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: legolas558, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

I am using Filezilla v2.2.26a and I have set in Connections -> Firewall settings a range of available ports to be used.

However, if Filezilla tries to bind to a port which is already in use (I have another program which might use a port from the same range) it will fail and break the current operation.

Wouldn't be possible to have Filezilla try with another port from the range?

Thank you

Change History (2)

comment:1 Changed 12 years ago by legolas558

I have also separated the port ranges used by Filezilla and other programs, leaving Filezilla with a reserved port range but looks like it does not close all the ports it opens! Or, at least, not fast enough before the subsequent bind trial.

The result is that with a ports range of 5 total ports and FTP upload of small files it will fail very soon reporting

Error: Transfer channel can't be opened. Reason:

And follows the error description for Windows error 10048

Are bound ports correctly closed before attempting to re-bind them?

This problem is very annoying...I hope it will be/is fixed in Filezilla3

Thank you

comment:2 Changed 12 years ago by Tim Kosse

Please upgrade to the latest version of FileZilla. There won't be
support for outdated versions.

See
http://sourceforge.net/project/showfiles.php?group_id=21558&package_id=15149
for download links.

Note: See TracTickets for help on using tickets.