Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The network was fine yesterday and as far as I know nothing has been changed or added. This morning some computers are connected to our domain but most of them are reporting limited connectivity. On checking our DHCP server we are getting this message.

Cannot find the DHCP Server:

The DHCP server you specified cannot be located. The DHCP server might be down, there might be a network problem, or the DHCP service might not be installed.

The Error was: The DHCP Server service is not running on target computer.

enter image description here

I had to temporary issue the PC's with a static IP for them to connect and continue to work.

This is when the issue appears to start -

Error Message:-

The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. enter image description here

Error message for below:-

The DHCP service failed to see a directory server for authorization.

enter image description here

I have checked the DHCP server Services and they are started.

In addition I have noticed that the DHCP Server service is not listed under Task Manager - Services Tab, but is listed as started in Services.msc. Is this normal?

enter image description here

share|improve this question
    
It could help if you typed out those error messages, the screenshots are too small to read. –  jscott Feb 26 '13 at 11:45
    
Is your DHCP server your domain controller? –  Dan Feb 26 '13 at 12:06
1  
@Matt Your DHCP Server service should be started, but it stands to reason that your errors have come from it attempting to start. Feel free to try it, though, it may have been just a momentary glitch. If it doesn't start, see if you can ping your Active Directory domain name. I.e., not a SERVER name, JUST your domain name. ping .net.ang[retracted]c.com –  Dan Feb 26 '13 at 14:17
1  
Also, if both your domain controllers are DNS servers then make sure that each domain controller points to the OTHER DNS server first, and then 172.0.0.1 second. –  Dan Feb 26 '13 at 14:18
1  
@Matt Restarting the DHCP service won't impact user PCs. No one will be able to get a DHCP lease while it's restarting, but they can't do that now anyway. –  HopelessN00b Feb 26 '13 at 16:05

1 Answer 1

up vote 0 down vote accepted

We could not find an exact reason why this has failed, however we did find out that the firewall was enabled which really did not help matters. After restarting the server it came back up and started to work as intended.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.