Link to home
Start Free TrialLog in
Avatar of brainbolt
brainbolt

asked on

DHCP Server not functioning

One of my Windows Server 2003 DHCP servers has stopped functioning. The machine acts as a DC, DNS, File Server and DHCP server for one of my small offices. The rest of the services listed appear to be working normally.

The local management console of the machine gives no indication that there is a problem with DHCP, but if I try to reach the DHCP application from a remote console, I get the following message:

Cannot find the DHCP Server
The DHCP Server you specified cannot be located. The DHCP server might be down, there might be network problems, or the DHCP service might not be installed.
The error was: The DHCP Server Service is not running on the target computer.
To retry the connection, either press F5, or on the action menu, click Refresh.

The problem that I am having is that the server is simply not assigning addresses to clients. Clients that obtained addresses before the problem started are functioning normally, as are machines that are manually assigned IPs. The server does not respond to renew requests for addresses.

I have restarted both the machine and the DHCP Server service, but it hasnt made a difference. The machine seems to behave normally otherwise: reponsive to pings, RDP connections, etc.. I cant narrow down the time of the failure precisely, but I suspect it coincides with a power failure at the office over the weekend. Event logs don't reveal anything substantial.

Any suggestions?
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Check that it is authorised. Right click on the DHCP Server in the DHCP Console. If Authoirize appears as an option select it. (if is says Unauthorize you are Ok on this front, don't do anything and get back to EE)
Avatar of brainbolt
brainbolt

ASKER

The local console says "Unauthorize."
Pity - that means its OK and I'll have to think again.
Is it possible that the power failure somehow corrupted the DHCP service and that it needs to be reinstalled?
What.
It has to be Autherized, not unautherized to be working.

When you look in DHCP is there a red X or a green arrow? If it is a Red X you need to Autherize it.

Get back to me.

Cheers
If it is unauthorized, then right click it and authorize it.
KCTS's post seems to indicate that if you have the option to Unauthorize it, it must already be authorized, which makes sense to me.

On the local console it is a green arrow. On the remote management console it is a red "X."
Ah,
My bad.

But a quick glance and it appears that you are saying different.

Cheers
Event log check time.

What kind of errors are you getting in your system logs?
Immeidately following the power failure, I started getting this:

**********************************
Event Type:      Warning
Event Source:      DhcpServer
Event Category:      None
Event ID:      1056
Date:            3/19/2007
Time:            8:07:24 AM
User:            N/A
Computer:      CUBEDC02
Description:
The DHCP service has detected that it is running on a DC and has  no credentials configured for use with Dynamic DNS registrations  initiated by the DHCP service.   This is not a recommended security configuration.   Credentials for Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the  DHCP Administrative tool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00               ....    
*********************************

Which was always follwed by this:

*********************************
Event Type:      Information
Event Source:      DhcpServer
Event Category:      None
Event ID:      1044
Date:            3/19/2007
Time:            8:07:29 AM
User:            N/A
Computer:      CUBEDC02
Description:
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain CUBE.CORP, has determined that it is authorized to start. It is servicing clients now.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00               ....    
*******************************************

So I followed the directions in MS KB282001 (http://support.microsoft.com/kb/282001/en-us), I used the DHCP Server Snap-In method and then restarted the DHCP service. I no longer get Event ID: 1056, but it didn't address the problem.

Nothing else in the logs that I can see as related to DHCP. There are other various events that relate to printers and an ACPI BIOS error that has to do with attempting to read form an illegal IO port address, but that is nothing new with this machine.

Go into Services and view the properties of the DHCP Server Service. Is it set to use the local sustem account or a specified account. Check that these accounts are not locked out or disabled.
The credentials can be set via command line as suggested, but that can be problematic sometimes. The changes can also be made via the DHCP MMC. Go into the properties of the DHCP server, not the scopes, and then select the "Advanced" tab and finally the "Credentials" button. Fill in the account information as requested.
KCTS; the Log On property of the DHCP Server service is set to "Local System account"

TEKWAZOO; I have actually already run that process through the DHCP Server properties.
Restart DHCP services and tell me what errors you get if any in system log.
When I Restart DHCP I dont get an error. I get the following event in the system log:

******************************************
Event Type:      Information
Event Source:      DhcpServer
Event Category:      None
Event ID:      1044
Date:            3/21/2007
Time:            1:15:38 PM
User:            N/A
Computer:      CUBEDC02
Description:
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain xxx.xxx, has determined that it is authorized to start. It is servicing clients now.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00               ....    
*******************************************
And the client stations still do not get an IP?

At the client station run:
Run CMD
ipconfig /release
ipconfig /renew

Anything?

When I run ipconfig /renew I get a message that says the DHCP server cannot be reached.

Everything that I see says it should be working. Hmmm

At this point I would start thinking about rebuilding DHCP. It is possible that during the power outage that DHCP took a real hard hit and is now corrupted.

Just to be sure, you have checked for the renew on other client stations. We are not just doing this on one machine? Correct.
Correct; I have tested it on more than one machine.

When you say "rebuilding" it sounds like you are talking about more than just reinstalling an OS component. What did you have in mind?
Correct and it is a lot faster then rebuilding the whole OS. You are just removing the DHCP and then reinstalling it. Once that is completed, you will just reconfigure it. Do you have many scopes in place?
Before you do any of this make sure you know what scopes you have inpace and how they are configured.

Add/Remove Programs
Add/Remove Windows Components
Network Services
Uncheck DHCP
Ok through
Reboot

Add/Remove Programs
Add/Remove Windows Components
Network Services
check DHCP
Ok through
Reboot

Administrator Tools
DHCP
Authorize
Configure scopes
Reboot

Test with client station
I followed the steps you recommended, but it didnt change anything. I am still getting no response from the DHCP server when attempting to renew the address on client computers.

After I uninstalled and reinstalled DHCP, I got the following entries in the system event log

***********************************
Event Type:      Error
Event Source:      DhcpServer
Event Category:      None
Event ID:      1046
Date:            3/22/2007
Time:            12:31:08 PM
User:            N/A
Computer:      CUBEDC02
Description:
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain xxx.xxx, has determined that it is not authorized to start.  It has stopped servicing clients.  The following are some possible reasons for this:
      This machine is part of a directory service enterprise and is  not authorized in the same domain.  (See help on the DHCP Service  Management Tool for additional information).

      This machine cannot reach its directory service enterprise and  it has encountered another DHCP service on the network belonging to  a directory service enterprise on which the local machine is not authorized.

      Some unexpected network error occurred.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00               ....    
**************************************
But it was then followed with this:

**************************************
Event Type:      Information
Event Source:      DhcpServer
Event Category:      None
Event ID:      1044
Date:            3/22/2007
Time:            12:38:36 PM
User:            N/A
Computer:      CUBEDC02
Description:
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain xxx.xxx, has determined that it is authorized to start. It is servicing clients now.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00               ....    
****************************************

I checked the details for the event, and according to microsoft, the first error simply means that the DHCP server is not authorized to start. My server is definately authorized to start, so that is probably why I get the second event (1044) that says everything has started.

I am starting to wonder if this could be a network connectivity issue of some sort. If I recall, DHCP clients utlize a broadcast method for finding servers. Anyone know how I can test a broadcast to make sure that something isnt having a problem?
It has to be something else. The DHCP service is running just fine.

There is not any other DHCP running on the network?
ASKER CERTIFIED SOLUTION
Avatar of brainbolt
brainbolt

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
By the way, to configure the firewall on a DHCP Server to allow it to function properly, you need to allow exceptions for UDP ports 67 and 2535.
check to make sure netbios over tcpip is running on server and on clients and that their is no router between, if there is a router then it may need netbios helper
The problem was that Windows Firewall didnt have the proper port exceptions for a DHCP Server.