Am Dienstag, den 10.04.2007, 12:18 -0500 schrieb Ryan Malayter: > It appears (at least from my location in Chicago, USA) that > time.windows.com is broken and unsynchronized. See below for details. > > First, can anyone outside the continental USA verify that > time.windows.com is broken globally? > > 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... >
Here the same (Germany, time.windows.com is 207.46.197.32, offset 148, stratum 16) I think it's not a real problem, offset=148 doesn't mean 2 minutes but 140 milliseconds (afaik...), so no user will notice it until they fix it... Max _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
