I have a WINDOWS 2000 domain controller with WINS enabled. All works just fine however I noticed I was getting some IP Spoof alerts from my internet access device. I traced it down to the DC - which for some reason was using the 169.254.x.x Microsoft Private IP address as it's own. This address space is handed out when a DHCP interface comes up but cannot find a DHCP server I believe. Sure enough when I looked on the console and brought up WINS admin interface my DC was presented with that IP address. The DC has 2 NICs - but only one is enabled and plugged in. WINS works - but I want to get this correct.
Can I change that IP address for the WINS server somehow? Is this happening because that second NIC is disabled and that is the NIC it tries to bind to at startup?

Re: WINS Server IP address is wrong by Marina

Marina
Tue Nov 18 15:44:33 CST 2003

The 169-IP is an address that couldn't find a DHCP-server. Do you have the
DHCP-client service running on the server? You can disable that.
Your WINS-server should be pointing to your server-IP.
Delete all invalid address from the WINS database (and possibly the
DNS-records) and restart WINS (and DNS).

Marina

"catbird" <anonymous@discussions.microsoft.com> schreef in bericht
news:BD03CCE8-1A30-438E-A9E4-FCBA53CC056C@microsoft.com...
> I have a WINDOWS 2000 domain controller with WINS enabled. All works just
fine however I noticed I was getting some IP Spoof alerts from my internet
access device. I traced it down to the DC - which for some reason was using
the 169.254.x.x Microsoft Private IP address as it's own. This address space
is handed out when a DHCP interface comes up but cannot find a DHCP server I
believe. Sure enough when I looked on the console and brought up WINS admin
interface my DC was presented with that IP address. The DC has 2 NICs - but
only one is enabled and plugged in. WINS works - but I want to get this
correct.
> Can I change that IP address for the WINS server somehow? Is this
happening because that second NIC is disabled and that is the NIC it tries
to bind to at startup?