Closed Network Connection

Advertisement

megandavis
Joined:
Posts:
3

Closed Network Connection

Version: 5.17.8 (Build 10803)
File Protocol: SFTP
OS: Windows 10 server

I am having an issue with WinSCP staying connected to a remote server to grab and transfer files to a folder on the file server (executed via powershell scripts and Windows task manger). After about 1 minute and 20 seconds the connection closes and the error says "Remote side unexpectedly closed network connection". WinSCP logs itself back in successfully, but continues this loop until I close out the program. I have turned off optimize connection buffer size. I do not see anything related to this timeout in the event viewer. I have enabled logs for WinSCP and I am getting this error:
2020-11-23 13:43:55.084 Remote side unexpectedly closed network connection
2020-11-23 13:43:55.085 (ESshFatal) Remote side unexpectedly closed network connection
I have searched both of these around online, but cannot find any additional information. Please let me know if you have run into this before or if you know how to resolve.

winscp.PNG

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
35,415
Location:
Prague, Czechia

Re: Closed Network Connection

I'm not sure from your post if the problem happens during a file transfer, or while WinSCP is idle.

In any case, please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. 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

megandavis
Joined:
Posts:
3

This is what I've got. I tried to remove any identifying info. Looks like it authenticates and connects successfully, but then closes out for some reason. In the task scheduler it also says that it was executed successfully so I am not sure of the disconnect.

Thanks for taking a look.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
35,415
Location:
Prague, Czechia

Can you clarify this?
I'm not sure from your post if the problem happens during a file transfer, or while WinSCP is idle.

Reply with quote

megandavis

Hey Martin,

I want to say the timeout occurs when the application is idle as it occurs right around the 60 second mark every time. I cannot get the files to even transfer or attempt to transfer so it has to be when it's idle.

Reply with quote

Advertisement

martin
Site Admin
martin avatar

Thanks. So to summarize the issue: After WinSCP is idle for about a minute, the server closes the connection. WinSCP then reconnects successfully. Is that correct? I'm note sure though what happens next. You wrote that "but then closes out for some reason". What closes? The connection? Or whole WinSCP? Immediately after the reconnect?

Reply with quote

Advertisement

You can post new topics in this forum