On Apr 10, 2007, at 10:18 AM, Ryan Malayter wrote: > First, can anyone outside the continental USA verify that > time.windows.com is broken globally?
I'm not outside the continental USA, but yes, I can confirm that they are returning a stratum-16 reply, indicating that the timeserver is not properly synchronized. This may not be a problem with Microsoft itself, but with Akamai's geographical distribution service, which apparently is being used to do load-balancing for "time.windows.com": 23% ntpdate -q -d time.windows.com 10 Apr 10:23:57 ntpdate[5566]: ntpdate [EMAIL PROTECTED] Mon Jan 30 08:32:53 PST 2006 (1) server 207.46.197.32, stratum 16, offset 20.064169, delay 0.06834 10 Apr 10:23:57 ntpdate[5566]: adjust time server 17.254.0.27 offset -0.057350 sec 24% ntpq -p time.windows.com siweb.microsoft.akadns.net: timed out, nothing received ***Request timed out > Second, assuming Microsoft doesn't fix this quickly, and is actually > intentionally depracating the time.windows.com service, what does this > mean for the pool? Will the pool see a sudden surge of Windows clients > looking for better time? Most people won't notice, but surely many > thosands of Windows users will see that their clock is more than two > minutes off... It will be some time (ahem :) before time.windows.com going down has a noticable impact upon normal Windows clients. It's likely that this is a temporary problem and that it will be fixed shortly, at least if someone notifies Microsoft and/or Akamai, and thus will not have much of an impact upon the NTP pool... -- -Chuck _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
