The easy way to avoid this problem is to not do that.Īppendix 1: Connecting Using a Different ClientĮCE Computing does not offer support for this. Note: things will be more complicated if you have started VNC server sessions on multiple hosts. Then, return to the top of the page to start a new server. This will wipe out any saved password for the VNC session: $ cd $ pwd / homes / nemoĪnd to be really sure nothing is running… $ pkill - u $USER Xvnc If You Need to Reset Your VNC Session PasswordĬlose any VNC sessions as in the previous section, then delete the vnc password file. X DISPLAY # PROCESS ID : 2 11720 $ vncserver - kill : 2 Killing Xvnc process ID 11720 $ vncserver - list TigerVNC server sessions : Then, run vncserver -kill to quit any sessions which need not remain open (note that you do not add 5900 in this case – use the exact display number reported). IMPORTANT: Close Your VNC Session When Finished!įrom the command line on the remote machine, use the vncserver -list command to determine the display number of your VNC session. If you see a blank window, be patient for a bit – but if it continues to be blank, end the current session and try starting over again using a different Linux Lab machine – the one you chose may already be bogged down with too many other users. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |