Using multiple gateways simoultaniously in Win2k Server

[Guest]

I've got 1 main office with a File Server, and 2 Citrix servers all running 2000 Server w/SP4, and 2 remote offices that connect to the main office via T1 lines and Cisco 1700 routers. The T1's are dedicated pipes, not an internet connection so the gateway addresses on the server must point to the cisco router's address to allow the remote offices to connect. I am also trying to get internet access via DSL on these servers and allow them to be connected to through the internet remotely(Terminal Services.) I thought I could add a second router, 2nd network card, and second network scheme/gateway to accomplish this. It kinda worked, but wasn't stable. I think the problem is having the 2 gateways, it wants to default to the main network (192.168.1.x) when attemping to go online. Windows should attempt the second card/network if it cannot find what its looking for on the first network, however that only happens if the first gateway cannot be contacted (is this correct?) My first gateway can always be contacted so it never pushes the web traffic out to the second NIC, if you add the gateways in a specific order you can get the inet to work, but then the remote offices get flaky connections. Does anyone have any ideas of how I can get this all to work correctly? Thanks!

 

[Bill Grant]

Two gateways are fine, but only one can be the default gateway. The
Internet gateway must be the default gateway, so that is the first question
answered. The LAN machines must have the Internet router only set as their
default gateway.

To get traffic to the remote sites does not require default routing. You
know exactly what IP addresses your sites use, so you can use static routing
to get that traffic to the T1 router. You can add this to each machine, or
you can simply add it to the default router to bounce the branch traffic to
the T1 router.

I've got 1 main office with a File Server, and 2 Citrix servers all

running 2000 Server w/SP4, and 2 remote offices that connect to the main
office via T1 lines and Cisco 1700 routers. The T1's are dedicated pipes,
not an internet connection so the gateway addresses on the server must point
to the cisco router's address to allow the remote offices to connect. I am
also trying to get internet access via DSL on these servers and allow them
to be connected to through the internet remotely(Terminal Services.) I
thought I could add a second router, 2nd network card, and second network
scheme/gateway to accomplish this. It kinda worked, but wasn't stable. I
think the problem is having the 2 gateways, it wants to default to the main
network (192.168.1.x) when attemping to go online. Windows should attempt
the second card/network if it cannot find what its looking for on the first
network, however that only happens if the first gateway cannot be contacted
(is this correct?) My first gateway can always be contacted so it never
pushes the web traffic out to the second NIC, if you add the gateways in a
specific order you can get the inet to work, but then the remote offices get
flaky connections. Does anyone have any ideas of how I can get this all to
work correctly? Thanks!