Host is not communicating for more than 15 seconds

I hadn't used winscp for a while, installed the new version when prompted but i keep getting this error connecting to a Pi zero. I found and turned off the "Optimize connection buffer size." but the issue is still there.

what can i try?

I've been using WinSCP for at least 10 years to administer servers on AWS and Digital Ocean, and have never had problems until recently. I was getting the problem you describe, where the application just closes itself (no error) when I've been connected to a server for 5-15 seconds. Updating to the latest version seemed to help.

Now it connects fine if I only browse around on the server, but if I try to access existing folders on my local hard drive the application hangs for a couple seconds with a flashlight icon then closes itself. No apparent errors. This is on Windows 10 Version 10.0.17134 Build 17134 (a recent version).

I've tried disabling Norton Security, in case that was blocking access to my local drive for some reason, but have been unable to resolve this. I was able to create a NEW folder on my computer from within WinSCP and that does NOT crash. But trying to open existing folders closes the app. If this were Linux I would suspect a permissions problem, but...Windows.

I've donated to WinSCP in the past because it's been so solid, but I'm ready to move to a different SCP app if I can't get this working. Any other ideas folks?

Thanks!

marymac wrote:

Now it connects fine if I only browse around on the server, but if I try to access existing folders on my local hard drive the application hangs for a couple seconds with a flashlight icon then closes itself. No apparent errors. This is on Windows 10 Version 10.0.17134 Build 17134 (a recent version).

Thanks for your report.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.

I also recently started experiencing this issue after using WinSCP for years. Installed a fresh copy on a different PC that also has FileZilla installed. WinSCP imported site from FZ so I know acount and password match. WinSCP will timeout but FileZilla connects.

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

marymac wrote:

I've been using WinSCP for at least 10 years to administer servers on AWS and Digital Ocean, and have never had problems until recently. I was getting the problem you describe, where the application just closes itself (no error) when I've been connected to a server for 5-15 seconds. Updating to the latest version seemed to help.

Now it connects fine if I only browse around on the server, but if I try to access existing folders on my local hard drive the application hangs for a couple seconds with a flashlight icon then closes itself. No apparent errors. This is on Windows 10 Version 10.0.17134 Build 17134 (a recent version).

I've tried disabling Norton Security, in case that was blocking access to my local drive for some reason, but have been unable to resolve this. I was able to create a NEW folder on my computer from within WinSCP and that does NOT crash. But trying to open existing folders closes the app. If this were Linux I would suspect a permissions problem, but...Windows.

Related:
https://winscp.net/tracker/1666

Log attached

crg wrote:

Log attached

Thanks. Can you also attach a verbose FileZilla log file?

Did you try turning off Attempt GSSAPI authentication?
https://winscp.net/eng/docs/ui_login_authentication

Disabling GSSAPI fixed my issue. Thanks for your help.

I also faced the same issue with the latest version of winscp (5.15.3), earlier versions were working fine!!

It works if u set the remote directory to a correct directory, try with root (/) if you have access to it, you might have set it some directory like /home/dir1, which may not exist on the server and while trying to read this, winscp (latest version) hangs, really silly bug

shashi wrote:

I also faced the same issue with the latest version of winscp (5.15.3), earlier versions were working fine!!

It works if u set the remote directory to a correct directory, try with root (/) if you have access to it, you might have set it some directory like /home/dir1, which may not exist on the server and while trying to read this, winscp (latest version) hangs, really silly bug

Thanks for your report.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.