VNC (remote graphics) sessions University Networking and Research Computing (UNRC)

Starting VNC--persistent session

Log into the server with a command-line shell, for example on Windows with the PuTTY application. Then start your session with the vncserver command.

mooreb@silvertip3:~> vncserver
You will require a password to access your desktops.
Would you like to enter a view-only password (y/n)? n
xauth:  creating new authority file /home/mooreb/.Xauthority
New 'X' desktop is silvertip3:59
Creating default startup script /home/mooreb/.vnc/xstartup
Starting applications specified in /home/mooreb/.vnc/xstartup
Log file is /home/mooreb/.vnc/silvertip3:59.log

You should only see the dialog prompting you to see the VNC password the first time you use VNC. The password for the VNC session is different from your system password.

Note your screen number, in the example above it is screen 59 on silvertip, or silvertip:59 .

Connecting to the VNC session with a VNC viewer

You need a VNC viewer program to connect to your VNC session. A typical one is from RealVNC; the viewer is free. Search for "realvnc viewer download," for example, Download and install the VNC client for your operating system.

Open the VNC view program and connect to the session you created.

vncviewer screenshot

If you successfully make the connection, you will be warned that it is not encrypted, and then asked to enter your VNC password (remember, NOT your system password). An example of a starting session on silvertip3 is shown below.

vncviewer session silvertip3

You can modify some of the properties of your VNC view session from the toolbar. In the screenshot above, it is just barely visible along the top border. Hover with the mouse in that area and it should appear.

vnc session toolbar

From the toolbar you can control fullscreen, scaling and session properties.

Killing the VNC session

The VNC session created in this example is persistent. This means that
you can close the VNC viewer program and the session remains active,
even though it is not being viewed. (Don’t log out inside the VNC
session, however; that will kill the session).

To kill your VNC session you must be logged in from the command-line (e.g. PuTTY) session and issue a vncserver -kill command; the argument is your screen number.

mooreb@silvertip3:~> vncserver -kill :59
Killing Xvnc process ID 5982

Finding your VNC sessions

If you don't know your screen number, you can find your running sessions from the command line.

mooreb@silvertip3:~> ps -fU $USER|grep vnc
mooreb    5982     1  0 13:20 pts/63   00:00:00 Xvnc :59 -desktop X -httpd /usr/share/vnc/classes -auth /home/mooreb/.Xauthority -geometry 1024x768 -depth 24 -rfbwait 120000 -rfbauth /home/mooreb/.vnc/passwd -rfbport 5959 -fp /usr/share/fonts/misc:unscaled,/usr/share/fonts/local,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/Type1,/usr/share/fonts/URW,/usr/share/fonts/Speedo,/usr/share/fonts/truetype,/usr/share/fonts/uni,/usr/share/fonts/CID -noreset
mooreb    6037  5903  0 13:23 pts/63   00:00:00 grep vnc

In this case we found that screen 59 was active. It is important to look for your running VNC sessions because frequently people start them and forget them, as you can see on silvertip3 we have 50 or more sessions, most of which have probably been long forgotten by their users.

Changing the resolution

A given VNC session works at a fixed resolution. If you want to change the resolution, you have to kill the session and start a new one at the new resolution.