Non grid related - but I have two windows servers on the internet - one is quite old and the clock drifts quite a bit. I was thinking I could set the good one to sync to NTP time servers occasionally, then use PTPSync to sync to keep the drifting one synced very closely to the other across my private management LAN back end.
I decided to test on a couple local win 10 pc’s before deploying to my servers to get a feel for the software. I set up one machine (lets call it PC1) without the -g switch so, if I understand correctly, it would broadcast it’s time to the rest of the network. I set the other PC (lets call it PC2) with default settings. I also turned windows default time syncing off.
At first, the PC2 synced as expected to PC1. Later I noticed PC2 seemed to be drifting, about a second slow after only a few hours & didn’t seem to be correcting itself. I checked my settings and and initialized - no effect. I decided to shut down the service on both PCs and restart to see if I could force a sync to get the PCs back close - this is when the clock PC2 started freaking out and flying into the future. I shut down the PTP service on both machines but it did not affect PC2 and the clock kept flying crazily into the future while the task manager showed “system interrupts” using 100% cpu.
The night before I did the same test but used a VMware win10 virtual as “PC2” - it did the same thing after messing with the PTP service a bit - I had chalked that up to maybe something iffy with the VMWare clock as I’ve run into issues with that before with linux instances.
The PC2 Machine is a Dell Precision 7510 laptop running an updated copy of Win10 if that helps. I uploaded a video of the time issue on PC2 - a reboot did stop the issue, luckily. https://www.youtube.com/watch?v=b8a66ghhGyQ