Solve a Remote Desktop Client port forwarding problem

Apr 22, '05 10:17:00AM

Contributed by: Anonymous

I recently ran into a port forwarding problem when trying to use Remote Desktop Client (RDC) on my home LAN. I originally used RDC locally (behind my router) to check on my XP machine quickly from across the house. With a laptop and Airport, it is a great way to be lazy. I also had a need to check on the XP machine over the internet, so I started using a dynamic IP service, and forwarded the default RDC port (3389) from my router to the XP machine. However, the port forwarding stops any communication between local machines using the default port, and my lazy log ins were stopped.

My solution was to forward port 3388 (can be anything) from the router to 3389 (default RDC port) on the XP machine, and connect two different ways using the RDC client.

A remote connection uses the dynamic IP address name and the 3388 port, using a colon to use an alternative port, as mentioned in a previous hint (ex. yourdnsname.org:3388). This is then forwarded to the default port on the XP machine, and everything is great. A local connection file uses the internal address of the XP machine to connect 192.168.xxx.xxx using the default port, which now does not need to be forwarded.

Using the RDC application, you can save these addresses and your connection settings, making it easy to connect locally and remotely, without having to worry about port forwarding problems!

Comments (7)


Mac OS X Hints
http://hints.macworld.com/article.php?story=20050420221431745