Windows 2003 R2 servers with Windows XP and Vista clients
Three Domain Controllers:
PDC1 - PDC and all primary FSMO roles on primary subnet - VMware
DC2 - Secondary DC on primary subnet - VMware
DC3 - Secondary DC on small secondary subnet - Physical Server
The Time on the domain over the past month crept from 1 to 5 minutes faster
than real time. The time on PDC1 and DC2 were correct. The time on DC3 was
incorrect by 5 mins. When I ran NET TIME command on PDC1, it showed the
time source to be DC3. I manually changed the time on DC3. I ran the
command on all PCs and servers - NET TIME /SYNC /PDC1 /YES on PDC1. Time
on the domain computers then returned to normal.
Even though DC3 is attached to a smaller secondary subnet,
When you run the command:
NET TIME on all PCs and servers that are attached to primary subnet, the result shows
the time from DC3.
When you run the following command:
w32tm /query /source
On all Vista PCs that are attached to primary subnet, the result shows the
time from DC3.
How do you suggest troubleshooting this problem? I would feel better
knowing that PDC1 is the time source for the Domain.
We already had followed the suggestions in KB 816042 about a year ago and we have not had any time issues until this one. DC3 is about 4 months old.
On the Time GPO, the following is set:
Windows Time Service
Configure Windows NTP Client
Listed there were the following: NtpServer - Set TO -
PDC1.Domain.com Type - Set to - NTDS5