#Vnc through ssh tunnel windows

For example, Make sure you select the Use SSH or SSL+SSL option before you connect. Under VNC Host:Display, type Replace SSHusername with the username you’d use for your SSH connection, and replace remoteIPaddress with your remote desktop IP address. Once you click connect, your VNC client will use the encrypted SSH tunnel and make the connection between local and remote machines on port 5901. Open the SSVNC client and, within the main SSVNC client window, fill in the required fields.

#Vnc through ssh tunnel windows

SSVNC is supported by Windows and Linux operating systems. The 127.0.0.1:5900 is the destination address and port. You connect your VNC client to this port. One example is SSVNC which, while basic, will tunnel over SSH before making a VNC connection. If you already have a SSH connection, you just need to add a port forwarding: ssh -J 192.168.1.22 -L 5990:127.0.0.1:5900 10.10.1.44 In -L 5990:127.0.0.1:59is an arbitrary port number for your local machine. Other VNC clients, however, do include SSH tunneling within the client itself. This ssh tunnel works in this way: when a packet goes to port 1111 on localhost, this packet is forwarded to sshd running on the vncserver, then the sshd running on the vncserver forwards this packet to localhost:5901 that is the port 5901 on itself (vncserver). While TightVNC is a popular Windows client for VNC connections, it doesn’t support SSH tunneling within the client itself, requiring you to use PuTTY to make the connection. ssh -L 1111:localhost:5901 usernamevncserver. If your SSH connection is working correctly, TightVNC should load your remote VNC desktop window, ready for you to use.