Re: Misbehaving routing tables
- From: DHK <DHK@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 13 Jul 2009 07:16:01 -0700
Thanks for your feedback, Bill. I made the change and I am watching activity
carefully of the coming days. I'll report back my findings at the end of the
week.
--
DHK
"Bill Grant" wrote:
.
"DHK" <DHK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8AF9959E-B2B9-49B9-AFDE-CCF8FAA4AED4@xxxxxxxxxxxxxxxx
My client has Windows Server 2003 R2 Standard Edition SP2. It has two
NICs
installed. 192.168.10.x is to an internal network. 192.168.20.x is only
attached to a firewall. The metrics are supposed to give priority to
192.168.20.x, but it isn't working out that way. I have written a bat file
for modifying the routing table, but it isn't working.
I have including a portion of the routing table below immediately
following
a restart of the server:
ctive Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.10.254 192.168.10.2 10
0.0.0.0 0.0.0.0 192.168.20.254 192.168.20.5 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.10.0 255.255.255.0 192.168.10.2 192.168.10.2 10
192.168.10.2 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.10.255 255.255.255.255 192.168.10.2 192.168.10.2 10
192.168.20.0 255.255.255.0 192.168.20.5 192.168.20.5 10
192.168.20.5 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.20.255 255.255.255.255 192.168.20.5 192.168.20.5 10
224.0.0.0 240.0.0.0 192.168.10.2 192.168.10.2 10
224.0.0.0 240.0.0.0 192.168.20.5 192.168.20.5 10
255.255.255.255 255.255.255.255 192.168.10.2 192.168.10.2 1
255.255.255.255 255.255.255.255 192.168.20.5 192.168.20.5 1
Default Gateway: 192.168.10.254
The .bat file I use to modify the routing table is as follows. It is run
every time the system restarts:
route change 0.0.0.0 Mask 0.0.0.0 192.168.20.254 Metric 10 IF 0x10004
route change 0.0.0.0 Mask 0.0.0.0 192.168.10.254 Metric 20 IF 0x10003
When I run the bat file manually, it does not change the routing table
metrics.
If the server is left alone, a user is able to access the server via the
external address. The router forwards all traffic to 192.168.20.x. A full
TCP
session is established and sustained. However, after a few days, the
routing
table changes as follows:
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.10.254 192.168.10.2 10
0.0.0.0 0.0.0.0 192.168.20.254 192.168.20.5 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.10.0 255.255.255.0 192.168.10.2 192.168.10.2 10
192.168.10.2 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.10.255 255.255.255.255 192.168.10.2 192.168.10.2 10
192.168.20.0 255.255.255.0 192.168.20.5 192.168.20.5 20
192.168.20.5 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.20.255 255.255.255.255 192.168.20.5 192.168.20.5 20
224.0.0.0 240.0.0.0 192.168.10.2 192.168.10.2 10
224.0.0.0 240.0.0.0 192.168.20.5 192.168.20.5 20
255.255.255.255 255.255.255.255 192.168.10.2 192.168.10.2 1
255.255.255.255 255.255.255.255 192.168.20.5 192.168.20.5 1
Default Gateway: 192.168.10.254
This issue was addressed more than a year ago and for reasons unknown to
me,
the problem has returned.
I did notice that the default gateway is the 192.168.10.x network, not the
192.168.20.x network. Is that part of the problem?
Can you advise me how I can fix this issue?
Thanks.
--
DHK
A machine should only have one default gateway set, and therefore only
one default route. The default gateway on the internal NIC should be blank.
- References:
- Misbehaving routing tables
- From: DHK
- Re: Misbehaving routing tables
- From: Bill Grant
- Misbehaving routing tables
- Prev by Date: Re: Networking Question
- Next by Date: Re: Networking Question
- Previous by thread: Re: Misbehaving routing tables
- Next by thread: Baxk-up SMTP (MX 2x, 3x, ect)
- Index(es):
Relevant Pages
|
Loading