Default Gateways and Route in Windows Server 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a Windows Enterprise 2003 server and 4 Windows 2003 Server jointed to
the Enterprise 2003 server. All servers has 2 NIC and been configured with 2
subnets which are 218.x.x.x and 192.x.x.x.
The 218 segment is a internal usage and the 192 is for the internet usage. I
understand that Windows only mounted to 1 Default Gateways at a time. So
there is a problem for the internet sometime.
We have tried out 4 solutions here, as below:
1. Running a Tracert Script through the IIS to keep the 192 up for internet
all time.
2. Take away the 218 segment as a Default Gateway.
3. Assigning Metrics for 2 Default Gateways.
4. Route add entries.

References information as below:
http://groups.google.com.sg/group/m...efault+Gateways&rnum=3&hl=en#9c47c03e7ee08ead
http://support.microsoft.com/kb/159168/EN-US/

But the thing here is that as our company partner mention, all 4 solution
stated above are not recommended. I can understand why solution 1 to 3 is not
recommended except for the 4th one (Route Add).
Can anyone help me up in explaining more to me why a Route Add is not
recommended? Besides, also if can help me up if there is/are any other better
solution for this?
 
We have a Windows Enterprise 2003 server and 4 Windows 2003 Server jointed to
the Enterprise 2003 server. All servers has 2 NIC and been configured with 2
subnets which are 218.x.x.x and 192.x.x.x.
The 218 segment is a internal usage and the 192 is for the internet usage. I
understand that Windows only mounted to 1 Default Gateways at a time. So
there is a problem for the internet sometime.
We have tried out 4 solutions here, as below:
1. Running a Tracert Script through the IIS to keep the 192 up for internet
all time.
2. Take away the 218 segment as a Default Gateway.
3. Assigning Metrics for 2 Default Gateways.
4. Route add entries.

References information as below:
http://groups.google.com.sg/group/m...efault+Gateways&rnum=3&hl=en#9c47c03e7ee08ead
http://support.microsoft.com/kb/159168/EN-US/

But the thing here is that as our company partner mention, all 4 solution
stated above are not recommended. I can understand why solution 1 to 3 is not
recommended except for the 4th one (Route Add).
Can anyone help me up in explaining more to me why a Route Add is not
recommended? Besides, also if can help me up if there is/are any other better
solution for this?
Click to expand...

Well, route add is definately the way I'ld do it. Just put your
Internet gateway as your default, and do a static route with the /p
(permanent) to your 218. Only down side I can think of is it would be
tedious to do manually for lots of machines, but on a small network
would take long at all. You can put it in your login scripts if you
have large network.

Hal
 
Thanks Hal.
This is what I suggested to my boss and also as well to the partner. But
they still insist in
adding the Route Add. And now they claim that the Metrics will help. But for
my experience
previously, this does not help much as the problem will still occur, just
that not that
frequent. So that's why I am wondering if there are any better solution.
I had a hard time fighting with them even with the prove and evidence. They
still insist
not to. Fainted!!!
 
Back
Top