Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Keeping Time With Your Network: Page 5 of 7

Windows 2000 machines in a domain use SNTP and W32time to automatically synchronize with the Windows Primary Domain Controller (PDC) in a process transparent to the user. But Windows 2000 uses a time source derived from SNTP to synchronize other hosts, so it's a good idea to have an NTP client in the PDC to synchronize to an external source.

Mike Fratto is a senior technology editor based in Network Computing's Syracuse University Real-World Labs®; he covers all security-related topics. Prior to joining this magazine, Mike worked as an independent consultant in central New York. Write to him at [email protected].

Post a comment or question on this story.

There are many ways clients can receive time-server information. It depends on your local architecture and requirements. NTP server authentication is a key part of this process because time data should come from a reliable, trusted source. The exception is a client-server model where the server is unknown to the client from the start of the conversation.

Here are the main NTP architecture models:

• Client-server: This is the typical mode used for NTP deployments, and the one described in this workshop. The client or server is configured to communicate with a specific set of NTP time servers.