Default Gateway Reverts to Old Setting



Having a problem with the default gateway setting on a WinSvr2003 Std box at
one of my clients.

This server is on the only IP subnet at the client's main office. It's
configured as a DC with another DC on the subnet, which is an SBS2003
Premium box which holds all the FSMO roles. Both DCs run DNS for the
domain, but onlly the SBS2003 server runs WINS.

The server has two identical 10/100/1000 NICs, plus a (Broadcom) BASP
Virtual Adapter which is part of optional NIC teaming. We're not doing any
of the teaming, and the BASP Virtual Adapter and one of the physical NICs
are disabled.

We re-numbered the IP subnet in this office as part of a IP numbering
architecture involving several branch offices VPNs with this main office as
the VPN hub. The previous subnet was 192.168.0.0/24 with the old default
gateway at 192.168.0.1. The renumbered subnet is 192.168.60.0/24 with the
default gateway at 192.168.60.254.

The server has static IP addressing on the active NIC. TCP/IP properties
are left to use DHCP on the two disabled NICs, not that it should matter.
TCP/IP is the only network protocol installed. DNS & WINS are set
correrctly and NetBIOS is enabled on the active NIC. Advanced Settings in
Network Properties look right as to sequence and protocol bindings.

The problem is that the default gateway setting for the active NIC keeps
reverting back to 192.168.0.1 from 192.168.60.254 at random times. After
it's set correctly, it'll revert back after the server runs for some period
of time. It may revert back after a reboot (but not always), overnight
(during which a backup normally occurs, using BackupExec Remote Agent) or
just after a few hours.

I've re-set the default gateway numerous times, but it always reverts back
to the old, now non-existent IP. I've searched the registry many times and
removed or updated any reference to the old 192.168.0.x network. I've also
changed which NIC is the active one and set the IP addressing correctly on
the new one only to have the gateway get changed to the old 192.18.0.1 one
on that NIC which had never been on that old network. Haven't found
anything on-point in the Microsoft Support KnowledgeBase.

We're at the point now of maybe removing/reinstalling the TCP/IP and/or
networking software on this box. But we don't know if that will cure this
and it's a hassle anyway.

Anyone have any ideas?

Thanks,
DD

Anyone have any i


.



Relevant Pages

  • Re: Dynamic DNS and failed journal
    ... changed control clause to be updated by localhost and server ... i thought it was odd too....but in retrospect, it means to listen on 127.0.0.1 and any other NICS using 192.168.10.0/24 netowrk that may be in the box ... ... I would have thought allow-wuery would have been ok with an acl ... ... had to be done outside of the subnet clauses. ...
    (Fedora)
  • Re: Default Gateway Reverts to Old Setting
    ... This server is on the only IP subnet at the client's main office. ... The server has two identical 10/100/1000 NICs, ... TCP/IP is the only network protocol installed. ...
    (microsoft.public.windows.server.networking)
  • Re: Problem using Remoting with 2 NICs
    ... I agree with you on the 2 NIC's with same subnet being a bad idea. ... Setting the http channels useIpAddress property to false on the server fixed ... I have clients connecting successfully on NIC 1, ... When both NICs are enabled. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: route trafic from external to internal adapter
    ... I am remoting into networks through PPTP and RDP and am on a subnet not ... behind o f SBS Server. ... gateway and proxy server for 192.168.30.x client computers. ... If the default gateway for 192.168.30.11 is to the RRAS router and the ...
    (microsoft.public.windows.server.networking)
  • Re: VPN Gateway
    ... The subnet mask certainly ... shouldn't be 255.255.255.255 and a gateway address is not relevant. ... The server itself will get an IP address of 192.168.21.n and the ... route is to the VPN server via the point to point link. ...
    (microsoft.public.windows.server.networking)