Jopa6460: /* Windows */

2020-09-09T20:21:21Z

‎Windows

Jopa6460: Created page with "=== Windows === The PuTTY SSH client can handle ssh tunneling on Windows based machines. You can download it [http://www.chiark.greenend.org.uk/~sgtatham/putty/ here]. When y..."

2020-09-09T20:21:02Z

Created page with "=== Windows === The PuTTY SSH client can handle ssh tunneling on Windows based machines. You can download it [http://www.chiark.greenend.org.uk/~sgtatham/putty/ here]. When y..."

New page

=== Windows ===
The PuTTY SSH client can handle ssh tunneling on Windows based machines. You can download it [http://www.chiark.greenend.org.uk/~sgtatham/putty/ here].

When you open putty, enter <code>jumpgate-phasta.colorado.edu</code> in the "Host Name" box. Then click the + button next to SSH on the left pane (to expand the SSH tree node). Choose the "Tunnels" page. The <code>start_vnc.sh</code> script should tell you to run <code>ssh -L59xy:portal1:59zw jumpgate-phasta.colorado.edu</code> on your machine. Those instructions are OK but a better practice is to ignore what that script suggested for <code>xy</code> (it always suggests 05 currently) and instead use <code>ssh -L59zw:portal1:59zw jumpgate-phasta.colorado.edu" where <code>zw</code> varies for each new session created. If you get <code>23</code> that just means there were <code>22</code> sessions created before you created this one (but the plan is for you to keep using 23 until the machine gets rebooted). Enter <code>59zw</code> in the "Source Port" box. Enter <code>portal1:59zw</code> in the "Destination" box (starting and ''click the add button''). Putty is a little strange about saving the session which you want to do to avoid having to do all the above every time you re-connect. ''BEFORE'' you click the "Open" button, you want to name your session (your choice) and click save. Then in the future when you start putty you should be able to just click that saved session name and click load. Then click "Open" and login as normal. You will then be able to use a vncviewer as instructed by the script.

Example:

The script says:
<code>ssh -L5905:portal1:5923 jumpgate-phasta.colorado.edu</code>
your <code>zw</code> from the instructions above is <code>23</code>
enter <code>5923</code> in the "Source Port" box
enter <code>portal1:5923</code> in the destination box.

====Connecting to your VNC with PuTTY====

Once we SSH to jumpgate (on the default SSH port 22), our main desktop on portal1 can be accessed via a VNC session as follows.

# The VNC server should already be running on portal1 using port 59zw.
#* To check the port, on portal1 run <code>/opt/vnc_script/findsession.sh</code>
#* To confirm the VNC server is running (and see port), run <code>ps aux | grep vnc</code>
# Open PuTTY on your local machine.
# Under "Session", SSH to <code>USERNAME@jumpgate-phasta.colorado.edu:22</code>, where <code>USERNAME</code> is your username on <code>jumpgate</code>, and <code>22</code> is the standard SSH port.
# Under "Session">"SSH">"Tunnels", select source port <code>59##</code> and destination port <code>portal1:59##</code>, where <code>##</code> is the two-digit number of your VNC session. Select destination <code>local</code> and click "Add".
#* We select <code>local</code> because we have a service (VNC Server) running on a machine (<code>portal1</code>) that can be reached from the remote machine (<code>jumpgate</code>), and we want to access it directly from the <code>local</code> machine.
# Confirm the dialog by clicking "Open", thus establishing an SSH connection between <code>localhost</code> and <code>jumpgate</code>, and tunneling <code>localhost:59##</code> to <code>portal1:59##</code> via this connection.
# Open RealVNC, and connect to <code>localhost:##</code>, which is shorthand for <code>localhost:59##</code>. VNC ports are enumerated starting with <code>5901</code>, so any two digit port <code>##</code> is assumed to be port <code>59##</code>.
# You should now have access to your desktop on <code>portal1</code>. DON'T FORGET-- no meshing, solving, post-processing, EVEN MATLAB on <code>portal1</code>. To run memory and/or processor and/or graphics intensive jobs you need to create a terminal and type <code>vglconnect -s viz00x</code> where, at this time <code>x</code> is either 2 or 3.

← Older revision		Revision as of 20:21, 9 September 2020
Line 1:		Line 1:
−	=== Windows ===	+	=== PuTTY for Windows users ===
	The PuTTY SSH client can handle ssh tunneling on Windows based machines. You can download it [http://www.chiark.greenend.org.uk/~sgtatham/putty/ here].		The PuTTY SSH client can handle ssh tunneling on Windows based machines. You can download it [http://www.chiark.greenend.org.uk/~sgtatham/putty/ here].

Deprecated methods - Revision history

Jopa6460: /* Windows */

Jopa6460: Created page with "=== Windows === The PuTTY SSH client can handle ssh tunneling on Windows based machines. You can download it [http://www.chiark.greenend.org.uk/~sgtatham/putty/ here]. When y..."