NTP problems/time.windows.com?
I haven't personally seen anything about this across my fleet; anyone here seeing tracks from it? http://www.ibtimes.com/how-change-ntp-server-microsofts-timewindowscom-cause... Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
Reddit has a big post on it. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Apr 3, 2017 9:25 PM, "Jay R. Ashworth" <jra@baylink.com> wrote:
I haven't personally seen anything about this across my fleet; anyone here seeing tracks from it?
http://www.ibtimes.com/how-change-ntp-server-microsofts- timewindowscom-causes-computers-display-wrong-time-2519884
Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
On Tue, Apr 04, 2017 at 01:23:58AM +0000, Jay R. Ashworth wrote:
I haven't personally seen anything about this across my fleet; anyone here seeing tracks from it? -snip- http://www.ibtimes.com/how-change-ntp-server-microsofts-timewindowscom-cause... -snip-
"One explanation that has gained traction online as users scramble for answers is the suggestion that a cluster of time servers may have lost connection with an external source that syncs the time and date." Haven't seen it, but if people are reporting sudden hour offsets, on the first Monday in April, I'd bet on a DST implementation bug that hijacked the system clock on their servers. This doesn't look like the sort of error you'd get with a free running clock. --msa
Majdi S. Abbas <msa@latt.net>:
Haven't seen it, but if people are reporting sudden hour offsets, on the first Monday in April, I'd bet on a DST implementation bug that hijacked the system clock on their servers.
This doesn't look like the sort of error you'd get with a free running clock.
I concur, about the one-hour shift anyway. The random garbage times aren't really likely either - jumps that large would tend to get the source rejected as a falseticker. It's a weird set of symptoms that rather looks as if they hit two different failure modes at once. Dunno. One of our NTPsec devs posted the link on one of our project channels and suggested maybe we ought to call M$ with an offer of help... -- <a href="http://www.catb.org/~esr/">Eric S. Raymond</a> Please consider contributing to my Patreon page at https://www.patreon.com/esr so I can keep the invisible wheels of the Internet turning. Give generously - the civilization you save might be your own.
----- Original Message -----
From: "esr" <esr@thyrsus.com> To: "Majdi S. Abbas" <msa@latt.net> Cc: "jra" <jra@baylink.com>, "North American Network Operators' Group" <nanog@nanog.org> Sent: Monday, April 3, 2017 10:34:21 PM Subject: Re: NTP problems/time.windows.com?
Majdi S. Abbas <msa@latt.net>:
Haven't seen it, but if people are reporting sudden hour offsets, on the first Monday in April, I'd bet on a DST implementation bug that hijacked the system clock on their servers.
This doesn't look like the sort of error you'd get with a free running clock.
I concur, about the one-hour shift anyway. The random garbage times aren't really likely either - jumps that large would tend to get the source rejected as a falseticker.
It's a weird set of symptoms that rather looks as if they hit two different failure modes at once. Dunno.
It's not entirely clear whether it's *entirely* MSWin clients; I can't imagine anything being pointed at those servers that wasn't, though, cause who the hell would? Anyone smart enough to manually select NTP upstreams isn't going *there*... Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
participants (4)
-
Eric S. Raymond -
Jay R. Ashworth -
Josh Luthman -
Majdi S. Abbas