The trust relationship between this computer and domain is broken

Error: The trust relationship between this workstation and the primary domain failed

the trust relationship between this computer and domain is broken

How to: FIX: the trust relationship between this workstation and the primary Here is how to fix it without leaving and rejoining the domain. TO FIX: The trust relationship between this workstation and the primary domain failed however, most of them ask you to rejoin your machine to the domain. If the broken machine is a domain controller it is a little bit more. The easy fix is to blow away the computer account within the Active Directory Users and Doing so reestablishes the broken-trust relationship.

Take Exchange Server, for example. Exchange Server stores messages in a mailbox database residing on a mailbox server. However, this is the only significant data that is stored locally on Exchange Server. All of the Exchange Server configuration data is stored within the Active Directory.

the trust relationship between this computer and domain is broken

In fact, it is possible to completely rebuild a failed Exchange Server from scratch aside from the mailbox database simply by making use of the configuration data that is stored in the Active Directory. The reason why I mention this particular example is that the Exchange Server configuration data is stored within the computer object for that server.

So with that in mind, imagine that a trust relationship was accidentally broken and you decided to fix the problem by deleting the Exchange Server's computer account and rejoining the computer to the domain. By doing so, you would lose all of the configuration information for that server. Worse yet, there would still be orphaned references to the computer account scattered elsewhere in the Active Directory you can see these references by using the ADSIEdit tool.

the trust relationship between this computer and domain is broken

In other words, getting rid of a computer account can cause some pretty serious problems for your applications. A better approach is to simply reset the computer account. Right click on the computer that you are having trouble with.

Select the Reset Account command from the shortcut menu, as shown in Figure 2. When you do, you will see a prompt asking you if you are sure that you want to reset the computer account.

Click Yes and the computer account will be reset. You can reset the computer account through the Active Directory Users and Computers console. In case you are wondering, computer accounts can also be reset through PowerShell version 2 or higher. The cmdlet used for doing so is Reset-ComputerMachinePassword.

Repair broken Windows trust relationship between domain controller and client machine

In my experience, broken trust relationships probably aren't something that you will have to worry about on a day-to-day basis, but they can happen as a result of using backup software or imaging software to revert a server to a previous state. When this happens, the best course of action is to reset the computer account. For those with Powershell skills, this is a much better option.

  • 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
  • Fix Trust relationship failed issue without domain rejoining

Powershell v3 ships with the latest version of Windows and can be downloaded from Microsoft: You can fix this by opening Powershell with administrative rights and running Update-Help.

You can use the Get-Credential cmdlet for a secure way to generate a PSCredential, which can be stored in a variable and used in a script. The Server parameter is the domain controller to use when setting the machine account password.

A better fix Just change your computer password using netdom. You need to be able to get onto the machine. I hope you remember the password. Another option is to unplug the machine from the network and log in with domain user. 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. You can do this in the Services MMC snap-in.

Repair broken Windows trust relationship between domain controller and client machine | TechiesWeb

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.