On Sat, 2 Feb 2019 at 12:35, Michael Junek <[email protected]> wrote: > > Thats correct. Windows only has a SNTP client implemented, and not an NTP > client. As such, it can only query a single NTP server, and does not have the > algorithms to determine the accuracy of the time sources. > >
If that's the case, I'd buy/find a 3rd party NTP client for my Windows boxes. (Don't have any so don't have this problem.) > > > ________________________________________ > From: AusNOG <[email protected]> on behalf of O'Connor, Daniel > <[email protected]> > Sent: Saturday, 2 February 2019 12:31 > To: Mark Smith > Cc: <[email protected]> > Subject: Re: [AusNOG] NTP Best Current Practices Internet Draft > > > On 2 Feb 2019, at 11:48, Mark Smith <[email protected]> wrote: > > The problem that occurred with 0.au.pool.ntp.org proving bad time > > wouldn't have had an effect if the Windows domain controller had at > > least 2 other NTP time sources. > > The behaviour of OPs system implies that a PDC does not use more than one > clock source. > > If that is true (I have no idea, but googling suggests it may be so) then you > are going to end up relying on a single time server. In that case you are > probably better firing up a tiny Linux VM running only ntpd (or chrony etc > etc) which is configured for multiple pool servers and then point your DCs at > that. > > It does seem pretty ridiculous than Windows server can't behave more sensibly > though.. > > -- > Daniel O'Connor > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > > _______________________________________________ > AusNOG mailing list > [email protected] > http://lists.ausnog.net/mailman/listinfo/ausnog _______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog
