Does anyone know why this doesn't work? I run into it quite a lot. Windows workstations and servers seem to ship with this value preconfigured in the registry for NTP. But it never works.
I read a thread from last summer in which the moderator (Mr. Arthur Xie) suggested it's caused by network settings, the firewall blocking it. But I'm always the guy who controls the firewalls, so if NTP were being blocked I would be able to see it. And without exception, whenever I edit the registry to change the value to time.nist.gov or time-a.nist.gov NTP instantly works. That's not consistent with a firewall issue.
Does time.windows.com require authentication? Does the server even exist? (DNS seems to resolve it.)
I guess I'm curious why Microsoft ships their operating systems with a time server preconfigured that doesn't work.
Ben
I read a thread from last summer in which the moderator (Mr. Arthur Xie) suggested it's caused by network settings, the firewall blocking it. But I'm always the guy who controls the firewalls, so if NTP were being blocked I would be able to see it. And without exception, whenever I edit the registry to change the value to time.nist.gov or time-a.nist.gov NTP instantly works. That's not consistent with a firewall issue.
Does time.windows.com require authentication? Does the server even exist? (DNS seems to resolve it.)
I guess I'm curious why Microsoft ships their operating systems with a time server preconfigured that doesn't work.
Ben