2

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.

Dennis Williamson
  • 62,149
  • 16
  • 116
  • 151
ArchieVersace
  • 141
  • 4

3 Answers3

7

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.

Keith Stokes
  • 907
  • 5
  • 7
  • 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
1

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).

Matt
  • 409
  • 1
  • 5
  • 11
0

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

vn.
  • 375
  • 2
  • 10