Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Solve a Remote Desktop Client port forwarding problem Apps
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. 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 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!
  • Currently 3.67 / 5
  You rated: 5 / 5 (3 votes cast)

Solve a Remote Desktop Client port forwarding problem | 7 comments | Create New Account
Click here to return to the 'Solve a Remote Desktop Client port forwarding problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Solve a Remote Desktop Client port forwarding problem
Authored by: Brian Hagemann on Apr 22, '05 11:41:49AM

Seeing this hint actually prompted me to register after 2 years of just reading the site! :)

Just to add my experience... this issue drove me CRAZY a year ago. I host my vanity website internally at home and was developing in Apache, mySQL and using MoveableType at the time. I experienced the same issue that when i turned on port forwarding (80) to point to my desktop, people outside my network could get into the site and MT worked fine, but I could no longer do testing internally. Using the local ip was of no help because of some issue with virtual domains in apache and the relationship with MT... the site would just break or parts would misbehave because they were expecting the referring URL to include the 'real' domain "" not an IP address.

Because I had the need to plug in an ethernet printer for home use, I replaced the Airport with a 4port Linksys WRTg router. To my surprise the problem completely disappeared. NOW i can get to the website and blog via from inside OR outside the house. At my office I have a dLink router. Similar need here for port mapping for incoming requests but need to do internal testing of same service. Works FINE.

My conclusion was that the Airport isn't routing properly. Now I don't claim to know the details of routers and how they 'actually' work... but I do know that the Airport was unable to handle this situation and two different other routers work as I would have expected. BTW I had the same problem on both an original Airport and a newer Airport Extreme BS.

[ Reply to This | # ]
Solve a Remote Desktop Client port forwarding problem
Authored by: mkutny on Apr 22, '05 11:48:07AM

I experienced something similar with an older D-Link router I had (although my newer routers - both D-Link and Linksys - haven't exhibited this). It wouldn't let you "loop back" to the external IP (nor its dynamic DNS entry). I did find that some simple entries to the hosts file took care of this (pointing the domain to my internal address), but I had to comment them out on my laptop when I was on the road (otherwise the would be looking for an IP on the LAN). Apache was listening on its local IP, so whether a request came via the router or directly on the LAN, it still worked as long as the host header was "".

One last note: you can allow Apache to handle multiple IPs for individual and multiple sites, using virtual directories and hosts. It involves some more entires to add to the httpd.conf, but it will work.

[ Reply to This | # ]
Solve a Remote Desktop Client port forwarding problem
Authored by: RiotNrrrd on Apr 23, '05 04:33:24AM

<pedant>It's actually Remote Desktop Connection.</pedant>

[ Reply to This | # ]
Never seen this problem
Authored by: kramrm on Apr 24, '05 11:52:56AM

I don't use AirPort stations as routers that often. I mostly connect to AirPorts as access points (no routing) or use Linksys or Netgear wireless routers. I've never had the problem mentioned in the original post.

[ Reply to This | # ]
Solve a Remote Desktop Client port forwarding problem
Authored by: macstibs on Apr 25, '05 12:09:52AM

When using RDC remotely, you should really tunnel the connection. Both OS X and Windows XP allow you to configure this.

[ Reply to This | # ]
Solve a Remote Desktop Client port forwarding problem
Authored by: macfly on Apr 26, '05 10:10:28AM

Hi macstibs,

Can you please explain in short steps how to do best the tunneling you are mentioning. Thanks in advance.

[ Reply to This | # ]
Solve a Remote Desktop Client port forwarding problem
Authored by: interfuse on Jun 06, '05 07:57:57AM

Hi there,

thanks for your Hint. It's exactly what I was looking for.

How ever, my Netgear RP114 Internet Router doesn't seem to let me port forward onto a different port. ie; port 3380 to 3389, it only enables me to forward ports onto the same port, but specify a machine ip.

Is there a way I can forward the port over the 3389 when it gets to my XP Machine?

ie; the router sends request to XP machine with port 3380, and the XP will then forward taht onto 3389 for RDC connection....

The Netgear RP114 only says, START PORT / END PORT / SERVER IP ADDRESS

Thanks again.

[ Reply to This | # ]