# NTP 4.x for Windows NT

## Introduction

The NTP 4 distribution runs as service on Windows NT 4.0, Windows 2000, Windows XP, Windows .NET Server 2003. It will NOT run on Windows 95, 98, ME, etc. The binaries work on multi-processor systems. This port has not been tested on the Alpha platform. This release now uses OpenSSL for authentication. IPv6 is not implemented yet for Win32 platforms.

## Authentication Keys

With this release ntp-keygen is supported. See the ntp keygen documentation for details on how to use ntp-keygen.

ntpd can now use the generated keys in the same way as on Unix platforms. Please refer to the Authentication Options for details on how to use these.

NOTE: ntpd and ntp-keygen both use OpenSSL which requires a random character file called .rnd by default. Both of these programs will automatically generate this file if they are not found. The programs will look for an environmental variable called RANDFILE and use that for the name of the random character file if the variable exists. If it does not exist it will look for an environmental variable called HOME and use that directory to search for a filed called .rnd in that directory. Finally, if neither RANDFILE nor HOME exists it will look in C:\ for a .rnd file. In each case it will search for and create the file if the environmental variable exists or in the C:\ directory if it doesn't. Note that ntpd normally runs as a service so that the only way that it will have either RANDFILE or HOME defined is if it is a System environmental variable or if the service is run under a specific account name and that account has one of those variables defined. Otherwise it will use the file "c:\.rnd". This was done so that OpenSSL will work normally on Win32 systems. This obviates the need to ship the OpenSSL.exe file and explain how to generate the .rnd file. A future version may change this behavior.

Refer to Compiling Requirements and Instructions for how to compile the program.

## Reference Clocks

Reference clock support under Windows NT is tricky because the IO functions are so much different. Some of the clock types have been built into the ntpd executable and should work but have not been tested by the ntp project. If you have a clock that runs on Win32 and the driver is there but not implemented on Win32 you will have make the required configuration changes in config.h and then build ntpd from source and test it. The following reference clocks are known to work and are supported by Windows NT:

Type 1 Undisciplined Local Clock (LOCAL)
Type 29 Trimble Navigation Palisade GPS (GPS_PALISADE)

## Functions Supported

All NTP functions are supported with some constraints. See the TODO list below. Note that the ntptrace executable is not supported and you should use the PERL script version instead.

## Accuracy

Greg Brackley has implemented a fantastic interpolation scheme that improves the precision of the NTP clock using a realtime thread (is that poetic or what!) which captures a tick count from the 8253 counter after each OS tick. The count is used to interpolate the time between operating system ticks.

On a typical 200+ MHz system NTP achieves a precision of about 5 microseconds and synchronizes the clock to +/-500 microseconds using the Trimble Palisade as UTC reference. This allows distributed applications to use the 10 milliseconds ticks available to them with high confidence.

## Binaries

Recent InstallShield based executable versions of NTP for Windows NT (intel) are available from:

- http://www.trimble.com/oem/ntp
- http://www.five-ten-sg.com/

## ToDo

These tasks are in no particular order of priority.

- Create a proper install/uninstall program
- Add sntp to the list of supported programs
- Add support for Visual C++ 7.0 or later (.NET)
- Add IPv6 support
- See if precision can be improved by using CPU cycle counter for tick interpolation.
- Make precision time available to applications using NTP_GETTIME API

## Compiling Requirements

- Windows NT 4.0 Windows 2000, Windows XP, or Windows.NET Server 2003
- Microsoft Visual C++ 6.0. NOTEVC++ 7.0 (aka .NET) is not yet supported but will probably work fine.
- Some way of uncompressing and untarring the gzipped tar file.
- OpenSSL must be built on the box before building NTP. Additional steps would be required to not use OpenSSL.

## Compiling Instructions

1. Unpack and build OpenSSL according to the OpenSSL instructions for building on Windows. Currently the NTP build requires OpenSSL 0.9.7b as it looks for the path to that build for the include and libeay32.lib files. If you have a different version you will need to adjust both the preprocessor path and the link path to point to the correct locations of the include files and the lib file respectively.
2. Unpack the NTP-4.x.tar.gz using utilities such as WinZip.
3. Open the .\ports\winnt\ntp.dsw Visual C workspace
4. Batch build all projects
5. The built binaries can be found in the port\winnt\bin\Release subdirectory
6. In addition you will need to install the OpenSSL libeay32.dll
7. If you are shipping binaries in a kit it is strongly recommended that you ship this file (winnt.html) along with the binaries.

## Configuration File

The default NTP configuration file path is %SystemRoot%`\system32\drivers\etc\.` (%SystemRoot% is an environmental variable that can be determined by typing "set" at the "Command Prompt" or from the "System" icon in the "Control Panel").
Refer to your system environment and `c`reate your`ntp.conf` file in the directory corresponding to your system installation.
`The older <WINDIR>\ntp.conf` is still supported but you will get a log entry reporting that the first file wasn't found.

## Installation Instructions

The `instsrv` program in the instsrv subdirectory of the distribution can be used to install 'ntpd' as a service and start automatically at boot time. Instsrv is automatically compiled with the rest of the distribution if you followed the steps above.

1. Start a command prompt and enter "instsrv.exe <pathname_for_ntpd.exe>"
2. Clicking on the "Services" icon in the "Control Panel" will display the list of currently installed services in a dialog box. The NetworkTimeProtocol service should show up in this list. Select it in the list and hit the "Start" button in the dialog box. The NTP service should start.
3. You can also stop and start the service by typing net start|stop NetworkTimeProtocol at the DOS prompt.
4. View the event log by clicking on the "Event Viewer" icon in the "Administrative Tools" group, there should be several successful startup messages from NTP. NTP will keep running and restart automatically when the machine is rebooted.

You can change the start mode (automatic/manual) and other startup parameters corresponding to the NTP service in the "Services" dialog box if you wish.

## Removing NTP

You can also use `instsrv` to delete the NTP service by entering: "instsrv.exe remove"

## Command Line Parameters and Registry Entries

Unlike the Unix environment, there is no clean way to run 'ntpdate' and reset the clock before starting 'ntpd' at boot time.
NTP will step the clock up to 1000 seconds by default. While there is no reason that the system clock should be that much off during bootup if 'ntpd' was running before, you may wish to override this default and/or pass other command line directives.

Use the registry editor to edit the value for the ntpd executable under LocalMachine\System\CurrentControlSet\Services\NTP.

Add the -g option to the ImagePath key, behind "%INSTALLDIR>\ntpd.exe". This will force NTP to accept large time errors (including 1.1.1980 00:00)

## Bug Reports

Send questions to news://comp.protocols.time.ntp and bug reports should be entered in Bugzilla on the NTP Web site.

## Change Log

### Last revision 2 July 2003 Version 4.2.0

by Danny Mayer (mayer@ntp.org>)

### Significant Changes:

This latest release of NTP constitutes a major upgrade to its ability to build and run on Windows platforms and should now build and run cleanly. More importantly it is now able to support all authentication in the same way as Unix boxes. This does require the usage of OpenSSL which is now a prerequisite for build on Windows. ntp-keygen is now supported and builds on Win32 platforms.

### Last revision 16 February 1999 Version 4.0.99e.

by Sven Dietrich (sven_dietrich@trimble.com)

Significant Changes:

- Perl 5 is no longer needed to compile NTP. The configuration script which creates version.c with the current date and time was modified by Frederick Czajka [w2k@austin.rr.com] so that Perl is no longer required.

### Last revision 15 November 1999 Version 4.0.98f.

by Sven Dietrich (sven_dietrich@trimble.com)

Significant Changes:

- Fixed I/O problem delaying packet responses which resulted in no-replys to NTPQ and others.
- The default configuration file path is `<WINDIR>\system32\drivers\etc\ntp.conf. The old <WINDIR>\ntp.conf` is still supported but you will get a log entry reporting that the first file wasn't found. The NTP 3.x legacy `ntp.ini` file is no longer supported.

Known Problems / TODO:

- MD5 and name resolution do not yet get along. If you define MD5, you cannot use DNS names, only IP numbers.

### Last revision 27 July 1999 Version 4.0.95.

This version compiles under WINNT with Visual C 6.0.

Greg Brackley and Sven Dietrich

Significant changes:
-Visual Studio v6.0 support
-Winsock 2.0 support
-Use of I/O completion ports for sockets and comm port I/O
-Removed the use of multimedia timers (from ntpd, others need removing)
-Use of waitable timers (with user mode APC) and performance counters to fake getting a better time
-Trimble Palisade NTP Reference Clock support
-General cleanup, prototyping of functions
-Moved receiver buffer code to a separate module (removed unused members from the recvbuff struct)
-Moved io signal code to a separate module

### Last revision: 20-Oct-1996

This version corrects problems with building the XNTP
version 3.5-86 distribution under Windows NT.

The following files were modified:
blddbg.bat
bldrel.bat
include\ntp_machine.h
xntpd\ntp_unixclock.c
xntpd\ntp_refclock.c
scripts\wininstall\build.bat
scripts\wininstall\setup.rul
scripts\wininstall\readme.nt
scripts\wininstall\distrib\ntpog.wri
html\hints\winnt (this file)

In order to build the entire Windows NT distribution you
need to modify the file scripts\wininstall\build.bat
with the installation directory of the InstallShield
software. Then, simply type "bldrel" for non-debug
or "blddbg" for debug executables.

Greg Schueman
<schueman@acm.org>

### Last revision: 07-May-1996

This set of changes fixes all known bugs, and it includes
several major enhancements.

Many changes have been made both to the build environment as
well as the code. There is no longer an ntp.mak file, instead
there is a buildntall.bat file that will build the entire
release in one shot. The batch file requires Perl. Perl
is easily available from the NT Resource Kit or on the Net.

The multiple interface support was adapted from Larry Kahn's
work on the BIND NT port. I have not been able to test it
adequately as I only have NT servers with one network
interfaces on which to test.

Enhancements:
* Event Logging now works correctly.
* Version numbers now work (requires Perl during build)
* Support for multiple network interface cards (untested)
* NTP.CONF now default, but supports ntp.ini if not found
* Installation procedure automated.
* All paths now allow environment variables such as %windir%

Bug fixes:
* INSTSRV replaced, works correctly
* Cleaned up many warnings
* Corrected use of an uninitialized variable in XNTPD
* Fixed ntpdate -b option
* Fixed ntpdate to accept names as well as IP addresses
(Winsock WSAStartup was called after a gethostbyname())
* Fixed problem with "longjmp" in xntpdc/ntpdc.c that
caused a software exception on doing a Control-C in xntpdc.
A Cntrl-C now terminates the program.

See below for more detail:

Note: SIGINT is not supported for any Win32 application including
Windows NT and Windows 95. When a CTRL+C interrupt occurs, Win32
operating systems generate a new thread to specifically handle that
interrupt. This can cause a single-thread application such as UNIX,
to become multithreaded, resulting in unexpected behavior.

Possible enhancements and things left to do:
* Reference clock drivers for NT (at least Local Clock support)
* Control Panel Applet
* InstallShield based installation, like NT BIND has
* Integration with NT Performance Monitor
* SNMP integration
* Fully test multiple interface support

Known problems:
* bug in ntptrace - if no Stratum 1 servers are available,
such as on an IntraNet, the application crashes.

### Last revision: 12-Apr-1995

This NTPv3 distribution includes a sample configuration file and the project
makefiles for WindowsNT 3.5 platform using Microsoft Visual C++ 2.0 compiler.
Also included is a small routine to install the NTP daemon as a "service"
on a WindowsNT box. Besides xntpd, the utilities that have been ported are
ntpdate and xntpdc. The port to WindowsNT 3.5 has been tested using a Bancomm
TimeServe2000 GPS receiver clock that acts as a strata 1 NTP server with no
authentication (it has not been tested with any refclock drivers compiled in).
Following are the known flaws in this port:
1) currently, I do not know of a way in NT to get information about multiple
network interface cards. The current port uses just one socket bound to
INADDR_ANY address. Therefore when dealing with a multihomed NT time server,
clients should point to the default address on the server (otherwise the
reply is not guaranteed to come from the same interface to which the
request was sent). Working with Microsoft to get this resolved.
2) There is some problem with "longjmp" in xntpdc/ntpdc.c that causes a
software exception on doing a Control-C in xntpdc. Be patient!
3) The error messages logged by xntpd currently contain only the numerical
error code. Corresponding error message string has to be looked up in
"Books Online" on Visual C++ 2.0 under the topic "Numerical List of Error
Codes".

Last HTML Update: November 17, 1999
Sven_Dietrich@Trimble.COM