Question : Need explanation on static IP's, port forwarding to multiple machines, and how to set up my network

I currently have a static IP via business class DSL.  I have a Motorola DSL modem connected to Linksys VPN wireless router, and then 2 gigabit switches.

The router has 1 of my 5 static IP's on the internet.

Behind that I have multiple machines including 2 Win2K8 servers.  One is our business server which I run Terminal Services off of so we can run Quickbooks for on site billing.

The other server is a test server which also runs TS, and a few other applications that I use to demo with.  I have both servers set static on the local LAN.  

To switch between them before I was going into the router remotely and changing the port forward from 1 ip to the other but now I want to be able to access both, at the same time.

I added a A record that points to my static IP, remote.xxxxxxx.xxx.  

How do I set this up so that I can access either box from the internet?  If the router itself has a static IP, how can I assign the box beyond the router one of my other 4 static IP's?  How will it route?

I've thought of changing the ports on each so RDP protocol on 1 port would be through 1 box, and another port on the other but since this is for demo'ing I don't want to reconfigure client machines to try out the demo server.

I understand how the router works, the confusion comes in on how does 1 static IP route through another?  If my static IP's are:

99.255.255.1
99.255.255.2
99.255.255.3
99.255.255.4
99.255.255.5

And the .1 is my main IP assigned to the router, how can I assign one of the Win2K8 boxes the .2 address, how would it know to route there?

What I'd really like is to add another A record with test.xxxxxx.xxx so people can resolve to a domain name but again if I point it to one of my other 4 available address, how do I configure the router?

Thanks

Answer : Need explanation on static IP's, port forwarding to multiple machines, and how to set up my network

From an earlier post of mine:
Connecting to multiple computers or servers, on the same network, from a remote location, using Windows Remote Desktop.

There are several ways to accomplish this. Method 1 allows multiple users to connect to multiple PCs or servers for various reasons. The other 3 methods are intended for management purposes.

Should you be using Small Business Server, none of this is necessary as you can make use of the built-in Remote Web Workplace service which works extremely well, and is very easy to set up. Option #4 is also integrated with a default install of SBS.

Method 1:
This will not work if the server has 2 network adapters, one external and one internal, and the other PC's and servers are behind the server.

Depending on your router you may have 2 options.
1) Some routers when configuring port forwarding allow you to map an external port to an internal port. So you could map a different external port for each PC or server to the appropriate device and port 3389. For example:
  Computer #1: on the router forward port 3389 to port 3389 on IP 192.168.0.101
  Computer #2: on the router forward port 3391 to port 3389 on IP 192.168.0.102
  Computer #3: on the router forward port 3393 to port 3389 on IP 192.168.0.103
  Computer #4: on the router forward port 3395 to port 3389 on IP 192.168.0.104
When connecting from the remote site in the connection window of the remote desktop connection manager you would enter the WAN IP and the port #, separated by a colon such as:
  66.66.123.123:3391

2) If the router doesn't allow mapping external to internal ports, then you still assign each computer a different external port, but map that directly to the appropriate PC or server. However, in this case you have to change the listening port on each computer or server. Instructions on changing the listening port can be found at:
http://www.petri.co.il/change_terminal_server_listening_port.htm
Though the router in this case does not show external and internal ports, it changes the mapping to effectively be:
  Computer #1: on the router forward port 3389 to port 3389 on IP 192.168.0.101
  Computer #2: on the router forward port 3391 to port 3391 on IP 192.168.0.102
  Computer #3: on the router forward port 3393 to port 3393 on IP 192.168.0.103
  Computer #4: on the router forward port 3395 to port 3395 on IP 192.168.0.104
Again when connecting from the remote site, in the connection window of the remote desktop connection manager you would enter the WAN IP and the port #, separated by a colon such as:
  66.66.123.123:3391

Method 2:
If you simply want to access multiple PC's or servers for management purposes, you can connect to the computer for which you have already set up port forwarding and remote desktop. Then, once connected, establish a connection from that computer to another computer on the same network using another remote desktop session within that window. In effect you are running a remote desktop session within a remote desktop session. As odd as it sounds it actually works very well.

Method 3:
Again if you are doing this for management purposes only, you can log onto a single PC or server using a typical Remote desktop connection and port forwarding, but on that unit install the Server 2003 Adminpak. This includes a "snap-in" management console that allows you to create and save connections for some or all of your devices. You can connect to one device or switch back an forth in the console window to different PC'sa and servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&displaylang=en#AdditionalInfo

Method 4:
Much the same as #3, however using a different tool; there is an Active directory add-on called rControlAD which adds a right click option on the context menu for any computer listed in Active Directory Users and Computers, such that you just right click on the computer name and choose "Remote Control".
http://www.microsoft.com/downloads/details.aspx?FamilyID=0A91D2E7-7594-4ABB-8239-7A7ECA6A6CB1&displaylang=en

Method 5:
Onlu available with Server 2008, is you can enable Terminal Server Gateway services, that allows a web portal to all PC's/Servers usinng a secure connection over SSL (port 443)