Re: There is a serious problem within Server 2003 SP1.
From: Doug Sherman [MVP] (dsherman_at_nospamtampabay.rr.com)
Date: 04/27/05
- Next message: Stephen Howe: "SFTP"
- Previous message: Polaris: "Thanks! Re: "admin" could not make entries in registry ..."
- In reply to: Backup: "There is a serious problem within Server 2003 SP1."
- Next in thread: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Reply: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 27 Apr 2005 12:58:28 -0400
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:
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
>
>
- Next message: Stephen Howe: "SFTP"
- Previous message: Polaris: "Thanks! Re: "admin" could not make entries in registry ..."
- In reply to: Backup: "There is a serious problem within Server 2003 SP1."
- Next in thread: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Reply: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|