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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity.
|English: Request a translation of the event description in plain English.|
If you have a Windows XP-based computer that is a member of a Microsoft Windows NT 4.0-based domain, see ME314345. Also, check ME216734 to find out how to configure an authoritative time Server in Windows 2000 and ME314054 to find out how to configure an authoritative time Server in Win XP.
ME555225 shows how to manually synchronize time between domain client and local time server.
See the link to "Configuring the Windows Time Service" for information on setting up an authoritative time server for a Windows Server 2003-based network running Active Directory.
I started getting this error after I demoted one domain controller and added a new one on the network. After researching quite a bit, I found out that some of the _msdcs/DC, GC, PDC records in the DNS server still had entries for the old domain controller. I deleted all the records of the old Domain Controller and the warning disappeared.
Make sure that UDP port 123, used by the Network Time Protocol is opened between the time server and the computer reporting the error.
The time services has not been able to connect to a time source. If a time source is configured check the connectivity between the computer reporting the error and the time server.
As per Microsoft: This issue can occur because of repeated network issues or if the Time service has been unable to find a domain controller to synchronize with for a long time. To reduce network traffic, the Time service will wait 960 minutes before it tries again, and no synchronization takes place during this interval, even if network connectivity is restored after being in a disconnected state for an amount of time that is less than the synchronization interval. See ME312534
|Private comment: Subscribers only. See example of private comment|
|Links: ME216734, ME258059, ME312534, ME314054, ME314345, ME555225, Configuring the Windows Time Service, NIST Internet Time Servers|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated