|
|
|
|
|
Changing Terminal Server's listening port
To change the default port for all new connections created on the Terminal
Server:
- Run Regedt32 and go to this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp
- Find the "PortNumber" subkey and notice the value of 00000D3D, hex for
(3389). Modify the port number in Hex and save the new value.
To change
the port for a specific connection on the Terminal Server:
- Run Regedt32 and go to this key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal
Server\WinStations\
- Find the "PortNumber" subkey and notice the value of 00000D3D, hex for
(3389). Modify the port number in Hex and save the new
value.
NOTE: Because the use of alternate ports has not
been fully implemented for Terminal Server 4.0, support will be provided as
"reasonable effort" only, and Microsoft may require you to set the port back to
3389, if any problems occur.
To Alter the Port on the Client Side
- Open Client Connection Manager.
- On the File menu, click New Connection,
and then create the new connection. After running the wizard, you should have a
new connection listed there.
- Making sure that the new connection is highlighted, on the
File menu, click Export. Save it as .cns.
- Edit the .cns file using Notepad changing "Server Port=3389" to "Server
Port=" where is the new port that you specified on Terminal Server.
- Now import the file back into Client Connection Manager. You may be prompted
to overwrite the current one, if it has the same name. Go ahead and overwrite
it. You now have a client that has the correct port settings to match your
change Terminal Server settings.
NOTE: The Terminal
Server ActiveX client listens on TCP port 3389 and cannot be
changed, that is at least Microsoft wants us to believe. Here's how you do it:
The old (first) ActiveX client:
Use MsTsc.AdvancedSettings2.RDPPort in connect.asp (after the entries starting with MsTsc.AdvancedSettings2.)
The second ActiveX client (after a serious security update)
Use MsRdpClient.AdvancedSettings2.RDPPort in default.htm (after the entries starting with MsRdpClient.AdvancedSettings2.)
NOTE: You must restart the Terminal Server
before the new listening port becomes active, or recreate the RDP listener via
Terminal Services configuration.
References:
How to Change Terminal Server's Listening Port
| Published: 3/07/2002 | Document Type: HOWTO |
| Last modified: 5/06/2006 | Target: Administrator |
| Visibility: Public | Language: English |
[top]
|
