[154290] in North American Network Operators' Group
Re: [c-nsp] NTP Servers
daemon@ATHENA.MIT.EDU (Jimmy Hess)
Sat Jun 30 19:23:52 2012
In-Reply-To: <CAPiURgU7ReDZX8iP4Yi77sQzTg1x3rw7dBBCW2_M_E23mEwB5A@mail.gmail.com>
Date: Sat, 30 Jun 2012 18:23:14 -0500
From: Jimmy Hess <mysidia@gmail.com>
To: Grant Ridder <shortdudey123@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 6/30/12, Grant Ridder <shortdudey123@gmail.com> wrote:
> I don't understand why anyone would use windows server for anything that
> needed precision like time.
Probably because they realize that in a Windows domain, their domain
controllers already provide a SNTP service with the Windows NT PDC
Emulator providing authoritative time for windows time service, and
all those windows servers can be enabled as a NTP server with a small
configuration change, and Windows Domain clients are required to
be synchronized with this using the Windows time service, as a
condition for Kerberos authentication and domain logon, for the
configuration to be a supported one.
So, given you already have those capabilities and those constraints...
how do you justify deploying another server for providing a separate
time service, running a new OS, instead of just using the same one
for all hosts?
In many cases it's not "Why use a windows time server" that has to
be justified;
the burden of proof is to answer the question "What can you say that
indicates you should definitely not use a windows time server for the
application?" :)
--
-JH
