Hello Tim,
If you have one or more dc's just follow this document:
http://support.microsoft.com/kb/816042
Even better is a new posting with your situation and event viewer errors.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
> Have you been able to resolve your questions? Can you post and answer
> your topic if so? I am curious about this exact topic, and if your
> configuration is working, i would like to apply it too, to my Root DC.
>
> "WPD" wrote:
>
>> Hi All
>>
>> I have reviewed all the documentation that I have located on the
>> Windows Time Service in Windows Server 2003. However, I still feel
>> somewhat shaky about this topic, so I would appreciate your help to
>> make sure that I have configured both the server and the clients
>> correctly.
>>
>> GENERAL INFORMATION
>> 1) We have a small client/server network. The Root Domain Controller
>> has THE
>> WinDOWS Server 2003 SP1 Op Sys, & there are 5 clients using either
>> Win XP Pro
>> SP2 or Win2000 Pro. Just to confirm, there is only 1 DC in this
>> network.
>> 2) The Root Domain Controller is the network's reliable time server
>> so the following entries are in its registry:
>>
>> -HKEY_LOCAL-MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ Config
>> has AnnounceFlags set to (5).
>>
>> -In W32Time\Parameters Type is set to NTP.
>>
>> -In W32Time\TimeProviders\NtpServer has Enabled set to (1)
>>
>> 3) In W32Time\Parameters,the entry in NtpServer is:
>>
>> 0.north-america.pool.ntp.org,0x1 1.north-america.pool.ntp.org,0x1
>> 2.north-america.pool.ntp.org,0x1 time-a.nist.gov,0x1
>>
>> QUESTIONS:
>> (a) In point 3) above, how is the manualpeerlist entry used?
>> -Does Windows Time Service try to connect to the first entry in the
>> list, 0.north-america.pool.ntp.org,0x1, and then if that fails does
>> it then try the second location in the list?
>>
>> -Or does it contact each address in the list, and then average the
>> times before synching the DC's time?
>>
>> -Or does it rotate sequentially through each address in the list as
>> each new time check is made?
>>
>> (b) In W32time\Paramters, I appended the 0x1 switch to the end of
>> each address entry. Please note that I did not place a space between
>> the end of the address name (time-a.nist.gov,0x1) and the comma
>> before the 0x1 switch. Is the lack of a space correct?
>>
>> (c) In W32Time\Parameters, I think that appending the 0x1 switch to
>> an address means that Windows Time Service in the Root Domain
>> Controller will connect to the internet-based time server(s) every
>> ??-seconds where (??-seconds) is the number entered in the
>> W32Time\TimeProviders\NtpClient entry for SpecialPollInterval. I have
>> 3600 entered here, so I believe that means that the RDC tries to
>> contact 0.north-america.pool.ntp.org0x1 every 1 hour. Is this
>> correct? If it is not, then how does one control how frequently the
>> RDC contacts the time server(s)?
>>
>> (d) All of the client computers were joined to the network and then
>> were set to their default w32time settings using the following
>> procedure from the command line:
>>
>> -w32tm /unregister <Enter Key>
>> -w32tm /register <Enter Key>
>> -net start w32time <Enter Key>
>> -w32tm /resync <Enter Key>
>> Will this procedure set the clients to automatically use the RDC as
>> their time source? Please advise Which setting controls how
>> frequently that they will automatically connect to the RDC to
>> synchronize their time?
>>
>> Thanks for your help!!
>>
Similar Threads
Linear Mode
