Short Timout on Connection despite high setting

Advertisement

lightbuoy
Joined:
Posts:
5

Short Timout on Connection despite high setting

Hi there,

we've been trying to run a WinSCP batch script that connects to an FTP server. We transmit via a slow satellite connection (<2400 bit/s) so the biggest problem is getting the connection to the FTP server up, the actual file transfer while connected is ok. In most cases the connection attempt fails after around 15–20 seconds despite setting the connection timeout to 60 seconds. (Still connected to the internet) What might be the reason for this? Is this a problem of our client or the remote server?

Thank you very much.

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
40,884
Location:
Prague, Czechia

Re: Short Timout on Connection despite high setting

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, use /log=C:\path\to\winscp.log command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

lightbuoy
Joined:
Posts:
5

Hi Martin,

we have no ability to connect to the satellite network currently so I have attached the translation of the german parts.

We do already run a batch skript that retries the connection, it usually results in the behavior depicted. If we connect successfully, then always slightly below ~15s time but that is hard to achieve with 2400 baud connection.

Reply with quote

Advertisement

martin
Site Admin
martin avatar

Thanks. I could translate the messages myself :) But I need exact original English error messages to investigate this.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
40,884
Location:
Prague, Czechia

Re: Short Timout on Connection despite high setting

It seems that the 21 seconds is Windows OS limit, that an application cannot override.
See for example:
Where does the socket timeout of 21000 ms come from?

Anyway, check this post:
Connection/Response timeout values don't seem to take effect in JMeter
It suggests, that you might increase the OS limit using:
netsh interface tcp set global MaxSynRetransmissions=3

Reply with quote

lightbuoy

Thank you Martin,

while MaxSynRetransmissions=3 did not change the 21s timeout (if I get it right that makes sense) but increasing this to 4 or 5 did work great and the connection did not timeout after 21s as before.

Reply with quote

Advertisement

You can post new topics in this forum