How To Configure a Terminal Server

You can use a Terminal Server to perform many tasks. Users on the remote locations can run programs, save files and use network resources with the help of Terminal Server. If you install any program on the Terminal Server, then it is certain that all the users will utilize the same version of the installed program. If you configure a computer as a Terminal Server, then from this computer multiple users can access a program at the same time.

You do not have to install Terminal Server, in case you want to use this computer for remote administration on Windows Server 2003 operating systems. In this case, you can use Remote Desktop for Administration. Remote Desktop for Administration will provide you the facility to manage the servers remotely from any client over a LAN, WAN, or dial-up connection. This will happen after you enable the remote connections.

If you are completed the Configure Your Server Wizard, then you have to perform the following steps. You have to confirm about your Internet Explorer Enhanced Security Configuration settings. After this, you have to configure a Terminal Server License Server. You can install both the Terminal Server and Terminal Server Licensing service on the same physical computer, in case of small deployments. It is required that you should install Terminal Server Licensing on a separate computer, in case of large deployments. You have to install client access licenses (CALs) on the Terminal Server License Server.

It is required that you should configure Terminal Server Licensing correctly, so that your terminal server can continue to accept connections from the clients. Terminal Server Support offers a licensing grace period, during which no license server is needed. In this grace period, a terminal server can accept connections from unlicensed clients without contacting a license server. After you have completed both the Configure Your Server Wizard and these additional needed tasks, you will get a basic terminal server.

Alteration in Terminal Server's Listening Port

As I have described earlier about Application Server Security that is securing your Terminal Servers now will describe how to alter listening port of your Server.

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.

• You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:


• You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp.


• Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389.


• After this, you have to change the port number in Hex and save the new value

If you want to change the port for a particular connection on the Terminal Server, then follow these steps:

• You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection.


• After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389.


• Then you have to change the port number in Hex and save this new value.


• After performing this, you have to make alteration in the Port on the Client Side.

Follow these steps to perform this:

• You have to open Client Connection Manager.


• Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there.


• Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export.


• Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server.


• Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one.


• If it has the same name, then overwrite it.

In this way, you will receive a client that has the correct port settings to match your Terminal Server settings. Hope it will help you out, Don’t Forget to subscribe to my blog for more tips and tricks on server and Microsoft Server Support Services