Remote Desktop Multiple Computers Behind Router

I have two computers running W7p that I want to access when I'm away from my office. I am able to use remote desktop from inside my home network on either computer. I am able to access one of the computers from outside with my router set to forward global port 3389 to host port 3389. I am guessing that what I need to do is set up two port forwards in my router; the global port will be different but the host port will still be 3389 in each case. Does that sound right? One thing I know is that going into the registry and changing the host port to something other than 3389 does nothing. In fact, if I do that I can no longer use remote desktop inside my home network. I've looked all over the web today and there are not any clear instructions on how to do this (that I could find). I read the W7 forum tutorial.

Ok, defining a second portforward using a different global port, but 3389 as the local port did not work. So now I've created a second portforward using 3389 for both the global and local port, but in this case I've enabled the portforward for a different host. This doesn't entirely make sense, so it'll probably work.

To make it way easier why not do away with Windows Remote desktop altogether.
Team Viewer is now regarded as the number one software for this purpose.

It bypasses all firewall and port rules and you wont need to set up anything other than
an install of the software on each machine. Basically, you would be able to
store the parter id's (office machines) and access them at will.

Check team viewer out here: TeamViewer - Free Remote Access and Remote Desktop Sharing over the Internet

I've also tried creating a new inbound rule in the Windows 7 firewall to redirect incoming on port xxxxx to 3389. This has no effect. Also, if I change the port assignment in the registry and then run netstat -a, I no longer see the 3389, but I do not see port xxxxx.

I finally got it to work by applying the patch you can find here:
Log into multiple RDP sessions and without interrupting user
and creating a firewall rule to allow a port other than 3389.

Glad to hear you got it sorted and good patch link by the way - :)