Win2k Time problem - always reboot with 10 minutes slow
This is a discussion about Win2k Time problem - always reboot with 10 minutes slow in the Customization Tweaking category; I just realized this problem, and I'm not sure when it actually first started. As my subject stated, the computer is running Win2k. I noticed that if I set the clock to a correct time (say 8:15) and then reboot, when the computer finished booting back into Windows, the clock is automatically adjusted 10 minutes slo ...
I just realized this problem, and I'm not sure when it actually first started.
As my subject stated, the computer is running Win2k. I noticed that if I set the clock to a correct time (say 8:15) and then reboot, when the computer finished booting back into Windows, the clock is automatically adjusted 10 minutes slow (to 8:05).
I re-correct the time again, reboot, go into BIOS setup to double check, and the time is correct. But once exit BIOS setup and let it boot into Windows, the clock is again auto adjusted 10 minutes slow.
There is no Time Server in the network, the network is local and private and it's not connected to the internet at all, and there is no time sync program running on that computer.
Does anyone has an explaination for this? Anyone knows how to correct this problem? This is an office computer that I use. I haven't check the other computers in the office to see if they have any similar problem.
s0l1d
As my subject stated, the computer is running Win2k. I noticed that if I set the clock to a correct time (say 8:15) and then reboot, when the computer finished booting back into Windows, the clock is automatically adjusted 10 minutes slow (to 8:05).
I re-correct the time again, reboot, go into BIOS setup to double check, and the time is correct. But once exit BIOS setup and let it boot into Windows, the clock is again auto adjusted 10 minutes slow.
There is no Time Server in the network, the network is local and private and it's not connected to the internet at all, and there is no time sync program running on that computer.
Does anyone has an explaination for this? Anyone knows how to correct this problem? This is an office computer that I use. I haven't check the other computers in the office to see if they have any similar problem.
s0l1d
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Responses to this topic
How to Configure an Authoritative Time Server in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734
Windows Time Service White Paper
http://www.microsoft.com/windows2000/docs/wintimeserv.doc
The basic gist is to run set your time service to an external time server. The first link above will show you how.
Quote:SNTP defaults to using User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers. Remember this if you are behind a firewall.
If problems persist, create a batch file to fix this for ya and leave it in the startup ..... we had this issue with some 95 clients,
http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734
Windows Time Service White Paper
http://www.microsoft.com/windows2000/docs/wintimeserv.doc
The basic gist is to run set your time service to an external time server. The first link above will show you how.
Quote:SNTP defaults to using User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers. Remember this if you are behind a firewall.
If problems persist, create a batch file to fix this for ya and leave it in the startup ..... we had this issue with some 95 clients,
