|
CHAPTER
FOUR - TELNET ACCESS
Telnet Access is only
available using SSH.
Telnet Access has been
restricted to experienced Telnet Users ONLY. Due to the amount of
server problems encountered from users with limited experience using
Telnet, we now request that all users wishing to gain access using
Telnet, contact Technical Support to
have SSH activated.
Any user requesting
such access assures AMS that they are an experienced Telnet user. In
the event that such user causes any server crashes/damages, their
Telnet Access Priveledges will be revoked and denied for any future
Telnet use.
If you need telnet
access to our servers, it can only be done using SSH. We have it set
up to use RSA authentication. You will need to create a key using
your PC's SSH software, then use this feature to upload the key to
our servers. Once it is uploaded, you will be able to connect to our
servers using SSH. We do not provide an SSH program for your use.
However, as a suggestion only, you can visit http://www.vandyke.com/ and
download their SecureCRT software. This software is available as a
30 day trial and afterwards must be purchased. Below we have
provided instructions on setting up the software.
SETTING UP
SECURECRT: Each time you run SecureCRT the following box will
appear on your screen. Ensure that the Session List tab is
selected and then click on the New button on the right hand side.
This will create the session that you will use each time you telnet
into your account.

Following is a screen
shot of the next screen you will see. (Instructions for this area
follow this screen shot.)

NAME - In the text box
next to Name, input a name that SecureCRT can use to identify this
session that you are creating.
PROTOCOL - Select SSH from the
drop down box.
As soon as you select SSH, additional boxes
will appear below that selection as follows.

Connect via firewall -
Leave this box unchecked.
HOST NAME OR IP - Enter your domain
name or ip number in this text box. (ie. yourdomain.com)
PORT
- Leave the default number that is there.
USERNAME - this is
the username that you use to FTP to your account.
CIPHER -
Select 3DES
AUTHENTICATION - Select Password from the drop
down box.
PASSWORD - This is the password for your account,
the same one you use to FTP to your account.
Next you will
need to click the Advanced button as indicated in the screen shot
below. Be sure to hit the Advance button and not the Advance
tab.

In the next screen
(Advanced SSH) the Use Global radio button is selected by default,
and the text box directly beneath that will automatically be filled
in with a file location.
Next locate and click
on the Create Identity File button as indicated in the screen shot
below. (Everything else on that screen should remain as
is.)

The next step will
generate the key that will identify to your sessions. This key will
be uploaded the first time that you Telnet to your account. Click on
Next as indicated in the screen shot.

In the next screen you
are asked to insert a Passphrase, by providing this passphrase your
key will be encrypted. Next you are asked to Confirm that passphrase
just as you are when you provide a password. Once you've provided
this information, click on Next as indicated in the screen shot
below.

In the next screen you
are asked for a length for your RSA pair, just accept the default
and click Next as indicated in the screen shot below.

In the next screen your
key is actually generated, move your mouse around until the status
bars are complete and then click on Next as indicated in the screen
shot below.

In the next screen you
are prompted for a location in which to save your Key and Key Pair,
you can accept the default, however if you want this information
saved in a different location be sure to write down the location as
it will be needed when you Telnet to your account the first time.
Also, you should save both files in the same location. Click on the
Finish button as indicated below when you have selected the
location.

You are now returned to
the Advanced SSH window, just click on the OK button at the bottom
of that window to close that screen, as which point you are returned
to the Session Preferences Window, again click on the OK button at
the bottom of that window to close that screen.
Install the key in the SSH section of
your control panel. In the space provided, copy and paste your
public (RSA) key from your software (this insures the key is exactly
as it appears in your software).
Note: You will also be asked to enter
your access addresses, which are the IPs or host names from which
you will be accessing the server. If you do not know your access
address(es), contact your ISP for the information. If your
address(es) is not static follow the examples below:
Example 1: ISP tells you that your IP
ranges from 209.239.4.1 through 209.239.4.30 (this means that each
time you log on, your IP address could be any number between these).
You should enter the address as 209.239.4.* (the * is a “wild card”
and can take the place of any digits.)
Example 2: ISP tells you that your
host name will either be home.name.you.aol.com or
home.name.me.aol.com. You should enter the address as *.aol.com (In
this case the * replaces anything that may come before
.aol.com).
Once addresses are listed, submit the
request. This generally takes about 10 minutes, then you will be
able to test it.
You are now ready to
Telnet to your account by clicking on File and then on Connect or
you can click on the Connect icon (3rd icon from the left).
When you have
successfully connected to your account, you will be prompted to save
the key that you just generated. Follow the instructions on your
screen and once you've done this you are ready to work within your
account. From here it's just like a normal Telnet
session.
If you receive a Remote
Site Disconnected message, don't be alarmed. Keep attempting to
connect.
Any
user requesting such access assures AMS that they are an experienced
Telnet user. In the event that such user causes any server
crashes/damages, their Telnet Access Priveledges will be revoked and
denied for any future Telnet use.
©Copyright
1998 AMS. All Rights Reserved. The entire contents of this site
is copyrighted and may not be reproduced for any purpose without
prior written permission.
Please contact the
Webmaster for AMS with comments or broken link
information on this
site. |