|The NTP FAQ and HOWTO: Understanding and using the Network Time Protocol (A first try on a non-technical Mini-HOWTO and FAQ on NTP)|
For platforms and operating systems other than those mentioned here, there may be software available under different conditions. Maybe there are binary program packages available for your computer system. A good starting point for your search is the NTP home page at http://www.eecis.udel.edu/~ntp that also offers a reference implementation (See Q: 188.8.131.52.). Specific issues are presented in Section 8.3.
Several national time keepers (NIST and USNO in USA PTB in Germany) allow reading the time via NTP. See their home pages for details.
Fortunately there is an implementation of an NTP client and server available for free (See the NTP Home Page at http://www.ntp.org/). The software is available as C source and it runs on most UNIX compatible operating systems. The software consists of the following components:
A daemon process that is both, client and server.
A utility to set the time once, similar to the popular rdate command.
Monitoring and control programs that communicate via UDP with ntpd.
A utility to back-trace the current system time, starting from the local server.
The documentation for the software is definitely worth reading.
There are also several scripts that might be useful or at least a source of ideas if you want to run and monitor NTP.
According to Gilles Vollant, Windows/2000 includes a built-in SNTP client. Follow this procedure:
Select a NTP server, using net time /setsntp:ntp-server. However "Only the domain controller that holds the PDC FSMO (Primary Domain Controller Flexible Single Master Operation) role can query an external time source to set the time."
Start the W32time service with net start W32Time. You can also set the start option of the Windows Time Synchronization Service (W32Time) to Automatic, so the service will start when Windows/2000 starts.
For further information about NTP in Windows/2000 see
Marc Brett contributed:
A Google search with "NET TIME /SET /SETSNTP" yields all sorts of clues, including several Microsoft Knowledgebase articles, and a bunch of W2K-specific stuff at http://www.labmice.net/timesynch.htm.
You may also want to run a Samba server on your Linux NTP box, and set it up as an SMB time server (time server = true in smb.conf) so your W2K boxes will find a it automagically.
The software discussed in Which Implementations are available for UNIX? has been ported only lately to Windows/NT. Therefore there exists a variety of products to support NTP, most of them are only an NTP client however.
|TimeServ (http://www.niceties.com/TimeServ.html or ftp://ftp.microsoft.com/reskit/y2kfix/x86/timeserv/timeserv.htm)|
|Tardis (http://www.kaska.demon.co.uk/) is an SNTP client|
XXX Note from the editor: More should be listed here, but isn't.
Theo Jakobus wrote:
TCPIP supports NTP version 3, see http://www.openvms.compaq.com:8000/72final/6526/6526profile_contents_002.html#toc_chapter_10. The configuration is done in SYS$SPECIFIC:[TCPIP$NTP]TCPIP$NTP.CONF. I just added different time sources in Germany like: server ntp.fhg.de server noc.belwue.de the service is activated using $@SYS$MANAGER:TCPIP$CONFIG. I'm getting the time using NTP and distibuting the time to Digital systems using DTSS.
The URL seems to be gone; however there's a copy at http://web.archive.org/web/20011029133318/http://labmice.net/timesynch.htm as Anand Kumria pointed out.