Windows Server

Trust relationship between this workstation and the primary domain failed

Windows domains provide network administrators with ways to administer a great number of devices and control them from a central location. Domains are generally made up of computers on the same local network. When a computer is joined to a domain, it doesn’t use its own local user accounts. User accounts and passwords are managed on the domain controller. When you log into a computer on that domain, the computer authenticates your user account name and password with the domain controller. This means you can log in with the same username and password on any computer joined to the domain. You may want to see the following articles: How to synchronize your on-premises AD with Azure Active Directory using the Azure AD Connect tool, Configure TCP/IP Parameters: Post OS Installation and configuration of Windows Server 2019 properties, and how to fix the trust relationship between this workstation and the primary domain failed.

This often happens when your computer password is "Out of Sync" between the computer and the domain controller and its reset after some time (30 days). Here is a similar error, see "The security database on the server does not have a computer account for this workstation trust relation", see the following link.

Here are ways to fix these issues.
Method 1: Try resetting the password of the computer, on your DC (Active Directory Users and Computers) and try again. Most times this fix does not work.

Then locate the machine (isolate it by removing the network cables, and turning off the Wireless etc, so it has no network connections) and login as an administrator.
– Click on start, on the search or run box option type the following command

sysdm.cpl

And press enter.
– On the Computer Name tab
– Click on Change and select the workgroup option, and type in Workgroup and press OK.

Note: This involves you leaving you domain, but if this is the case use the Netdom option (method 2) to fix it and reboot as it is easier.

Rerun sysdm.cpl again and re-join it to your domain again and supply the domain user account name.
Note: This step will definitely require a restart.

Method 2: This method is a good fix as leaving the Domain is usually not recommended. Ensure to remove all network cables and turn off the Wireless as well.
– Type this command below on windows command prompt

netdom.exe resetpwd /s:{domain controller name} /ud:{username} /pd:*

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x
Kindly subscribe to TechDirectArchive
This is default text for notification bar