MobaXterm

Owned by Andong Li
Last updated: Aug 20, 2024
4 min read

For windows users, MobaXterm is a popular and one of the recommended software to connect to the cluster.

“MobaXterm is your ultimate toolbox for remote computing. In a single Windows application, it provides loads of functions that are tailored for programmers, webmasters, IT administrators and pretty much all users who need to handle their remote jobs in a simpler fashion.”https://mobaxterm.mobatek.net/

Install MobaXterm

  1. Link to download: https://mobaxterm.mobatek.net/download.html

image-20240820-160158.png

  1. The “Home Edition” is more than enough for accessing the cluster and includes features such as:

    1. SSH

    2. X11-fowarding

    3. SFTP browser

  2. Select the current version and choose either “portable” or “installer edition”.

    image-20240820-160307.png

  3. Locate the installer

    1. In chrome and Microsoft edge, “ctrl+j” opens your downloads

  4. Extract the installer

    1. Right click on the installer and extract to your desired location.

  5. Run the installer

  6. Congrats you’ve successfully installed MobaXterm!

    1. You can start a local terminal and explore your windows file system in a “Linux” bash shell.

Quick Connect

  1. Although it is recommended for users connect through “User sessions”, after opening MobaXterm, you can connect to the cluster immediately through your local terminal by clicking “Start local terminal”

  2. In the prompt enter the following:

ssh insert_NetID_here@hpc2.storrs.hpc.uconn.edu

  1. You should then be prompted for a password and a DUO 2FA.

We are aware of issues with logins through this method. Please set up “User sessions” if you are having trouble connecting through your local terminal.

User Session Setup

  1. Select the “Session” Icon on the top left

  2. Select “SSH” and enter the following relevant information:

    1. “Remote host”: hpc2.storrs.hpc.uconn.edu

    2. Check “Specify username”: enter your NetID

    3. “Port”: 22

  3. Select “Bookmark Settings”

    1. You can change the nickname of the session here or do it later

      1. We named ours “hpc2”

    2. You can create a desktop shortcut here for even easier access

    3. Click “ OK” to save.

  4. You should now have the session available in your bookmarks on the left column in the application as well as a shortcut directly. DoubleClick them to connect and click “accept” to the following message.

Creating user sessions will save you time in the future including troubleshooting login nodes. It is recommended that you create the following 3 sessions with the same steps as above. (You can also duplicate a session by right clicking on one, then edit session’s information as you see fit).

Change the “Remote host” to:

  1. login4.storrs.hpc.uconn.edu

  2. login5.storrs.hpc.uconn.edu

  3. login6.storrs.hpc.uconn.edu

Troubleshooting

  1. Unable to start local terminal

    1. You’ll see a message at the bottom of your window “CygUtils plugin not found on your system”. Once you click on it, you’ll get another message along with a link to download the plugin.

    2. Once downloaded, move the file to the location where your MobaXterm executable is. Typically, this would be under: C:\Program Files (x86)\Mobatek\MobaXterm

    3. Restart MobaXterm and you should be able to access your local file system through the terminal

  2. Remote Host Identification Error

    1. If you receive the following error message when login on or when connecting to any node, fear not!

      1. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed.

    2. In your terminal, enter the following command and replace node name with the appropriate node. Using cn571 for example:

      1. ssh-keygen -R cn571

    3. If the error is during login, you may need to use the following

  3. Login node issues

    1. If you get stuck landing on a login node or find that a login node is behaving significantly slower than normal, you can simply use one of the other sessions created earlier that targets a specific login node when connecting.

    2. Feel free to submit a ticket and let us know if you suspect a node is misbehaving