VNC - Revision history

Jrwrigh: /* Killing a VNC Server */

2024-06-12T20:05:18Z

‎Killing a VNC Server

Jeffhadley: /* Clients (Step 2) */

2023-10-04T20:58:00Z

‎Clients (Step 2)

Jeffhadley: /* Clients (Step 2) */

2023-10-04T20:56:52Z

‎Clients (Step 2)

Jeffhadley: /* Clients (Step 2) */

2023-09-21T18:05:06Z

‎Clients (Step 2)

Jeffhadley: /* Clients (Step 2) */

2023-09-21T18:03:26Z

‎Clients (Step 2)

Jeffhadley: /* Clients (Step 2) */

2023-09-21T18:03:06Z

‎Clients (Step 2)

Jeffhadley: /* Start VNC Server (Step 1) */

2023-09-21T18:00:08Z

‎Start VNC Server (Step 1)

Jeffhadley: /* Clients (Step 2) */

2023-09-21T17:55:08Z

‎Clients (Step 2)

Jeffhadley: /* Start VNC Server (Step 1) */

2023-09-21T17:44:05Z

‎Start VNC Server (Step 1)

Jeffhadley: /* Starting a VNC viewer (Step 3) */

2023-09-21T17:11:58Z

‎Starting a VNC viewer (Step 3)

← Older revision		Revision as of 20:05, 12 June 2024
Line 30:		Line 30:

	ONLY run this if you want to kill your virtual desktop. Most users will never need to do this as the idea is to create one session and continue to use that one for all future usage.		ONLY run this if you want to kill your virtual desktop. Most users will never need to do this as the idea is to create one session and continue to use that one for all future usage.
		+
		+	NOTE this will kill ''all'' your VNC sessions.

	=== Changing the VNC Password ===		=== Changing the VNC Password ===

@@ Line 90: / Line 90: @@
   <code>portal1:59zw</code>, again replacing <code>zw</code> with your assigned port number.
   - Click the "Add" button.
-  - Click on "Open". You now have an established VNC connection with <code>portal1</code>.
+  - Click on "Open". You now have an established VNC connection with <code>portal1</code> and it will ask you to enter your (jumpgate) password.
   - Remaining steps are the same as non-Windows 8.

@@ Line 82: / Line 82: @@
   '''Windows 8'''
-  Same concept, so close the terminal that was established with PuTTY. Start a new one using PuTTY and entering the following in the Host Name, replacing zw with your assigned port number:
+  - Same concept as above... close the terminal that was established with PuTTY. Start a new one using PuTTY and entering the following in the Host Name:
-  <code>-L59zw:portal1:59zw USERNAME@jumpgate-phasta.colorado.edu</code>
+  <code>USERNAME@jumpgate-phasta.colorado.edu</code>
-  Again ensuring connection type is set to SSH. In the "Port" field, enter the <code>zw</code> assigned port number. Click on "Open". You now have an established VNC connection with <code>portal1</code>. Remaining steps are the same as non-Windows 8.
+  Again ensuring connection type is set to SSH.

@@ Line 77: / Line 77: @@
 The instructions given when you started the session on <code>portal1</code> (the ones you should have taken a screen shot of in Step 1 above) are OK, but it always tells you to start a session (in a terminal on your mac or linux machine command line) with the <code>ssh -L5905:portal1:59zw jumpgate-phasta.colorado.edu</code> command, where <code>zw</code> will be different for each user. That suggestion is OK if you never plan to connect to anyone else's session, but since we often collaborate by sharing VNC sessions, the better practice we adopt is to use <code>zw</code> in place of the suggested 05 (which just an arbitrary local port on your laptop). For example, when I created a session the last four numbers of the connection were <code>5923</code>, thus <code>zw</code> for me is <code>23</code> and the best practice is to ignore the script suggestion in favor of <code>ssh -L5923:portal1:5923 jumpgate-phasta.colorado.edu</code>
-The easiest way to set up the portal from the get-go (after you have created the VNC session on the PHASTA Machien side of things and left it open, AKA Step 1 above) is to close out of the terminal on your personal machine, reopen it, and run only this command where <code>zw</code> is your assigned port number:
+The easiest way to set up the portal from the get-go (after you have created the VNC session on the PHASTA machine side of things and left it open, AKA Step 1 above) is to close out of the terminal on your personal machine, reopen it, and run only this command where <code>zw</code> is your assigned port number:
   ssh -L59zw:portal1:59zw USERNAME@jumpgate-phasta.colorado.edu
   '''Windows 8'''
-  Close the terminal that was established with PuTTY. Start a new one using PuTTY and entering the following in the Host Name, replacing zw with your assigned port number:
+  Same concept, so close the terminal that was established with PuTTY. Start a new one using PuTTY and entering the following in the Host Name, replacing zw with your assigned port number:
   <code>-L59zw:portal1:59zw USERNAME@jumpgate-phasta.colorado.edu</code>
   Again ensuring connection type is set to SSH. In the "Port" field, enter the <code>zw</code> assigned port number. Click on "Open". You now have an established VNC connection with <code>portal1</code>. Remaining steps are the same as non-Windows 8.

← Older revision		Revision as of 18:03, 21 September 2023
Line 75:		Line 75:


−	The instructions given when you started the session on <code>portal1</code> (the ones you should have taken a screen shot of in Step 1 above) are OK, but it always tells you to start a session (in a terminal on your mac or linux machine command line) with the <code>ssh -L5905:portal1:59zw jumpgate-phasta.colorado.edu</code> command	+	The instructions given when you started the session on <code>portal1</code> (the ones you should have taken a screen shot of in Step 1 above) are OK, but it always tells you to start a session (in a terminal on your mac or linux machine command line) with the <code>ssh -L5905:portal1:59zw jumpgate-phasta.colorado.edu</code> command, where <code>zw</code> will be different for each user. That suggestion is OK if you never plan to connect to anyone else's session, but since we often collaborate by sharing VNC sessions, the better practice we adopt is to use <code>zw</code> in place of the suggested 05 (which just an arbitrary local port on your laptop). For example, when I created a session the last four numbers of the connection were <code>5923</code>, thus <code>zw</code> for me is <code>23</code> and the best practice is to ignore the script suggestion in favor of <code>ssh -L5923:portal1:5923 jumpgate-phasta.colorado.edu</code>
−
−	where <code>zw</code> will be different for each user. That suggestion is OK if you never plan to connect to anyone else's session, but since we often collaborate by sharing VNC sessions, the better practice we adopt is to use <code>zw</code> in place of the suggested 05 (which just an arbitrary local port on your laptop). For example, when I created a session the last four numbers of the connection were <code>5923</code>, thus <code>zw</code> for me is <code>23</code> and the best practice is to ignore the script suggestion in favor of <code>ssh -L5923:portal1:5923 jumpgate-phasta.colorado.edu</code>

	The easiest way to set up the portal from the get-go (after you have created the VNC session on the PHASTA Machien side of things and left it open, AKA Step 1 above) is to close out of the terminal on your personal machine, reopen it, and run only this command where <code>zw</code> is your assigned port number:		The easiest way to set up the portal from the get-go (after you have created the VNC session on the PHASTA Machien side of things and left it open, AKA Step 1 above) is to close out of the terminal on your personal machine, reopen it, and run only this command where <code>zw</code> is your assigned port number:

@@ Line 19: / Line 19: @@
 This will setup the VNC viewer for your session on the PHASTA machine side of things. Read through the output from <code>start_vnc.sh</code> as it contains crucial information and some tips which are elaborated on in this wiki.
-IMPORTANT: Make sure to remember the generated password and port number ("You should connect to 59** on portal1", "Your password is abcd1234ExamplePW") so that you can reuse the session you just started. Hint: take a screenshot of the output of <code>start_vnc.sh</code> and store it somewhere safe.
+IMPORTANT: Make sure to remember the generated password and port number ("You should connect to 59zw on portal1", "Your password is abcd1234ExamplePW") so that you can reuse the session you just started. Hint: take a screenshot of the output of <code>start_vnc.sh</code> and store it somewhere safe.
 It is common practice to leave your VNC session running on <code>portal1</code>. Next time you want to access your desktop, just ssh into jumpgate with a tunnel between portal1's VNC port (59**) and some port on your machine. Then use a VNC client to connect to the port on your machine. See the Client (Step 2) section below for an explanation of this process.

@@ Line 12: / Line 12: @@
 <code>portal1</code> is designated to host VNC sessions.
-First connect to jumpgate via ssh in a terminal on your personal machine. To start a VNC session on portal1 type the following in your jumpgate terminal with a return after each line:
+First connect to jumpgate via ssh in a terminal on your personal machine (If following the On Ramp you should already have this terminal opened). To start a VNC session on portal1 type the following in your jumpgate terminal with a return after each line:
   ssh portal1
   source /etc/profile.d/vncscript.sh

@@ Line 97: / Line 97: @@
 The <code>zw</code> here will need to be whatever you used for the <code>-L59zw:portal1:59zw</code> part of the tunnel. What the number is actually doing is telling this local VNC viewer on which port you have established a tunnel with the session for which you are starting the VNC viewer. Note it is possible to have several different simultaneous sessions. Each needs its own tunnel (established by repeating the process above with a unique <code>zw</code>) and then a corresponding "new" VNC viewer. In this way we might continue to work in our own session but then take a break to look at a collaborator's session without having to close out the tunnel and viewer pair.
-Now that you've connected to the PHASTA machines, it's time to learn a bit mroe about using a UNIX based system (Linux). To continue with the On Ramp click [UNIX|here]
+Now that you've connected to the PHASTA machines, it's time to learn a bit mroe about using a UNIX based system (Linux). To continue with the On Ramp click [[UNIX|here]]
 === Web Based Viewer ===