DC time is slow - 15 seconds = 28 seconds, causing havok on entire domain

The PDC DC in the domain has since yesterday started having the clock run slow. Example - 15 seconds is really 28 seconds. We have removed the updates that were applied just before this all happened, first we applied the updates of the 15th (we release them in batches), then all this happened. so the next day we applied to apply the system updates, and we hoped it would correct the ntp issue from the night before  -
on the 15th (these are mostly IE updates)
976662
971961
982632
981332
on the 16th (these are mostly Win updates)
2121546
2347290
982802
2259922
981322
981550
975558
2141007

We have set the clock to an external source at University of Toronto but as it sync's the clock is still running slow. This DC is a VM so it shouln't be the BIOS battery is dieing.


keystonetechAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Danny McDanielConnect With a Mentor Clinical Systems AnalystCommented:
if you have multiple hosts and have vmotioned the vm at all, you might try powering down the vm completely and then powering it back on.  doing a restart or reset won't do the same job...you need to completely destroy the world that vm lives within.  I have heard of an occaisional issue with timing getting messed up after a vmotion and if you have DRS it could have been migrated without you knowing it.

Also, the global recommendation from VMware is that you use external time synchronization and not rely on VMware tools to do your time sync, so make sure that you can use NTP or another utility to keep your DC's time up to date.
0
 
ewkellyCommented:
Look at the bios of the machine that the vm is running on.
 
0
 
bgoeringCommented:
More info please. Windows version? Virtualization platform (ESX, VMware Server, Hyper-V, etc)
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
kevinhsiehCommented:
I had problems when running MS Virtual Server 2005 R2 and it did the same thing you describe. It really sounds like the virtualization layer. I suggest looking for patches, and reboot the host machine.
0
 
ChiefITCommented:
most firewalls will block the port needed to synchronize from broadcasted time.

Instead, I use Symmtime on the PDCe in order to synch with an outside time server...

Symmtime uses port 80 instead of port 123 for time synchronization.

Symmtime was created by Symmetricom, and they make Time servers (like atomic clocks, and GPS servers) for network time. The utility is SUPER easy to configure. Also, Symmetricom has a second utility called LMcheck. This checks your domain computers to see how out of synch they are with the PDCe.

I recommend both utilities.

http://www.symmetricom.com/resources/downloads/symmtime/
0
 
keystonetechAuthor Commented:
0
 
keystonetechAuthor Commented:
Thanks to everyone for being prompt and helping - danm66 you were very close
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.