DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
If you Google “the trust relationship between this workstation and to come up very often and there has been a lot of positive response. On Windows Vista and Windows 7 you can get it from the Remote Server Administration Tools ( RSAT). If the broken machine is a domain controller it is a little bit more. In Windows 7 Professional I got an error saying that "the trust relationship to complete so it must have been reconnecting the "relationship". How to: FIX: the trust relationship between this workstation and the primary domain failed I have had this issue only on Windows 7 computers.
Error: The trust relationship between this workstation and the primary domain failed
The most obvious classic way to restore trust relationship is: Reset local Admin password Move computer from Domain to workgroup Reboot Reset Computer account in the domain using ADUC console Rejoin computer to the domain Reboot again This method is the easiest, but not the fastest and most convenient way and requires multiple reboots.
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!
- DON’T REJOIN TO FIX: The trust relationship between this workstation and the primary domain failed
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.
How To Fix Domain Trust Issues in Active Directory -- promovare-site.info
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! 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. 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. As a freelance writer, Posey has written thousands of articles and contributed to several dozen books on a wide variety of IT topics. Prior to going freelance, Posey was a CIO for a national chain of hospitals and health care facilities.
He has also served as a network administrator for some of the country's largest insurance companies and for the Department of Defense at Fort Knox.
In addition to his continued work in IT, Posey has spent the last several years actively training as a commercial scientist-astronaut candidate in preparation to fly on a mission to study polar mesospheric clouds from space.
Another option is to unplug the machine from the network and log in with domain user.
Fix Trust relationship failed issue without domain rejoining
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. 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: