The latest Microsoft Windows operating systems have a time synchronisation utility installed by default called ‘Windows Time’. The Windows time service allows a Microsoft network to provide time synchronisation of machines in a domain. This article introduces how to configure the Microsoft Windows 2000 and 2003 operating systems to operate as a SNTPNTP time server. The article discusses how to change Windows registry entries to configure the Time Service.
Before modifying any Windows registry settings, it is a good idea to save the registry. In the even of any difficulties, the registry can be restored to its former state.
Windows 2000 Time Service
Windows 2000 has an integrated network time synchronization service, installed by default, which can be configured to synchronize to a Time Server. In fact, by changing associated registry settings, the service can act as both a time client and a time server to synchronize other network time clients.
The Windows Time service should be present in the systems service list. The application executable is 'w32time.exe'. The parameter list for time service should be present in the in the registry at:
The Windows 2000 operating system can operate as a time client and synchronise to a time server by setting the parameter 'NTP Server' to the IP address of a Time Server.
By default, the Windows 2000 machine will synchronize to the specified time server every 8 hours, or 3 times a day. This may not be enough to maintain accurate synchronization and can be easily increased. Setting the ‘Period’ parameter to how many times each day synchronisation is required can reduce the period. Setting the ‘Period’ parameter to 48 will activate synchronization with the time server once every half hour.
The Windows 2000 operating system can also be configured to act as a time server by setting the 'Local NTP' registry setting to '1'.
After changing any of the registry settings for the windows time service, the service must be restarted for the settings to take effect. The time service can be started or stopped from the service control applet in the Administrative Tools menu. The service can also be controlled via the DOS net command thus:
‘net start w32time’ and ‘net stop w32time’
Windows 2003 Time Service
With Windows 2003, Microsoft has expanded on the original Windows 2000 SNTP time service by providing a true NTP implementation. The Windows 2003 time service, installed by default, can synchronise to a NTP Server. Indeed, by changing registry settings, the time service can act as both a time server and client to synchronize other time clients in the domain.
The 'Windows Time' service should be present in the systems service list. The application executable is 'w32time.exe'. The parameter list for the Windows 2003 time service should be present in the registry at:
The ‘Special Poll Interval’ registry entry defines the period in seconds that the Windows 2003 operating system should poll the time server. A recommended value is 900, which equates to a polling period of every 15 minutes.
The ‘NTP Server’ parameter is used to provide a list of DNS names or IP addresses, separated by a space, of time servers that the Windows 2003 operating system can synchronize to.
Troubleshooting the Time Service
A number of isuues may be encountered when configuring the Microsoft Windows Time Service. SNTP and NTP operates using the UDP protocol over TCP/IP. Therefore, the TCP/IP network protocol must be active for SNTPNTP to operate. Synchronisation issues may also arise when SNTPNTP attempts to synchronise to an inaccurate time server reference or if network delays are excessive.
Synchronising Network Device and Components
In addition to synchronizing Microsoft Windows servers and workstations, time servers can also be used to synchronise network devices, such as switches, routers and hubs. Any network infrastructure that can synchronise to a NTP or SNTP time server can be pointed to the Windows time server to obtain synchronisation. In this way the whole network and accompanying infrastructure can be accurately synchronised to a time reference.
How To Configure Windows Server
The Microsoft Windows operating systems from Windows 2000 onwards has a built-in time synchronization service – ‘Windows Time’. This article describes how to configure the Microsoft Windows 2003 and Windows 2000 time service as a NTP time server. It shows how to modify registry entries to configure the Microsoft Windows Time Service. The Windows Time service allows a Windows network to provide synchronisation of all machines within a domain.
Windows 2003 Server Configuration
Windows 2003 has expanded on the original Windows 2000 time service by providing a true NTP implementation. The time service, installed by default, can synchronise to a NTP Server. Indeed, by manipulating registry settings for the service it can act as both an NTP server and client to synchronise other network clients in the domain.
The 'Windows Time' service should be present in the systems service list. The application executable is 'w32time.exe'. The parameter list for w32time can be found in the registry at:
Before modifying registry entries it is good a dood idea to backup the registry settings. The registry can then be restored in the event of problems being encountered.
To configure a Windows 2003 machine to synchronise to an external NTP server, edit the following registry entries:
The ‘Special Poll Interval’ registry entry defines the period in seconds that the Windows 2003 machine should poll the NTP server. A recommended value is 900 seconds, which equates to every 15 minutes.
The ‘NTP Server’ parameter is used to provide a list of IP addresses or DNS names, separated by a space, of NTP servers that the Windows 2003 machine can synchronise to.
Change the server type to NTP by specifying ‘NTP’ in the ‘Type’ registry entry.
Windows 2000 Time Service Configuration
Windows 2000 has an integrated time synchronisation service, installed by default, which can synchronise to a NTP Server. Indeed, by manipulating registry settings, the service can act as both an SNTP client and SNTP server to synchronise other network clients.
Before modifying registry entries it is good a dood idea to backup the registry settings. The registry can then be restored in the event of problems being encountered.
The 'Windows Time' service should be present in the systems service list. The application executable is 'w32time.exe'. The parameter list for w32time can be found in the registry at:
Windows 2000 can operate as an NTP client and synchronise to an NTP server by setting parameter 'NTP Server' to the IP address of a NTP Server.
By default, the Microsoft Windows 2000 machine will synchronise to the specified NTP time server every 8 hours (or 3 times a day), which may not be enough to maintain accurate synchronisation. The period can be reduced by setting the 'Period' parameter to how many times a day synchronisation is required. Setting the period to 48 will activate synchronisation with the NTP server once every half hour.
Windows 2000 can also be configured to act as an NTP server by setting the 'Local NTP' parameter to '1'.
After editing any of the registry entries for the windows time service, the service must be restarted for the settings to take effect. The services can be started or stopped from the service control applet in 'administrative tools'. Alternatively the service can be controlled via the DOS net command thus:
net start w32time
net stop w32time
NTP Troubleshooting
A number of problems can be encountered when configuring the Windows Time Service. NTP operates using the UDP protocol over TCP/IP. Therefore the TCP/IP network infrastructure must be operational for NTP to be effective. Synchronisation issues may arise when NTP attempts to synchronise to an inaccurate time reference or if network delays are excessive.
Synchronising Time on Network Devices
As well as synchronising Microsoft Windows servers and workstations, NTP can also be used to synchronise network devices, such as hubs, switches and routers. Any network device that can synchronise to a NTP server can be pointed to the Windows server to achieve time synchronisation. In this way the whole network and accompanying infrastructure can be synchronised.
Dave Evans has sinced written about articles on various topics from Personal Desktop, Health and Networking. D. Evans develops Windows SNTPNTP time server synchronisation solutions that ensure accurate time on PC's and networks. Dave has been heavily involved in the development of dedicated Windows time server systems, NTP synchronized digital clock systems and. Dave Evans's top article generates over 6600 views. Bookmark Dave Evans to your Favourites.
Break A Commercial Lease Note that before untaken into the affair, as in any business, careful assessment should be made before a decision is made. Plan it sensibly. Good Luck