There is a serious problem within Server 2003 SP1.

There is a serious problem within Server 2003 SP1.

I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
noticed some strange networking problems. Now the server has a multi homed
network configuration where it has two gateways. One point's to the
internal network here in the office LAN the other rests on the DMZ so that I
can forward traffic to that server for http / https and SMTP. This has
worked fine with out any problem for over a year. It seems SP1 changes the
main gateway when ever it feels like it. and I don't know why.



I am posting a few route prints of how it was when all was working fine.



================================================== =========================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1 20

0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1 20

10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20

10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20

10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1 20

192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1 20

224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20

255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1

Default Gateway: 192.168.1.3



Then in about 3 days time with no info in event viewer at all I now have:



================================================== =========================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1 20

0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1 20

10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20

10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20

10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1 20

192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1 20

224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20

255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1

Default Gateway: 10.0.0.2



The 2nd route print is the one that doesn't work

You really aren't supposed to have multiple default gateways configured that go
to different networks. The default gateway is the IP address Windows is supposed
to send traffic to that isn't local and it doesn't otherwise have a static route
for.

If you configure multiple gateways you are setting up primary and secondary
gateways and this enables dead gateway detection capability (this has been
forever, at least back to NT4 SP3) where if a current default gateway is
determined to be dead or underperforming, the system will switch the gateway to
the backup gateway to get better performance.

It is possible that changes in the IP stack in SP1 have changed this dead
gateway detection functionality but that is really beside the point. This was
working previously only from luck, you weren't using the default gateway feature
as designed.

I would also be more than a little concerned about operating the internal
machine as an edge device as well unless you are running some firewall software
of some sort on it.


--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Backup wrote:
> There is a serious problem within Server 2003 SP1.
>
> I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
> noticed some strange networking problems. Now the server has a multi homed
> network configuration where it has two gateways. One point's to the
> internal network here in the office LAN the other rests on the DMZ so that I
> can forward traffic to that server for http / https and SMTP. This has
> worked fine with out any problem for over a year. It seems SP1 changes the
> main gateway when ever it feels like it. and I don't know why.
>
>
>
> I am posting a few route prints of how it was when all was working fine.
>
>
>
> ================================================== =========================
>
> Active Routes:
>
> Network Destination Netmask Gateway Interface Metric
>
> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1 20
>
> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1 20
>
> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20
>
> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
>
> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20
>
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
>
> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1 20
>
> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1 20
>
> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1 20
>
> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20
>
> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1
>
> Default Gateway: 192.168.1.3
>
>
>
> Then in about 3 days time with no info in event viewer at all I now have:
>
>
>
> ================================================== =========================
>
> Active Routes:
>
> Network Destination Netmask Gateway Interface Metric
>
> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1 20
>
> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1 20
>
> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20
>
> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
>
> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20
>
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
>
> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1 20
>
> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1 20
>
> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1 20
>
> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20
>
> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1
>
> Default Gateway: 10.0.0.2
>
>
>
> The 2nd route print is the one that doesn't work
>
>

Yes, the default gateway was changed. assuming one nic goes to 192 and anotehr one goes to 10 lan. I would make routing table looks like this, route to 192 using gateway 192.168.1.3 and routeto 10 using 10.0.0.1. we don't know which one will point to the internet, but you can make that one point to 0.0.0.0.

For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

"Backup" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
There is a serious problem within Server 2003 SP1.

I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
noticed some strange networking problems. Now the server has a multi homed
network configuration where it has two gateways. One point's to the
internal network here in the office LAN the other rests on the DMZ so that I
can forward traffic to that server for http / https and SMTP. This has
worked fine with out any problem for over a year. It seems SP1 changes the
main gateway when ever it feels like it. and I don't know why.



I am posting a few route prints of how it was when all was working fine.



================================================== =========================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1 20

0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1 20

10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20

10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20

10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1 20

192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1 20

224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20

255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1

Default Gateway: 192.168.1.3



Then in about 3 days time with no info in event viewer at all I now have:



================================================== =========================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1 20

0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1 20

10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 20

10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20

10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1 20

192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1 20

224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1 20

255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1 1

Default Gateway: 10.0.0.2



The 2nd route print is the one that doesn't work

Not sure why this ever worked or how SP1 would affect it. But if you are
determined to have two default gateways, you should be able to restore the
prior behavior by changing/editing the automatic gateway settings. See:

http://www.microsoft.com/technet/pro...2e736faff.mspx

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Backup" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> There is a serious problem within Server 2003 SP1.
>
> I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
> noticed some strange networking problems. Now the server has a multi
homed
> network configuration where it has two gateways. One point's to the
> internal network here in the office LAN the other rests on the DMZ so that
I
> can forward traffic to that server for http / https and SMTP. This has
> worked fine with out any problem for over a year. It seems SP1 changes
the
> main gateway when ever it feels like it. and I don't know why.
>
>
>
> I am posting a few route prints of how it was when all was working fine.
>
>
>
>
================================================== =========================
>
> Active Routes:
>
> Network Destination Netmask Gateway Interface
Metric
>
> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
20
>
> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
20
>
> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
20
>
> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
20
>
> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
20
>
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
>
> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
20
>
> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
20
>
> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
20
>
> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
20
>
> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
1
>
> Default Gateway: 192.168.1.3
>
>
>
> Then in about 3 days time with no info in event viewer at all I now have:
>
>
>
>
================================================== =========================
>
> Active Routes:
>
> Network Destination Netmask Gateway Interface
Metric
>
> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
20
>
> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
20
>
> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
20
>
> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
20
>
> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
20
>
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
>
> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
20
>
> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
20
>
> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
20
>
> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
20
>
> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
1
>
> Default Gateway: 10.0.0.2
>
>
>
> The 2nd route print is the one that doesn't work
>
>

All that was posted about the gate ways and having only one default is the
standard way of doming things.

My point is that it was working and it's not the 1st time I setup something
in this manor.

Another thing is this . if it isn't a problem how come if I go to the
network card settings and then on the Support Tab I do a "Repair" it sets it
back and all is working again.



It would seem that this is SP1 that is messed up and the tcp/ip stack is
damaged.

I also can repeat these issues in other systems.

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Not sure why this ever worked or how SP1 would affect it. But if you are
> determined to have two default gateways, you should be able to restore the
> prior behavior by changing/editing the automatic gateway settings. See:
>
> http://www.microsoft.com/technet/pro...2e736faff.mspx
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Backup" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> There is a serious problem within Server 2003 SP1.
>>
>> I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
>> noticed some strange networking problems. Now the server has a multi
> homed
>> network configuration where it has two gateways. One point's to the
>> internal network here in the office LAN the other rests on the DMZ so
>> that
> I
>> can forward traffic to that server for http / https and SMTP. This has
>> worked fine with out any problem for over a year. It seems SP1 changes
> the
>> main gateway when ever it feels like it. and I don't know why.
>>
>>
>>
>> I am posting a few route prints of how it was when all was working fine.
>>
>>
>>
>>
> ================================================== =========================
>>
>> Active Routes:
>>
>> Network Destination Netmask Gateway Interface
> Metric
>>
>> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
> 20
>>
>> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
> 20
>>
>> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
> 20
>>
>> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
> 20
>>
>> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> 20
>>
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> 1
>>
>> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
> 20
>>
>> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
> 20
>>
>> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
> 20
>>
>> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
> 20
>>
>> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> 1
>>
>> Default Gateway: 192.168.1.3
>>
>>
>>
>> Then in about 3 days time with no info in event viewer at all I now have:
>>
>>
>>
>>
> ================================================== =========================
>>
>> Active Routes:
>>
>> Network Destination Netmask Gateway Interface
> Metric
>>
>> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
> 20
>>
>> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
> 20
>>
>> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
> 20
>>
>> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
> 20
>>
>> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> 20
>>
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> 1
>>
>> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
> 20
>>
>> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
> 20
>>
>> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
> 20
>>
>> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
> 20
>>
>> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> 1
>>
>> Default Gateway: 10.0.0.2
>>
>>
>>
>> The 2nd route print is the one that doesn't work
>>
>>
>
>

Your config is wrong - even if it worked in the past. Read the text pasted
below which is from
http://www.microsoft.com/technet/pro...g/tcpip03.mspx.
It's likely that SP1 made some changes that's causing the gateways to switch,
but it doesn't matter: your config is not supported - heck, when you add a
second gateway on a system that already has a gateway on a multihomed system,
you get the following warning:

"Warning - Multiple gateways are intended to provide redundancy to a single
network (such as an intranet or the Internet). They will not function
properly when the gateways are on two separate, disjoint networks (such as
one on your intranet and one on the Internet). Do you want to save this
configuration?"


When a computer is multihomed with NICs attached to disjoint networks
(networks that are separate from and unaware of each other, such as a private
network using private addressing and the Internet), routing problems may
arise. It is often necessary to set up static routes to the private networks
in this situation.

When configuring a computer to be multihomed on two disjoint networks, the
best practice is to configure the default gateway on the interface connected
to the largest and least-known network, in which the default route summarizes
the most destinations. Then, either add static routes or use a routing
protocol to provide connectivity to the hosts on the smaller or better-known
network. Avoid configuring a different default gateway on each side; this can
result in unpredictable behavior and loss of connectivity. For more
information, see Default Gateway Behavior for Windows TCP/IP.

Note There can only be one active default gateway for a computer at any
moment in time.



"Backup" wrote:

> All that was posted about the gate ways and having only one default is the
> standard way of doming things.
>
> My point is that it was working and it's not the 1st time I setup something
> in this manor.
>
> Another thing is this . if it isn't a problem how come if I go to the
> network card settings and then on the Support Tab I do a "Repair" it sets it
> back and all is working again.
>
>
>
> It would seem that this is SP1 that is messed up and the tcp/ip stack is
> damaged.
>
> I also can repeat these issues in other systems.
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Not sure why this ever worked or how SP1 would affect it. But if you are
> > determined to have two default gateways, you should be able to restore the
> > prior behavior by changing/editing the automatic gateway settings. See:
> >
> > http://www.microsoft.com/technet/pro...2e736faff.mspx
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Backup" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> There is a serious problem within Server 2003 SP1.
> >>
> >> I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
> >> noticed some strange networking problems. Now the server has a multi
> > homed
> >> network configuration where it has two gateways. One point's to the
> >> internal network here in the office LAN the other rests on the DMZ so
> >> that
> > I
> >> can forward traffic to that server for http / https and SMTP. This has
> >> worked fine with out any problem for over a year. It seems SP1 changes
> > the
> >> main gateway when ever it feels like it. and I don't know why.
> >>
> >>
> >>
> >> I am posting a few route prints of how it was when all was working fine.
> >>
> >>
> >>
> >>
> > ================================================== =========================
> >>
> >> Active Routes:
> >>
> >> Network Destination Netmask Gateway Interface
> > Metric
> >>
> >> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
> > 20
> >>
> >> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
> > 20
> >>
> >> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
> > 20
> >>
> >> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
> > 20
> >>
> >> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> > 20
> >>
> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> > 1
> >>
> >> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
> > 20
> >>
> >> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
> > 20
> >>
> >> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
> > 20
> >>
> >> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
> > 20
> >>
> >> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> > 1
> >>
> >> Default Gateway: 192.168.1.3
> >>
> >>
> >>
> >> Then in about 3 days time with no info in event viewer at all I now have:
> >>
> >>
> >>
> >>
> > ================================================== =========================
> >>
> >> Active Routes:
> >>
> >> Network Destination Netmask Gateway Interface
> > Metric
> >>
> >> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
> > 20
> >>
> >> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
> > 20
> >>
> >> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
> > 20
> >>
> >> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
> > 20
> >>
> >> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> > 20
> >>
> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> > 1
> >>
> >> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
> > 20
> >>
> >> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
> > 20
> >>
> >> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
> > 20
> >>
> >> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
> > 20
> >>
> >> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
> > 1
> >>
> >> Default Gateway: 10.0.0.2
> >>
> >>
> >>
> >> The 2nd route print is the one that doesn't work
> >>
> >>
> >
> >
>
>
>

> My point is that it was working and it's not the 1st time I setup something
> in this manor.

This is called luck, or possibly it would break for short periods and you
wouldn't catch it. I have seen many attempts at this that all worked great until
it didn't. The didn't was due to something forcing it to switch which was the
current active default gateway and I have seen things such as a router having
issues, viruses on the network causing router saturation, to whatever. In all
cases, it doesn't matter, you are misconfigured.

If you want, feel free to call MS Product Support and pay the money to hear the
same exact thing.

joe


--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Backup wrote:
> All that was posted about the gate ways and having only one default is the
> standard way of doming things.
>
> My point is that it was working and it's not the 1st time I setup something
> in this manor.
>
> Another thing is this . if it isn't a problem how come if I go to the
> network card settings and then on the Support Tab I do a "Repair" it sets it
> back and all is working again.
>
>
>
> It would seem that this is SP1 that is messed up and the tcp/ip stack is
> damaged.
>
> I also can repeat these issues in other systems.
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>Not sure why this ever worked or how SP1 would affect it. But if you are
>>determined to have two default gateways, you should be able to restore the
>>prior behavior by changing/editing the automatic gateway settings. See:
>>
>>http://www.microsoft.com/technet/pro...2e736faff.mspx
>>
>>Doug Sherman
>>MCSE, MCSA, MCP+I, MVP
>>
>>"Backup" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed)...
>>
>>>There is a serious problem within Server 2003 SP1.
>>>
>>>I have updated my Server 2003 EE to SP1 and soon after (about 3 days) I
>>>noticed some strange networking problems. Now the server has a multi
>>
>>homed
>>
>>>network configuration where it has two gateways. One point's to the
>>>internal network here in the office LAN the other rests on the DMZ so
>>>that
>>
>>I
>>
>>>can forward traffic to that server for http / https and SMTP. This has
>>>worked fine with out any problem for over a year. It seems SP1 changes
>>
>>the
>>
>>>main gateway when ever it feels like it. and I don't know why.
>>>
>>>
>>>
>>>I am posting a few route prints of how it was when all was working fine.
>>>
>>>
>>>
>>>
>>
>>================================================ ===========================
>>
>>>Active Routes:
>>>
>>>Network Destination Netmask Gateway Interface
>>
>>Metric
>>
>>> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
>>
>>20
>>
>>> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
>>
>>20
>>
>>> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
>>
>>20
>>
>>> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
>>
>>20
>>
>>> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
>>
>>20
>>
>>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>>
>>1
>>
>>> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
>>
>>20
>>
>>> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
>>
>>20
>>
>>> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
>>
>>20
>>
>>> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
>>
>>20
>>
>>> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
>>
>>1
>>
>>>Default Gateway: 192.168.1.3
>>>
>>>
>>>
>>>Then in about 3 days time with no info in event viewer at all I now have:
>>>
>>>
>>>
>>>
>>
>>================================================ ===========================
>>
>>>Active Routes:
>>>
>>>Network Destination Netmask Gateway Interface
>>
>>Metric
>>
>>> 0.0.0.0 0.0.0.0 10.0.0.2 10.0.0.1
>>
>>20
>>
>>> 0.0.0.0 0.0.0.0 192.168.1.3 10.0.0.1
>>
>>20
>>
>>> 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
>>
>>20
>>
>>> 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
>>
>>20
>>
>>> 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
>>
>>20
>>
>>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>>
>>1
>>
>>> 192.168.1.0 255.255.255.0 192.168.1.110 10.0.0.1
>>
>>20
>>
>>> 192.168.1.110 255.255.255.255 127.0.0.1 127.0.0.1
>>
>>20
>>
>>> 192.168.1.255 255.255.255.255 192.168.1.110 10.0.0.1
>>
>>20
>>
>>> 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
>>
>>20
>>
>>> 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
>>
>>1
>>
>>>Default Gateway: 10.0.0.2
>>>
>>>
>>>
>>>The 2nd route print is the one that doesn't work
>>>
>>>
>>
>>
>
>

So would the best thing for a person to do is to install a 2nd NIC and
assign one of them the 192.168.1.* network address and the other the
10.0.0.* address?



Wouldn't I run into the same wall of default gateway?



The only reason they have the IP for 192.168**** is so that they can reach
their OWA and so they can fwd SMTP email back into exchange.

<(E-Mail Removed)> wrote:
> So would the best thing for a person to do is to install a 2nd NIC and
> assign one of them the 192.168.1.* network address and the other the
> 10.0.0.* address?

If your DMZ is actually on the same network why not just add a second IP
address to the same card?

Alternatively, if it's actually on a different network behind your 2-ported
firewall, then your firewall must be routing packets through from the 10/24
to the 192.168.1/8... in which case all of this is redundant and you just
need the single default route to the gateway.

G