Re: There is a serious problem within Server 2003 SP1.

From: me (me_at_discussions.microsoft.com)
Date: 04/27/05 

Date: Wed, 27 Apr 2005 12:52:56 -0700

Your config is wrong - even if it worked in the past. Read the text pasted
below which is from
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/networking/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]" <dsherman@nospamtampabay.rr.com> wrote in message
> news:OjJcXp0SFHA.2768@tk2msftngp13.phx.gbl...
> > 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/prodtechnol/windowsserver2003/library/ServerHelp/2f4f2924-f6a8-44e2-9b1e-c752e736faff.mspx
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Backup" <backup@yahoo.com> wrote in message
> > news:ujfIvczSFHA.1152@tk2msftngp13.phx.gbl...
> >> 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
> >>
> >>
> >
> >
>
>
>

Relevant Pages

  • Re: connect to bridge modem
    ... ISA console, Configuration, Networks, Internal. ... IP address' wiz and move out of the .0 subnet, ... I understand that the external gateway has no business routing private IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Help with theory question on network topology
    ... of the difference between a gateway and a hub. ... >> of devices are attached to each of the networks. ... >> Not all data packets pass through the gateway (My guess, ... > Token Ring and something else, the nature of Token Ring has little to do ...
    (comp.dcom.lans.ethernet)
  • RE: Quickie... Hopefully!
    ... both ISPs feeds end up coming into a hub/switch ... route on the machine would be 1.1.1.1 and all traffic goes there. ... via the 1.1.1.1 gateway. ... addresses on the same NIC that are different networks. ...
    (freebsd-questions)
  • Re: [Newbie] Info about ISP Gateways
    ... Regarding the private networks, this is just means that they are just a ... The ISP gateway (not on the customer ... should be unaffected by how the ISP has chosen to structure the network. ...
    (Pen-Test)
  • Re: single-name questions for 2000
    ... I am unfamiliar with all the networks ... > address in it's config. ... Nor does it configure the Primary DNS SUffix. ... > Microsoft Windows MVP - Active Directory ...
    (microsoft.public.win2000.dns)