maredzki
asked on
Windows 2008R2 AD time sync issue with NTP
I used Microsoft Link to configure my clock on the domain controller to which the 3 others point to. I rolled back the clock so that all 4 have the same time (3 minute difference) and ran the tool. I entered pool.ntp.org,0x1 in the settings for the server.
Checked after a while using w32tm /query /peers on the source domain controller, got the following:
C:\Users\administrator.AD0
#Peers: 1
Peer: pool.ntp.org,0x1
State: Active
Time Remaining: 705.1104493s
Mode: 1 (Symmetric Active)
Stratum: 2 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 6 (64s)
HostPoll Interval: 6 (64s)
Checked on the other domain controllers (which pointed to it for time):
C:\Users\administrator.AD0
#Peers: 1
Peer: SERVER01
State: Active
Time Remaining: 239.9177806s
Mode: 1 (Symmetric Active)
Stratum: 3 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 10 (1024s)
HostPoll Interval: 10 (1024s)
The time was OK yesterday when I left. This morning the clock rolled forward to the same as yesterday, 3 minutes ahead.
What else can I check? This server is a VM on VMware 5.5 and have the "Sync with host" unchecked.
Checked after a while using w32tm /query /peers on the source domain controller, got the following:
C:\Users\administrator.AD0
#Peers: 1
Peer: pool.ntp.org,0x1
State: Active
Time Remaining: 705.1104493s
Mode: 1 (Symmetric Active)
Stratum: 2 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 6 (64s)
HostPoll Interval: 6 (64s)
Checked on the other domain controllers (which pointed to it for time):
C:\Users\administrator.AD0
#Peers: 1
Peer: SERVER01
State: Active
Time Remaining: 239.9177806s
Mode: 1 (Symmetric Active)
Stratum: 3 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 10 (1024s)
HostPoll Interval: 10 (1024s)
The time was OK yesterday when I left. This morning the clock rolled forward to the same as yesterday, 3 minutes ahead.
What else can I check? This server is a VM on VMware 5.5 and have the "Sync with host" unchecked.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Madison,
I apologize for not responding but I made some changes last week to the host, especially the NTP. It was running a few minutes ahead as was the PDC so I did put it on pool.ntp.org and since last Thursday it kept time. I also rolled back the clock on the PDC and all of the other DCs have kept the time as well. So even though there were no indications that the VM is taking time from the host (indications meaning that the checkboxes were not checked for the time sync with host), the VM was still syncing time with host.
Once the host had proper time, it seems the rest followed.
Thank you for your response and I'm pretty sure the diagnostics you added to the comments will help others if this is encountered.
I apologize for not responding but I made some changes last week to the host, especially the NTP. It was running a few minutes ahead as was the PDC so I did put it on pool.ntp.org and since last Thursday it kept time. I also rolled back the clock on the PDC and all of the other DCs have kept the time as well. So even though there were no indications that the VM is taking time from the host (indications meaning that the checkboxes were not checked for the time sync with host), the VM was still syncing time with host.
Once the host had proper time, it seems the rest followed.
Thank you for your response and I'm pretty sure the diagnostics you added to the comments will help others if this is encountered.
w32tm /debug /enable /file:C:\windows\temp\w32t
w32tmlog.txt