HELP! Time Synchronization

[Guest]

I have configured my XP workstation to sync with NTP server every 30minutes
(SepcialPollInterval) . The workstation only in WORKGROUP and without any
Domain Controller.

When I added the multiple NTP server entries with COMMA separate in between,
the time will be synchronize every 17 minutes. However, if I enter multiple
NTP server entries with SPACE in between, the time will be synchronize every
30minutes as I defined. This is followed Microsoft Article ID 223184.

However, I wish to know what is goes wrong with COMMA added in the entries
and caused the time synchronize every 17minutes? Anybody know answer?

Many thanks.

 

[Ramesh, MS-MVP]

Hi Polar Bear,

HOW TO: Turn On Debug Logging in the Windows Time Service:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;816043

I turned ON debugging and then typed the NtpServer values with COMMA
de-limited

time.windows.com,time.nist.gov,clock.isc.org,usno.pa-x.dec.com,tock.usno.navy.mil,timekeeper.isi.edu,0x1

Stopped / Restarted W32time serviced. Then, synched with the time servers

Here is what the LOG shows:

147694 06:57:25.9508403s - Resolving
time.windows.com,time.nist.gov,clock.isc.org,usno.pa-x.dec.com,tock.usno.navy.mil,timekeeper.isi.edu,0x1
147694 06:57:25.9820903s - PeerPollingThread: WaitTimeout
147694 06:57:25.9820903s - PeerPollingThread: waiting forever
147694 06:57:26.0289653s - Peer poll: Max:1024.0000000s Cur:00.0000000s
147694 06:57:26.0289653s - PeerPollingThread: waiting 0.000s
147694 06:57:26.0445903s - PeerPollingThread: WaitTimeout
147694 06:57:26.0445903s - Polling peer time.windows.com
(ntp.m|0x0|192.168.1.10:123->207.46.130.100:123)
147694 06:57:26.0445903s - Sending packet to time.windows.com
(ntp.m|0x0|192.168.1.10:123->207.46.130.100:123) in Win2K detect mode, stage
1.
147694 06:57:26.0445903s - Peer poll: Max:1024.0000000s Cur:00.0000000s
147694 06:57:26.0445903s - PeerPollingThread: waiting 1024.000s
147694 06:57:26.3883403s - ListeningThread -- DataAvailEvent set for socket
0 (192.168.1.10:123)
147694 06:57:26.3883403s - ListeningThread -- response heard from
207.46.130.100:123

It trues to resolve to the whole path
(time.windows.com,time.nist.gov,clock.isc.org,usno.pa-x.dec.com,tock.usno.navy.mil,timekeeper.isi.edu)
and fails. Then, retries contacting time.windows.com (which might be
hard-coded) and successfully updates the clock.

But, I still don't know where that 17 min interval comes from.