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: 5721 Source: NETLOGON

The session setup to the Windows NT or Windows 2000 domain Controller for the Domain <domain name> failed because the Domain Controller does not have an account for the computer <computer name>
This event and EventID 1055 from source Userenv appeared on a Dell PowerEdge 2850 running VMware windows beta. The NIC is an INTEL PRO 1000 MT. The virtual machines had trouble communicating with the domain controllers. For example, you would join the domain successfully but the computers would not should up in the COMPUTERS section of the Active Directory.
It turns out that the solution to the problem is to not use the drivers from the DELL site (dated 2004) but to get them from Intelís site (dated 2006). This solved my 2-week-old problem.
When you upgrade a LAN Manager backup domain controller (BDC) to a Windows NT BDC, the NetLogon service terminates and this event is written to the system log. This problem occurs if the computer name is the same as an existing user name. See ME130742 for a solution to this problem.

Upon starting, Netlogon attempts to find a domain controller (DC) for the domain in which its machine account exists. If a machine account cannot be found, this event will be logged. See ME266729 for more information about this issue.
This problem appears to be random and may occur on several BDCs. If you remove the BDC computer account and synchronize the BDC with the PDC, the problem is solved until the NetLogon service is restarted on the PDC. See ME154398 for more information about this issue.

You may also see this event when you try to log on to a Windows NT 4.0 domain from a Windows XP-based computer. See ME810497 for detailed information about this problem.
In my case, the computer account was suddenly disabled. I have not found a reason for that, but enabling the computer account and then rebooting the computer solved the problem.
There are several Microsoft articles with information about this event: ME150518, ME175024, ME160324, ME257623, ME258703 and ME295335.

We could not establish trust between Win2K and WinNT domains and we were getting Event id 5721 until we modified the registry as per ME296405.

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.