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...
>ntpdate -q -d time.windows.com
10 Apr 12:12:35 ntpdate[2244]: ntpdate [EMAIL PROTECTED] Dec 11 20:58:13 (UTC+01
0) 2005 (3)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
207.46.232.182: Server dropped: strata too high
server 207.46.232.182, port 123
stratum 16, precision -6, leap 11, trust 000
refid [207.46.232.182], delay 0.11935, dispersion 0.00684
transmitted 4, in filter 4
reference time: c989ae87.10189374 Fri, Feb 23 2007 12:18:47.062
originate timestamp: c9c64469.ec000000 Tue, Apr 10 2007 12:14:17.921
transmit timestamp: c9c64403.ddc118af Tue, Apr 10 2007 12:12:35.866
filter delay: 0.13498 0.11935 0.13498 0.13498
0.00000 0.00000 0.00000 0.00000
filter offset: 102.0087 102.0009 102.0087 102.0087
0.000000 0.000000 0.000000 0.000000
delay 0.11935, dispersion 0.00684
offset 102.000955
10 Apr 12:12:35 ntpdate[2244]: no server suitable for synchronization found
--
RPM
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
