Page History

...

This document contains instructions for setting up a connection from a Windows PC to a VNC linux session.  

IMPORTANT, PLEASE NOTE:

• Remote access with vnc works best when the server session is restarted every time you need to use it.
• Due to timeouts associated with things like afs tokens, kerberos tickets, vpn, and ssh tunnelling, vncserver sessions left running can become inaccessible to vnc clients, and need to be restarted. Troubleshooting section below has some possibilities for getting around the problem, but they are not always successful. So, please do not leave unsaved work in an inactive session
• The iris group of SCCS machines are equipped with fonts necessary for running edm displays like lclshome. Other machines like noric or yakut do not have these fonts

Set up your PC

...

(one time

...

)

• Install vpn if you don't have it already. Instructions from SCCS are here: https://confluence.slac.stanford.edu/display/NetMan/How+to+Connect+to+SLAC+VPN
• Download and install the vnc for windows viewer client software executable from here: http://www.realvnc.com/products/free/4.1/winvncviewer.html; (make a shortcut on your desktop)
• Download and install putty, if you don't have it already. Once you install and run vpn, you can get putty from the SLAC xweb: https://xweb.slac.stanford.edu

Configure your vncserver

...

(one time

...

)

• vpn into the SLAC network, see https://confluence.slac.stanford.edu/display/NetMan/How+to+Connect+to+SLAC+VPN
• Using putty (or XWin-32 if you prefer) log into iris01.slac.stanford.edu, providing your unix username and password
• Create your vnc password:
  • > vncpasswd
    Provide a password following the usual SLAC password guidelines.
    The password will be stored in ~/.vnc/passwd
    To reset the password, run vncpasswd again.

...

• Edit your vnc xstartup file to invoke kde at startup:
  • > emacs ~/.vnc/xstartup
    change last line from "twm" & to "startkde&", save and close

Run your vnc server (as needed)

As needed.

• > vncserver -localhost -nolisten tcp -geometry 1440x900
  (or use desired display parameters, see.....)
  Again, make note of the displaynum - you'll need to use it to connect from Windows.

The session will continue to run until you -kill it, or until SCCS does.
Warning - tokens, kerberos tickets, vpn, and ssh tunnelling can all conspire to prevent you from reconnecting to an existing vncserver session. See troubleshooting section below. The safest thing is to re-start a vncserver for every use, and -kill it when done.

Connect from Windows (every time you connect)

Every time you need a new session.

...

• Now run the vnc client.
• In the Server box, enter localhost:pcport
  for example localhost:5902
• click OK
• The vnc viewer authentication popup will appear; this could can take some time, perhaps up to 30 seconds or a minute.
• Enter your vnc server password (you don't need to enter username in the popup).
• Your linux desktop should appear.
• When you're ready to close the vnc client, simply click the window close icon, "X", at the upper righthand corner of the display.

...