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: 14 Source: W32Time

The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 15 minutes.
See the information about this event in this article: EV100160.
In my case, this problem was caused by the "AEGIS Protocol (IEEE 802.1x) v" driver that was probably installed together with the ASUS WLAN driver. This event occurred together with Event ID 5719 from source NETLOGON, Event ID 29 from source W32Time and Event ID 1054 from source Userenv. After disabling this item in the network card properties, all these errors were gone.
See the link to "How to fix time synchronization errors" for details on time synchronization errors.
To fix this problem I stopped and restarted the w32time service on the PDC using “net stop w32time” and “net start w32time”.
Network connectivity has been lost between the ntpclient and the domain controller.

This happens when W2K/XP workstations are used with NT4 DC(s) because NT4 does not have a time service, so cannot provide time. Workaround: install a SNTP/NTP service for NT4, such as TimeServ from NT4 Resource Kit Supplement 4.

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.