⚑ Deus Ex Machina ➽ Eventlog Lookup

Deus Ex Machina » Eventlog » Event 1046 - DhcpServer

DhcpServer - 1046


Error

Description »
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain ad.fqdn.local, 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.
Data formatted as » WORDS
0000: 00000000 

The data section always appears to be 0 on this event.

If you are seeing this even on your DHCP server, it means that the DHCP service on this machine has not been authorised in your Active Directory forest. It could mean that the service is on a machine which is not joined to a domain in a forest, but that there is another DHCP server on the same subnet which is joined to and authorised by a domain.

To authorise a DHCP server, you can either use the DHCP Manager GUI or you can use the netsh command like this
netsh.exe dhcp add server [servername.fqdn] [ip.add.re.ss]
Use the command netsh dhcp show server to display a list of authorised DHCP servers:

25 Servers were found in the directory service:

	Server [nyc-netd04.addom.fqdn.local] Address [10.120.120.26] Ds location: cn=10.120.120.26 

	Server [mk-addc11.addom.fqdn.local] Address [10.15.3.26] Ds location: cn=10.15.3.26 

	Server [mk-netd03.addom.fqdn.local] Address [10.15.3.33] Ds location: cn=10.15.3.33 

	Server [ad-addc11.addom.fqdn.local] Address [10.17.3.126] Ds location: cn=10.17.3.126 

	Server [db-addc11.addom.fqdn.local] Address [10.17.3.26] Ds location: cn=10.17.3.26 

	Server [ad-netd03.addom.fqdn.local] Address [10.18.3.33] Ds location: cn=10.18.3.33 

	Server [za-addc11.addom.fqdn.local] Address [10.19.3.26] Ds location: cn=10.19.3.26 

	Server [za-netd03.addom.fqdn.local] Address [10.19.3.33] Ds location: cn=10.19.3.33 

	Server [lon-netd02.addom.fqdn.local] Address [172.28.4.32] Ds location: cn=172.28.4.32 

	Server [tok-addc01.addom.fqdn.local] Address [10.14.3.26] Ds location: cn=tok-addc11.addom.fqdn.local 

	Server [db-netd03.addom.fqdn.local] Address [10.17.3.33] Ds location: cn=db-netd03.addom.fqdn.local 

	Server [hq-netd03.addom.fqdn.local] Address [10.11.3.33] Ds location: cn=hq-netd03.addom.fqdn.local 

	Server [cam-netd03.addom.fqdn.local] Address [10.16.3.33] Ds location: cn=cam-netd03.addom.fqdn.local 

	Server [tok-netd03.addom.fqdn.local] Address [10.14.3.33] Ds location: cn=tok-netd03.addom.fqdn.local 

	Server [hk-netd03.addom.fqdn.local] Address [10.10.3.33] Ds location: cn=hk-netd03.addom.fqdn.local 

	Server [hk-netd11.addom.fqdn.local] Address [10.10.3.31] Ds location: cn=hk-netd11.addom.fqdn.local 

	Server [lon-netd21.addom.fqdn.local] Address [172.28.4.33] Ds location: cn=lon-netd21.addom.fqdn.local 

	Server [nyc-netd03.addom.fqdn.local] Address [10.120.3.33] Ds location: cn=nyc-netd03.addom.fqdn.local 

	Server [nyc-netd11.addom.fqdn.local] Address [10.120.3.31] Ds location: cn=nyc-netd11.addom.fqdn.local 

	Server [cam-addc11.addom.fqdn.local] Address [10.16.3.26] Ds location: cn=cam-addc11.addom.fqdn.local 

	Server [sng-addc12.addom.fqdn.local] Address [10.190.3.27] Ds location: cn=sng-addc12.addom.fqdn.local 

	Server [sng-netd21.addom.fqdn.local] Address [10.190.3.40] Ds location: cn=sng-netd21.addom.fqdn.local 

	Server [ind-addc12.addom.fqdn.local] Address [10.50.3.27] Ds location: cn=ind-addc12.addom.fqdn.local 

	Server [ind-netd20.addom.fqdn.local] Address [10.50.3.33] Ds location: cn=ind-netd20.addom.fqdn.local 

	Server [hq-addc11.addom.fqdn.local] Address [10.11.3.26] Ds location: cn=hq-addc11.addom.fqdn.local 

Alternatively, you can see the authorised DHCP Servers in the Active Directory Sites and Services snap-in. To do this, open Sites and Services, click View, Show Services Node - then navigate to Services - NetServices. Another alternative is to use ADSI Edit. You'll need to connect to the naming context Configuration, then navigate to CN=NetServices,CN=Services,CN=Configuration,DC=addom,DC=fqfn,dc=local.