J
John
Very weird problem on a W2000 workstation, that's connected to a Windows
2000 AD.
When booting the workstation, the clock is always running 10 minutes ahead.
Manually correcting it goes fine, but a reboot causes the clock to go 10
minutes ahead again... Login off and back on does not give any time issues
(so it's not a loginscript problem). Further investigation showed that the
W32time service is causing the problem when starting. The time on the
server is ok, and also all the other W2000 workstations are having no
problems with their time.
Typing NET TIME /DOMAIN /SET in a dosbox shows indeed the 10 minutes
differences (after rebooting), en replying "Yes" to this question results in
a correct local time on the workstation.
But, after a NET STOP W32TIME followed by a NET START W32TIME the clocks
jumps 10 minutes ahead! If I then enter NET TIME /DOMAIN /SET (and reply
"Yes") the clock is adjusted correctly again...
What could this be??? Any help would be greatly appreciated!
2000 AD.
When booting the workstation, the clock is always running 10 minutes ahead.
Manually correcting it goes fine, but a reboot causes the clock to go 10
minutes ahead again... Login off and back on does not give any time issues
(so it's not a loginscript problem). Further investigation showed that the
W32time service is causing the problem when starting. The time on the
server is ok, and also all the other W2000 workstations are having no
problems with their time.
Typing NET TIME /DOMAIN /SET in a dosbox shows indeed the 10 minutes
differences (after rebooting), en replying "Yes" to this question results in
a correct local time on the workstation.
But, after a NET STOP W32TIME followed by a NET START W32TIME the clocks
jumps 10 minutes ahead! If I then enter NET TIME /DOMAIN /SET (and reply
"Yes") the clock is adjusted correctly again...
What could this be??? Any help would be greatly appreciated!