DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
Seeing "The trust relationship between this workstation and domain failed"? Don't panic, potential fix is two lines of code in an admin. This issue is seen when the session logon is attempted through Remote Desktop Protocol, ICA, or directly at the console. Only logons using. This error message stated that the trust relationship between the workstation and the primary domain failed. You can see the actual error.
Although the restore operation succeeded, it had some unforeseen consequences. After the restoration, all of the other servers in the domain displayed an error message at log in. This error message stated that the trust relationship between the workstation and the primary domain failed.
You can see the actual error message in Figure 1. The reason why this problem happens is because of a "password mismatch. However, in Active Directory environments each computer account also has an internal password.
Fix Trust relationship failed issue without domain rejoining
If the copy of the computer account password that is stored within the member server gets out of sync with the password copy that is stored on the domain controller then the trust relationship will be broken as a result.
So how can you fix this error? Unfortunately, the simplest fix isn't always the best option. The easy fix is to blow away the computer account within the Active Directory Users and Computers console and then rejoin the computer to the domain. Doing so reestablishes the broken-trust relationship. This approach works really well for workstations, but it can do more harm than good if you try it on a member server.
The reason for this has to do with the way that some applications use the Active Directory. You will be able to do disconnected authentication, but in the case of a reset machine, remember that you may have to use an old password.
You need to make sure you have netdom.
Where you get netdom. Windows Server and Windows Server R2 ship with netdom. Google can help you get them. For other platforms see this link: If the broken machine is a domain controller it is a little bit more complicated, but still possible to fix the problem. Turn off the Kerberos Key Distribution Center service.
- The trust relationship between this workstation and domain failed, a Windows fix in two lines
- DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
- Error: The trust relationship between this workstation and the primary domain failed
You can do this in the Services MMC snap-in. Set the startup type to Manual.
Remove the Kerberos ticket cache. A reboot will do this for you, or you can remove them using KerbTray. You can get that tool here: Do these in conjunction with 5 below: Also, we know cases when user profile is not reconnecting correctly after rejoining. We will show how to restore a trust relationship and restore secure channel without domain rejoin and reboot!
Fix Trust relationship failed issue without domain rejoining – TheITBros
The method is fast and efficient. To use it, login to the target system with Local administrator!!! You can check for a secure connection to the domain using Netdom by using the following command: This is the fastest and most convenient way to reset the password of a computer that does not require a reboot.
Unlike the Netdom utility, PowerShell 3.
You can install it manually see here on this platforms: If you want to restore a trust relationship as a local Administrator, run PowerShell console and execute this command: Cmdlet does not display any messages on success, so just change the account, no reboot required.
Accordingly, if you log on to the computer under the local account and attempting to execute the command, you will receive an access denied error. Because of this, the method does not always work.
As you can see, it is quite easy to solve Trust relationship failed issue in a domain! Hope this was useful for you! You may also like: Add Calendar Permissions in Office via Powersh