w32tm won't change time backwards

I've set up a scheduled task on my W2K-SP4 machine which runs `w32tm -once` periodically, but I've noticed that the time is not being synced to my linux ntp box running ntpd.
My W2K box's clock seems to be running fast, and when I run w32tm the ouptut contains:
"Skewing for backwards, badj, btime = <nnnnn> <nnnnn>"
I'm assuming that it doesn't allow the time to be moved backwards, (is badj "Bad Jump"?)

However, if I manually change the time to 2 hours ahead of time, and run w32tm, it syncs ok.
(Actually, I kept moving the time ahead by a minute at at a time, and resyncing. I found the w32tm syncs if the client time is 4 min or more in the future
Is there any way of forcing w32tm to change the time (I've tried the -s switch but it doesn't make a difference)

Thanks,
John
LVL 15
oobaylyAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
oBdAConnect With a Mentor Commented:
You're just not patient enough. If the time on your Windows machine is three minutes or less ahead of the ntp time, the time is slowed (and not corrected immediately) until it's correct again.
But why use the scheduled anyway? If this is a stand-alone machine or a PDC Emulator, you can use this (with 1.2.3.4 being your ntp machine's IP address):
net time /setsntp:1.2.3.4
net stop w32time
net start w32time
and let the time service do the rest.
If the machine happens to be a domain member of an AD domain, just do nothing. It will automatically synchronize with the authenticating DC.

Basic Operation of the Windows Time Service
http://support.microsoft.com/?kbid=224799
0
 
oobaylyAuthor Commented:
My bad, I hadn't read the documentation properly. I had always assumed that running `net start w32time` was a server, not a client.
I take it that all I have to do is set the "Windows Time Service" to start automatically after I've run `net time /setsntp:myntpserver`

Thanks, it does appear the patience is a virtue :D
0
 
oobaylyAuthor Commented:
As usual it was a case of RTFM!
I've been running tcpdump on the machine running ntpd and have seen that the client running w32time has been polling it every so often. No obvious pattern, but I guess that's because it polls it depending on how the system clock is acting.


0
All Courses

From novice to tech pro — start learning today.