Annoyance with FTP

[j7n]

There is a little annoyance with FTP that's been there for a long time. I try to connect to a server that not reachable for whatever reason. I realize this and I press Abort. The FTP dialog closes and I'm back at the file list. Then I quickly open the dialog again and select a working server, and it will say to me "IP Address not found" because it still has he memory of trying to contact the unreachable server. Then I have to repeat the connection, and it works. It doesn't take long to work around of course. But why is this?

[petermad]

I cannot reproduce the described.

[ghisler(Author)]

Could it be that the unreachable server uses its own name server hosted on the server itself, and they aren't reachable either? Then the FTP client would only show the server name but not the IP address. This could make the Windows IP lookup function to hang, and make future IP lookups fail until the first lookup timed out.

[j7n]

The name server is on the router. It also happens when using IP addresses. See here the connection number is indicated as 1: because it knows that there is a connection 0 (unreachable) still active.

https://i.imgur.com/sFEeN6R.png

[ghisler(Author)]

I cannot reproduce the error when using the IP address to connect.

[j7n]

I tried the latest beta and the error is still there. It shows only if the second attempt to connect to a working server is made within a short time after pressing Abort. But it is long enough to open the dialog again at a normal pace.

[ghisler(Author)]

I tried to simulate it by duplicating a connection and changing the port - this would hang the connection, and I had to abort it. Immediately after getting the error "Connection aborted!" I tried to connect to the correct port, and it worked immediately.