Export (0) Print
Expand All

Manual Time Source Acquisition

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

An Active Directory forest has a predetermined time synchronization hierarchy. The Windows Time service (W32time) synchronizes time between computers within the hierarchy, with the most accurate reference clocks at the top. If more than one time source is configured on a computer, Windows Time uses Network Time Protocol (NTP) algorithms to select the best time source from the configured sources, based on the computer’s ability to synchronize with that time source. The Windows Time service acquires a time source peer from the domain heirarchy. By default, computers running the Windows Time service attempt to synchronize time only with a domain controller or a manually configured time source. Currently, the Windows Time service is synchronizing with a manually configured time source peer (as opposed to a time source peer from the domain hierarchy).

Events

Event ID Source Message

16

Microsoft-Windows-Time-Service

Time Provider NtpClient: An unexpected error occurred during DNS lookup of the manually configured peer '%1'. This peer will not be used as a time source. The error was: %2

17

Microsoft-Windows-Time-Service

Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer '%1'. NtpClient will try the DNS lookup again in %3 minutes. The error was: %2

47

Microsoft-Windows-Time-Service

Time Provider NtpClient: No valid response has been received from manually configured peer %1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: %2

48

Microsoft-Windows-Time-Service

Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer '%1'. NtpClient will continue to try the DNS lookup every %3 minutes. This message will not be logged again until a successful lookup of this manually configured peer occurs. The error was: %2

134

Microsoft-Windows-Time-Service

NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on '%3'. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1

135

Microsoft-Windows-Time-Service

NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '%3'. The same time source '%4' has been either specified as manual peer in NtpServer or selected as domain peer. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1

136

Microsoft-Windows-Time-Service

NtpClient was unable to set a manual peer to use as a time source because of an unexpected error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1

137

Microsoft-Windows-Time-Service

NtpClient succeeds in resolving manual peer %1 after a previous failure.

Related Management Information

Time Source Peer

Active Directory

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft