HowTo: Tunneling VNC Connections Over SSH

by on May 8, 2006 · 12 comments· LAST UPDATED July 20, 2010

in , ,

Virtual Network Computing (VNC) is a desktop sharing system which uses the RFB (Remote FrameBuffer) protocol to remotely control another computer. It transmits the keyboard presses and mouse clicks from one computer to another relaying the screen updates back in the other direction, over a network.

Step by step procedure

You can easily tunnel VNC connections over ssh so that entire traffic get encrypted. Type the following command to tunnel VNC connections over SSH (you need to type command on your desktop computer running UNIX or Linux):
$ ssh -L 5901:localhost:5901 -N -f -l rocky sshserver.mydomain.com
OR
$ ssh -L 5901:127.0.0.1:5901 -N -f -l rocky 192.168.1.100

Where,

  • -L 5901:localhost:5901 : Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. Here you are using port 5901 on the localhost to be forward to sshserver.mydomain.com on the 5901 port.
  • -N : Do not execute a remote command i.e. just forward ports.
  • -f : Requests ssh to go to background just before command execution. Requests ssh to go to background just before command execution. Once password supplied it will go to background and you can use prompt for type commands on local system.
  • -l rocky : rocky is the user to log in as on the remote machine (sshserver.mydomain.com).
  • sshserver.mydomain.com (192.168.1.100): Remote system with VNC server

In your localhost VNC client use 127.0.0.1:5901 for connection. Make sure you use appropriate port i.e. 5901 (VNC server running on display 1). This tunnel will provide nice enhanced security.

TwitterFacebookGoogle+PDF versionFound an error/typo on this page? Help us!

{ 12 comments… read them below or add one }

1 weyasey February 2, 2009 at 12:42 pm

Great tutorial, it was clear and the explanation of the switches made it all understandable.
Thanks very much it helped me a great deal.

Reply

2 Anonymous April 17, 2010 at 3:54 am

Thank you, very good and clear. Indeed simpler than that from vnc client on windows

Reply

3 TT January 30, 2011 at 9:02 pm

Do you know if I need the SSH protocol over a network and behind a firewall in Window platform using tight VNC?

Reply

4 baba February 8, 2011 at 7:02 pm

great reference on a great site! however, following the scenario i am prompted with a password in my vnc client (vinagre) and none of the ones i provide work. any ideas?

Reply

5 baba February 8, 2011 at 9:02 pm

sorry, my bad, it was the vnc password

Reply

6 YBR February 11, 2011 at 3:17 pm

Thanks for this Ho-To. One additional note – you don’t have to specify “localhost” in the ssh -L command….I used this to tunnel from work into my home Linux box, and pointed it at the VNC server running on a laptop on my home network. Now I can nannycam! Here is what I did: ssh -L 5600:10.248.26.18:5900 plony@plony.com
(note, IP numbers/names have been changed to keep honest people honest :-)

Reply

7 Allen May 26, 2011 at 9:03 pm

Is there a way to force all users to tunnel to use vnc?

Reply

8 Dhairya August 9, 2011 at 12:08 pm

I followed these steps and could easily connect to remote machine. But now the problem is my localhost is not working as nginx server is unable to listen to 127.0.0.1. any solution?

Reply

9 Michael October 25, 2012 at 2:38 pm

For windows, to connect to a remote ssh session just download the free putty program and configure “tunnels” under the “SSH” category. You set the Source port to the local computers port that is connecting (i was connecting to a vnc session) like port 5900 and the destination port to localhost:5900 then when you open your favorit vnc program you can simply connect to the remote computer by typing “localhost” as long as your remote computer is setup to connect on port 5900. Thats my two cents for windows users.

Reply

10 Basu March 22, 2013 at 9:03 pm

Very clear n concise information.

thanks

Reply

11 dllehr February 24, 2014 at 7:33 pm

Thanks for the writeup! I was mistaking the -L hostname to be the one I was connecting to, not localhost. Cleared my issue up. Thanks!

Reply

12 waregle82 June 21, 2014 at 5:20 am

ssh -L 5902:127.0.0.1:5902 -N -f -l pi 192.168.0.100
pi@192.168.0.100‘s password:
channel_setup_fwd_listener: cannot listen to port: 5902
Could not request local forwarding.

Thoughts?

Reply

Leave a Comment

Tagged as: , , , , , , , , , , , , , , , , , , ,

Previous post:

Next post: