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

  • Question

  • Hi,

    I have various error logs in event viewer that captures error messages such as below:

    "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 processing of Group Policy failed. Windows attempted to read the file \\....\gpt.ini from a domain controller and was not by one or more of the following:

    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another doamin controller has not replicated to the current domain controller)
    c) The distributed File System (DFS) client has been disabled."

    Appreciate any advise.

    Thank you.

    Thursday, December 12, 2013 9:10 AM


All replies

  • Hi,

    Did this issue occur on Window 7 client site or windows Server site?

    Please confirm if this solution is applied to your issue:

    Event ID 129 - Microsoft-Windows-Time-Service


    Karen Hu
    TechNet Community Support

    • Marked as answer by Karen Hu Tuesday, January 7, 2014 4:43 AM
    Monday, December 16, 2013 8:18 AM
  • Hi Karen,

    This issue occurs in Windows 7 Client. Thanks for the advise, I will try and revert.

    Tuesday, December 17, 2013 8:29 AM
  • Hi,

    Thanks for your feedback. Keep update in order to provide further help.

    Karen Hu
    TechNet Community Support

    Wednesday, December 18, 2013 3:03 AM
  • Seriously?  Thanks for the feedback and that's the end of it and it's been 3 years!?!?!?!?

    Why does Microsoft expect US, the end users, to solve all their problems?

    Wednesday, August 3, 2016 1:29 PM