[AusNOG] NTP Best Current Practices Internet Draft
markzzzsmith at gmail.com
Sat Feb 2 12:53:59 EST 2019
On Sat, 2 Feb 2019 at 12:35, Michael Junek <michael at juneks.com.au> 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 <ausnog-bounces at lists.ausnog.net> on behalf of O'Connor, Daniel <darius at dons.net.au>
> Sent: Saturday, 2 February 2019 12:31
> To: Mark Smith
> Cc: <ausnog at lists.ausnog.net>
> Subject: Re: [AusNOG] NTP Best Current Practices Internet Draft
> > On 2 Feb 2019, at 11:48, Mark Smith <markzzzsmith at gmail.com> 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
> AusNOG at lists.ausnog.net
More information about the AusNOG