DC Authorise DHCP 1

[martyday]

I have a server which is Win2k DC with DHCP installed.
The server is reporting "event Id:1051" "The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: dom.net.co.uk." Now according to everything I can find(e.g. Q300429 ) I do not need to authorize a DC. I suspect authorizing will fix the issue, however we are about to roll this to several hundred servers, so I would like to know why this is happening?

Do I need to authorise these servers or not?

 

[GrnEyedLdy]

Martyday,

Windows 2000 DHCP servers require authorization before begining to hand out IP addresses. To authorize a Win2K DHCP server you must be a member of the Enterprise Admins.

Hope this helps,

Patty

 

[martyday]

Patty,

Thanks for your help, but I don't believe that's the complete picture.

Domain Controllers "typically" do not need to be manually authorised. To quote Q300429 "When you install and configure the DHCP service on a domain controller, the server is typically authorized the first time that you add the server to the DHCP console" I've been in out of the DHCP console and left it a few days to allow replication and it was still getting DHCP authorization errors.


A DHCP DC doesn't alter the Netservices part of AD, which manual authorising does. I guess it must alter part of AD somewhere to say it is a DC DHCP server...?

So I guess what I'm really after is how authorization of DHCP on a DC works and what it sets to say it is a authorized?

 

[ricpinto]

Martyday,

I agree with you if your server is DC, no need to authorize because it's automatically done. But for whatever reason sometimes it's not automatically done, you still have to authorize it. So nothing to worry there buddy, it happens to me during my "testing" times.

Note:
Any user running Windows 2000 server could install the DHCP server service causing potential problems and so Windows 2000 adds the concept of authorizing the servers with the Active Directory before they can service client requests. If the server is not authorized in the Active Directory then the DHCP service will not be started.

 

[GrnEyedLdy]

Thanks Marty, I didn't know that the DHCP service (when installed on a DC) did not require manual authorization...everything I have ever read on DHCP says that 2000 requires authorization. This is good to know.

Patty

 

[GlenJohnson]

Patty is correct. If a dhcp server is not authorized in AD, then it is seen as a rouge dhcp server. The dhcp service will try and start, and when it realizes it's not authorized, then the service will stop. DHCP MUST be authorized in AD, or it will not work. Good luck. Patty, here's a star. You did it again.

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

"Once the game is over, the king and the pawn return to the same box."