Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Connection timed out when using tunneling

Please attach a full log file showing the problem (using the latest version of WinSCP).
Plus a log from your SSH client.

To generate 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.

Connection timed out when using tunneling

Hi, I'm using Windows 7. I am trying to create a connection to one server and configure a tunnel to another server. The connection to the first server, without the tunnel, works alright.

The second server is up and running, in fact I am logged in it at this very moment via SSH tunnel from a Linux computer right next to my Windows one.

The SSH ports in both servers are 22 (both are correct), however, everytime I try to connect, I get a message saying:

Opening tunnel...
Searching for host...

Network error: Connection to "..." timed out.

There is no firewall in my Windows, in fact, using SSH Secure Shell for Windows, it works (but not on WinSCP). I am absolutely sure that all the ports, addresses and usernames are correct. What could this be? I've tried multiple Local tunnel ports, including the automatic choice.

Thank you very much,