Connect to your new server via the secure shell protocol
(commonly known as SSH) using one of these provided IP addresses. In the
following examples, an arbitrary private IP address (192.168.224.109)
the user name brucelee
is used instead. Replace this private IP address
with your actual public server IP and the user name supplied by your hosting provider.
To establish a connection with your dedicated server, you will need to have a valid
Linux user name (for example, brucelee), appropriate password, and a tool supporting
the secure shell (SSH) protocol such as Putty. If you are using Linux already, just
open a terminal window and type in the following from the command prompt.
The secure shell may issue a warning regarding your supplied IP address as following,
just type yes to proceed to enter the required password.
$ ssh firstname.lastname@example.org
The authenticity of host '192.168.224.109 (192.168.224.109)' can't be established.
RSA key fingerprint is a1:f7:f1:44:ae:9b:c3:47:94:f1:f9:c5:c4:8f:6b:19.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.224.109' (RSA) to the list of known hosts.
If you are on Windows (2000/XP/Vista), you will need to install and configure your client
SSH session (see the package Putty) to get to the login prompt.
Launch Putty from your Windows desktop. The above screenshot shows how to connect to
your dedicated server via the secure shell protocol SSH by supplying some basic parameters.
Hostname (or IP address)
. You need to enter the IP address of your dedicated server here.
Once the server is actually deployed and its domain name is resolved correctly to this IP address,
you can then supply the domain name instead. The safest bet is always using the IP address instead
of the domain name. Enter a name in the 'Saved Sessions' and click 'Save' to save your session data.
If you have more than one servers to manage, you should assign a unique session name for each server.
You can leave all other parameters at their default settings. The above screenshot shows how to
customize the appearance of your session by choosing an appropriate display font via the Change...
button (at the cursor position). Remember to save your changed settings by clicking on the Session node
and save to the appropriate session names.
The very first time you log in your dedicated server, Putty does not yet have the correct key from the server
and may display a warning that the server's host key does not match the one that Putty has cached in the
registry. Click Yes to update the Putty's cache and continue connecting. Once you see the terminal window
with the login prompt (usually a $ symbol following the user name and the server IP address in a pair of
square brackets), the remaining administration procedures are identical to a Linux terminal window.
This means that your dedicated server is alive and responding. The connection to your server is
established securely via the secure shell protocol and is awaiting commands from your remote shell.
You need to enter the initial login user name supplied by your hosting provider (brucelee,
in this example). If the login name is correct, your dedicated server will prompt for a
corresponding password. Be careful when entering the password since a mistyping will cause
the error message 'Access denied'
If both the login name and password are entered correctly, a login or shell prompt appears
as shown in the above screenshot. Note that the shell name consists of the login name
following by the @ sign and the server's IP address.