Looking for some help here. Mentally fried after trying to figure this out.
Overview of our servers
PDC - purple2
ops2 - DC\DHCP
NTMX2 - old mail server, DC and backup for AD
Below is the results of the "DCDIAG" command on the Server "Ops2"
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = ops2
The GUID based DNS Name resolved to several IPs (::1, 172.16.10.8), but not all were pingable. Replication and other operations may fail if a
non-pingable IP is chosen. The first pingable IP is 172.16.10.8.
[ops2] Directory Binding Error 5:
Access is denied.
This may limit some of the tests that can be performed.
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Central\OPS2
Starting test: Connectivity
......................... OPS2 passed test Connectivity
Doing primary tests
Testing server: Central\OPS2
Starting test: Advertising
......................... OPS2 passed test Advertising
Starting test: FrsEvent
......................... OPS2 passed test FrsEvent
Starting test: DFSREvent
The event log DFS Replication on server ops2.wallenpaupack.org could not be queried, error 0x5 "Access is denied."
......................... OPS2 failed test DFSREvent
Starting test: SysVolCheck
......................... OPS2 passed test SysVolCheck
Starting test: KccEvent
The event log Directory Service on server ops2.wallenpaupack.org could not be queried, error 0x5 "Access is denied."
......................... OPS2 failed test KccEvent
Starting test: KnowsOfRoleHolders
[PURPLE2] DsBindWithSpnEx() failed with error -2146893022,
The target principal name is incorrect..
Warning: PURPLE2 is the Schema Owner, but is not responding to DS RPC Bind.
[PURPLE2] LDAP bind failed with error 8341,
A directory service error has occurred..
Warning: PURPLE2 is the Schema Owner, but is not responding to LDAP Bind.
Warning: PURPLE2 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: PURPLE2 is the Domain Owner, but is not responding to LDAP Bind.
Warning: PURPLE2 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: PURPLE2 is the PDC Owner, but is not responding to LDAP Bind.
Warning: PURPLE2 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: PURPLE2 is the Rid Owner, but is not responding to LDAP Bind.
Warning: PURPLE2 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: PURPLE2 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... OPS2 failed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... OPS2 passed test MachineAccount
Starting test: NCSecDesc
......................... OPS2 passed test NCSecDesc
Starting test: NetLogons
......................... OPS2 passed test NetLogons
Starting test: ObjectsReplicated
......................... OPS2 passed test ObjectsReplicated
Starting test: Replications
[Replications Check,OPS2] A recent replication attempt failed:
From PURPLE2 to OPS2
Naming Context: DC=ForestDnsZones,DC=wallenpaupack,DC=org
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2019-07-09 15:57:41.
The last success occurred at 2019-05-23 11:35:10.
128 failures have occurred since the last success.
[Replications Check,OPS2] A recent replication attempt failed:
From PURPLE2 to OPS2
Naming Context: DC=DomainDnsZones,DC=wallenpaupack,DC=org
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2019-07-09 15:57:41.
The last success occurred at 2019-05-23 11:35:10.
128 failures have occurred since the last success.
[Replications Check,OPS2] A recent replication attempt failed:
From PURPLE2 to OPS2
Naming Context: CN=Schema,CN=Configuration,DC=wallenpaupack,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2019-07-09 15:57:41.
The last success occurred at 2019-05-23 11:35:10.
129 failures have occurred since the last success.
[Replications Check,OPS2] A recent replication attempt failed:
From PURPLE2 to OPS2
Naming Context: CN=Configuration,DC=wallenpaupack,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2019-07-09 15:57:41.
The last success occurred at 2019-05-23 11:35:10.
128 failures have occurred since the last success.
[Replications Check,OPS2] A recent replication attempt failed:
From PURPLE2 to OPS2
Naming Context: DC=wallenpaupack,DC=org
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2019-07-09 15:57:41.
The last success occurred at 2019-05-23 11:35:09.
128 failures have occurred since the last success.
......................... OPS2 failed test Replications
Starting test: RidManager
......................... OPS2 failed test RidManager
Starting test: Services
......................... OPS2 passed test Services
Starting test: SystemLog
The event log System on server ops2.wallenpaupack.org could not be queried, error 0x5 "Access is denied."
......................... OPS2 failed test SystemLog
Starting test: VerifyReferences
......................... OPS2 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : wallenpaupack
Starting test: CheckSDRefDom
......................... wallenpaupack passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... wallenpaupack passed test CrossRefValidation
Running enterprise tests on : wallenpaupack.org
Starting test: LocatorCheck
......................... wallenpaupack.org passed test LocatorCheck
Starting test: Intersite
......................... wallenpaupack.org passed test Intersite