Harvard-MIT Data Center | Providing tools, resources, and support for analyzing data.

Accessing the RCE Classic

Guide Overview

This is an historical guide that describes how to access the Research Computing Environment (RCE) through a legacy secure network connection. A newer version of this guide is available from this web site's Accessing the RCE menu option.

Refer to the guide Working in the RCE Summer 2009 for information about how to use the desktop applications, tools, and utilities after you connect.

You can use the Easy Connection script if you connect:

From a system that operates on a minimum of Windows version 2000
To any server running the RCE

You can connect manually to the RCE if you use a Mac OS or Linux workstation. Before you connect to the RCE, read Setting Your Password in the guide Connecting to the RCE Summer 2009.

Note: If you connect to the RCE from a public machine, read Security Issues for Public Machines.

Connecting from a Windows Workstation

Connecting from a Windows Workstation

To connect to the RCE using the Easy Connection script after you change your assigned password, perform the following steps. To connect to the RCE manually, see Connecting Manually from Windows.

Step 1 Download the Easy Connection script.
1. Click the following link and save the Easy Connection script file to your system:
  
  HMDC Easy Connection Script
2. Double-click the executable file to extract the script.
3. Double-click the folder HMDC_VNC to open it.
Step 2 Start the script.
1. Double-click the icon Double_Click_Me to start the script.
2. In the Enter Hostname window, accept the VNC server hostname default, rce.hmdc.harvard.edu.
3. Click OK to continue.
  
  Note: If you receive a Windows AntiSpyware Notice, click Allow to enable the script to function.
Step 3 Enter your login account information and connect to the RCE.
1. In the Enter Username window, enter your login account username and click OK.
2. In the SSH Login Password window, enter your login account password and click OK.
3. In the Host Key Warning message window, click Yes to save the VNC server hostname to your local system cache and press Enter to continue.
4. In the Starting VNC Session window, note the session number and host server name.
5. Click OK to connect to the RCE.

You now are connected to the HMDC RCE. The viewer opens in full-screen mode. Move your mouse to the top-center of the desktop to view the menu for the VNC-client viewer application (vncviewer), which includes Minimize, Maximize, and Close buttons. The WinSCP file transfer window also opens in the background. Refer to the guide Working in the RCE Summer 2009 for details about how to use the desktop. Also see Working in the RCE Using VNC in this guide for specific information about working with your VNC connection.

To reconnect to the same VNC server with your original session parameters, perform the following:

Double-click the <Hostname>-<username> batch file to launch the reconnection script.
Enter your login account password and click OK.
At the Starting VNC Session prompt, click OK to connect to the RCE.

Details to Connecting Using Scripts

Details to Connecting Using Scripts

This section describes in detail how to connect to the RCE from a Windows workstation by using the Easy Connection script, and how to reconnect by using a batch file created by the script.

If you connect to the RCE from a public machine, read Security Issues for Public Machines.

Connecting by Using the Script

Connecting by Using the Script

You can connect to the RCE from a system that operates on a minimum of Windows version 2000, from within the HMDC network or outside of it, by using the HMDC Easy Connection script. You also can connect to the RCE on more than one system.

Download the Easy Connection script to your workstation.
1. Click the following link or go to the URL and save the executable file to the location you choose on your system:
  
  HMDC Easy Connection Script
2. Double-click the executable file.
  
  The executable file runs and creates a folder called HMDC_VNC on your desktop. It also opens the following two files within that folder:
  - Quickstart.txt - A short text file listing basic connection steps
  - HMDC_VNC_DOC.pdf - This guide, Connecting to the RCE
  Note: If this is the first time that you execute this type of file on your machine, your system might prompt you with warning messages about viruses or machine code issues. You can acknowledge these messages and permit the file to execute.
3. Double-click the new folder HMDC_VNC to open it.
  
  Figure 1 shows the contents of an example HMDC_VNC folder.
  
  Figure 1. Example HMDC_VNC Folder Contents
  
  Note: You can delete the HMDC_VNC.EXE executable file if you choose, but you must keep the HMDC_VNC folder on your system to use the Easy Connection script.
Start the script and enter the VNC server hostname.
1. To start the Easy Connection script, double-click the icon Double_Click_ME.
  
  The Enter Hostname window opens (Figure 2).
  
  Figure 2. Enter Hostname Window
2. In the Enter Hostname window, the VNC server hostname defaults to rce.hmdc.harvard.edu.
  
  Accept this default, or change this value to the hostname of a machine assigned to you as a VNC server. You can have more than one VNC server assigned to you; names of these server machines are listed in the email that contains your login account information. For example, vnc.hmdc.harvard.edu is another common VNC server hostname.
3. Click OK to continue.
  
  The Enter Username window is displayed (see Figure 4 in the following step).
  
  Note: If you use Windows XP Server Pack 2 or later and have Windows AntiSpyware enabled, the software might prompt you with a script notice, as shown in Figure 3. Click the Allow button to continue. Click the check box to enable the option Remember this action to prevent this message from reappearing.
  
  Figure 3. AntiSpyware Script Notice
Enter your login account information and connect to the RCE.
1. In the Enter Username window (Figure 4), enter your <login account username>, and then click OK to continue.
  
  Figure 4. Enter Username Window
  
  The SSH Login Password window is displayed (Figure 5).
  
  Figure 5. SSH Login Password Window
2. Type your <login account password>, and then click OK to continue.
  
  A warning message is displayed (Figure 6), and the system prompts you to store the key for the VNC server in your system cache. If you save the VNC server hostname the first time that you connect to the RCE, you are not prompted to repeat this step the next time you connect. This also ensures more security each time you log in to the VNC server.
  
  Figure 6. Host Key Warning Message
3. Click Yes to save the VNC server hostname to your local system cache, and then press Enter to continue.
  
  If your connection is successful, the Starting VNC Session message (Figure 7) indicates that you are connected to a VNC session. (This might take a few seconds to occur.) This message contains your VNC session number.
  
  Figure 7. Starting VNC Session Message
  
  If you provided an invalid value in any of the previous steps, the SSH connection fails and an error similar to the one shown in Figure 8 is displayed. Click OK, and then begin again at Step 2 (Windows).
  
  Figure 8. SSH Connection Failure Error Message
4. Note your session number and host server name in the Starting VNC Session window.
  
  In the example shown in Figure 7, the session number is 6. You can manage multiple VNC sessions using SSH, but usually you use the same session.
5. In the Starting VNC Session window, click OK.
  
  You now are connected to the HMDC RCE, as shown in Figure 9. You can begin work on the server.
  
  Figure 9. HMDC RCE with Viewer Application Menu
  
  Note: When you first log in to the RCE by using the Easy Connection script, the viewer opens in full-screen mode. Move your mouse to the top-center of the desktop to view the menu for the VNC-client viewer application, vncviewer, which contains standard Minimize, Maximize, and Close buttons.
  
  The WinSCP file transfer window, shown in Figure 10, also opens in the background. WinSCP enables you to transfer files between the RCE and your local workstation by dragging the files between the WinSCP window and a file browser on your workstation.
  
  Figure 10. WinSCP File Transfer Window
6. To view the WinSCP file transfer window, click the viewer application's Minimize button in the RCE.
  
  The first time you log in to the RCE and the WinSCP window is displayed, the system prompts you in a pop-up window to save the RSA key for use by WinSCP.
7. Click Save to save the key.
  
  All subsequent logins to a valid VNC session open WinSCP automatically.

Image(s):

Reconnecting by Using the Batch File

Reconnecting by Using the Batch File

You can reconnect to a VNC server easily by executing the reconnection batch file created when you execute the Double_Click_ME.bat Easy Connection script. A separate batch file is created for each VNC host to which you connect using the script. This reconnection batch file includes information about the VNC host and connection. When you use this file to reconnect to the RCE, you skip most of the steps needed when you connect in any other way.

The reconnection batch file naming convention is <Hostname>-<username>.bat. Figure 11 shows an example batch file, rce.hmdc.harvard.edu-astark.bat.

Figure 11. Example rce.hmdc.harvard.edu Batch File

To reconnect to an HMDC server with your original session parameters:

Double-click the reconnection batch file.

The SSH Login Password window is displayed (see Figure 5).
Type your <login account password>, and then click OK.

The Starting VNC Session Message is displayed (see Figure 7).
Click OK to connect to the RCE.

Note: If the AntiSpyware application is enabled, you might experience a slight delay while the batch file executes scripts.

You can create a shortcut to a reconnection batch file from your desktop. If you copy the batch file to another location, the session parameters are not valid.

Image(s):

16RCEConnect.gif

Security Issues for Public Machines

Security Issues for Public Machines

When you use the Easy Connection script to log in to the RCE from a public machine, be sure to delete the HMDC_VNC folder and all its contents from the machine when you are done. The batch file contains your login account username and the server hostname, which present security and privacy risks.

Connecting Manually from Windows

Connecting Manually from Windows

To connect manually to the RCE, begin at step 1. To reconnect, begin at step 21. If you try to connect to a session that no longer exists, or if you try to connect to another user's session, the UltraVNC viewer does not open, but you are logged on to the VNC server in an SSH tunnel.

Note: You must set your password before you can connect manually to an RCE server.

Install a secure shell (SSH) client application.

An SSH client application enables you to set up an SSH tunnel to a VNC server and to use your session securely on that server. HMDC supports use of the SecureCRT application, which is available at the FAS software URL (if you are an FAS affiliate):

http://www.fas-it.fas.harvard.edu/
Install a VNC client application.

HMDC supports use of the UltraVNC application, which is open-source software. You can download UltraVNC at the following URL:

http://ultravnc.sourceforge.net/
To configure a new connection to the VNC server, launch the SSH client you installed.

If you launch SecureCRT, the Connect window is displayed (Figure 12).

Figure 12. New SecureCRT Connect Window

Note: The first time you launch a program like SecureCRT you might receive a Windows Security Alert, such as the example shown in Figure 13. Click the Unblock button to enable SecureCRT to function as required.

Figure 13. Windows Security Alert Message
Click the New Session button.

The New Session Wizard appears (Figure 14).

Figure 14. New Session Wizard
Use the Protocol pull-down menu to select the SSH2 protocol, and then click Next.

The wizard prompts you to enter the VNC server hostname to which you choose to connect (Figure 15).

Figure 15. New Session Wizard - VNC Server Hostname
Enter the VNC server hostname to which you choose to connect, and then click Next.

You received email from HMDC with this server hostname. This is the machine name to which you are granted access. Usually, you connect to one of the rce.hmdc.harvard.edu servers.

The New Session Wizard prompts you to name the session (Figure 16). The session name defaults to the server hostname that you just entered.

Figure 16. New Session Wizard - Session Name
Accept the default session name, and click Finish.

The Connect window is displayed, and your VNC server connection appears in the list of options (Figure 17).

Figure 17. SecureCRT Connect Window with New Entry
Select the VNC server connection, and then click the Connect button.

The system prompts you with a New Host Key warning (Figure 18).

Figure 18. New Host Key Warning Message
Click the Accept & Save button to save the host key in your local system cache.

Note: If you click the Accept Once button, the system prompts you to accept this key again the next time log in to this server.

The Enter SSH Username window is displayed (Figure 19).

Figure 19. Enter SSH Username Window
Type your <login account username>, provided in email from HMDC. Then, click OK.

The Enter Secure Shell Password window is displayed (Figure 20).

Figure 20. Enter Secure Shell Password Window
Type your <login account password>, provided in email from HMDC. Then, click OK.

The connection window contains an active connection, as shown in Figure 21. You now are logged in to the HMDC server through SSH, and can start your VNC session.

Figure 21. Active SSH Connection in Connect Window
Type the command vncpasswd and press Enter to set the password for the VNC server.

The system prompts you to enter and verify a password for the VNC server. At both the Password and Verify prompts, type <login account password> and press Enter. Type "N" at the view-only password prompt, and again press Enter.
```
<Hostname:Login account username> [~]> vncpasswd
password: <login account password>
Verify: <login account password >
Would you like to enter a view-only password (y/n)? N
```
Type the command vncserver_once and press Enter to start your VNC session.

The system responds with your VNC session number.
```
<Hostname:Login account username> [~]> vncserver_once
3
<Hostname:Login account username> [~]>
```
Remember your session number now.
Log out of the SSH connection by typing exit in the connection window or by clicking the Close button.

The Connect window is displayed again (see Figure 17).
Select the VNC server connection, and then click the Properties button.

The Session Options window appears (Figure 22).

Figure 22. Session Options Window
In the Category panel on the left, select the Connection option Port Forwarding.

The right panel prompts you for Local Port Forwarding information, as shown in Figure 23. This is the VNC session information needed to connect to the RCE.

Figure 23. Session Options - Port Forwarding Category
Click the Add button.

The Local Port Forwarding Properties window appears (Figure 24). You configure the VNC session parameters in this window.

Figure 24. Local Port Forwarding Properties Window
Create the VNC session in an SSH tunnel connection using the following parameters. Note that the your local machine and the remote VNC server must use the same port number to connect your VNC session.
- Name - Enter a descriptive name for this connection, such as VNC.
- Local Port - Enter the port number for the local machine to use to connect to your VNC session. The VNC server assigns VNC session numbers sequentially to ports that begin at 5900. Type 59<VNC Session Number>.
  
  Note: Make sure that your VNC session number is two digits in the port assignments, and that both port assignments are the same. For example, if your VNC session number is 6, then add a leading zero and type 5906 for both Local and Remote ports.
- Remote Port - Enter the port number that the VNC server uses to provide a connection to your VNC session. Again, the VNC server assigns VNC session numbers sequentially to ports that begin at 5900. Type 59<VNC Session Number>.
- Application - SecureCRT enables you to set up an application to launch when you connect to the VNC session. If you know the location of your VNC client application, click the ellipsis button, navigate to that file location, and then select the executable file. If you do not know the location of the application, use your local desktop search function to find the vncviewer.exe file, and then enter that location.
- Arguments - Enter the options for the VNC client to include in the command to connect. Type localhost:<VNC Session Number>. This specifies on the command line which port number on your local machine the VNC client uses. (Do not add a leading zero to the session number in this command.)
Click OK in the Local Port Forwarding Properties window.

The Session Options window updates to include the VNC session information that you added (Figure 25).

Figure 25. Session Options with VNC Session Tunnel Connection
Click OK in the Session Options window to save the VNC session configuration.

The Connect window is displayed. The VNC server option is now configured with the session details.
In the SecureCRT Connect window, select your VNC server and click Connect to connect your VNC client to the server.

The Enter SSH Username window is displayed (see Figure 23).
In the Enter SSH Username window, type your <login account username>, and then click OK.

The Enter Secure Shell Password window is displayed (see Figure 24).
Type your <login account password>, and then click OK.

The VNC Authentication window is displayed (Figure 26). This indicates that you are connecting to your VNC session.

Figure 26. VNC Authentication Window
Type your <login account password>, and then click Log On.

You are connected to the RCE.

Note: The RCE does not open in full-screen mode if you do not connect to it using the HMDC Easy Connection script, and you are unable to change the size of the RCE window.

Image(s):

Connecting from a MacOS Workstation

Connecting from a MacOS Workstation

To connect from a system that operates on a minimum of MacOS X after you change your assigned password, perform the following:

Step 1 Install a VNC client and start a session.
1. Install the VNC client Chicken of the VNC for MacOS. Go to:
  
  http://sourceforge.net/projects/cotvnc/
2. Use the SSH client built into MacOS to connect to your assigned host. In a terminal window, type:
  ssh <username>@<Hostname>
3. At the host warning prompt, type yes to connect to the system and press Enter.
4. Enter your login account password and press Enter to continue.
5. The first time you log in to this server, type vncpasswd at the system prompt and press Enter to set the password for the VNC server. If this is not the first time you logged in to this server, skip to the next step.
  
  At both the Password and Verify prompts, type a new <login account password> and press Enter. Type "N" at the view-only password prompt, and again press Enter.
6. To start the VNC session and acquire a session number, type vncserver_once. Note the session number now.
7. To log out of the VNC server, type exit.
Step 2 Create an SSH tunnel.
1. In a terminal window, type the following command to create an SSH tunnel. Enter the <VNC Session#> as two digits:
```
> ssh -L 59<VNC Session#>:localhost:59<VNC Session#> <Username>@<Hostname>
```
2. Enter your login account password and press Enter.
Step 3 (MacOS) Start the VNC client and log in to the RCE.
1. Launch Chicken of the VNC viewer, click the Connection pull-down menu, and select Open Connection.
2. In the Servers panel select the option New Server to set up a new session connection.
3. Enter the following details to configure your session connection:
  - Host - Accept the default value, localhost.
  - Display - Type <VNC Session Number>(do not add a leading zero to the session number).
  - Password - Type <Login account password>.
4. Click Connect.

You now are connected to the HMDC RCE. Refer to the guide Working in the RCE Summer 2009 for details about how to use the desktop. Also see Working in the RCE Using VNC in this guide for specific information about working with your VNC connection.

Details to Connecting from MacOS

Details to Connecting from MacOS

To connect to the RCE the first time, begin at step 1. To reconnect, begin at step 2.

This procedure requires that you connect from a system that operates on a minimum of MacOS X.

Install a VNC client for MacOS and start a new VNC session.

This procedure requires that you connect from a system that operates on a minimum of MacOS X. For information about the commands used in these procedures, see the appendix section VNC Commands.

To connect to the RCE the first time, begin at step 1. To reconnect, begin at step 2.
1. Install a VNC client for MacOS and start a new VNC session.
  1. Download and install a VNC client application, such as Chicken of the VNC by Open Source Technology Group, available at the following URL:
    
    http://sourceforge.net/projects/cotvnc/
  2. Open a terminal window and use the SSH client built into the MacOS to connect to the VNC server. Type the following:
```
> ssh <username>@<Hostname>
```
    The first time that you connect to the VNC server, your system prompts you with a warning message about the host.
```
The authenticity of host '<Hostname (address)>' can't be established. 
RSA key fingerprint is <fingerprint>.
Are you sure that you want to continue connecting (yes/no)?
```
  3. Type yes, and then press Enter to continue.
    
    The system notifies you that you added the host permanently to the list of known servers on this machine, and then prompts you to enter your login account password.
```
Warning: Permanently added '<Hostname (address)>' (RSA) to the list of know hosts.
<Login account username>@<Hostname>'s password:
```
  4. Type <login account password> and press Enter to continue.
    
    A welcome message is displayed, followed by the system prompt.
```
*****************
* Welcome to rce-2.hmdc.harvard.edu *
* *
* For information about this and other HMDC servers: *
* http://support.hmdc.harvard.edu/kb-983/research_support_overview *
* *
* Please note that you are governed by the IT standard uses and practices*
* of Harvard University while using this machine. See the following URL *
* for more information: *
* http://support.hmdc.harvard.edu/kb-930/hmdc_policies
* *
*****************

<Hostname:Login account username> [~]>
```
  5. If this is the first time you log in to this server, type vncpasswd and press Enter to set the password for the VNC server. If this is not the first time that you logged in to this server, skip to the next step.
    
    The system prompts you to enter and verify a password for the VNC server. At both the Password and Verify prompts, type a new <login account password> and press Enter. Type "N" at the view-only password prompt, and again press Enter.
```
<Hostname:Login account username> [~]> vncpasswd
Password: <login account password>
Verify: <login account password >
Would you like to enter a view-only password (y/n)? N
```
  6. To start the VNC session and acquire a session number, type the command vncserver_once.
```
> vncserver_once
<VNC Session Number>
```
    Remember your session number for later. Now that you have acquired a <VNC Session#>, log out of the VNC server.
  7. Log out of the VNC server. Type exit.
2. In a terminal window, create an SSH tunnel.
  
  Creating an SSH tunnel on a MacOS X workstation is easy.
  1. In a terminal window, type the following command.
    
    Note: Type the <VNC Session#> as two digits. For example, if your session number is 6, then add a leading zero and enter 06.
```
> ssh -L 59<VNC Session#>:localhost:59<VNC Session#> <Username>@<Hostname>
```
  2. The system prompts you for your <login account password>.
    
    Type your <login account password> and press Return to create the tunnel.
3. Start your VNC client and log in to the RCE.
  
  The following example uses the Chicken of the VNC application:
  1. Launch Chicken of the VNC viewer.
    
    The VNC Login window is displayed (Figure 27).
    
    Figure 27. VNC Login Window
  2. In the Servers panel (on the left) select the option New Server, or click the plus-sign (+) button to set up a new session connection.
    
    If your session connection is already configured, select that server option and then go to step 4.
  3. Enter the following details to configure your session connection:
    - Host - Accept the default value, localhost.
    - Display - Type <VNC Session Number> (do not add a leading zero to the session number).
    - Password - Type <Login account password>.
  4. Click Connect.
    
    You now are connected to the HMDC RCE. You can begin work on the server.

Image(s):

17RCEConnect.gif

Connecting from a Linux Workstation

Connecting from a Linux Workstation

To connect to the RCE from a Linux workstation after you change your assigned password, perform the following:

Identify the VNC viewer application provided by your workstation distributor, such as vncviewer.
Use your SSH client that is built into Linux to connect to your assigned host. Type ssh <username>@<Hostname>.
The first time you log in to this server, type vncpasswd at the system prompt and press Enter to set the password for the VNC server. If this is not the first time you logged in to this server, skip to the next step.

At both the Password and Verify prompts, type a new <login account password> and press Enter.
Type "N" at the view-only password prompt, and again press Enter.
Start a new VNC session. In a terminal window, type vncserver_once. Note the session number now.
Create an SSH tunnel and connect to the VNC session. In a new terminal window, type the following command. Do not add a leading zero to the VNC session number:
```
> <vncviewer> â€“via <username>@<Hostname> localhost:<VNC Session Number>
```

Details to Connecting from Linux

Details to Connecting from Linux

For information about the commands used in these procedures, see the appendix section VNC Commands.

To connect to the RCE the first time, begin at step 1. To reconnect, begin at step 4.

Identify the VNC client application provided by your workstation distributor, such as vncviewer.
Use your SSH client that is built into Linux to connect to your assigned host. Type the following command:
```
> ssh <username>@<Hostname>
```
The first time you log in to this server, type vncpasswd and press Enter to set the password for the VNC server. If this is not the first time that you logged in to this server, skip to the next step.

The system prompts you to enter and verify a password for the VNC server. At both the Password and Verify prompts, enter a new <login account password> and press Enter. Type "N" at the view-only password prompt, and again press Enter.
```
<Hostname:Login account username> [~]> vncpasswd
Password: <login account password>
Verify: <login account password >
Would you like to enter a view-only password (y/n)? N
```
Start a new VNC session if you do not have an existing session.

Open a terminal window and type the command vncserver_once:
```
> vncserver_once
<VNC Session Number>
```
Note your VNC session number for use later.
Create an SSH tunnel using the SSH client resident on the Linux workstation and connect to the VNC session.

In a new terminal window, type the following command. Do not add a leading zero to the VNC session number:
```
> <VNC client application> -via <username>@<Hostname> localhost:<VNC Session Number>
```
You now are connected to the HMDC RCE. You can begin work on the server.

To exit the RCE from a Linux workstation, close the VNC client window.

Exiting the RCE

Exiting the RCE

When you finish working in the RCE, you can close the RCE and keep your VNC session active, or close the RCE and terminate the session.

Close the RCE.

Click the Close (X) button on the RCE window. Move the cursor to the top-center of the window to see the viewer menu.

This closes the VNC client window, but does not end your VNC session.
Close the SSH tunnel.

To keep your VNC session intact when you close the SSH tunnel, click the Close button on the plink.exe window (PuTTY Link application window), or type exit in the window. (If you connected manually, type exit in the connection window.)

To terminate your VNC session when you close the SSH tunnel, type the following command in the plink.exe window (if you connected manually, type in the connection window), and then close the window:
```
> vnccleanup
```
Note: There is no harm in closing the plink.exe window before you close the desktop, but the VNC client might issue a warning.
If you connected using the Easy Connection script, close the WinSCP file transfer window on your local machine.

Click the Close button in the top-right corner of the WinSCP window.

Working in the RCE Using VNC

Working in the RCE Using VNC

These sections describe specific tasks that you perform differently when connecting to the RCE by using the legacy VNC application.

Resizing the RCE Window Using VNC

Resizing the RCE Window Using VNC

If you connect to the HMDC RCE by using VNC, close your existing session and start a new one with your desired session size.

Please see Connecting from a Windows Workstation (or the appropriate Mac OS or Linux workstation sections) for more information.

Transferring Files Between Environments Using WinSCP

Transferring Files Between Environments Using WinSCP

The WinSCP file transfer window, shown in Figure 28, opens in the background when you connect to the RCE by using the Easy Connection script. WinSCP enables you to transfer files between the RCE and your local workstation by dragging the files between the WinSCP window and a file browser on your workstation.

To view the WinSCP file transfer window, click the RCE viewer application's Minimize button.

Figure 28. WinSCP File Transfer Window

WinSCP is an open source, free, secure shell (SSH) File Transfer Protocol (SFTP) client for Windows. HMDC recommends use of WinSCP in the RCE. For detailed information about installation and use of this utility, use to the following link:

http://www.winscp.net/eng/docs/start

Image(s):

12RCEWork.jpg

Transferring from the RCE

Transferring from the RCE

To transfer a file from the RCE to your local workstation, drag the file from the WinSCP window to a file browser on your workstation. WinSCP prompts you to copy the file, as shown in Figure 29. This figure shows that the file issue_report_template.txt is transferred from the RCE to the drop target you selected on your local workstation. Click the Copy button to transfer the file to your workstation.

Figure 29. WinSCP Remote to Local File Transfer

Image(s):

13RCEWork.jpg

Transferring to the RCE

Transferring to the RCE

To transfer a file from your local workstation to the RCE, drag the file from a file browser on your workstation to the WinSCP window. WinSCP prompts you to copy the file, as shown in Figure 30. This figure shows that the file issue_report_template.txt is transferred from your local workstation to remote directory you selected in the RCE. Click the Copy button to transfer the file to the RCE.

Figure 30. WinSCP Local to Remote File Transfer

Image(s):

14RCEWork.png

Terminating Environments Accessed Using VNC

Terminating Environments Accessed Using VNC

Some functions in the RCE run outside of the RCE and require you to use commands. The RCE is built on the X Windows platform. You create a VNC session within which the RCE runs on X Windows, but the session functions separately from the RCE. This section describes how to to terminate an unusable RCE environment using the command vnccleanup. Refer to Implementation Details for information about other commands that you might use.

Terminating a Frozen or Unusable Environment

Terminating a Frozen or Unusable Environment

Sometimes, because of system issues, the RCE hangs or freezes. In a frozen environment, you can open your VNC session, but one or more applications do not work properly. For example, the icons on the toolbar might not respond or you might not be able to move between workspaces. Another problem occurs if your window display is not matched to your monitor settings, making your desktop window out of proportion with your workstation monitor. Any one of these events constitutes an unusable work session and requires that you terminate it.

To terminate a frozen or unusable environment, you must use SecureCRT or another SSH application to perform the following:

Set up an SSH connection to your VNC server and connect to it.

You can execute the HMDC Easy Connection script to connect automatically to the server. Refer to the guide for information about how to use SecureCRT to set up a manual SSH connection to your VNC server.
Locate the connection window.

If you connect using the Easy Connection script, close the RCE window and move to the plink.exe window to continue.

If you connect manually using SecureCRT, close the RCE viewer and move to the SecureCRT connection window.

If you connect manually from a Linux workstation, close the RCE viewer. Then, in the terminal window from which you connected to the RCE, press Ctrl+z and type the command bg to return to the connection prompt.

In the connection window, type the command vnccleanup and respond to the system prompt. For example:

> vnccleanup
This will end your current session. If you have unsaved work, it may be lost.
Would you like to continue? <Enter y or n>: y
Shutting down VNC session...Killing Xvnc process ID 4331...done
Shutting down gconfd-2...done
Shutting down bonobo...done
Shutting down GNOME keyring daemon...done
Remote access session has been cleaned up.
You should now be able to start a new session.

When the system informs you that you can start a new session, close the session window.

Now you can connect to a new VNC session of the RCE.

Terminating a Frozen Environment on a Non-HMDC Server

Terminating a Frozen Environment on a Non-HMDC Server

To terminate a frozen environment on a non-HMDC server:

Perform steps 1 and 2 in the section "Terminating a Frozen or Unusable Environment."
If you do not know your session number, type the following command in the connection window to find the session number:
```
> ps -fu `whoami` | grep Xvnc
```
Type the following command to terminate (kill) your VNC session:
```
> vncserver â€“kill :<VNC Session Number>
```
For example, the user rfrost owns session number 12 and issues the command shown in Figure 31 to terminate it.

Figure 31. Example kill Command
Type the following commands to terminate remaining processes related to your session:
```
> gconftool-2 --shutdown
> bonobo-slay
> killall gnome-keyring-daemon 
```
You might receive one or more error messages similar to the following:
```
gnome-keyring-daemon(<number>): Operation not permitted. 
```
These messages indicate that you cannot terminate the gnome-keyring-daemons process for any other user.
Type exit in the plink.exe window or connection window, and then close it.

Now you can create and connect to a new session.

Image(s):

16RCEWork.gif

Legacy FAQ

Legacy FAQ

These legacy FAQ questions concern tasks that are related to the VNC protocol connection to the RCE.

How can I avoid creating multiple RCE sessions?

How can I avoid creating multiple RCE sessions?

Multiple RCE sessions may result from running the HMDC Easy Connection Script from more than one Windows workstation.

Once you have established an RCE session, take note of the server to which you are connected (for example, rce-2.hmdc.harvard.edu) and specify it when you are prompted for a hostname by Double_Click_Me.bat on your additional Windows workstation.

How do I kill an active RCE session I am not using?

How do I kill an active RCE session I am not using?

To kill an active RCE sessions that you are not using, connect to the server on which the session exists by using ssh and run the vnccleanup command.

See Terminating Environments Accessed Using VNC for more information.

How do I log out of an RCE session?

How do I log out of an RCE session?

As a general rule, you do not need to log out of an RCE session; when you want to stop working at a particular workstation. Just close your VNC viewer and your SSH client (plink on Windows, command-line ssh on a Mac or a Linux workstation). The next time you reconnect to the RCE, all the items on your desktop are right where you left them. However, there are some circumstances which require you to terminate your RCE session. For example, you need to terminate a session when moving between workstation whose monitors differ in size and resolution.

To terminate your RCE session, open a terminal and enter the command vnccleanup. Enter y when prompted. Make sure you save your work first.

Your session closes, and you are free to reestablish a new one.

This process is documented in the section Working in the RCE Using VNC.

I see an error message that says I have multiple sessions open!

I see an error message that says I have multiple sessions open!

You might see the following error message (Figure 32) when you connect to the RCE.

Figure 32. Multiple Sessions Error Message

This indicates that previously you started an RCE session on a different server, and that instead of reconnecting to that server, you have started a new session. We recommend against running multiple sessions; the environment may behave unpredictably, and you may have difficulty working.

The most common cause of this problem is failing to make note of the name of the RCE server to which you initially connected (see "How can I avoid creating multiple RCE sessions?"). If you use the HMDC Easy Connection Script, make sure that you reconnect by double-clicking the custom batch file (it is named something like <server-name>.hmdc.harvard.edu-<username>.bat) instead of double-clicking Double_Click_ME.bat again.

If you do not terminate your superfluous sessions, you see this error message over and over again. To resolve the issue, follow the instructions in the error message. You can proceed in one of two ways, either terminating your new session or terminating your old session. Make note of the hostname on which your other session is running (in the example above, it's rf-1.hmdc.harvard.edu), then open a terminal window.

Type vnccleanup and press Return. This command will terminate your session; once your VNC window has closed, reconnect to your old session. This is the recommended procedure for resolving this issue.
Type ssh <hostname>, entering the hostname oon which your other session is running. Once you see a command prompt, type vnccleanup and press Return. Be aware that if you have any unsaved work in your old session, it might be lost. Then, click OK to dismiss the error message.

If you have followed this procedure for each superfluous session listed in the error message, and the error message comes back, please contact us.

Image(s):

Multiple sessions error message

Implementation Details

Implementation Details

This appendix describes the legacy implementation of VNC supported by HMDC for access to the RCE.

VNC Basics

VNC Basics

The VNC protocol enables you to establish a virtual desktop on any machine that can access the internet and runs a VNC server. Your local computer runs a VNC client program that connects to the server using four parameters:

VNC server hostname
VNC session number
Login account username
Login account password

After you connect to the VNC server, your VNC client will display a virtual desktop. When you connect to HMDC servers, you will see the RCE.

You perform your work in the RCE during a VNC session, which is the period during which your virtual desktop exists. If you disconnect your VNC client, the session remains active. You can reconnect to this session and find that the desktop remains exactly as you left it, with windows open and programs running.

Usually, you start a session one time and reconnect to that same session each time you access the RCE. There are times, however, when you might need to start a new session. For example, if HMDC staff reboots the machine on which your session is running, then your session is terminated. Also, if the RCE is frozen or unresponsive, you must terminate the current session and start a new session.

VNC Application

VNC Application

The VNC application used at HMDC is open-source software by UltraVNC, Ltd. Go to the following URL for information about this product:

http://ultravnc.sourceforge.net/

When you connect to the RCE using the Easy Connection script, first you open an SSH connection to the VNC server, and then you establish a VNC session.

When you connect to the desktop manually, first you establish a VNC session, and then you open an SSH connection to that session.

VNC Commands

VNC Commands

This section describes the following commands, which you can use to manage your VNC session:

Set your VNC session password using vncpasswd.
Start a session using vncserver_once.
Check you session status using vncfinger.
On a non-HMDC server, check your connection status using ps.
Terminate a frozen or nonfunctional session using vnccleanup.

vncpasswd

vncpasswd

Unless you use the HMDC Easy Connection script to connect to the RCE, your VNC client prompts you for a password when connecting to a session. This VNC session password is separate from the login account password required when you log in to the server. If you use the Easy Connection script, the script sets your VNC session password to your login account password.

On HMDC systems, the command vncserver_once sets your VNC session password to your login account password. On non-HMDC systems, the command vncserver prompts you to create a session password.

If you do not know your VNC session account password or if you choose to change it, type the command vncpasswd in the SSH connection window as follows:

> vncpasswd
Password: <new password>
Verify: <new password>

vnccleanup

vnccleanup

To terminate a frozen or non-functional VNC session type the following command:

> vnccleanup

You will receive the following messages:

WARNING: This will end your current session. If you have unsaved work, 
WARNING: it may be lost.
Would you like to continue? [y/n]: y
*** Shutting down VNC session...Killing Xvnc process ID 4331...done
*** Shutting down gconfd-2...done
*** Shutting down bonobo...done
*** Shutting down GNOME keyring daemon...done
Remote access session has been cleaned up. 
You should now be able to start a new session.

Now you can connect to a new session of the RCE.

vncserver_once

vncserver_once

To start a new session on a VNC server, log in using an SSH utility and then type the command vncserver_once. For example:

> vncserver_once
3

In this example, a user created a new VNC session and the system assigned session number 3 to that user.

vncfinger

vncfinger

To find your session number on a VNC server, use the command vncfinger to list the active VNC sessions and the username that owns each session. For example:

> vncfinger

Username VNC Session
dho 4
eray 3
hstoll 2
olau 5
svanderh 1

ps

ps

To find your session number on a non-VNC server, use the command ps as follows:

> ps -fu `whoami` | grep Xvnc

user 24904 1 0 Jul19 ? 00:00:00 Xvnc :1 â€“desktop login.hmdc.harvard.edu:1X1

In this example, the session number is 1.

Alternate Connection Applications

Alternate Connection Applications

Examples and procedures in this guide use the SSH application SecureCRT, the SFTP application WinSCP, and the VNC application UltraVNC. You can use other VNC, SSH, and SFTP applications and utilities, but HMDC does not provide user support for these tools. Alternate applications include TightVNC, PuTTY, SecureFX, and scp.

TightVNC

TightVNC

TightVNC enables you to connect to a VNC session, and provides the viewer with which you use the RCE. It is available at the following URL:

http://www.tightvnc.com/download.html

PuTTY

PuTTY

PuTTY is a free implementation of Telnet and SSH that you can use to connect to the RCE. PuTTY is available at the following URL:

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

SecureFX

SecureFX

SecureFX is available from HMDC at the following URL:

http://www.fas-it.fas.harvard.edu/

The SecureFX application enables you to perform secure file transfers. You can use a licensed version of SecureFX in the HMDC computer labs. If you are a registered HMDC user logging in from a remote system, contact us to receive a licensed version of SecureFX. Anyone can download a 30-day trial version of the application, as described in the document Using SecureFX provided by the distributed computing environment (DCE) at Harvard University's Church Street Computer Facility. This document is available at the following URL:

http://lab.dce.harvard.edu/2003/docs/secure_ftp.pdf

Note: When transferring files between environments, be sure to choose the Binary (non-text) transfer type for formatted data or image files to prevent corruption or loss of data.

SCP

SCP

The scp application is a secure copy utility provided in UNIX and Linux distributions. To transfer files in the CLI by using the scp utility, open a terminal window on your local workstation and type the following:

To transfer a file from your local workstation to the RCE, type:

>scp <file name> <Hostname>: 
<username@Hostname>'s password: <login account password>

To transfer a file from the RCE to your local workstation, type the following command. You must include a space followed by a period at the end of the command. The period indicates the current directory on your local machine.
```
>scp <Hostname>:<file name> .
<username@Hostname>'s password: <login account password>
```

HMDC Easy Connection Script

HMDC Easy Connection Script

The HMDC Easy Connection Script is a bundled set of scripts and applications that enable you to connect to the RCE quickly, easily, and securely from your Windows computer.

To download the script, please click the following link:
HMDC_VNC.EXE

After you download this script, double-click the file to run it. You see the files shown in the following figure.