Windows server 2003 DHCP error

[Rakesh]

I am getting this DHCP errors in my whenever i check the system log. The error and everything regarding that is given below. We dont use a DHCP in our network and all the servers are configured properly with the correct IP addresses. Cud anyone tell me what this is all about.

Event Type: Error

Event Source: ipnathlp

Event Category: None

Event ID: 30013

Date: 12/09/2005

Time: 07:44:30 PM

User: N/A

Computer: DC

Description:

The DHCP allocator has disabled itself on IP address 192.X.X.X, since the IP address is outside the 169.254.0.0/255.255.0.0 scope from which addresses are being allocated to DHCP clients. To enable the DHCP allocator on this IP address, please change the scope to include the IP address, or change the IP address to fall within the scope.

[InTheWayBoy]

Well if you don't use DHCP, then why not just uninstall it?

By the looks of the error message, it seems that you have your DHCP server setup on one IP range, but it's configured to hand out a different range of IP's. I don't think you can do that...least, that is what it looks like according to that error message.

Edited September 12, 2005 by InTheWayBoy

[Rakesh]

no we dont have a dhcp installed as is said on the message could it be some rogue server tryin to act as a dhcp or other reasons for this one.

[Rakesh]

its our domain controller which is having this problem its a win2k3 with sp1 installed

[InTheWayBoy]

Well I guess it could be a rouge DHCP server, but the error seems to be very specific on what computer is causing the errors: DC. And you say it's your domain controller which is causing the error, so I would really check again to make sure you're not missing something. Maybe the DC is thinking there should be a DHCP server elsewhere...I'm really out of ideas at this point.

[chilifrei64]

yes.. if you are receiving this error on your event log on your system then it is talking about your system. Go to Add/remove programs -> add remove components -> Networking Services -> DHCP.

Uncheck the box and hit next.

[ixion]

169.254 is an APIPA address, if a network connection detects physical connectivity and is configured to use DHCP and it cannot obtain an IP address then it will assign itself an APIPA address randomly.

It sounds as if you have DHCP installed on this server, DC, and that it has a scope configured in the 192.x range and that it is bound to the adapter which has assigned intself an APIPA address

[Rakesh]

no guys i dont have dhcp service installed in this machine and it has a static ip since its a DC and though it says it has got iself an APIPA address it still has the static IP that i gave. m thoroughly confused as to wht else to luk for cud it be a rogue dhcp from some other system or somebody trying to act smart from outside my network.

[InTheWayBoy]

And that's what is so wierd...according to the error message the DC has DHCP...but as you say it doesn't. I can't say I've ever run across that.

Let's see if maybe some more info would help. Sounds like you have other servers on the network, and obviously clients. How many other servers do you have, and what functions do they perform.

You say you use static IP's, does that include all the clients? Do you have a router that is doing DHCP for you? Maybe that could be getting in the way, although I don't see how that would result in the error you are getting.

I did a little searching on the event ID and came across a few things that might help:

http://msmvps.com/bradley/archive/2004/04/24/5452.aspx

http://forums.ocmodshop.com/default.aspx?f=17&m=15450

http://www.eventid.net/display.asp?eventid...pnathlp&phase=1

Looks like one of the issues had to do with ICS...are you using that?