Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1051 Source: DhcpServer

Source
Level
Description
The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: <domain name>.

Data: 0000: 00 00 00 00
Comments
 
See the links to "Troubleshooting network problems", "Dell Support Document Number: TT1089673" and "JSI Tip 3958" to solve this problem.
I found that there were two of the same servers listed in NETSERVICES in AD sites and services. I delete the bad one and the DHCP server came back on line.
See the link to "EventID 1051 from source DHCP" for information on this event.
The authorization continues to fail although you exercise ME306925 and ME303351. A possible reason could be a misconfigured DNS entry in the TCP/IP properties. If the DNS is running on the same machine, verify that the IP of the local NIC(local DNS) is listed in the Preferred DNS server box.
(On a multihomed system this NIC must be listed at first under Advanced Settings in Adapters and Bindings.)
If the DNS is running somewhere in the LAN, verify that the IP address of that machine is listed in the Preferred DNS server box. In both cases perform the steps listed in ME306925 (Deleting and Reauthorizing the DCHP Servers)after you you change the DNS settings. In rare cases you have to reboot the system. In very rare cases you have to remove and reinstall DHCP.(Take care about the SP version).
A Windows 2000-based DHCP server in a Active Directory configuration needs to be authorized in order to serve DHCP requests. Use the DHCP administration interface to authorized the server (if the server is legit).


This error started occuring after I installed in the network a firewall acting as a DHCP server.
I had the same problem, but my Server was authorized. The Microsoft article ME299363 helped me to solve the problem.
This problem can occur if the LDAP filter request for the DHCP server in Active Directory was incorrect. To work around this problem, use either of the following methods:
Change the IP address so that is has less than 12 digits.
Change the hostname of the DHCP server in lowercase, or create the DHCP server hostname value in Active Directory in uppercase.
See ME303525 link below.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...