Can't authorize DHCP server - Event ID 1059

Question

_{Tuesday, January 8, 2019 4:50 PM}

So currently, I am unable to authorize my DHCP server (can't even see the option for it).

I receive event 1059 in EV, "The DHCP service failed to see a directory server for authorization."

This is running on a Server 2016 DC, with one other DC in the network (still 2008 Server).

repadmin /replsum returns no errors

repadmin /syncall completes successfully

dcdiag /c passes all tests, from both DC's

I'm kind of at a loss here. I've tried removing the role and reinstalling, but to no avail. I did see mention in the *many* forums and articles I've read to this point that there can be issues with installing the AD role and the DHCP role simultaneously, but I'm not sure why this would ever be an issue. 

If anyone has any insights, I'd appreciate them. Thanks in advance!

All replies (3)

_{Wednesday, January 9, 2019 12:56 AM | 1 vote}

OK, so I figured this out after two nights.

I am not at all sure why this occurred, but for me what was missing was "CN=NetServices". I also added "CN=DhcpRoot" inside of the NetServices container, though I'm not positive this is necessary.

You can use ADSI to get to where NetServices should be:

Configuration-->CN=Configuration,DC=YOURDOMAIN-->CN=Services

Add a new container, "NetServices" with no added options and try to authorize again. If it works, check in Active Directory Sites and Services and navigate to this same location. You should see the DHCP server you authorized was added.

You may have to select "View Services Node", or something of that nature, in ADSS in order to actually see the Services node, mine was hidden by default. I believe it was in the "View" menu up top, the option is no longer displaying for me given I already have visibility.

There are other options out there to try first, like making sure you are attempting to authorize with a user with correct permissions (I have seen both Domain Admin and Enterprise Admin mentioned, I just assigned both temporarily).

Also, make sure DNS resolution is proper for your DC's and the domain itself.

However, if you have been banging your head against the wall on this like I have, check to see if the CN=NetServices container even exists. If it doesn't, you are probably in the same boat I was.

_{Wednesday, January 9, 2019 7:33 AM | 1 vote}

Hi,

Thanks for your sharing.

I think other users in this community will be benefited by your sharing. 

Have a nice day!

Best Regards.

Eric

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, May 6, 2019 3:10 PM}

Voted UP. Thanks for Sharing