Rank: Advanced Member
Groups: Member
Joined: 12/23/2007
Posts: 50
Points: 150
|
1. Run Regedit.exe on your Terminal Server.
2. Navigate to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Terminal Server\WinStations\RDP-Tcp
3. Export the entire key to a .REG file by selecting the key (click on it...) and going to File > Export.
4. Give it any name you want.
5. 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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Terminal Server\WinStations\RDP-Tcp-New
Lamer Note: Do not double-click on the .REG file, instead right-click it and choose Edit.
6. In the .REG file find
PortNumber
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).
7. 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.
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2007
Posts: 50
Points: 150
Location: Malaysia
|
Thanx for the info boss..
|
Rank: Advanced Member
Groups: Member
Joined: 12/25/2007
Posts: 51
Points: 153
Location: India
|
Good work really helpful for the admin people.
|
Rank: Advanced Member
Groups: Member
Joined: 12/25/2007
Posts: 50
Points: 150
Location: victoria
|
i am always so wary of playing around in reg settings but this seems to be pretty straight forward. Good info.
|