In: Categories » Computers and technology » Servers » How to Configure a NTP Network Time Server in Windows 2000
| Summary: This article describes how to configure Windows 2000 to act as an authoritative time server using NTP (Network Time Protocol). Computer time synchronisation is highly important in modern computer networks, precision and time synchronization is critical in many applications, particularly time sensitive transactions. Just imagine buying an airline seat only to be told at the airport that the ticket was sold twice because it was purchased afterwards on a computer that had a slower clock! Modern computers do have internal clocks called Real Time Clock chips (RTC) that provide time and date information. These chips are battery backed so that even during power outages, they can maintain time but personal computers are not designed to be perfect clocks. Their design has been optimized for mass production and low-cost rather than maintaining accurate time. For many applications, this is can be quite adequate, although, quite often machines need time to be synchronised with other PC's on a network and when computers are out of sync with each other problems can arise such as sharing network files or in some environments even fraud! Microsoft Windows 2000 has a time synchronisation utility built into the operating system called Windows Time (w32time.exe) which can be configured to operate as a network time server. Microsoft and others strongly recommend that you configure a time server with a hardware source rather than from the internet where there is no authentication. If you want to configure Windows Time service to use the internal hardware clock, then first check that w32time is located in the system services list in the registry, to check: Click Start, Run then type regedit then click ok. It is highly recommended that you back up the registry as serious problems may occur if you modify the registry incorrectly, modifications to the registry are done at your own risk. To begin configuration for an internal clock, click on the following subkey: To restart the Windows Time Service click Start, Run (or alternatively use the Command Prompt facility). To reset the local computers’ time, type the following on all computers except for the time server which must not be synchronised with itself: To configure the Windows Time service to use an external time source, click Start, Run and type regedit then click OK. Locate the following subkey: Now in the right pane, right click ReliableTimeSource, then click Modify. Right-click NtpServer in the right pane then click Modify. For Windows 2000 Service Pack 4 only, set the time correction settings to do this locate: To set the poll intervals locate: Click Start, then Run then type the following and press Enter: To reset the local computers’ time, type the following on all computers except for the time server which must not be synchronised with itself: Network Time Protocol (NTP) is an Internet protocol used for the transfer of accurate time, providing time information along so that a precise time can be obtained To enable the Network Time Protocol; NTPserver, locate and click: Now go back and click on Locate and click the following To configure the time correction settings, locate: Now go back and click: Exit Registry Editor And on each computer, other than the time server, type: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industries. For more information about NTP servers please visit http://www.galsys.co.uk
|
legal disclaimer
1) Our website is not responsible for the information contained by this article as well for any and all copyright infringements by authors and writers. E-articles is a free information resource. If you suspect this article for any copyright infringements, please read the Terms of service and contact us to investigate the problem.
2) The E-articles directory team is not responsible for inaccuracies, falsehoods, or any other types of misinformation this tutorial may contain and will not be liable for any loss or damage suffered by a user through the user's reliance on the information gained here. Please read the Terms of service
Useful tools and features
related articles
Previous versions of Exchange essentially forced many organizations into deploying servers in sites with greater than a dozen or so users. With the concept of site consolidation in Exchange Server 2007, however, smaller numbers of Exchange servers can service clients in multiple locations, even if they are separated by slow WAN links. For small and medium-sized organizations, this essentially means that one or two servers should suffice for the needs of the organization, with few exceptions. Larger organizations require a larger numbe...
2. Configuring Exchange Server 2007 for Maximum Performance and Reliability
After decisions have been made about AD design, Exchange server placement, and client access, optimization of the Exchange server itself helps ensure efficiency, reliability, and security for the messaging platform. Designing an Optimal Operating System Configuration for Exchange As previously mentioned, Exchange Server 2007 only operates on the Windows Server 2003 operating system, and is scheduled to be able to run on the next version of the Windows Server operating system, currently referred to as Windows L...
3. Managing Identity Information Between LDAP Directories and Exchange Server 2007
LDAP directories are commonplace today and can be found in many business environments. UNIX applications in particular make wide use of the LDAP standard for directories. Along with this proliferation of LDAP directory structures comes a need to synchronize the information contained within them to an Exchange 2007 environment. The Enterprise version of MIIS 2003 contains MAs that support synchronization to LDAP directories. Consequently, a good understanding of LDAP concepts is required before syncing between the environments. ...
4. Understanding DNS Requirements for Exchange Server 2007
In Active Directory, all client logons and lookups are directed to local domain controllers and GC servers through references to the SRV records in DNS. Each configuration has its DNS and resource requirements. Exchange relies on other servers for client authentication and uses DNS to find those servers. In an Active Directory domain controller configuration, on the other hand, the Exchange server also participates in the authentication process for Active Directory. Using DNS in Exchange Server 2007 As has bee...
5. Securing and Maintaining an Exchange Server 2007 Implementation
One of the greatest advantages of Exchange Server 2007 is its emphasis on security. Along with Windows Server 2003, Exchange Server 2007 was developed during and after the Microsoft Trustworthy Computing initiative, which effectively put a greater emphasis on security over new features in the products. In Exchange Server 2007, this means that the OS and the application were designed with services “Secure by Default.” With Secure by Default, all nonessential functionality in Exchange must be turned on if needed. Thi...
6. Improvements in Exchange Server 2007 Relative to Security and Compliance
One of the improvement goals Microsoft has had with all of their products over the past few years has been to constantly improve the security in the products. More recently with all of the regulatory compliance laws and policies being implemented, Microsoft has focused a lot of security enhancements to address privacy, information archiving, and compliance support. The release of Exchange 2007 was no different—Microsoft added in several new enhancements in the areas of security and compliance support. One of the addition...
7. Designing Exchange Infrastructure
After Active Directory and the physical OS has been chosen and deployed, the Exchange infrastructure can be set up and optimized for the specific needs of the organization. With these needs in mind, you can do several things to optimize an Exchange 2007 setup, as detailed in the following sections. Determining the Exchange Version When installing Exchange, the choice of Exchange version needs to be made. As with Windows Server 2003, there are two versions of Exchange, Standard and Enterprise. The Standard Edit...










