Disjoint W2K3 Server Network with Term Services

Hello All,

This is driving me nuts, so hopefully someone has an answer. I have a Windows 2003 Standard Server. It has two network cards. Each card is on a different physical network (disjointed) with different subnets, from two different providers. NIC1 is intranet connected, NIC2 is Internet connected. The server is set up as part of a workgroup, not using AD (yet).

I would like Terminal Services Server, which is up and running on this machine, to accept connections from either network card. The problem is that when one is being used, if the second comes online, or a connection is initialized through it, the other goes down. If I adjust the settings for the network card, it complains about disjoint networks and them not working properly.

How can I make it so these will play nice the way they are. Do I need to do some special routing table work or something? If so, can you give me an idea of how?

Do I need to turn on Routing and Remote Acess and somehow set this server to forward all packets coming in on the Internet side (NIC2) to route to NIC1? I am really missing some small part here.

Thanks,

William Deniston

 

Follow-Up - getting closer...

Okay,

I managed to make the cards co-exist without complaints of a "disjoint network" simply by removing the gateway from NIC2 and adding a persistent static route to the gateway in the routing tables (thanks to a Microsoft doc for that one).

I can internally (from the NIC1 side) connect to either card with Terminal Services, however, externally it is as if the NIC2 interface isn't there. Do I need another route added in here somewhere? Any ideas?

The odd thing is I can ping the server and trace route to it just fine from the outside connection. And I definitely have the firewall turned completely off for testing purposes. Everything looks good, but no go.

Thanks.