Archived from groups: microsoft.public.win2000.setup (
More info?)
Hello Raji,
Here is some info from KB article Q816042 that might be helpful:
INTRODUCTION
============
This step-by-step article describes how to configure the Windows Time service in Windows Server
2003. The article describes how to configure the Windows Time service to use an internal time source
and how to configure the Windows Time service to use an external time source. The article contains
troubleshooting tips for the most common problems. This article also discusses reliable time source
configuration, manually-specified synchronization, all available synchronization, and the
MaxNegPhaseCorrection and MaxPosPhaseCorrection registry entries.
#1: back to the top
Configuring the Windows Time service to use an internal hardware clock
-----------------------------------------------------------------------
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you
to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result
from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To configure the PDC master without using an external time source, change the announce flag on the
PDC master. The PDC master is the server that holds the forest root PDC master role for the domain.
This configuration forces the PDC master to announce itself as a reliable time source and uses the
built-in complementary metal oxide semiconductor (CMOS) clock. To configure the PDC master by
using an internal hardware clock, follow these steps.
1. Click "Start", click "Run", type "regedit" (without the quotation
marks), and then click "OK".
2. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\Ann
ounceFlags"
3. In the right pane, right-click "AnnounceFlags", and then click
"Modify".
4. In "Edit DWORD Value", type "A" (without the quotation marks) in the
"Value data" box, and then click "OK".
5. Quit Registry Editor.
6. At the command prompt, type the following command to restart the Windows Time service, and then
press ENTER:
"net stop w32time && net start w32time" (without the quotation marks)
Note The PDC master must not be configured to synchronize with itself. If the PDC master is configured
to synchronize with itself, the following events are logged in the Application log:
The time provider NtpClient cannot reach or is currently receiving
invalid time data from 192.168.1.1
(ntp.m|0x0|192.168.1.1:123->192.168.1.1:123).
No response has been received from Manual peer 192.168.1.1 after 8
attempts to contact it. This peer will be discarded as a time source
and NtpClient will attempt to discover a new peer from which to
synchronize.
The time provider NtpClient is configured to acquire time from one or
more time sources, however none of the sources are currently
accessible. No attempt to contact a source will be made for 960
minutes. NtpClient has no source of accurate time.
When the PDC master runs without using an external time source, the following event is logged in the
Application log:
Time Provider NtpClient: This machine is configured to use the domain
hierarchy to determine its time source, but it is the PDC emulator for
the domain at the root of the forest, so there is no machine above it
in the domain hierarchy to use as a time source. It is recommended that
you either configure a reliable time service in the root domain, or
manually configure the PDC to synchronize with an external time source.
Otherwise, this machine will function as the authoritative time source
in the domain hierarchy. If an external time source is not configured
or used for this computer, you may choose to disable the NtpClient.
This text is a reminder to use an external time source and can be ignored.
#1: back to the top
Configuring the Windows Time service to use an external time source
-------------------------------------------------------------------
To configure an internal time server to synchronize with an external time source, follow these steps:
1. Change the server type to NTP. To do this, follow these steps:
a. Click "Start", click "Run", type "regedit" (without the quotation marks), and then click
"OK".
b. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
\Parameters\Type"
c. In the right pane, right-click "Type", and then click "Modify".
d. In "Edit Value", type "NTP" (without the quotation marks) in the "Value data"
box, and then click "OK".
2. Set
AnnounceFlags to 5. To do this, follow these steps:
a. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
\AnnounceFlags"
b. In the right pane, right-click "AnnounceFlags", and then click "Modify".
c. In "Edit DWORD Value", type "5" (without the quotation marks) in the "Value
data" box, and then click "OK".
3. Enable NTPServer. To do this, follow these steps:
a. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
\TimeProviders\NtpServer\Enabled"
b. In the right pane, right-click "Enabled", and then click "Modify".
c. In "Edit DWORD Value", type "1" (without the quotation marks) in the "Value
data" box, and then click "OK".
4. Specify the time sources. To do this, follow these steps:
a. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
\Parameters\NtpServer"
b. In the right pane, right-click "NtpServer", and then click "Modify".
c. In "Edit Value", type <Peers> in the "Value data" box, and then click "OK".
Note <Peers> is a placeholder for a space-delimited list of peers from which your
computer obtains time stamps. Each DNS name that is listed must be unique. You must append
",0x1" (without the quotation marks) to the end of each DNS name. If you do not append ",0x1" (without
the quotation marks) to the end of each DNS name, the changes made in step 5 will not take effect.
5. Select the poll interval. To do this, follow these steps:
a. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
\TimeProviders\NtpClient\SpecialPollInterval"
b. In the right pane, right-click "SpecialPollInterval", and then click "Modify".
c. In "Edit DWORD Value", type <TimeInSeconds> in the "Value data" box, and
then click "OK".
Note <TimeInSeconds> is a placeholder for the number of seconds that you want
between each poll. A recommended value is 384. This value configures the Time Server to poll every
15 minutes.
6. Configure the time correction settings. To do this, follow these steps:
a. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
\MaxPosPhaseCorrection"
b. In the right pane, right-click "MaxPosPhaseCorrection", and then click "Modify".
c. In "Edit DWORD Value", select "Decimal" in the "Base" box.
d. In "Edit DWORD Value", type <TimeInSeconds> in the "Value data" box, and
then click "OK".
Note <TimeInSeconds> is a placeholder for a reasonable value, such as 1 hour (3600)
or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition,
and external time source.
e. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
\MaxNegPhaseCorrection"
f. In the right pane, right-click "MaxNegPhaseCorrection", and then click "Modify".
g. In "Edit DWORD Value", select "Decimal" in the "Base"box.
h. In "Edit DWORD Value", type <TimeInSeconds> in the "Value data" box, and
then click "OK".
Note <TimeInSeconds> is a placeholder for a reasonable value, such as 1 hour (3600)
or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition,
and external time source.
7. Quit Registry Editor.
8. At the command prompt, type the following command to restart the Windows Time service, and then
press ENTER:
"net stop w32time && net start w32time" (without the quotation marks)
If there are one or more child domains, consider configuring the PDC emulator of each child domain to
synchronize with an external stratum 1 NTP server. This configuration synchronizes time more
accurately than the default domain hierarchy configuration. However, the default domain hierarchy
synchronization typically provides sufficiently accurate time synchronization.
Troubleshooting
---------------
For the Windows Time service to function correctly, the networking infrastructure must function correctly.
The most common problems that affect the Windows Time service include the following:
- There is a problem with TCP/IP connectivity, such as a dead gateway.
- The Name Resolution service is not working correctly.
- The network is experiencing high volume delays, especially when
synchronization occurs over high-latency wide area network (WAN) links.
- The Windows Time service is trying to synchronize with inaccurate
time sources.
*****************************************************************************
David Hancock
Microsoft Server Setup Team
MCSA 2000
MCP
Search our Knowledge Base at
http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.
******************************************************************************
Facebook
Twitter
Instagram