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

The system failed to register host (A) resource records (RRs) for network adapter
with settings:
Adapter Name : <adapter name>
Host Name : <host name>
Primary Domain Suffix : <domain>
DNS server list: <DNS servers>
Sent update to server : None
IP Address(es): <IP address(es)>

The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. For specific error code, see the record data displayed below.
0000: 00002329
In my case, I could log in via the console with my domain credentials, but RDP would error out with "Logon rejected for <user> Unable to obtain Terminal Server User Configuration. Error: The RPC server is unavailable."
I could browse to other computers via Network Places, but was getting Access Denied when I'd try to browse to the problem machine from another box. I was also getting Event ID 1219 from Winlogon, Event ID 5719 from Netlogon, and Event ID 18 from W32Time. I tried every fix out there from all of the different sites (including with no success. Finally, I looked at Winsock2 and noticed that it was corrupt! The server was a Windows 2003 Enterprise SP2 and I ran "netsh winsock reset" at the command prompt, which fixed the issue. In my case, I had to re-add the server to the domain, but that's only because I''d just removed it to troubleshoot. You may be able to get away with just resetting winsock and rebooting the server. You can find more information about troubleshooting Winsock problems at ME811259.
Running nslookup <netbios_name_of_server> returned no info. Attempts to run ipconfig /flushdns and ipconfig /registerdns resulted in this event being logged. To resolve this problem, configure the firewall to open port 53 UDP. Then run dcdiag /test:registerindns /dnsdomain:FQDN  /v.

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.