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: 1097 Source: Userenv

Windows cannot find the machine account. <error description>
See ME955410 for a hotfix applicable to Microsoft Windows Server 2003.

See WITP79913 to see possible reasons of this events appearance.
For Windows 2003 apply hotfix ME913463 to resolve this problem.
This issue may occur if the client's computer system clock is set to a different time than the time that is set on the domain controller computer. See ME886516 to solve this problem.

As per Microsoft: "This error is usually caused by a missing or corrupt computer account in the domain". See MSW2KDB for more information on this event.

Additional information can be obtained by enabling user environment debug logging. See ME221833 for information on how to enable user environment debug logging.
Error: "The clocks on the client and the server machines are skewed." From a newsgroup post: "The time sync issues are caused by the clocks on your DC and client showing different times; you might want to do a net time /set."

Error: "No authority could be contacted for authentication." - See ME832215.
Error: "The clocks on the client and the server machines are skewed." - Use the net time /set even though the times showing are identical.

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.