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!

 

[Doug Sherman [MVP]]

Only the DSL connection is a default gateway. The Cisco router connection
is a route to whatever specific networks exist at the 2 remote offices.
There should be no conflict if you configure the Server with one default
gateway and 2 or more static routes to the destination networks.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

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!

 

[Guest]

Static routes added to Windows or the Cisco router? The Cisco already has the routes in it, and if I remove 192.168.1.1 (the cisco router address) from the default gateway, the other offices cannot connect. If the routes should be added to Windows and I want to route from 192.168.1.x to 2.x & 3.x, what is the command structure for this? Thanks alot.

Nick

 

[Guest]

Should the static routes be added to Windows or the Cisco router? The Cisco already has the routes for the remote networks in it. If I remove 192.168.1.1 (Cisco router address) from the default gateway on the server, the remote networks cannot connect. If I need to add those routes to Windows, what is the command and structure to do this? Also, do I need to write a batch file to add these routes on every bootup? Thanks.

P.S. My main network is 192.168.1.x & the remotes are 2.x & 3.x.

Nick

 

[Doug Sherman [MVP]]

On the Server:

route -p add 192.168.2.0 MASK 255.255.255.0 192.168.1.1

and

route -p add 192.168.3.0 MASK 255.255.255.0 192.168.1.1

Configure a default gateway only on the NIC connected to the DSL router.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

Should the static routes be added to Windows or the Cisco router? The

Cisco already has the routes for the remote networks in it. If I remove
192.168.1.1 (Cisco router address) from the default gateway on the server,
the remote networks cannot connect. If I need to add those routes to
Windows, what is the command and structure to do this? Also, do I need to
write a batch file to add these routes on every bootup? Thanks.