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: 11151 Source: DnsApi

The system failed to register network adapter with settings:
   Adapter Name : {4E880E65-2C4B-48E3-A44E-5065E0A869E4}
   Host Name : NORML
   Adapter-specific Domain Suffix :
   DNS server list :
   Sent update to server : None
   IP Address(es) :
The cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.  (The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.
Make sure the server or machine is pointing to the correct DNS server, as I had this problem where the Primary DNS was moved to another server, and this machine still had a DNS primary entry pointing to the decommissioned DNS server.
This issue may occur if you have implemented a single-label domain namespace. Microsoft does not recommend that you use Active Directory directory service domains with single-label DNS names.
I started to get this event on several Windows 2000 Pro workstations after updating them to SP4. In addition, I got Netlogon errors with EventID 5781 on a Windows 2000 Advanced Server with SP4 that is a DC for a subdomain in our forest. The Windows 2000 clients would not register themselves with their DNS server. It turns out that the problem resulted from the name of our root domain being "single-label". To be more specific, the internal DNS name of our root domain is <companyname> instead of <companyname>.com (or similar) as Microsoft recommends. After following the steps in MS KB article ME300684, which instructs you to make a registry change on each WinXP or Win2k SP4 client allowing it to perform dynamic DNS updates to a domain with a single-label DNS name, my errors went away.
This message indicates that the Windows 2000 computer is trying to register itself with a DNS server that does not support dynamic updates (i.e. Windows NT 4.0 DNS). You have to disable the requirement for the network card to register with the DNS.

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



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.