|Updated: December 30, 2001
This article assumes that you have read and already setup the Terminal
Services Server. If you have not done this yet, please take a look
at this article: Terminal
Services Server Configuration.
We'll cover the standard
Terminal Services Client program here.
On your Terminal Services
Server, there is an icon labeled "Terminal Services Client Creator" which
creates disks that are used to install the Terminal Services Client program
on the computer you plan to use to remote administer the server.
You must install this client program on each computer you plan on using
to remote administer the server.
Double click on the "Terminal
Services Client Creator" icon. You will see the following screen.
You must choose which version of windows (16-bit or 32-bit) the client
disks should support. As a gross simplification, windows 3.1 is 16-bit
while windows 95 and later are 32-bit. The 16 bit version of the
Terminal Services Client requires 4 disks while the 32 bit version of TS
Client requires only 2 disks.
Choose which version of the
client you require and follow the directions. After you are done
making the Terminal Services Client disks, you can now install the TS Client
on any computer you will use to remotely administer your server.
1: The client computer that you use to remote administer your server can
be on the external WAN or the internal LAN. If you are using a LAN
computer to access Terminal Services on your server, then you do not need
to do anything with your router. However, if you are planning on
accessing Terminal Services from a computer across the Internet, you will
need to forward port 3389 to your server. This is very important
since Terminal Services listens on port 3389.
2: By default, Terminal Services Server and Client talk to each other over
port 3389. You can change this port number through a registry hack.
However, if you decide to change the port number, you must make the described
changes on the server and client side (the changes are different for the
server and client). Here is the how to do it: How
to Change Terminal Server's Port
Let's install the Terminal
Services Client on a computer that you will use to remote administer your
On a different computer (not
your server), insert the first TS Client floppy disk into your disk drive.
My Computer -> 3.5 Floppy
Drive (A:) -> Double Click on "Setup.exe".
Click on "Continue" at this
Click on "I Agree" at the
Here you can choose the directory
that the Terminal Services Client will be installed into. Once you
choose, click on the icon to begin installation.
You are prompted to choose
whether the Terminal Services will be installed for just the current user
or for everybody who uses this workstation. This is your choice.
If you work at a computer that many people have to log in separately, then
it would be best to only install it on your account. If you're the
only one who uses the computer, then the choice doesn't really matter.
Disk 1 installing..
Now it asks for Disk 2
Disk 2 installing..
Terminal Services Client
Setup was completed successfully. Click "OK"
Now under your Start -> Programs,
you'll have "Terminal Services Client"
Double Click on "Client Connection
Manager". This menu allows you to create new connections to Terminal
Click on the left most icon
to configure a connection to the server. You'll see this Wizard.
Under "Connection name" type
in a descriptive name such as "Server" or "Home Web Server".
Under "Server name or IP
address", type in the IP address of the Terminal Services Server.
If you're on a LAN, you can use the local IP numbers such as "192.168.1.xxx".
However, if you are on the WAN or Internet, you must type in your WAN IP
address since LAN IP numbers are not accessible from the WAN.
Since I'm so creative, I've
named my server simply "Server" and my local LAN IP address for the server
is 192.168.1.20. Fill in your own information, I'm just giving an
example. Click on "Next".
Here you have the option
for the TS Client to remember your password and log on automatically.
I strongly suggest that you do not enable this function. Do you want
people to log onto your server without your permission? I don't think
so. Click "Next".
Here you choose the size
of the screen that the client will run in. Note that depending on
how fast your DSL/Cable line is, the larger the screen, the slower the
connection between your client and server. You can experiment with
these settings until you get them to your liking. I personally like
800x600 in full screen mode. Once you make your choices, click "Next".
Here you can choose to enable
data compression or cache bitmaps. No matter what your DSL/Cable
connection speed is, both options are a good idea.
This next window allows you
to automatically start a program when you use your Terminal Services connection.
I left my setup blank. Click "Next"
Here you get to choose which
icon and program group your client connection goes into. Default
is fine. Click "Next".
This screen tells you you're
done. Click "Finish".
Now when you go back to your
"Client Connection Manager", you'll see the icon for your connection.
All you have to do to connect to the Terminal Services Server is double
click on the icon. To make your life easier, you can make a shortcut
to your connection and put it on your desktop.
If you ever want to change
the settings of the connection you just configured, all you have to do
is right click on the icon and select "Properties".
You'll see 3 tabs that allow
you to control all the settings we just configured.
Let's go back to the "Terminal
Services Client" program group and double click on the "Terminal Services
Client" icon. This is another way to connect to your Terminal Services
Server. This client browses your network and looks for Terminal Services
Servers. Depending on your setup, you may or may not be able to connect
through this method. The "Client Connection Manager" is the better
way to go.
Once you connect to you server
through Terminal Services, you have full control over the server.
However, the desktop you see is not exactly the one that is open on the
server itself. The Terminal Services logs in separately, so technically,
it is a different session. However, everything you do in the Terminal
Services session will be executed on the server.
Once you are done working
with terminal services, how do you get out?
Go to "Start -> Shut Down".
You'll see four options.
||This shuts down all applications
and terminates your Terminal Services session.
||This physically shuts down
the computer and does not give you a way to restart the computer.
||This physically restarts
the computer and in the process breaks your Terminal Services connection.
However, you will be able to reconnect once the server reboots.
||This is like logging off,
but leaves your applications and open so you can reconnect and pick up
work where you left off.
For most purposes, "Log off"
and "Disconnect" will be your best choices. I personally like "Disconnect".
Next step: Terminal Services
Advanced Client Configuration (Web Client)