Overview
Due to a corrupt Active Directory database the server was demoted to a normal member server using the DCPROMO utility. This was successful so we then DCPROMO again to make it a full Active Directory server. This recreated the SYSVOL share automatically which meant that users were now able to authenticate logon and default domain policies were applied. (From another DC, not the problem one.)
It should be noted that as part of the DCPROMO process, the system will automatically generate inter site links for replication. (which it has)
An account was deleted from another Active Directory server on 9th May and this still has not replicated to the problem DC and the event log show various NTDS replication errors such as EventID 1265 NTDS KCC, Event ID 1311 NTDS KCC and Event ID 13508 NTFRS.
All of these events point to a failure with replication between AD sites.
This is a copy of one of the events from the problem DC
Event Type: Warning
Event Source: NTDSKCC
Event Category: Knowledge Consistency Checker
Event ID: 1265
Date: 13/05/2002
Time: 16:06:32
User: N/A
Computer: HLYDCMX01
Description:
The attempt to establish a replication link with parameters
Partition: CN=Schema,CN=Configuration,DC=caaroot,DC=internal
Source DSA DN: CN=NTDS Settings,CN=LUTDCMX01,CN=Servers,CN=CAA-Luton,CN=Sites,CN=Configuration,DC=caaroot,DC=internal
Source DSA Address: 6a8e42e3-048e-4fba-ac90-d69f247d13c8._msdcs.caaroot.internal
Inter-site Transport (if any): CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=caaroot,DC=internal
failed with the following status:
Replication access was denied.
Strangely enough, the AD replication monitor also said that Horley is NOT adomain controller but it is. (DCPROMO proves that it is) .
Any ideas on this would be appreciated.