[ntp:questions] Windows time question.

Rob nomail at example.com
Wed Apr 20 09:04:20 UTC 2011

DaveB <g8kbv at uko2.co.uk> wrote:
> but as above, sometimes the pool server that responds seems to do 
> something odd, and kill (or seriously destabilize) W32Time as a result.
> At least, looking in the system error and info logs, after recovering 
> from a lockup, it's related to W32Time going bad, not long after first 
> boot of the day.

What do you mean with "a lockup"?
Is your entire machine locking up?  that is not normal.
Is the W32Time simply losing sync and declaring the timeserver as
unresponsive?  That is normal.  It is just the build quality of W32Time,
it seems you have to live with it.
(or install another time service when you don't like it)

More information about the questions mailing list