Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows Server » The trust relationship between this workstation and the primary domain failed

The trust relationship between this workstation and the primary domain failed

Posted on 11/04/201606/04/2023 Christian By Christian No Comments on The trust relationship between this workstation and the primary domain failed

Windows domains provide network administrators with ways to administer 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. In this article, you will learn how to fix “the trust relationship between this workstation and the primary domain failed”.

Why was the error ‘The trust relationship between this workstation and the primary domain failed’ prompted?

This often happens when your computer password is “Out of Sync” between the computer and the domain controller. And it reset after some time (30 days). Here is a similar error. “The security database on the server does not have a computer account for this workstation trust relation”. Please see the following link. Here are some similar articles. Active Directory Forest – Trees and Domain and Sites. How to set up a third-party DNS server on a Linux Server, and how to set up a third-party DNS server on a Linux Server. How to enable Hyper-V on a VMware Workstation.

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.

Here are ways to fix the trust relationship

Method 1: Fix PC and Domain Out of Sync

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 log in 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 your 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.

Please learn how to fix the Security Database on the Server does not have a Computer account for this workstation. How to add a second Domain Controller, What happens when WDS and DNS are installed on the same Windows, and AD Connect Sync Service not running: Cannot proceed because the sync service is not running.

Method 2: Fix PC and DC Out of Sync

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 the Windows command prompt.

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

I hope you found this blog post helpful on how to fix the Trust relationship between this workstation and the primary domain failed. If you have any questions, please let me know in the comment session.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:DNS, Domain, Domain Controller, Microsoft Windows, Windows 10

Post navigation

Next Post: How to run the Cisco ASDM launcher

Related Posts

  • Banner
    How to determine Tombstone Lifetime in Active Directory Windows Server
  • Add a second domain to your domain
    How to add a new Domain Controller to an Existing Domain Windows Server
  • Screenshot 2020 07 28 at 15.34.51
    Nslookup unknown: Fix cannot find non-existent domain Windows Server
  • v13 harding   Veeam
    Hardening Your Infrastructure: A Guide to VMware VBS and MS GPO Credential Guard in VBR v13 Backup
  • Perform Site Maintenance or reset this site greyed out
    Fix “Perform Site Maintenance or reset this site” greyed out Windows Server
  • Distributed File System DFS
    All About Distributed File System Windows

More Related Articles

Banner How to determine Tombstone Lifetime in Active Directory Windows Server
Add a second domain to your domain How to add a new Domain Controller to an Existing Domain Windows Server
Screenshot 2020 07 28 at 15.34.51 Nslookup unknown: Fix cannot find non-existent domain Windows Server
v13 harding   Veeam Hardening Your Infrastructure: A Guide to VMware VBS and MS GPO Credential Guard in VBR v13 Backup
Perform Site Maintenance or reset this site greyed out Fix “Perform Site Maintenance or reset this site” greyed out Windows Server
Distributed File System DFS All About Distributed File System Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • Screenshot 2021 02 01 at 12.25.27
    MySQL Workbench could not connect to MySQL server Oracle/MSSQL/MySQL
  • ADO Self hosted agent
    How to Create Self-Hosted Agent for Azure DevOps Pipelines Automation
  • Screenshot 2020 05 13 at 19.23.25
    AWS Command-Line Interface: How to configure AWS CLI [Part 1] AWS/Azure/OpenShift
  • Restrict the number of tabs a user can open in Chrome and Edge
    Restrict the number of tabs a user can open in Chrome and Edge Network | Monitoring
  • MBAM Client
    How to Check if MBAM Agent is installed on Windows PC Windows
  • images 3
    Install Minimal Container Templates on Proxmox Server Virtualization
  • Resolvederror MBAM
    MBAM Policy was detected: Verify the OU used for pre-deployment does not apply MBAM policy Windows Server
  • Windows Server 2019
    The virtual machine has terminated unexpectedly during startup with exit code 1 (1×0): Failed to open a session for the virtual machine Windows Server 2019 Virtualization

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,824 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.