Setting Up VNC Session

From Cheaha
Revision as of 13:30, 24 July 2012 by Pavgi@uab.edu (talk | contribs) (Added instructions for setting up VNC server)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


Attention: Research Computing Documentation has Moved
https://docs.rc.uab.edu/


Please use the new documentation url https://docs.rc.uab.edu/ for all Research Computing documentation needs.


As a result of this move, we have deprecated use of this wiki for documentation. We are providing read-only access to the content to facilitate migration of bookmarks and to serve as an historical record. All content updates should be made at the new documentation site. The original wiki will not receive further updates.

Thank you,

The Research Computing Team

Virtual Network Computing (VNC) is a cross-platform desktop sharing system to interact with remote system's desktop using a graphical environment. This page covers basic instructions to access Cheaha using VNC. These basic instructions should be helpful for many use cases. If you are interested in knowing more options or detailed technical information, then please take a look at man pages of specified commands.

One Time Setup

Follow these instructions to configure VNC server for the first time. You can directly run a vncserver command to start a VNC session with default options, however, commands listed below will help you to get started quickly with Gnome desktop environment.

  • Create a password for your VNC server sessions using vncpasswd command. It stores an obfuscated version of the password in the given file (default $HOME/.vnc/passwd). Remember this password as you will be prompted for it when you try accessing the VNC session later. The password is validated each time a connection comes in, so it can be changed on the fly using vncpasswd command anytime later.
$vncpasswd 
  • By default a VNC server displays graphical environment using a tab-window-manager. Since we want to use a normal dekstop environment (default: Gnome on Cheaha), we need to add following settings to ~/.vnc/xstartup file. If this xstartup file is absent, then a file with default tab-window-manager settings will be created by the vncserver command during startup.
$ cat > $HOME/.vnc/xstartup <<\EOF
#!/bin/sh

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &
EOF

$ chmod +x $HOME/.vnc/xstartup

This completes one-time setup in which we set up VNC server password and display environment options. In the following section we will take a look at commands to start a VNC server.

Starting a VNC server

A VNC server can be started using vncserver command on Cheaha.

$ vncserver 
New 'cheaha.uabgrid.uab.edu:25 (pavgi)' desktop is cheaha.uabgrid.uab.edu:25
Starting applications specified in /home/pavgi/.vnc/xstartup
Log file is /home/pavgi/.vnc/cheaha.uabgrid.uab.edu:25.log

The above command output indicates that a VNC server is started on VNC port 25 which is system port 5925. The actual system port on which VNC server is listening for connections is obtained by adding a VNC base port (default 5900) and a VNC server port (25 in above case). Alternatively you can specify a high numbered system port directly (e.g. 5927) using '-rfbport <port-number>' option and the vnc server will try to use it if it's available. See vncserver's man page for details.

Connecting to VNC server

  • As shown in above example, a VNC server starts listening on a higher numbered port which isn't directly accessible from the internet. Hence, we need to use SSH local port forwarding to connect to this server. On Linux or Mac systems we can setup SSH port forwarding as shown below.
# ssh -L <local-port>:<remote-system-host>:<remote-system-port> USERID@<SSH-server-host>
$ ssh -L 5925:localhost:5925 USERID@cheaha.uabgrid.uab.edu

Above command will forward connections on local port 5925 to a remote system's (same as SSH server host Cheaha - hence localhost) port 5925.

  • Once we have a local port available for connection, we can access the VNC server using a VNC client. Following is a list of VNC client softwares and you can any one of it to access VNC server.
* http://www.tightvnc.com/ (Mac, Linux and Windows)
* http://www.realvnc.com/ (Mac, Linux and Windows)
* http://sourceforge.net/projects/cotvnc/ (Mac)

Note, Mac OS comes with a native VNC client support and hence you don't need to use any third-party software. On Linux systems you can use vncviewer command to access a VNC server. If you using Windows OS then you will need to install one of the supported VNC client as mentioned above. Once we have a VNC client installed, we can access VNC server using following connection string:

# vnc://<vnc-server>:<vnc-port>
vnc://localhost:5925 

Since we are using SSH local port forwarding to access our VNC server, our VNC connection string will look as shown above.