OK so this is a fairly serious problem.
The DCs in this place seem to be all broken except one that NTFRS doesn't work from. It is the only DC advertising SYSVOL and has an error in FRS that states:
Log Name: File Replication Service
Date: 18/09/2020 00:04:25
Event ID: 13562
Task Category: None
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller DC2.domain.local for FRS replica set configuration information.
The nTFRSSubscriber object cn=domain system volume (sysvol share),cn=ntfrs subscriptions,cn=dc2,ou=domain controllers,dc=domain,dc=local has a invalid value for the attribute frsMemberReference.
<Provider Name="NtFrs" />
<TimeCreated SystemTime="2020-09-17T23:04:25.000000000Z" />
<Channel>File Replication Service</Channel>
<Data>The nTFRSSubscriber object cn=domain system volume (sysvol share),cn=ntfrs subscriptions,cn=dc2,ou=domain controllers,dc=domain,dc=local has a invalid value for the attribute frsMemberReference.
Looking at the setting in ADSIEdit
Under Default Naming > Domain > Domain Controllers > NTFRS Subscriptions:
I could see that the error was being caused by this value at not set
When I tried to enter the correct value, taken from a different DC with the name corrected, it threw an 0X20B5 error saying that the data was invalid.
Operation Failed. Error Code: 0x20b5
The name reference is invalid
00020B5: AtrErr: DSID-03152804, #1:
(Constraint_ATT_TYPE), data 0, Att 903b
But it would let me enter the data if I used the value from the other DC. So the DC I was trying to fix must have lost its settings in ADSIEdit > Domain> System > File Replication Services.
So I navigated to System > File Replication Services, and sure enough:
The server was missing.
So I recreated the nTFRSmember object with the settings based on the entries for the other servers, making sure I was checking all writable values in ADSIEdit and after applying the data, I was able to return to the frsMemberReference and correct the entry and it was accepted.
I was then able to restart the NTFRS service which then started trying to replicate.
All I have to do now is find out what is stopping the communication between the DCs as they are still not actually advertising...
Edited by moderator
3 months ago
| Reason: Not specified