Y
Y Joe
Guest
We have 2 DCs (Windows server 2008 R2 Enterprise) in our exchange domain, as one of them (not the GC) failed to startup properly after applying patch, we have restored it with the backup a day before.
The DC was restored with non-authoritative mode with the procedure in the link below, and boot into DSRM on the first boot,
How to recover a Domain Controller (DC) - Best practices for AD protection
After restoring, the NTDS replication between servers failed with the error “The target principal name is incorrect”.
we found a solution in the link below
https://support.microsoft.com/en-us...ion-error-2146893022-the-target-principal-nam
In the first normal boot of the restored DC,- DNS on the restored DC can be launched
- Repadmin /replicate successful from GC to DC
- REPADMIN /SHOWREPS all passed
- REPADMIN /SHOWREPL all passed
- REPADMIN /replsummary with “The target principal name is incorrect” error- REPADMIN /SYNCALL with “The target principal name is incorrect” and exited with fatal Win32 error: 8440 (0x20f8)
After the above test and rebooting the restored DC, DNS failed to launch with access denied error. Some connectivity test failed as well.
As the top resolution in the above link doesn’t resolve the issue, it is suggested changing the password on the PDC Emulator operations master role holder with netdom resetpwd.
https://support.microsoft.com/en-sg...cipal-name-is-incorrect-when-manually-replica
which means we have to make amendment on GC ( currently the only workable DC) in production site. We hope to know is there any alternative in stead of making amendment on the GC.
Any one has idea on how to solve the replication error with “The target principal name is incorrect”? Thank you.
Continue reading...
The DC was restored with non-authoritative mode with the procedure in the link below, and boot into DSRM on the first boot,
How to recover a Domain Controller (DC) - Best practices for AD protection
After restoring, the NTDS replication between servers failed with the error “The target principal name is incorrect”.
we found a solution in the link below
https://support.microsoft.com/en-us...ion-error-2146893022-the-target-principal-nam
In the first normal boot of the restored DC,- DNS on the restored DC can be launched
- Repadmin /replicate successful from GC to DC
- REPADMIN /SHOWREPS all passed
- REPADMIN /SHOWREPL all passed
- REPADMIN /replsummary with “The target principal name is incorrect” error- REPADMIN /SYNCALL with “The target principal name is incorrect” and exited with fatal Win32 error: 8440 (0x20f8)
After the above test and rebooting the restored DC, DNS failed to launch with access denied error. Some connectivity test failed as well.
As the top resolution in the above link doesn’t resolve the issue, it is suggested changing the password on the PDC Emulator operations master role holder with netdom resetpwd.
https://support.microsoft.com/en-sg...cipal-name-is-incorrect-when-manually-replica
which means we have to make amendment on GC ( currently the only workable DC) in production site. We hope to know is there any alternative in stead of making amendment on the GC.
Any one has idea on how to solve the replication error with “The target principal name is incorrect”? Thank you.
Continue reading...