Coming Soon: GET:IT Endpoint Management 1-Day Conference on September 28th at 9:30 AM ET Coming Soon: GET:IT Endpoint Management 1-Day Conference on September 28th at 9:30 AM ET

How can I add a new RDP listening port to Windows 2000/2003 Terminal Server?

You cannot add a new listening port to your Terminal Server via the GUI (Terminal Server Configuration in Administrative Tools) because there is no option for changing the listening port via the GUI.

What you need to do is create the new RDP listening port via the registry.

This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.
  1. Run Regedit.exe on your Terminal Server.
  2. Navigate to the following key:
  1. Export the entire key to a .REG file by selecting the key (click on it...) and going to File > Export.
  1. Give it any name you want.
  2. Edit the .REG file you've just created and change the name of the key at the 3rd line of the file to something like:
Lamer Note: Do not double-click on the .REG file, instead right-click it and choose Edit.
  1. In the .REG file find


and change it to whatever port you want. Make sure you write it in hexadecimal format. For example, for 3390 you must enter D3E (use calculator in scientific mode to easily convert decimal to hexadecimal format).

Sponsored Content

Say Goodbye to Traditional PC Lifecycle Management

Traditional IT tools, including Microsoft SCCM, Ghost Solution Suite, and KACE, often require considerable custom configurations by T3 technicians (an expensive and often elusive IT resource) to enable management of a hybrid onsite + remote workforce. In many cases, even with the best resources, organizations are finding that these on-premise tools simply cannot support remote endpoints consistently and reliably due to infrastructure limitations.

  1. Import the .REG file back to the registry by double-clicking on it, and bingo!!!

You can now connect to the new port by using the “old” Windows 2000 Terminal Server client. A better option is to use the RDP client found in Windows XP, or even better, the newer Windows Server 2003 SP1 RDP 5.2 client (Download RDP 5.2).

You’ll need to configure your TS client to connect to the new port. Although changing the connection port on the RDP clients is quite easy, you CAN also change the connection port for the TS client. See Related Articles list for more info.

Related articles

You might also want to read the following related articles:

Related Topics:

Live Webinar: Active Directory Security: What Needs Immediate Priority!Live on Tuesday, October 12th at 1 PM ET

Attacks on Active Directory are at an all-time high. Companies that are not taking heed are being punished, both monetarily and with loss of production.

In this webinar, you will learn:

  • How to prioritize vulnerability management
  • What attackers are leveraging to breach organizations
  • Where Active Directory security needs immediate attention
  • Overall strategy to secure your environment and keep it secured

Sponsored by: