I use Ultrasound to manage my replica set, and lately I have been alerted of clock skews on several of my DCS. Looking in the event log revealed the following.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13548
Time: 3:15:41 AM
The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside the range of plus or minus 30 minutes.
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\BRIDGE01\8B02DD2A-5
7D84A8 -> B\WATER02$ RemoteCxt"
The detected time difference is: 291 minutes.
Note: If this time difference is close to a multiple of 60 minutes then it is likely that either this computer or its partner computer was set to the incorrect time zone when the computer time was initially set. Check that the time zone and the system time are correctly set on both computers.
If necessary, the default value used to test for computer time consistency may be changed in the registry on this computer. (Note: This is not recommended.)
To change this parameter, run regedit.
Click on Start, Run and type regedit.
Click down the key path:
Double click on the value name
"Partner Clock Skew In Minutes"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
Odd thing is, I checked the time, date, and Time Zone on all the DCs and they are perfect in sync. I also have them pointed to my auth time server. I don't undersand why they would suddenly be 200+ minutes of difference.