Windows domain time issue

I am having an issue with time on my domain. The time is 10 minutes behind. I have attempted to use MS KB articles to resolve this issue and also added external NTP services but the time continually reverts to the 10 minute delay which is affecting all workstations.

The DC is virtualized and I have verified that the server is not synching to the hardware time that is hosting the the vm.

Below is the output of my w32tm query.

Anyone have any thoughts of on a resolution?

T.I.A



Hmmm ... W32time, the timekeeping service in Windows. I experienced enough trouble with that piece of crap (esp. when in NTP mode) to avoid using it whenever I can.

My recommendation:
Use a Windows port of the classic *ix NTP service, sync a master (or two, three) with an external source (i.e. from pool.ntp.org) and sync the clients and DCs to the master(s). The NTP service software is free. Easy to install and configure, works like a charm and is stable as a rock. And it is nicer when it comes to one of the rare cases of troubleshooting.

See this article for more details and a "How To".

The NTP service has a low ressource footprint, therefore the NTP functionality could be hooked onto existing machines or VM's like webservers, ftp servers, mailservers or database hosts - even in a DMZ - without visible performance impact.

If securtity is an issue, you might as well place radio controlled clock appliances into your LAN who serve time very reliable and precise.



Hmmm ... W32time, the timekeeping service in Windows. I experienced enough trouble with that piece of crap (esp. when in NTP mode) to avoid using it whenever I can.

My recommendation:
Use a Windows port of the classic *ix NTP service, sync a master (or two, three) with an external source (i.e. from pool.ntp.org) and sync the clients and DCs to the master(s). The NTP service software is free. Easy to install and configure, works like a charm and is stable as a rock. And it is nicer when it comes to one of the rare cases of troubleshooting.

See this article for more details and a "How To".

The NTP service has a low ressource footprint, therefore the NTP functionality could be hooked onto existing machines or VM's like webservers, ftp servers, mailservers or database hosts - even in a DMZ - without visible performance impact.

If securtity is an issue, you might as well place radio controlled clock appliances into your LAN who serve time very reliable and precise.



Please read the attached to see if that helps you--have used this for 10 plus years to fix any time issues--works 99% of the time. In one instance where time is an critical issue (and I cannot fix it) I use http://www.nist.gov/pml/div688/grp40/its.cfm -- it has worked for me on a bank's server for 10+ years (see download button on right side of page).



@frankhelk...Thanks for this but it does not seem to run as a service. Is this right?



Nope - your query sure runs in foreground, but W32time runs as service under all circumstances. And when running in NTP mode, it's a constant source of hassle (just last week I helped a coworker with w32time not syncing correct to the DC).

Still the same advice: Use the classic NTP client ...

The classic NTP ports run as service, too, and could be identified in task manager as ntpd.exe.



No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:Accept: frankhelk (http:#40662778)

If you feel this question should be closed differently, post an objection and a moderator will read all objections and then close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer

Share this

Related Posts

There was an error in this gadget