Windows 2003 + Term Serv + Disjoint Networks

Hello,

Hopefully someone can give me an idea on how to resolve this. I have a Windows 2003 Standard edition server with two network cards. One is addressed for my WAN and used for Terminal Services within the organization. The other is addressed for a backup internet connection and used for outside access, but I am running into the "disjoint network" issue, and unless the WAN interface is disabled, I can't access the server via its external (Internet side) IP Address. For reasons too complicated to explain, I have two internet connections on different providers and one is inaccessible through the firewall, so the only access to the network (on the WAN IP range) is through the backup internet provider on a different subnet.

Is there any way to adjust the server itself to route traffic so that they can come in on NIC B (backup internet side) and access the network on NIC A (WAN side), all the while allowing people on my WAN to still come in on NIC A, all into terminal services on this same machine?

Any help (especially step by step) would be great.

Thanks.

 

It should be simple enough to set things to do what you want. However, I'd like to be more comfortable that I know what your setup is like so the suggestions fit the situation.

- NIC-A & NIC-B are on different subnets?
- NIC-A & NIC-B are on different physical networks?
- How, exactly, do you get to NIC-B from the outside?
- Domain or workgroup? If domain, AD or classic NT?
- Any physical routers in place?
- You want users on the LAN connecting to NIC-A to see only the server but users coming in on NIC-B to be able to get out via NIC-A (to that network)?