G
Guest
i'm really stuck on this one...
i have a station in our call center that keeps having its system time race
ahead. i have replaced the comptuer with a different model, i have even
changed the physical location of the station yet the problem persists. As
far as i can tell, this is the only station having this problem (and one of
the only ones where time is crucial).
the even log only shows time corrections, those entries look like this:
date: 18/02/2005 w32time 20:11 event id 593 user N/A
Time service corrected the clock error by 89 seconds.
date: 18/02/2005 w32time 21:38 event id 593 user N/A
Time service corrected the clock error by 70 seconds
date: 19/02/2005 w32time 17:47 event id 593 user N/A
Time service corrected the clock error by 784 seconds
date: 19/02/2005 w32time 18:58 event id 593 user N/A
Time service corrected the clock error by 350 seconds
date: 19/02/2005 w32time 20:11 event id 593 user N/A
Time service corrected the clock error by 314 seconds
There are others both those 5 were all logged consecutively, with no reboot
of the machine or any other entries in the system log in between.
Assuming no one can tell me what is causing this, can anyone shed any light
on where to look? the machine in on a domain, the domain synchs with no
problems to internet time, the computer is shared by users who only have USER
local group permissions (and therefore cannot change the time), it does seem
to be only affecting this one station.
I'm going to try a registry change to force all clock adjustments to be
logged but still would like to know if there are any other
tools/methods/spells i can use to help troubleshoot this one.
Thanks,
Matt
i have a station in our call center that keeps having its system time race
ahead. i have replaced the comptuer with a different model, i have even
changed the physical location of the station yet the problem persists. As
far as i can tell, this is the only station having this problem (and one of
the only ones where time is crucial).
the even log only shows time corrections, those entries look like this:
date: 18/02/2005 w32time 20:11 event id 593 user N/A
Time service corrected the clock error by 89 seconds.
date: 18/02/2005 w32time 21:38 event id 593 user N/A
Time service corrected the clock error by 70 seconds
date: 19/02/2005 w32time 17:47 event id 593 user N/A
Time service corrected the clock error by 784 seconds
date: 19/02/2005 w32time 18:58 event id 593 user N/A
Time service corrected the clock error by 350 seconds
date: 19/02/2005 w32time 20:11 event id 593 user N/A
Time service corrected the clock error by 314 seconds
There are others both those 5 were all logged consecutively, with no reboot
of the machine or any other entries in the system log in between.
Assuming no one can tell me what is causing this, can anyone shed any light
on where to look? the machine in on a domain, the domain synchs with no
problems to internet time, the computer is shared by users who only have USER
local group permissions (and therefore cannot change the time), it does seem
to be only affecting this one station.
I'm going to try a registry change to force all clock adjustments to be
logged but still would like to know if there are any other
tools/methods/spells i can use to help troubleshoot this one.
Thanks,
Matt