Event Id | 24 |
Source | Microsoft-Windows-Time-Service |
Description | Time Provider NtpClient: No valid response has been received from domain controller %1 after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: %2 |
Event Information | According to Microsoft : Cause : This event is logged when no valid response has been received from domain controller after 8 attempts to contact it. Resolution : Address discoverability issues The Windows Time service cannot discover the configured time source peer. Ensure that the time source peer is online and available. There should be other events in Event Viewer that indicate that there is a problem locating a domain controller. Review those event messages and resolve them as appropriate. When you have resolved them, resynchronize the local Windows Time service with the time source peer. Perform the following procedure on the computer that is logging the event to be resolved. To perform this procedure, you must have membership in Administrators or you must have been delegated the appropriate authority. To resynchronize the client with the time source peer:
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To verify that the Windows Time service is synchronizing correctly:
|
Reference Links | Event ID 24 from Source Microsoft-Windows-Time-Service |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.