Last Few BDCs Perform Full UAS Synch Instead of Partial (114802)



The information in this article applies to:

  • Microsoft LAN Manager 2.2

This article was previously published under Q114802

SUMMARY

During a partial synchronization of the user accounts subsystem (UAS) database, the last few backup domain controllers (BDCs) start performing a full synch about ten minutes after the first BDC starts performing the partial. You can find this out by using DOMAINVU or SYNCSTAT.

MORE INFORMATION

This happens when the BDC clock is more than ten minutes off from the PDC clock or when the PDC is very slow and takes more than ten minutes to process the partial synchs.

The PDC sends the BDC a UAS replication pulse, which contains the current time at the PDC. The BDC then waits a random amunt of time and responds with an authenticator and the PDC pulse time. The PDC compares the time to its current time in CheckAuthenticator(). If the time difference exceeds:
   #define RATIONAL_TIME (10 * 60) \\ min.
				
the BDC partial replication is refused with NERR_TimeDiffAtDC (0x999, 2457) and a full synch is begun.

This error is recorded in the BDC error log as:
   Program     Message                    Time
   ===========================================

   NETLOGON     3226             mm-dd-yy hh:mm
   NET3226:  Error synchronizing with primary
             domain controller [PDC name]
    99 09
				

Modification Type:MajorLast Reviewed:9/30/2003
Keywords:KB114802