obyapka
asked on
clock on WS1003
Hi,
I run a windows 2003 server (sbs) from home and yesterday we had an household power failure. When I rebooted the server all is fine except that the clock periodiaclly resets itself to January 1 1999.. but the time element is being set to somethign specific... it happened at 11:30am (GMT) but the time was set to 18:15...
I've just checked the application event log and there are errors relatign to time (they've never been there before)
"Windows cannot find the machine account, The clocks on the client and server machines are skewed. ."
and
"Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this."
Any ideas whats going on?
At first I thought it was the PCs internal battery but if I switch it off and back on, its kept time... its only when its online that at specific times (not worked out what yet) the clock resets itself...
Brian
I run a windows 2003 server (sbs) from home and yesterday we had an household power failure. When I rebooted the server all is fine except that the clock periodiaclly resets itself to January 1 1999.. but the time element is being set to somethign specific... it happened at 11:30am (GMT) but the time was set to 18:15...
I've just checked the application event log and there are errors relatign to time (they've never been there before)
"Windows cannot find the machine account, The clocks on the client and server machines are skewed. ."
and
"Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this."
Any ideas whats going on?
At first I thought it was the PCs internal battery but if I switch it off and back on, its kept time... its only when its online that at specific times (not worked out what yet) the clock resets itself...
Brian
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
its just changed the clock again... it appears to happen at half-past specific hours... and its set it to 1 Jan 1999 22:15 ... I just find it rather odd how its happens at a specific time and sets it to a specific time for it to be CMOS battery related!
Okay, whether or not you have any PC's attached you still need to make sure that the server is accessing a proper NNTP server to get the proper time through the Internet.
And that behavior of resetting to 1 Jan 1999 22:15 is exactly what would happen if your battery was running low. That's the signal to get a new one.
Jeff
TechSoEasy
And that behavior of resetting to 1 Jan 1999 22:15 is exactly what would happen if your battery was running low. That's the signal to get a new one.
Jeff
TechSoEasy
ASKER
I would have thoguht the clock be reset to Jan 1 1999 00:00 every time, hence I found it confusing how it manages to set a time which is always x-hours different to the current time.
it's just weak, not dead.
ASKER
"make sure that the server is accessing a proper NNTP server to get the proper time through the Internet. "
how would I do that?
how would I do that?
ASKER
I'll follow up your leads. Many thanks for your input. I'll get that battery changed asap.
ASKER