Solved

NTP server, one DC updates correctly another adds 4 minutes

Posted on 2013-02-07
4
337 Views
Last Modified: 2013-02-26
I have two data centers in two different physical locations about 60 miles apart (in the same timezone).  I have them both acting as NTP servers for the respective domains.  They are syncing time to north-america.pool.ntp.org.  When I restart the w32time service both system logs indicate they are receiving good data from north-america.pool.ntp.org.

I then change the time manually so both servers have the same time and run w32tm /resync /nowait on each server.  One server corrects itself to the correct time.  The other server corrects itself to the correct time for just a instant then it suddenly goes 4 minutes into the future.

Every resync does the same thing.  They match for just a second then boom 4 minutes ahead.  Any suggestions on how I find out whats really going on here with this one server?

The server that works correctly is running Server 2003 SP2, the one that is visting the future is 2008R2.
0
Comment
Question by:-Darvin-
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 29

Expert Comment

by:becraig
ID: 38865893
Do you get any events in the system log when this occurs  ?
0
 

Author Comment

by:-Darvin-
ID: 38868397
I tried this again.  Manually changing the time and the behavior has changed.  As I said previously.  I would change the time, run the w32tm command it would change to the 'right' time and then forward.  Now, when I change the time I don't even get a chance to run the command before it puts itself back.  It's nearly instant.

System log shows this.

The system time has changed to ¿2013¿-¿02¿-¿08T16:00:00.000000000Z from ¿2013¿-¿02¿-¿08T16:09:30.964103500Z.

The system time has changed to ¿2013¿-¿02¿-¿08T16:00:00.000000000Z from ¿2013¿-¿02¿-¿08T16:00:00.000000000Z.

The system time has changed to ¿2013¿-¿02¿-¿08T16:09:34.765000000Z from ¿2013¿-¿02¿-¿08T16:00:03.796496900Z.

Very strange behavior.
0
 

Accepted Solution

by:
-Darvin- earned 0 total points
ID: 38914979
I found the solution.  Something I neglected to mention was that the domain controller is a hyper-v guest.  It works so well I often forget it's virtual.  The problem is that hyper-v has it's own time keeping mechanism that it passes along to the guests.  By disabling this feature in the integrated services area hyper-v stopped changing the time.  I don't know where it was getting the bad time from as the hyper-v server was taking time from the domain controller.  Perhaps it was in bios of the hyper-v server.  

In either case that solved the problem.
0
 

Author Closing Comment

by:-Darvin-
ID: 38929145
This is the solution.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A quick step-by-step overview of installing and configuring Carbonite Server Backup.
Learn about cloud computing and its benefits for small business owners.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question