Incorrect Time and Date on Domain Computers
I was doing maintenance work on a computer when I noticed that the clock was ahead by about five minutes. I went to change the clock, but that did not fix the problem. (Time immediately reverted back after a Windows Update reboot). I then remembered that the primary domain controller controls the time on every machine in the domain, and sure enough the rest of the computers were ahead by about five minutes. I am extremely anal about the time after experiencing the results of sloppy timekeeping.
During the last switch to daylight savings, my BlackBerry's time was not correctly syncing with Verizon and I unknowingly adjusted my car and wrist watch to it. While I was five minutes early for everything, I kept thinking that the world must be experiencing serious time problems - my GPS and television show times were wrong! I couldn't understand what was happening. I googled in hopes others were experiencing the same problem, thinking this was some widespread issue. It sounds laughable, but when you adjust every clock in your house, car, etc. - you live by that time. Fortunately, I figured the problem out before publishing some asinine article about how the world was experiencing a time delay.
With my recent time drama in mind, I considered this domain-wide time problem and decided it was worth resolving. My first instinct was that the battery in the domain controller needed replaced. Since it was after hours, I simply powered down the machine and changed the battery. These come in handy, so I usually have a few in my work bag. After booting the machine, I adjusted the clock and assumed all was well. Unfortunately, when I returned two weeks later for maintenance, the clock had again drifted by a few minutes. Subsequently, all of the computers in the domain had incorrect times. Time to start pulling hair out? Maybe not yet.
Something else to consider is the Microsoft NTP settings which come default on Microsoft Windows computers. What is the address? Ntp.Microsoft.com? Whatever it is, I am fed up. Obviously something changed my correct time and synchronized it with the wrong time, or maybe it isn't synchronizing at all. Regardless, I was able to enter the following commands into the command prompt to solve the problem.
net time /setsntp:pool.ntp.org
net stop w32time
net start w32time
The first command tells Windows which NTP server you want to use. The second two commands restart your time service. All of the computers on the domain now abide by the correct time.
Update: On Server 2008 R2 you have to use these commands instead:
w32tm /config /syncfromflags:manual /manualpeerlist:pool.ntp.org
w32tm /config /reliable:yes
w32tm /config /update
w32tm /resync
net stop w32time
net start w32time
August 24th, 2010 - 00:08
Worked a dream for the server (W 2003)
However the workstations XP Sp 3 refused to update
1.from command line or
2.automatically.
3.on reboot
Ideas?
August 24th, 2010 - 05:48
Are you experiencing the problem on all of your client machines or just on one? Do you have all of the latest Windows updates?
You could try running the net stop w32time and then starting it again, but a reboot should have taken care of that.
I can honestly say, I have used this command dozens of times and never had an issue. Something strange is up with that client pc.