Remote Desktop under different network

No, you need to forward port 3389 to your computer. Here's what I mean: let's say I have 2 computers in my network, and I use RD for both. I could tell my router to forward port 3333 to one computer, and 3389 to the other. I would need to instruct the router to change 3333 to 3389 after it's forwarded.

Say my IP address is 66.67.111.111. Outside my network, to access computer 1, I would enter 66.67.111.111:3333.

To access computer 2: 66.67.111.111:3389

If you leave off the port, it automatically sends out the request on port 3389.

Actually...that's half right...or half way there I should say.
The computer that is using port 3333 on the router would have the change the registry entry to listen for RDP traffic on port 3333...or the traffic wouldn't get to it. Even though you told the router to forward to a specific IP inside your LAN...RDP by default will listen to port 3389 on the computer.
This is how you change the listening port for RDP:
How to change the listening port for Remote Desktop

I sat there playing with a RDP app for my iPod for half an hour before I realized my brain fart...

dajogejr said:

Actually...that's half right...or half way there I should say.
The computer that is using port 3333 on the router would have the change the registry entry to listen for RDP traffic on port 3333...or the traffic wouldn't get to it. Even though you told the router to forward to a specific IP inside your LAN...RDP by default will listen to port 3389 on the computer.
This is how you change the listening port for RDP:
How to change the listening port for Remote Desktop

I sat there playing with a RDP app for my iPod for half an hour before I realized my brain fart...

You could always have the router change 3333 to 3389 before it sends it to the computer.

Too much work, IMO...
Here's a screen shot of what I mean, my setup in my router.
Not all routers may support that...either.

It's a bit easier with mine:

Very nice post...
I just have my ATT provided router/modem...no need for anything fancy...and I don't have a public/private programming option.
At work, I would program a Cisco PIX or ASA device to do what you're talking about...obviously a lot more options and keeps from having to customize and put your hands on PCs, when you can do it with hardware.
Central administration is the name of the game!!
If the user doesn't have the ability to port map inside/outside interfaces...he'll have to do my way.
If he does...go your way...:)

Good info JK.