Robinson,

I was just thinking about your comments to Mark and I want to clarify
that my UI sync gives an error and does not change the system time. In
addition, my w32time service does run but it never actually updates the
time nor does it put any entries in the event log. Moreover, I have run
a command like

w32tm /stripchart /computer:time.nist.gov /samples:5

and by doing that I can confirm that the service itself can a) contact
a remote ntp server and give back a time value and b) what the
persistent time offset (my machine is currently about 35 seconds fast)
between my system and that server is because the the system time is not
being updated. Here's what the output looks like


Tracking time.nist.gov [192.43.244.18:123].
Collecting 5 samples.
The current time is 6/14/2009 7:13:53 PM.
19:13:53 d:+00.0899897s o:-35.0706906s [@ |
]
19:13:55 d:+00.0889824s o:-35.0722007s [@ |
]
19:13:57 d:+00.0899897s o:-35.0708540s [@ |
]
19:13:59 d:+00.0899897s o:-35.0717943s [@ |
]
19:14:01 d:+00.0879894s o:-35.0722139s [@ |
]


What I'm driving at here is that Mark's problem and mine a very likely
exactly the same and my conjecture is that the failure is a failure in
the UI and w32time's ability to UPDATE the system time and not in their
ability to get the time from the remote ntp server.

I suspect that this issue is widespread but people don't realize that
their time sync isn't working and nothing's going into the event log to
tip them off.

Thanks,
Mike


--
mmetts
Posted via [url]http://www.vistaheads.com[/url]