Link to home
Create AccountLog in
Avatar of DarthRater
DarthRater

asked on

Clock Skew Errors in Ultrasound Tool

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
Date:            6/7/2013
Time:            3:15:41 AM
User:            N/A
Computer:      BRIDGE
Description:
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-5A84-4643-926A-CA11487D84A8 -> 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.
 
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
   "System\CurrentControlSet\Services\NtFrs\Parameters"
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.
ASKER CERTIFIED SOLUTION
Avatar of Sarang Tinguria
Sarang Tinguria
Flag of India image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Agree with Sarang, check the Time Server settings on all DCs and make PDC as authoritative Time Server for the domain and rest of the machine shall sync with PDC server for Time source.

Authoritative Time Server
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of DarthRater
DarthRater

ASKER

Lots of great answers here. Upon further investigation the previous firm did not set up proper time sync. I theorize that some of the other time servers had an issue which temporarily skewed the time and then auto-corrected.

Now I's no longer an issue. Thanks everyone.

Also, the below link is a great way to keep the PDCe flexible with the time server.

http://www.xenappblog.com/2012/time-server-group-policy/
I would never prefer to deploy any group policy for time sync  in normal circumstances