Windows 10: W11 Pro NTP Client Fails

Discus and support W11 Pro NTP Client Fails in Windows 10 Gaming to solve the problem; I just upgraded my GPU from Nvidia to AMD which caused some random crashing, even after using gpu driver removal tool, so I did a clean install of W11... Discussion in 'Windows 10 Gaming' started by Randy W.Sims, Jan 30, 2023.

  1. W11 Pro NTP Client Fails


    I just upgraded my GPU from Nvidia to AMD which caused some random crashing, even after using gpu driver removal tool, so I did a clean install of W11 Pro which seems to have fixed it. However the Windows NTP Client is not working now. It did work before."An error occurred while Windows was synchronizing with...."I'm attempting to sync to a local router that is verified working by other devices on my network, but the standard remote ntp servers also fail.I found this python script that retrieves time from ntp server and it works correctly from the same desktop both to local and remote ntp serv

    :)
     
    Randy W.Sims, Jan 30, 2023
    #1

  2. Why is NTP client using local UDP port 123 - fails to sync time

    Hello,

    My Windows 10 installation fails to sync network time.

    It looks like the windows SNTP client uses UDP port 123 for both source and destination and my ISP is blocking local port 123 in all likelihood.

    NTP updates work on linux distros and I also tried a tool called "NetTime" on Win10 which works because the source port is a random unprivileged port in the 60,000 range.

    I am posting here to make a request to change the behaviour of Win10 NTP client to use a random higher port (unprivileged) so people do not face this issue - I have seen umpteen complaints online of people not being able to sync network time on Windows.

    Thank you.

    edit: I tried sync with a different ISP and it works. So I have posted on answers.microsoft.com asking whether the client side bind port can be changed to a random high value to avoid ISP blocks.

    I observed the port behavioural anomaly using the WireShark network traffic monitor.

    It looks like because Win10 can also act as an NTP server, the port 123 must be hardcoded somewhere causing it to be used as client side source bind/accept port and an ISP like mine is blocking that port on the client/incoming side.
     
    Vishal Rao, Jan 30, 2023
    #2
  3. Surface Pro 3 with Windows 11 Insider Preview OS vs. Surface Pro 4 with W10 Pro that cannot upgrade to W11

    Two questions:

    1. My Surface Pro 3 continues to download and install W11 updates on the Insider Preview Channel. How long might I expect to have access to updates? In other words, will I lose access and be forced to revert to W10?
    2. Can I enroll in Windows Insider Preview on my Surface Pro 4 and upgrade to W11 Insider Preview?
    I'm finding more and more to like about W11 and would certainly prefer to continue to move forward, not backward.
     
    GlenHemingson, Jan 30, 2023
    #3
  4. AMDCam Win User

    W11 Pro NTP Client Fails

    NTP Help

    Hi guys, I know this is not the site for bull**** networking but you've been the most reliable tech site I've ever been on for any computer stuff. So I've got a question about a network. I'm with the Marines, and we're running secure networks branching off from everywhere. I mean I'm in Japan right now. But we're trying to sync our hardware (Cisco devices, switches and routers) to NTP. I created a test setup with a router, easy as pie to sync that, but it was a direct connection from the router to our linksys gateway directly to the ISP. But in the real setup, we pull NTP data on every piece of hardware I set up to sync...we just don't sync. "Show NTP associations" shows full reach, stratum 3 servers all working perfect but our offsets are off (I'd love to know what the numbers for offset mean), but show ntp status shows no synchronization, not even a hint that it realizes it's got a working NTP server to pull off of. NTP is supposed to be an easy setup, but for over a month now myself and everyone I know have tried everything from our end to get a sync and we got nothing. Maybe it's not close enough to the NTP time, so we set the time and timezone a billion times, nothing there. I'm assuming since we can pull data from NTP servers, the port's gotta be open right? If it's impossible to sync because somewhere along the way a firewall is blocking it's UDP port, that's totally cool, then I'll have an excuse as to why we're gonna have to manually set clocks. But the fact that it pulls information (diagnostics at least, ping, offset, freq, stratum) I feel like we should be able to pull time, we just can't for some reason. If you guys have any idea what I can do please let me know. Thank you
     
    AMDCam, Jan 30, 2023
    #4
Thema:

W11 Pro NTP Client Fails

Loading...
  1. W11 Pro NTP Client Fails - Similar Threads - W11 Pro NTP

  2. Switching NTP Client from one NTP server to another

    in Windows 10 Gaming
    Switching NTP Client from one NTP server to another: Hello all,I am struggling a bit with NTP synchronization and seeking some help.I configured a windows server as an NTP server. And I configured several clients to sync their time with this server.Now I am finding a small skew between one of the clients PC-A and the server...
  3. Switching NTP Client from one NTP server to another

    in Windows 10 Software and Apps
    Switching NTP Client from one NTP server to another: Hello all,I am struggling a bit with NTP synchronization and seeking some help.I configured a windows server as an NTP server. And I configured several clients to sync their time with this server.Now I am finding a small skew between one of the clients PC-A and the server...
  4. Switching NTP Client from one NTP server to another

    in Windows 10 Network and Sharing
    Switching NTP Client from one NTP server to another: Hello all,I am struggling a bit with NTP synchronization and seeking some help.I configured a windows server as an NTP server. And I configured several clients to sync their time with this server.Now I am finding a small skew between one of the clients PC-A and the server...
  5. Windowsbasierte NTP-Server und nicht windowsbasierte Clients

    in Windows 10 Gaming
    Windowsbasierte NTP-Server und nicht windowsbasierte Clients: Hallo zusammen,ich verstehe das Verhalten der Stammabweichung von Windows NTP-Servern nicht ganz.Ich würde gerne ein Netzwerk aus windowsbasierten und nicht windowsbasierten Geräten aufbauen.Dazu möchte ich einen Rechner mit Windows 10 Enterprise LTSC Version 1809 als...
  6. Windowsbasierte NTP-Server und nicht windowsbasierte Clients

    in Windows 10 Software and Apps
    Windowsbasierte NTP-Server und nicht windowsbasierte Clients: Hallo zusammen,ich verstehe das Verhalten der Stammabweichung von Windows NTP-Servern nicht ganz.Ich würde gerne ein Netzwerk aus windowsbasierten und nicht windowsbasierten Geräten aufbauen.Dazu möchte ich einen Rechner mit Windows 10 Enterprise LTSC Version 1809 als...
  7. Windowsbasierte NTP-Server und nicht windowsbasierte Clients

    in Windows 10 Network and Sharing
    Windowsbasierte NTP-Server und nicht windowsbasierte Clients: Hallo zusammen,ich verstehe das Verhalten der Stammabweichung von Windows NTP-Servern nicht ganz.Ich würde gerne ein Netzwerk aus windowsbasierten und nicht windowsbasierten Geräten aufbauen.Dazu möchte ich einen Rechner mit Windows 10 Enterprise LTSC Version 1809 als...
  8. W11 Pro NTP Client Fails

    in Windows 10 Software and Apps
    W11 Pro NTP Client Fails: I just upgraded my GPU from Nvidia to AMD which caused some random crashing, even after using gpu driver removal tool, so I did a clean install of W11 Pro which seems to have fixed it. However the Windows NTP Client is not working now. It did work before."An error occurred...
  9. Log NTP client pull requests

    in Windows 10 Ask Insider
    Log NTP client pull requests: Hello, I've setup a windows 10 pro as an NTP server with a raspberry pi as a client. And I want to log the requests that the raspberry pi is making in windows. Is there any way to do it? submitted by /u/Mundane_Bid_7438 [link] [comments]...
  10. Why is NTP client using local UDP port 123 - fails to sync time

    in Windows 10 Network and Sharing
    Why is NTP client using local UDP port 123 - fails to sync time: Hello, My Windows 10 installation fails to sync network time. It looks like the windows SNTP client uses UDP port 123 for both source and destination and my ISP is blocking local port 123 in all likelihood. NTP updates work on linux distros and I also tried a tool...