#Putty ssh tunnel windows 7

The contents of this last paragraph are only hunches and should not be treated as a fact. Go back to Session section of PuTTY, type Ubuntu IP Address for Host Name (or IP address), and type 22 for Port, then click Open. In Tunnels section of PuTTy, type 5902 for Source port, and type localhost:5900 for Destination, then click Add.

Maybe some networking configuration changes caused this? Maybe it is a Putty issue? I recently enabled IPv6. Run PuTTY and go to PuTTY configuration window: Connection > SSH > Tunnels.

#Putty ssh tunnel windows 7

I am wondering if this issue has started with some of the recent Windows 7 updates. I am pretty sure I was able to do it with earlier versions of Windows 7 as well, both 32 and 64 bit. To Create a Tunnel to that container and access its UI via the internet: Open PuTTY and Load your Session that we saved above. When I was running Putty on XP to the same Ubuntu server, there would not be any issues. If it detects an SSH request to that port, it relays that connection request back to itself, down the established connection. The remote computer listens on a network port on the local computer. When I run telnet on the Ubuntu server to localhost using port 10005, I can establish a connection but it is immediately closed and the following message appears - 'Connection closed by foreign host'. Reverse SSH tunneling relies on the remote computer using the established connection to listen for new connection requests from the local computer. Go to and confirm that your IP address matches the host IP that you are tunneling through. The entry in the Forwarded ports window shows as R10005 localhost:10005 when I run telnet on the Ubuntu server to my Windows 7 ip address using port 10005, I can establish a connection and it stays open. As long as your PuTTY SSH connection remains connected, your proxy tunnel will be open and you will be able to use the internet through this proxy. I set up Putty SSH Tunnel to a remote Ubuntu server with port forwarding. I have arrived at a concise way of descrbing the problem. I am running into similar issues as Trevor and I agree that this is a Windows 7 / Putty networking issue and nothing to do with Explorer or Firefox as I am not using either one in my use of Putty. I have been tearing my hair out on this one as well.