How To Add Hummingbird Secure Shell To Your Workstation
Last Modified: March 26, 2013
This document is also available on the WEB at
http://jilawww.colorado.edu/~software/installs/secureconnectivity.htm
[NOTE: Notation below referring to the “N:” drive means the samba drive served from node jilau1. Check your drive mappings and change the N: drive if necessary to be
\\jilau1\apps
]
Preliminary:
You MUST be logged in as the local machine Administrator in order to install for All Users. Notation throughout this document refers to x.x or xx, this implies the most recent version of the software.
Secure Shell requires that you install a version that matches your installed copy of Exceed. If you have an earlier version, stop now and install the most recent version of Exceed. Please see
http://jilawww.colorado.edu/~software/installs/exceedxx.htm
for instructions. Then return here and install the matching version of Exceed Secure Shell
NOTE Connections via the Secure Shell SSH protocol will be slower that without. Most of this will be seen on the initial connection but graphics displays may also appear a bit slower.
This program will provide Secure Shell connectivity with Exceed between your computer and the host. If you are mostly connecting to servers within our JILA subnets this is probably not really necessary. However, if for example you want to use Exceed on a laptop away from JILA then this program is strongly suggested.
Workstation Installation:
Each workstation must do a local installation of Secure Shell. Just run the program
N:\Win\ExceedxxSecureShell\Msetup.exe
where ‘xx’ is the numeric part of the most recent version. Select the “Install Open Text Secure Shell” and then the “Personal Install” and “English” language options.
The process is
- Splash screen (Next)
- The installer will detect that you have an existing version of Secure Shell and prompt with a check box to migrate your settings and replace your existing version. It is not necessary to do an uninstall later. (However, after the install, remember to delete any previous desktop icons you may have made and replace them with the new ones.)
- License screen - We have a 10 seat site license. Click the Radio button for Accept (Next)
- Customer Info - For our site license this information should be
Name: JILA Software Manager
Company: JILA, University of Colorado
(Next)
- Destination Folder - accept (Next)
- User Directory - Select the Per-User radio button. Click Next.
- Setup Type - Radio button for Typical (Next)
- Additional - nothing is needed here.
- Ready screen - (Install)
The installer will whirl for a while with various status thermometers. This may take a while, be patient, it is also doing the uninstall of the previous version.
- Complete screen - (Finish)
You may be requested to reboot, do so if asked. The reboot will do some more installation steps, so again be patient.
Updates and Patches:
Once the install is complete you need to check for any patches or updates. Your initial installation of Exceed and Secure Shell will be at Level-0 and it is necessary to patch them to the most recent level. This can be done by using your Internet browser and going to
http://support.hummingbird.com/customer/
to access the Hummingbird web site and get the latest patches. This site will require you to create a login account, do so and save the information for future use. You can get downloaded patches and generate service requests from this site. These patches will apply to both Exceed and Secure Shell.
Using the SSH connection with Exceed:
You can not use any of the XDM type connections with SSH since they do not use the TCP/IP protocol. Therefore you must use the XStart and XSession tools to make your connection to a host. It is not necessary to make your own, I have created some template XStart items that may be copied and modified. They are located in
N:\Win\ExceedxxSecureShell\Xstart-Samples\
and are of the form “jilau1-ssh.xs”. You may also want to read the file “Xstart-SSH-ReadMe.html” to see the different types of command lines needed for various platforms. I have placed samples there for Linux and VMS. You may just drag and drop these files to your local area and it will show up in your XSession list by default. The locations to drag and drop are
- NT/Win2000/XP - (you may have to hunt a bit depending on your OS). First try
c:\Documents and Settings\UserNameHere\Application data\Hummingbird\Connectivity\xx.xx\Exceed
or an alternate is
c:\Documents and Settings\UsernameHere\Application Data\Hummingbird\Connectivity\XX.xx\Profile
To make additional .xs files to other hosts, start one of the example .xs files, modify the Host name and if necessary the Host Method and Description. Then save it out with a different name. This too will then show in your XSession chooser list.
To run:
- Start XSession. You should see it in the Available Program list of all the XStart items that were made. If they are not showing in the initial screen you may need to click on the Add button and include them. If they don’t show from the Add button, then they may need to be moved to one of the other locations mentioned in that step above on saving the .xs files.
- Select one and double click on it to begin the XStart session.
- Click on the Run! menu item to start the program and fill in your User ID and Password and click OK.
- On the first connection to any new host you will get a message that says something about the secure key for that host. Save the host key and won’t ask again in the future.
- Exceed will open up and connect to the desired host. Notice that if you normally use Exceed with an XDMCP Broadcast type connection, this chooser window will pop up too. Just click the “Passive” button to close the chooser window.
You may either just use a desktop shortcut to XSession to display a chooser list of all the .xs files that you made, or you may drag and drop shortcuts to your desktop that point directly to the individual .xs files themselves.
Firewall Issues:
You may need to make an exception in your machine firewall. You will need to allow the executable of
“C:\Program Files\Hummingbird\Connectivity\XX.xx\Security\HumShSrv.exe”
and allow
TCP In and Out for local ports 6000 and 22
TCP Out for remote port 22
In a granular firewall like Outpost you can make one Application rule for the executable and then add in the rules for the ports. In Windows Firewall you will need to make one Program rule for the executable and separate Port rules for anyone that wants to use them.