A mysterious issue is affecting the default Windows NTP server (time.windows.com), according to multiple complaints coming from Reddit and Twitter users, screwing up everyone's computer clocks.
Based on reports, the time.windows.com NTP server is sending Windows users the incorrect time, sometimes off by seconds, but in other cases, off even by hours. The issue was spotted today, April 3, early in the morning, and is ongoing for at least 10 hours.
The impact was felt immediately by servers that rely on the Windows NTP service to schedule and execute tasks. Unhappy admins found their servers launching routines early or too late, botching scripts and crashing their applications.
[...] UPDATE: A Microsoft representative acknowledged the issue. "We investigated and quickly resolved the issue our time service experienced," the Microsoft spokesperson wrote in an email. Tests carried out by Bleeping Computer confirmed the Windows NTP serrvice is up and running at the time of this update.
Source: Bleeping Computer
(Score: 2) by driverless on Thursday April 06 2017, @02:59PM (1 child)
If you've got access to Silicon Chip magazine, you can find an article on DIY'ing it here [siliconchip.com.au]. I went for the Tindie option because it was pre-built and tested so I wouldn't have to worry about things not working properly. Since the 5680s are recycled from things like old cellphone towers they can be of variable quality and remaining operational life, and sometimes a bit finicky to get going. The painful thing is that if it doesn't work fairly quickly you can end up sinking an awful lot of time into it trying to figure out what's wrong.
(Score: 2) by LoRdTAW on Thursday April 06 2017, @03:12PM
Thank you for the information.