310-DC1 DHCP back up and running

310-dc1 was having a problem with DHCP. Though netdiag results were all checking out, DHCP would not correctly authorize in Active Directory.

Attempts have been made to:

• Create a new DHCP scope –>  to eliminate the fact that the DHCP database corrupt
• Create the DHCP server on a different server (tried 310-studc) –> to eliminate the fact that the physical server is the problem.

Both of these tests still failed DHCP, and narrowed down the problem to an Active Directory problem. The Authorization of the DHCP server would never show up in AD, even after forcing replication, and making sure that all AD communication is working correctly.

The next attempt was to check in ADSI Edit to see if the DHCP entry for 310-dc1 exists. 

Going to Configuration/Services/Net Services shows all the DHCP registrations in the enterprise. Sure enough, 310-dc1 had a CNF entry next to it, which means it was non functional. I figured that this was the problem. I deleted the CNF entry from ADSI, and reinstalled DHCP from scratch  with a  brand new scope on 310-dc1. After rechecking DHCP at 11:00pm, it finally showed that the server was Unauthorized. At this point, I  Authorized it, and it came right back up.

I then restored the original DHCP database with all the reservations therein.

DHCP is now fully functional at Levi DIckey

• Change made on 06/15/2009 @ 11:00pm