Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1046 Source: DhcpServer
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain <domain>, 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.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is DHCP?
What is BINL?
What is a DHCP Lease?
What is a directory service?
This also applies to a server that is acting as a DHCP server when you do not want it to act as one. You will get this error message if you have authorized a server to act as a DHCP server but have not created the scope. Uninstall the DHCP server in add/remove Windows components>Networking Services.
This issue may occur if there is an object conflict inside the Active Directory directory service configuration container. See ME938456 for information on how to resolve this issue.
See ME941464 for additional information about this event.
Our company bought a new server with Windows 2003 to replace our older Windows 2000 server. After exporting the DHCP database from Windows 2000 using the DHCPExim utility and importing to the Windows 2003 server, DHCP would not authorize on the new server. The old server was successfully removed, but the new server would only authorize for a minute and then automatically de-authorize in the MMC. It appeared authorized in the managed servers list, AD Sites and Services and the netsh "dhcp show servers" list, but appeared with a red arrow in the MMC, with the corresponding Service log error. Right-clicking the server in the MMC would only allow you to Unauthorize. Restarting the DHCP service on the new server fixed the problem.
I had this problem on Server 2003. The problem was cured by authorizing the DHCP server after it had been created. Within DHCP, select the server and then on the Actions menu select Authorize.
From a newsgroup post, from a Microsoft Partner: "This event occurs because the Boot Information Negotiation Layer (BINL) service must be authorized even though DHCP may not be running on the server and non-Windows 2000 DHCP servers are being used. If your environment includes other non-Windows 2000 DHCP servers, they must be authorized. Authorizing a server sets an attribute in the Active Directory that allows it to function. To authorize the client:
1. Load the Administrative tools from the Windows 2000 CD-ROM. This is a file named "Adminpak.msi". Initiate the installation by right-clicking the file and then clicking Install.
2. Once installed, load the DHCP snap-in by clicking Start, pointing to
Programs, pointing to Administrative Tools, and then clicking DHCP.
3. On the Action menu, click Browse Authorized Servers.
4. Add your server by clicking Add.
5. When you are finished, close the DHCP snap-in".
See MSW2KDB for additional information on this issue.
This problem is self explanatory. We ran into this problem on our network when one of our Jr. Network admins installed the server with a DHCP server, when we already have a DHCP server on the network. Other problems that may be causing this error are explained in the Event Description. See ME241484 for more detailed information.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated