Disjoint Networks, Routing and Terminal Services

[wdeniston]

Hello All,

I have a W2K3 Std Server with Terminal Services licenses. I also have two NICs in the machine. It is part of my local workgroup and NOT using AD. Currently NIC1 is hooked to my internal network. NIC2 is hooked to my secondary internet connection (I have two network connections). I want users to be able to connect to Terminal Services from either the outside world (NIC2) or the inside world (NIC1).

Here is the trick, they are disjoint networks. Both are on different subnets. with different gateways. Windows reports that it is a disjoint network when I edit the network properties for either NIC. It also says that the connections will be unrelyable, and it very much is. If one NIC has a connection and the other tries to connect, it either doesn't work at all, or it allows the login and disables the other NIC. I know it is very confused, and I am out of ideas.

Is there some way that I can set this up to work? Can this be accomplished through setting changes and use of the Routing and Remote Access features in W2K3 Server? If so, how?

If you have any ideas, please let me know.

Thanks in advance.

 

[wdeniston]

Okay, I managed to stop the error message from Windows of this being a disjoint network simply by removing the gateway entry for NIC2, and adding a route to the router for that interface. However, the outside world still can't get to that machine. I am not sure what is going on still. Wonder if I need to add a second route back from the router to the card or something. Maybe I need to adda route from NIC2 to NIC1?

I am really not sure. Anyone have ideas?