SimCafe

Space shortcuts

Child pages
  • How to connect to Swanson Lab remotely

Versions Compared

Old Version 17

changes.mady.by.user Rajesh Bhaskaran

Saved on

compared with

New Version 18

changes.mady.by.user Rajesh Bhaskaran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Update (Oct. 2020): A remote access portal has been set up for the Swanson lab to simplify the connection process. You may want to try that: https://remoteaccess.labstats.com/cornell-swanson-lab.html

 


Please watch the following video to learn how to connect remotely.

HTML
<iframe width="640" height="360" src="//www.youtube.com/embed/k7nu3dvIm2U" frameborder="0" allowfullscreen></iframe>

 


A few things have been changed since this video was recorded, please use the links and tips included below.

  1. There are a limited number of computers and many remote users due to the Covid-19 pandemic. Please be sensitive to this and log out of the computers when you are done. Go to this page for determining what machines are available. They are not clickable links, only a representation.  Machines 17, 20, 23 and 26 are reserved for in-person use. The rest of the machines have been made available for remote use. Remote machines # 21, 22, 24 have Wasp and #25 has the Adobe suite. 

  2. Install VPN (you may be able to skip this if on some parts of the Cornell campus network and jump to step 4)
  3. Open CiscoAnyConnect and connect to VPN (skip if on Cornell campus network)VPN

  4. Log in to VPN  (skip if on Cornell campus network) OR Launch the secure mobility client on your computer by typing cuvpn.cuvpn.cornell.edu in the address bar. Note that you need the @en-ma-vpn-acad extension after your netID.

     


  5. When using Remote Desktop, the extension for the Swanson computers has changed slightly, please use: en-ma-swsn-##-u.coecis.cornell.edu. Simply replace the ## with the number of the computer you want to use (17-28 are available). Use the link above to check which computers are available. You will have to use your personal netid login, not a team login such as Baja or FSAE.

  6. Make sure your remote desktop client is the most recent. Some older versions do not connect properly and give nondescript errors which are difficult to troubleshoot.

...