Opened 10 years ago
Last modified 9 years ago
#9624 closed Bug report
No retry after failed to sent a command. — at Initial Version
| Reported by: | San | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | TCP NAT NAT444 port binding retry rename command connection | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | 7 |
Description
Hello
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.
