Win NT 4.0 Server /Bizarre Time Change ?

[Gamegirl]

We are running several Win NT 4.0 servers all running SP6a.
This morning one of the servers had it's internal clock mysteriously changed to 02/22/2036. This caused several scheduled jobs to kick off at once (Backup Exec., NAV)due to the future date . The scheduled jobs began competing for virtual memory and caused the server to eventually hang, which alerted us there was a problem. The server had to have a hard reboot. After rebooting it's internal clock was reset back to the proper date/time. The change in date/time on the server was not discovered until after rebooting, the desktop was frozen and unaccessible.
Could this be a Y2K issue relating to hardware? software?
I'm at a loss...

 

[pcorchary]

Check for anykind of NTP client running perhaps?

 

[yizhar]

Hmmm....

I've never seen this exact problem, but just for your info,
year 2036 has some relation to W2K bug.
For several MS VC modules and applications, this year in the internal binary format used by the programs, is something like 9999999 or 0000000 in Decimal notation.

But I still cannot see the reason for the fault.

You can suspect -
Hardware problem (BIOS/Motherboard? But also RAM/CPU fault),
Is this an Intel MB? Anyway go to board manufacture web site and look for BIOS updates.

OS issue (Reapplying latest SP can be a good idea. Maybe some DLL was replaced with an older one and this might fix it).

Check also for other posible causes and hackers.

Bye


Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar