Re: There is a serious problem within Server 2003 SP1.
From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 04/28/05
- Next message: Roger Abell: "Re: Security update dated 2/13/2002?"
- Previous message: PA Bear: "Re: Security update dated 2/13/2002?"
- In reply to: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Next in thread: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 27 Apr 2005 19:05:29 -0400
> 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]" <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 >>> >>> >> >> > >
- Next message: Roger Abell: "Re: Security update dated 2/13/2002?"
- Previous message: PA Bear: "Re: Security update dated 2/13/2002?"
- In reply to: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Next in thread: Backup: "Re: There is a serious problem within Server 2003 SP1."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
