Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

How do I connect from Windows 2003 server to a dedicated host using terminal server

I am feeling dumb asking this question, but I have only used Remote Desktop in the past to connect to local computers on a local network.

How would I, using Terminal Services, connect to another dedicated server on the internet when the port they give me is different that the normal connection.

example: (not real Ip or info, for demo purposes only)

domain: somedomain.com
IP: 69.4.56.83
Gateway: 69.4.56.1
Server login ID: administrator
password: somepassword

Instructions: To Access your Server you will have to use Terminal Server or, https:69.4.56.83:8098


Thanks in advance for your help.
0
Canamshopping
Asked:
Canamshopping
1 Solution
 
pcmagic2004Commented:
I think you can change the listening port for terminal services. I'm not sure if thats what you asking but I will post the info here anyway

By default Terminal Server and Windows 2000 Terminal Services uses TCP port 3389 for client connections. Microsoft does not recommend that this value be changed. However, if it becomes necessary to change this port, follow these instructions.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To change the default port for all new connections created on the Terminal Server: 1. Run Regedt32 and go to this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
NOTE: The above registry key is one path; it has been wrapped for readability.

 
2. 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\connection
NOTE: The above registry key is one path; it has been wrapped for readability.
 
3. 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
1. Open Client Connection Manager.
2. 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.
3. Making sure that the new connection is highlighted, on the File menu, click Export. Save it as name.cns.
4. Edit the .cns file using Notepad changing "Server Port=3389" to "Server Port=xxxx" where xxxx is the new port that you specified on Terminal Server.
5. 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 this cannot be changed. The Remote Desktop Protocol (RDP) client that is available in Microsoft Windows XP and Windows .NET (version 5.1 and later) has this ability.
NOTE: You must restart the Terminal Server before the new listening port becomes active, or recreate the RDP listener via Terminal Services configuration.

--------------------------------------------------------------------------------
0
 
WeHeCommented:
To Alter the RDP 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 name.cns.
Edit the .cns file using Notepad changing "Server Port=3389" to "Server Port=xxxx" where xxxx 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 this cannot be changed. The Remote Desktop Protocol (RDP) client that is available in Microsoft Windows XP has this ability.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now