Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

After a reboot the windows time reset itself to 26 March 2007. This meant it could not connect to any other servers in the domain. We have set the time to the correct value but we are having intermittent NetBios name problems. I want to understand whether the clock resetting is a red herring or a clue to the problem.

share|improve this question
1  
what is in the event log? –  MDMarra Sep 10 '09 at 11:36
    
Nothing of a note, apart from the event times. It just did its shut down events with correct time signature and then the start up events were at the March 2007 time. –  ArchieVersace Sep 10 '09 at 12:04
add comment

3 Answers

Is the hardware clock set correctly?

You could also have a dead BIOS battery, causing the hardware clock to reset to a default if the power is removed.

share|improve this answer
1  
I second. I would suggest looking at the hardware clock and CMOS battery as the culprit here. –  joeqwerty Sep 10 '09 at 11:42
1  
There's no reason not to fix the battery issue (should be less than $5), and then deal with any other issues afterward, if they persist. That's an odd time, though - I expect to see 1980 on a dead battery. –  Kara Marfia Sep 10 '09 at 12:03
    
Seems to be especially a problem on VMs when the host time is wrong. –  K. Brian Kelley Sep 10 '09 at 14:07
add comment

We had a similar problem that occurred whenever windows updates would run and sit for a while before the required reboot. The clock would always reset to midnight. It drove me nuts, and always killed our database replication.

The only solution we were able to find was to disable automatic updates. Now we manually run updates and reboot immediately. (And are in the process of moving the content to a new virtual Windows 2008 Server).

share|improve this answer
    
This happened to my server last night and cost me an hour of time-shifting invoices, payments, jobs and quotes. –  pate Nov 21 '12 at 15:18
add comment

Could that be related to the DST Timezone change that happened in 2007? some weird patches can cause this...and the date fits

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.