Opened 9 years ago
Closed 8 years ago
#9624 closed Bug report (fixed)
No retry after failed to sent a command.
|Reported by:||San||Owned by:|
|Keywords:||TCP NAT NAT444 port binding retry rename command connection||Cc:|
|Component version:||Operating system type:||Windows|
|Operating system version:||7|
Description (last modified by )
I'm using internet behind NAT444.
My ISP's NAT device allow port binding just for some time.
After NAT device doesn't see activity on the port it will silently drop port binding to home's client.
To solve this You should add some option to send some null command for every X seconds. (Like in Putty)
but for particular issues I found is when I can connect to a server and then inactive for a period of time.
Filezilla won't retry by restart a connection with the server when encounter an Error.
Here the log:
Command: RNFR something.html
Error: Connection closed by server
I expect when this happen it should restart connection with the server.
Either you resolve the issue by adding option to make some TCP activity periodically or retry when encounter an error is fine by me but I think both would be the best.
Change History (2)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
|Status:||new → closed|
Should be fixed in the most recent version of FileZilla.
This would be great. I commonly open the connection to a server and use it for some time and then not use it for some time. When I then try to do anything, e.g. open a folder, I get the message:
Error: Network error: Software caused connection abort
Error: Failed to retrieve directory listing
Retrying manually gets FileZilla to re-establish the connection and perform the action. It would be a good improvement if FileZilla would retry automatically upon timeout due to inactivity.