NtpClient was unable to set a domain peer to use as a time source because of discovery error.

Hi guys,
I saw the following error after moving the PDC role to another DC, and thus changing the Time Sync server:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)

Additionally to changing the ‘Type’ parameter to NT5DS, you will also have to change the ‘AnnounceFlags’ back to 10 (in hex).

Incoming search terms:

  • NtpClient was unable to set a domain peer to use as a time source because of discovery error
  • ntpclient was unable to set a domain peer
  • 0x800706e1
  • NtpClient was unable to set a domain peer to use as a time source because of discovery error NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter The error was: The entry is not found (0x800706E1)
  • The entry is not found (0x800706E1)
  • NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on \\ NtpClient will try again in 3473457
  • NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error
  • ntpclient was unable to set a domain
  • ntpclient was unable
  • ntp client will try again in 3473457

Leave a Reply to Anonymous Cancel reply