Some EECS Linux systems allow remote access via the RealVNC® VNC Viewer, providing a secure (encrypted) desktop connection. This is often much faster than using X11-forwarding via SSH. Please not that, unlike with Microsoft Windows Remote Desktop connections, disconnecting the client will not leave your session open on the system but will instead end it. Please log out properly before disconnecting from the remote system.
system_name.eecs.utk.edu:99as the VNC Server. For example, to connect to
vnc11.eecs.utk.edu, enter the following:
By default, the VNC system will create a window with a resolution of 1024x768. You can change this, both temporarily or for every login. To change resolutions on the fly, open a terminal window and run the following command to see the available resolutions:
SZ: Pixels Physical Refresh
*0 1024 x 768 ( 260mm x 195mm ) *0
1 1440 x 900 ( 366mm x 229mm ) 0
2 1600 x 1200 ( 406mm x 305mm ) 0
Current rotation - normal
Current reflection - none
Rotations possible - normal
Reflections possible - none
You can now choose a new resolution by using the
xrandr -s command, e.g. to switch to 1440x900 in the above example, run
xarndr -s 1.
To change your default resolution for all your login sessions, regardless of VNC server, create a file called
~/.vnc/config. Add a
-geometry option to the file, e.g.:
jruser@vnc11:~/.vnc> cat config
The next time you log into a VNC system, your window will have the resolution you specified. Note: This has to be one of the available resolutions as shown by the
xrandr command explained above.
Just like on regular EECS Linux systems, you can print to departmental printers while connected via VNC. In addition, the VNC client will automatically add the default printer on your client computer to the list of available printers. This allows you to print a remote document directly through the VNC Viewer to your own printer. If your default printer is called "My Printer", VNC will create a printer list entry called
IPNAME is the network name of your client system. You can still pick any of the departmental printers from the printer list if you prefer.
The RealVNC® Viewer has a secure file transfer feature built-in, similar to a simple FTP or SFTP client. To send files from your local computer to the VNC server, click on the VNC toolbar (by default, this is at the top of your VNC window and will pop-out when you hover over it) and select the File Transfer icon:
To transfer files from the remote VNC server to your local computer, open the VNC Server application in the remote system's status bar, then click "More" and select File Transfer:
Simply follow the instructions to transfer files between the computers.
Yes - but with some important caveats. The access method described above makes it easy to connect to a VNC system, do your work, and then disconnect without leaving a lot of processes running. It is, however, possible to create a persistent connection that will survive disconnecting. You can then later reconnect to the same session, finish your work, log out, and remove your session.
NOTE: The EECS IT Staff reserves the right to kill any sessions that are using an undue amount of system resources (CPU time, RAM, etc.) and make it impossible for other users to share the system. Please remember that these computers are shared resources.
To get a persistent VNC connection, first log into the system of your choice (it has to be a system supporting RealVNC®) via SSH - see the Remote Access knowledgebase article for more information on SSH connections.
Once you are logged in, run the vncserver-virtual command manually.
VNC(R) Server 5.0.3 (r97046)
Built on Oct 2 2012 16:42:29
Copyright (C) 2002-2012 RealVNC Ltd.
VNC is a registered trademark of RealVNC Ltd. in the U.S. and in other
Protected by UK patent 2481870.
See http://www.realvnc.com for information on VNC.
For third party acknowledgements see:
Running applications in /home/jruser/.vnc/xstartup
VNC Server signature: 54-40-b9-e9-77-5c-99-f3
Log file is /home/jruser/.vnc/vnc11:1.log
New desktop is vnc11:1 (184.108.40.206:1)
Make a note of the desktop number. In the above example, it is desktop 1 (
New desktop is vnc11:1 (220.127.116.11:1)). You can now log off from your SSH session if you so choose. Connect to desktop 1 instead of desktop 99 (in our example
vnc11.eecs.utk.edu:1) using the RealVNC® Viewer.
To end the persistent VNC session, first log out of your desktop environment as usual. Next, log in using SSH and run
vncserver-virtual -kill :desktop_number - in our example this would be:
vncserver-virtual -kill :1. If you neglect to kill your VNC server, it will continue to respond to login requests but will not have an associated desktop environment and thus become unusable.
Each RealVNC® enabled EECS system has manual pages for the various components of VNC (e.g. vncserver-virtual and Xvnc). Simply use the "man" command to get more information on command-line options, etc. Most manual pages are also available at the RealVNC® command line reference website. Additionally, user guides can be found at the RealVNC® documentation site.
Knoxville, Tennessee 37996 | 865-974-1000
The flagship campus of the University of Tennessee System