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

The system failed to update and remove registration for the network adapter with settings:
Adapter Name : {_adapter_number_}
Host Name : webapp
Adapter-specific Domain Suffix :
DNS server list:
Sent update to server : None
IP Address(es) :
The reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time.
From a newsgroup post: "Sometimes the following procedure cleared the error:
1. Boot into save mode
2. From the device manager uninstall the Nic
3. Boot normal, the Nic will be reinstalled
4. Type from the command prompt:
ipconfig /flushdns
ipconfig /registerdns
Wait about 15 minutes and look in the Event log for related events".
In my case, this event occurred in the following scenario. The machine was a member of an Active Directory Domain. It used an Internal NIC card on the first domain. It had to be moved to a new domain, where it could NOT be a member of the same domain and with a new user that was not a member of the original domain.  The new domain would be wireless.
After moving, a wireless NIC was then installed and made functional on the same subnet as the new domain that it was going to join. The Internal NIC was "uninstalled (but not removed)". Upon reboot, it was installed and "disabled". At this point it was changed from the OLD domain to a workgroup. On reboot, it was joined to it's new domain. The old users were deleted using the "user profiles" tab, under system applet. The error messages were a result of the old entries for the Internal NIC being left in the registry. I did a search for the entries based on the Adapter's original name (ie: B71BA72D-E261-4D21-9C9D-6AA702E8663B)and removed all references - including the entire key when necessary (in most instances it is necessary.. but not all). I also searched for the old domain name and original user, removing OR renaming them when "applicable".
This is not for the weak of heart but it does work. Error messages have never returned, the machine is on the new domain and everything works fine. There were some other error messages (dnsapi related) that this cleared as well.
This error occurred on servers when the DNS server was unavailable.
On a Win2k computer with this problem, it was resolved by completely uninstalling TCP/IP, then reinstalling and reconfiguring it to its original settings. After doing this, the system worked perfectly.

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.