On 4 October 2010 10:25, Greg Keogh <[email protected]> wrote: > Folks, I just noticed that the time on all of the machines in my domain are > drifting forward. I’ve never configured any time services on the domain, > it’s the default behaviour. > > > > I *thought* that the Win3K domain controller automatically became the time > server in a domain and all of the other machines would sync to it. That > seems to be true, as all machines are wrong by the same amount. > > > > I also *thought* that the domain controller would sync to an external > server, like time.windows.com, which I can see in the registry for the > W32Time service. But I guess it’s not doing that. > > > > I’m still web searching this subject and getting lots of confusing advice. > Asking network admins, is there some simple trick I can pull to make the > domain controller sync to the external source?
Not daylight-savings related? Is the time on the DC the same as all other machines? If so, then they are syncing. The culprit is likely to either be a bad timezone setting. Also, if the DC is running as a guest VM, you might want to check the host as well. Hyper-V has/had issues with the clock drifting under certain circumstances. > > Cheers, > > Greg
