NtpClient connection problem


  1. Posts : 308
    Windows 10
       #1

    NtpClient connection problem


    I am getting this error.

    Event ID 134
    NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
    Can I use something different than 'time.nist.gov,0x9' ? How? Thanks.
      My Computer


  2. Posts : 30,077
    Windows 11 Pro x64 Version 23H2
       #2

    Hi Curious

    Right click clock > Adjust Date & Time > Additional Date and Time & REgional Settings > Set Time & Date > Internet Time Tab > Change Settings > use time.windows.com.

    I saw the nist.gov is also listed, no 0x9

    I use time. windows.com
      My Computer


  3. Posts : 308
    Windows 10
    Thread Starter
       #3

    Thank you.
    (no thumbs up on the mobile web site).
      My Computer


  4. Posts : 30,077
    Windows 11 Pro x64 Version 23H2
       #4

    That's cool. As long as it is fixed.

    Can you mark it solved on mobile?
      My Computer


  5. Posts : 308
    Windows 10
    Thread Starter
       #5

    Nope. I'll do it next time I'm on the laptop.
      My Computer


  6. Posts : 103
    Windows 7-pro-sp1 and windows 10-pro-1803
       #6

    Caledon Ken said:
    Hi Curious

    Right click clock > Adjust Date & Time > Additional Date and Time & REgional Settings > Set Time & Date > Internet Time Tab > Change Settings > use time.windows.com.

    I saw the nist.gov is also listed, no 0x9

    I use time. windows.com
    I get the same stuff both for windows time server and for NIST servers. Been like this ever since 1709 came.
    Windows filtering platform blocks with that "can't resolve DNS", usually on 2 packets, and then it works and time updates just fine.
    I suspect windows time service doesn't wait sufficiently long (in microseconds) for the DNS replies from port 53, or doesn't assign local port for receiving quickly enough.
      My Computer


  7. Posts : 308
    Windows 10
    Thread Starter
       #7

    Ah well. One step forward and 2 steps back.
    so far so good.
      My Computer


  8. Posts : 308
    Windows 10
    Thread Starter
       #8

    91fw said:
    I get the same stuff both for windows time server and for NIST servers. Been like this ever since 1709 came.
    I have Windows 10 home. How do I find out which version number (1709 ?) I have? Thanks.

    Please ignore. DuckDuckGo gave me the answer. I have 1709.
      My Computer


  9. Posts : 30,077
    Windows 11 Pro x64 Version 23H2
       #9

    In case this was different

    Windows key + R, type winver, enter

    This gives version and build. This link shows you history of builds.

    https://support.microsoft.com/en-us/help/4043454
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:45.
Find Us




Windows 10 Forums