NTP server, one DC updates correctly another adds 4 minutes
Posted on 2013-02-07
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.