On 2010-11-12, Harry <[email protected]> wrote: > On Nov 10, 9:36 pm, Steve Kostecke <[email protected]> wrote: > >> Which associations are you attempting to "secure"? LAN client to LAN >> server? LAN server to remote time server? > > "LAN server to remote time server." So, this LAN host will be a client > of the remote time server but will act as a local time server to other > hosts on the LAN.
OK. I have to question the wisdom of using only one remote time server. As has been stated elsewhere you're better off using a large enough set of remote time servers (i.e. 4 or more) to allow NTP to detect and discard "false-tickers" (bad clocks). Multiple time sources also provide you with redundancy in the event of server failure/connectivity issues. If this is a case of regulatory compliance then you really ought to have the budget to solve the problem correctly (with GPS-synced NTP applicances). -- Steve Kostecke <[email protected]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
