Use RDP Client to Connect to a Different Port

When working with Terminal Server or RDP and trying to connect using RDP to different port,you have the choice to change the XP RDP 5.1 or 5.2 client connecting port.

For the “old” Windows 2000 Terminal Server client port changes see Use Terminal Server Client to Connect to a Different Port.

If you’ve changed the listening port on the TS from its’ default – 3389 (Change Terminal Server Listening Port)- you’ll also need to configure your client to connect to the new port. Changing the connection port on the RDP clients is quite easy.

To Alter the Port on the client side:

1. Go to the Start menu and click on Run.
2. On the Run menu type MSTSC and click Enter.
3. In the RDP window, in the Computer box, scroll to the computer name or IP to which you wish to connect.
4. Add a “:Port” (without the quotes) where “Port” is the decimal value of the destination port.

5. Press Connect.

Another method of connecting to a different port that default is to run the MSTSC command with the required command line parameters:

/v:ServerName[:Port]

For example

to connect rdp to different port:

MSTSC /v:192.168.0.150:3390

Note: To use RDP on computers with operating systems other than Windows XP/2003 you will first need to install the RDP client (Download RDP 5.2).

FAQs

How can I troubleshoot connection issues when setting up RDP to different port numbers?

When configuring RDP to different port connections, verify firewall rules allow the new port, ensure the port isn’t used by other services, and test connectivity using telnet. If issues persist, check server logs and confirm both client and server are properly configured for the new RDP port.

What are the security benefits of changing RDP to different port settings?

Changing RDP to different port numbers than the default 3389 helps prevent automated attacks, reduces vulnerability to port scanners, and adds an extra layer of security through security-by-obscurity principles, making it harder for malicious actors to identify RDP services.

Can I set up multiple RDP to different port configurations on one server?

Yes, you can configure multiple RDP to different port settings on a single server using port forwarding rules, allowing different users or departments to connect through unique ports for better access management and security control.

What are the limitations when configuring RDP to different port numbers?

When setting up RDP to different port connections, consider that some firewalls may block non-standard ports, certain port numbers might be reserved by the system, and some legacy applications may not support custom RDP port configurations.

How do I backup my RDP to different port settings before making changes?

Before modifying RDP to different port configurations, export your current registry settings, document existing port assignments, and create a system restore point to ensure you can recover if issues arise during the port change process.

Related articles

You might also want to read the following related articles:

• Add a new RDP Listening Port to Terminal Server
• Change Terminal Server Listening Port
• Download RDP 5.2
• Download Remote Desktop Web Connection for XP SP1
• Enable Remote Desktop on Windows Server 2003
• Install Remote Desktop Web Connection on Windows XP
• Install Remote Desktop Web Connection on Windows Server 2003
• Offer Remote Assistance in Windows XP/2003
• Quickly Connect to Remote Computers
• Remotely Enable Remote Desktop on Windows Server 2003
• Securing RDP/Terminal Services Communications
• Use Terminal Server Client to Connect to a Different Port
• What’s Remote Desktop in Windows XP/2003?
• What’s Remote Assistance in Windows XP/2003?
• How to Fix the “Remote Desktop Connection: An Internal Error Has Occurred” Error