Connecting using VNC from a Linux computer to a Linux server
VNC allows you to remotely start a desktop environment on a computer, and interact with that desktop from your local machine. Unfortunately, VNC doesn’t have built-in encryption, which means that all information sent through VNC can be caught by dubious third parties. One solution to this problem comes from utilizing ssh (The Secure Shell) to encrypt the traffic between you and your remote host.
This tutorial will cover the basics of starting a VNC server, wrapping it in ssh, and connecting to your remote desktop securely. In the following examples we will be connecting to mo.ece.pdx.edu using display 44, which means my port number will be 5944 (VNC port numbers are equal to 5900 plus the display number). Wherever mo.ece.pdx.edu is mentioned, one could also use any Ubuntu or Redhat/Centos Linux machine in MCECS.
If you are attempting to make a VNC connection to a firewalled Linux computer, you will need to make sure that your localLinux computer is connected to one of our VPNs. Popular Linux hosts that are firewalled include:
- auto.ece.pdx.edu, mo.ece.pdx.edu, archive.cecs.pdx.edu
- Computers in the CS Particle Lab (FAB 88-09)
There are many other Linux computers that do not require you to use a VPN. If you are using one of our supported Linux computers with a wired network connnection in FAB/EB, you don’t need to worry about the VPN.
Step 1 – Starting the VNC Server on the remote computer
Before we can connect to the remote desktop, we need to start the VNC server on the remote machine. In order to do this, ssh in to the machine where you’ll be accessing the remote desktop. In a terminal, run the following command:
This will start the VNC server on the machine and tell it to only accept connections from the localhost, which is to say from users logged into the machine hosting the VNC server. You will be prompted for a password to log you into your VNC session (This is _not_ like logging in with your MCECS account. This password is arbitrarily chosen by you. It is _strongly_ advised that you not use your MCECS account password here!)
NOTE: This password must be under 8 characters!
It will also ask if you want to assign a view-only password. This would be a password you would give to someone if you wanted them to observe your VNC session without being able to interact the desktop. Afterwards, you should receive some output that looks like this:
New 'X' desktop is mo.ece.pdx.edu:44 Starting applications specified in /u/cecsuser/.vnc/xstartup Log file is /u/cecsuser/.vnc/mo.ece.pdx.edu:44.log
NOTE: The display number is where your VNC session funneling your desktop. My server was started on display number 44, as it was the next display available. In theory, the display number can be anywhere from 1 to 9999, and you can manually choose a display granting that it’s not already in use. (for reference, :0 is considered the root display, for displays physically connected to the machine).
Troubleshooting: If you have forgotten your vnc password, or wish to change it use the vncpasswd command. It will prompt you for a new vncpassword and immediately change the vncpassword.
Step 2 – Creating the SSH Tunnel from your computer
Now that we have the VNC server running, we need to create the ssh tunnel from your local machine to the remote host. Log out of your ssh session (don’t worry about vncserver dying when you quit, it’s backgrounded) and reconnect to the same machine with the following commands in a terminal window:
ssh email@example.com -L 5944:localhost:5944
Where cecsuser would be replaced with your MCECS account username.
NOTE: The syntax -L 5944:localhost:5944 is what is responsible for creating the ssh tunnel VNC will be using between your local host and the remote host. In essence, what it’s saying is take everything that is being sent through the remote computer’s port 5944 (the second number) and funnel it into the local computer’s port 5944 (the first number). We’re using the same two numbers here for simplicity’s sake, but as above you can specify the port on the local computer (any number between 1024 and 65535).
Step 3 – Connecting to Linux via VNC using Remmina (Linux GUI)
Remmina is the default remote desktop viewer included with Ubuntu (as of version 14.04). To start Remmina, you can either press the windows key, or open a run prompt (Alt+F2 by default)
Then click the blank page to create a new connection.
Next, enter the information below:
Now you can click save, or connect. If you entered a password for your VNC session (which you really should do!), you will be prompted for it now:
Finally, you can enjoy your remote desktop session! Since you have a tunnel to the remote machine starting from your port 5944 and ending at the remote machine’s port 5944, which is used by VNC, Remmina will treat the VNC session as if it’s running locally.
If you clicked save, it will remember the port you used to connect to your VNC session. If next time the port changes, you can edit this connection by clicking on the connection, and then the pencil.
Troubleshooting: If you are having problems connecting, make sure the SSH tunnel is set up.
Alternate VNC Client – VNC from the Linux shell
If you are using your own Linux laptop/desktop, there are a number of available commandline VNC viewers available, among them is a commandline version of Vinagre as well as xtightvncviewer, which is the counterpart to tightvncserver. To install xtightvncviewer in Ubuntu, type the following into a terminal:
sudo apt-get install xtightvncviewer
To start the viewer, follow the steps under Preliminaries and then enter the following:
You will be prompted for your VNC server password.
NOTE: This password must be under 8 characters!
Once you authenticate, the vnc viewer will display the remote vnc desktop.
You’ll notice that xtightvncviewer has a much more spartan interace than Vinagre. In order to affect setting in xvncviewer, hit F8 to bring up a menu
NOTE: It is important to log out from inside your remote connection. If you close your VNC viewer without logging out, the VNC server will continue running on the remote host and use system resources. If you leave it for too long, it will eventually be forcibly killed by a system administrator and you will be notified via e-mail. Please be considerate of others and correctly terminate your VNC servers!