Ntpclient Was Unable To Set A Domain Peer

ntpclient was unable to set a domain peer 2023 April

Why is ntpclient not synchronizing time with a domain peer?

Currently, the Windows Time service is synchronizing time with a time source peer from the domain hierarchy. NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter.

Why can’t I set a domain peer as a time source?

NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1 The Windows Time service cannot discover the configured time source peer. Ensure that the time source peer is online and available.

What is the event ID of ntpclient?

Event ID 35 : The time service is now synchronizing the system time with the time source x (ntp.d| [::]:123-> [x). Event ID 37 : The time provider NtpClient is currently receiving valid time data from x (ntp.d| [::]:123-> [x). Event ID 138: NtpClient succeeds in resolving domain peer xafter a previous failure.

What if there is no NTP server out there?

If there is no NTP server out there, you’ll get an answer such as error: 0x80070584 The delay (d) is the delay between computers and the offset is the time difference between the 2 computers


Posted

in

by

Tags:

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *