Hi,
I have two Domain Controllers which provide redundant DC, DHCP and DNS services. One of the servers would not startup after a normal shutdown to replace a failed fan. The server appeared to be getting so far through the startup process and spinning up the
disks, but the screen remained blank - I think that the motherboard must have fried. Anyway, I swapped the disks into an identical server and tried to boot up the machine without connecting it to the network. The machine came up and looked to be operating
correctly, but did flash up a message about reconfiguring something - not sure what exactly.
I thought that the server was working fine, so connected it back to the domain, but unfortunately didn't realise that the clock was way behind the current date/time, so the server didn't connect properly until I noticed the time and reset it to current and
restarted the server. The machine then appeared to connect OK, but Windows asked to be reactivated (which I did).
The first indication of problems were an Event ID 2092 "This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any
of its partners since this server has been restarted. Replication errors are preventing validation of this role . . . . . . ." and now the DCs won't synchronise.
repadmin /showrepl on the (rebuilt) server says
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\DC1-DL360G4P
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 655c44df-9346-4c0b-9822-7aa1c9bd9825
DSA invocationID: c5e40518-52ed-47c9-8cb1-6d78ff89b979
==== INBOUND NEIGHBORS ======================================
DC=daveathome,DC=org
Default-First-Site-Name\DC2-DL360G4P via RPC
DSA object GUID: 50e35970-760a-4e1f-872f-dedbb8de04e9
Last attempt @ 2019-08-15 13:51:04 was successful.
CN=Configuration,DC=daveathome,DC=org
Default-First-Site-Name\DC2-DL360G4P via RPC
DSA object GUID: 50e35970-760a-4e1f-872f-dedbb8de04e9
Last attempt @ 2019-08-15 13:51:04 was successful.
CN=Schema,CN=Configuration,DC=daveathome,DC=org
Default-First-Site-Name\DC2-DL360G4P via RPC
DSA object GUID: 50e35970-760a-4e1f-872f-dedbb8de04e9
Last attempt @ 2019-08-15 13:51:04 was successful.
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.
And on the good server, says
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\DC2-DL360G4P
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 50e35970-760a-4e1f-872f-dedbb8de04e9
DSA invocationID: ca46f00b-f7ac-4c75-b1c8-9b7cf0b28092
==== INBOUND NEIGHBORS ======================================
DC=daveathome,DC=org
Default-First-Site-Name\DC1-DL360G4P via RPC
DSA object GUID: 655c44df-9346-4c0b-9822-7aa1c9bd9825
Last attempt @ 2019-08-15 14:16:03 failed, result -2146893022 (0x8009032
2):
The target principal name is incorrect.
286 consecutive failure(s).
Last success @ 2019-08-14 16:51:55.
CN=Configuration,DC=daveathome,DC=org
Default-First-Site-Name\DC1-DL360G4P via RPC
DSA object GUID: 655c44df-9346-4c0b-9822-7aa1c9bd9825
Last attempt @ 2019-08-15 13:55:08 failed, result -2146893022 (0x8009032
2):
The target principal name is incorrect.
24 consecutive failure(s).
Last success @ 2019-08-14 15:55:08.
CN=Schema,CN=Configuration,DC=daveathome,DC=org
Default-First-Site-Name\DC1-DL360G4P via RPC
DSA object GUID: 655c44df-9346-4c0b-9822-7aa1c9bd9825
Last attempt @ 2019-08-15 13:55:08 failed, result -2146893022 (0x8009032
2):
The target principal name is incorrect.
22 consecutive failure(s).
Last success @ 2019-08-14 15:55:08.
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.
It appears that the internal ID of the first server may have changed (?) and the linkage between the servers broken?
("The target principle name is incorrect")
Can someone PLEASE help me understand how to proceed from here to recover the replication etc.?
I really don't want to have to rebuild the domain controller and would struggle to do that properly anyway, but any guidance on how to use DCDIAG etc. to recover this state of affairs would be really appreciated
regards
Dave
Dave