There may be somewhat of a delay, but after all this you should soon see a new VNC window containing a Linux desktop session. The next prompt will ask for the VNC password you chose when you set up the VNC session. First, you will need to provide your UW NetID password. Once you’ve filled in all the fields, hit the “Connect” buttonĪfter pressing the Connect button, you will be asked for two passwords.“SSH User” is your NetID – if you leave this blank, you will be asked for it right after the next step.“SSH Server” must be the name of the server you started the VNC server on (.edu in this example).You must check the box “Use SSH tunneling”.For “Port”, use the port number from steps 3 and 4 of the previous section (e.g.For “Remote Host”, use either “localhost” or “127.0.0.1”.Launch TightVNC’s Java Viewer, then do the following: The ECE Linux Lab machines require you forward your VNC session over SSH, which is why we only support use of the TightVNC Java Viewer – that software can manage SSH forwarding automatically. With your VNC session now running, you can now connect to that hostname and port number using TightVNC. If it tells you the display is “:3”, you’d need to use port 5903 and so on. VNC ports start at 5900 – so when TigerVNC refers to “Display :2”, the port number VNC maps to that display is 5900 + 2 = 5902. Take note of the display number associated with the session.To verify whether a VNC session is already running, use the “-list” argument: $ vncserver - list TigerVNC server sessions : edu : 2 Starting applications specified in / homes / nemo /. 0.1 New '.edu:2 (nemo)' desktop is linux - lab - 069.ece. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |