<div>
Try this procedure:<br />
<br />
<a href="http://support.microsoft.com/kb/290762" rel="ugc">http://support.microsoft.com/kb/290762</a><br />

</div>


<div>
To be honest, when I has similar problem, I tried that also with no luck, and few other things, but at the end I simply demoted DC, disjoined from domain, cleaned metadata, joined again and promoted DC again. It solved all the problems.<br />

</div>


<div>
We've researched a bit further, and have spotted this in the event log:<br />
<br />
Event Type: &nbsp; &nbsp; Warning<br />
Event Source: LSASRV<br />
Event Category: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SPNEGO (Negotiator) <br />
Event ID: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 40960<br />
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 02-03-2009<br />
Time: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 14:13:01<br />
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; N/A<br />
Computer: &nbsp; &nbsp; &nbsp; DEADLINEAUTH<br />
Description:<br />
The Security System detected an authentication error for the server cifs/DEADLINEPDC.deadline.<wbr />com. &nbsp;The failure code from authentication protocol Kerberos was &quot;{Operation Failed}<br />
The requested operation was unsuccessful.<br />
&nbsp;(0xc0000001)&quot;.<br />
<br />
For more information, see Help and Support Center at <a href="http://go.microsoft.com/fwlink/events.asp" rel="ugc">http://go.microsoft.com/fwlink/events.asp</a>.<br />
Data:<br />
0000: 01 00 00 c0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ...À &nbsp; &nbsp;<br />
<br />
Sounds like Kerberos is a sick dog. Is there an easy fix to this? <br />

</div>


<div>
Kerberos can cause such problems. Check this (there is plenty to read...):<br />
<br />
<a href="http://support.microsoft.com/kb/249256" rel="ugc nofollow">http://support.microsoft.com/kb/249256</a>
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
We have an otherwise healthy domain in a single physical location, but our Netlogon/Sysvol folders don't syncronize. AD replication between the 3 servers work fine, and I have no entries in the Error log that signifies that anything goes wrong. I've tried looking around for tools to diagnose this, but with little luck. DNS works, and the shares works fine for our users.<br />
I have <br />
&quot;The File Replication Service is no longer preventing the computer from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. <br />
&nbsp;<br />
Type &quot;net share&quot; to check for the SYSVOL share.&quot; entries on all 3 servers, so it seems like they just don't know that they have to be in sync. <br />
<br />
Any good ideas on how to work this out? <br />
<br />
I have already messed around with resetting Netlogon.chg, but with no result. 
</div>
</div>


Hi,

We have an otherwise healthy domain in a single physical location, but our Netlogon/Sysvol folders don't syncronize. AD replication between the 3 servers work fine, and I have no entries in the Error log that signifies that anything goes wrong. I've tried looking around for tools to diagnose this, but with little luck. DNS works, and the shares works fine for our users.
I have 
"The File Replication Service is no longer preventing the computer from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. 
 
Type "net share" to check for the SYSVOL share." entries on all 3 servers, so it seems like they just don't know that they have to be in sync. 

Any good ideas on how to work this out? 

I have already messed around with resetting Netlogon.chg, but with no result. 

Netlogon and Sysvol folders don't sync

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).