Forum » Support and Bug Reports »

WinSCP's "Connect through SSH tunnel" feature stopped working after Windows 10 1809 update

Advertisement

supergarry
Guest

WinSCP's "Connect through SSH tunnel" feature stopped working after Windows 10 1809 update

Hello,
WinSCP's "Connect through SSH tunnel" feature stopped working after Windows 10 1809 update.
It says:
Cannot find free local listening port number for tunnel in range 50000 to 50099
I rolled back to 1803 version and WinSCP works again.

Best regards,
Igor

Reply with quote

Advertisement

supergarry
Guest

Re: WinScp's "Connect through SSH tunnel" feature stopped working after Windows 10 1809 update

Unfortunately I didn't save session log before rolling back to 1803.
But I remember when I selected some port (ex. 50002) it said something similar to: "Can't connect to 127.0.0.1"

Reply with quote

martin◆
Site Admin
martin avatar
Joined:
Posts:
42,062
Location:
Prague, Czechia

Re: I'm too

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.

You will find my address (if you log in) in my forum profile.

Reply with quote

Advertisement

ApolloX
Guest

I'm having the exact same problem. Have had to manually go into each connection and set a random port for the past month or so.

Reply with quote

Advertisement

martin◆
Site Admin
martin avatar
Joined:
Posts:
42,062
Location:
Prague, Czechia

@ApolloX: 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.

You will find my address (if you log in) in my forum profile.

Reply with quote

eactors
Guest

Still exists (5.13.8)

I still have the same problem running 5.13.8.
The problem was gone some times and is back now. I tried a full reboot of Windows 10 but it did not help (shutdown /g /f /t 0).

Reply with quote

Advertisement

martin◆
Site Admin
martin avatar
Joined:
Posts:
42,062
Location:
Prague, Czechia

Re: Still exists (5.13.8)

@eactors: 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.

You will find my address (if you log in) in my forum profile.

Reply with quote

curvers
Donor
Joined:
Posts:
1

Same problem

Same problem here using latest WinSCP version 5.15.1
OS Name Microsoft Windows 10 Pro
Version 10.0.17763 Build 17763

I did not have the problem before.
Few days ago I upgraded from Windows Home to Windows Pro, so maybe its related to this issue.

Reply with quote

martin◆
Site Admin
martin avatar
Joined:
Posts:
42,062
Location:
Prague, Czechia

Re: Same problem

@curvers: Thanks for your report.
For me it works fine with the same setup.

Anyway, I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.

Reply with quote

dteller
Joined:
Posts:
1

I'm having the same problem where the connect through SSH tunnel stopped working after an update

I've tried versions 5.15, 5.15.1 and 5.13.9
Windows 10 version 1809 build 17763.437

The error is
Cannot find free local listening port number for tunnel in range 50000 to 50099.
When I look in TCPView, there aren't actually any ports used in that range.

If I set the port manually to 49999 (which is free) I get
Network error: Connection "127.0.0.1" refused.
I also tried running it as an Administrator.

If I manually set the port to 51000 it works.

Reply with quote

Advertisement

martin◆
Site Admin
martin avatar

Re: I'm having the same problem where the connect through SSH tunnel stopped working after an update

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.

Reply with quote

Saksham
Guest

Cannot find free local listening port number for tunnel in range 50000-50099

Hey,

I started getting this problem after updating my Windows version to 1809.
The solutions listed here involve manually changing the port. How can I do that?
And is there no better solution to this?

Thanks

Reply with quote

Guest

Re: I'm having the same problem where the connect through SSH tunnel stopped working after an update

@dteller: Manually set the port to 51000 it works.
If hit "SSH warring: Authorized users only. All activity may be monitored and reported" press continue next!

Reply with quote

matesstar

Re: I'm having the same problem where the connect through SSH tunnel stopped working after an update

@dteller: For me there were some versions working and some not working. I am not sure if it was caused by Windows version or WinSCP version. In actual combination it works (WinSCP 5.15.4, Windows 10 1809 build 17763.805)

Reply with quote

Advertisement

martin◆
Site Admin
martin avatar

Re: Cannot find free local listening port number for tunnel in range 5000 to 50099

@payal.parikh: 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.

Reply with quote

martin◆
Site Admin
martin avatar

Re: Cannot find free local listening port number for tunnel in range 5000 to 50099

Please post only if you are willing to really help me debugging the problem. Otherwise, there's no point in posting "me too".

Reply with quote

Advertisement

You can post new topics in this forum

Documentation

Support

Associations

Follow Us