Hello Marcus Mostamandi,
Thank you for posting in Microsoft Community forum.
You can try to reset secure channel between problematic DC and its partner DC.
netdom resetpwd /s:<server> /ud:<domain\User> /pd:*
-
/s:<server>is the name of the domain controller to use for setting the machine account password. It's the server where the KDC is running. -
/ud:<domain\User>is the user account that makes the connection with the domain you specified in the/sparameter. It must be in domain\User format. If this parameter is omitted, the current user account is used. -
/pd:*specifies the password of the user account that is specified in the/udparameter. Use an asterisk (*) to be prompted for the password. For example, the local domain controller computer is Server1 and the peer Windows domain controller is Server2. If you run Netdom.exe on Server1 with the following parameters, the password is changed locally and is simultaneously written on Server2. And replication propagates the change to other domain controllers:
Reset domain controller's password with Netdom.exe - Windows Server | Microsoft Learn
Here is a similar thread for your reference.
[f02c-b7a6-58b-6fc0] (microsoft.com)
I hope the information above is helpful.
If you have any question or concern, please feel free to let us know.
Best Regards,
Daisy Zhou