Setting Up SBS to Sync w/ External Time Source

Through some suggestions I found in this newsgroup and on the Internet, I
used the following to setup time synchronization between my XP Pro SP2
client PCs and my my SBS 2003 server. The server is synching with an
external time source.

Here are the commands I ran on the server:

w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
net stop w32time
net start w32time
w32tm /resync

Here are the commands I ran on the clients:

net time /setsntp:<MY_SERVER>
w32tm /resync /nowait


This seemed to work, but about two days later I received the following event
in the SBS 2003 System Event Log:

Type: Error
Source: W32Time
Event ID: 46
Description: The time service encountered an error and was forced to shut
down. The error was: 0xC0020018

>From then on I started getting this sequence of Info, Warning, Error events
1 to 3 times a day:

Type: Information
Source: W32Time
Event ID: 38
Description: The time provider NtpClient cannot reach or is currently
receiving invalid time data from <MY_SERVER>
(ntp.m|0x0|10.0.0.3:123->10.0.0.3:123).

Type: Warning
Source: W32Time
Event ID: 47
Description: Time Provider NtpClient: No valid response has been received
from manually configured peer <MY_SERVER> after 8 attempts to contact it.
This peer will be discarded as a time source and NtpClient will attempt to
discover a new peer with this DNS name.

Type: Error
Source: W32Time
Event ID: 29
Description: 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 XX minutes.
NtpClient has no source of accurate time.

XX varies from 15 to 960 minutes. Does anyone have an idea of what the
issue is here? Any help would be MUCH appreciated. Thanks!


.

Relevant Pages

  • Re: Time Sync Issue on DCs
    ... Configure the PDCEmulator to sync with an external time source and reconfigure the other machines to use only domain time. ... Time Provider NtpClient: No valid response has been received from ... configured peer time.windows.com,0x1 after 8 attempts to contact it. ...
    (microsoft.public.windows.server.general)
  • Re: Forgot to ask, Routing and Remote Access question
    ... > Can you double check your router, that it has UDP port 123 open in and ... >> The time provider NtpClient cannot reach or is currently receiving invalid ... >> will be discarded as a time source and NtpClient will attempt to discover ... >> new peer with this DNS name. ...
    (microsoft.public.windows.server.sbs)
  • Re: Time syncing
    ... I configured a test server to use tock.usno.navy.mil as the time source and had success. ... System Event Log entry 37 from Time-Service ... Time Provider NtpClient: No valid response has been received from manually ... configured peer tock.usno.navy.mil after 8 attempts to contact it. ...
    (microsoft.public.windows.server.general)
  • Time syncing
    ... I also have it setup to sync to an external time source, ... Time Provider NtpClient: No valid response has been received from manually ... configured peer tock.usno.navy.mil after 8 attempts to contact it. ...
    (microsoft.public.windows.server.general)
  • Re: Problem Administrative Services
    ... The time provider NtpClient is configured to acquire time ... see Help and Support Center at ... determine its time source, but the computer is joined to ... a Windows NT 4.0 domain. ...
    (microsoft.public.windowsxp.security_admin)