Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

The trust relationship between this workstation and the primary domain failed

Posted on 11/04/201617/08/2026 Christian By Christian No Comments on The trust relationship between this workstation and the primary domain failed
  1. Home
  2. Windows Server
  3. The trust relationship between this workstation and the primary domain failed
Login screen displaying 'Other user' with an error message about trust relationship failure between the workstation and the primary domain.

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. 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.

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.

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.

Pop-up message indicating successful change to computer name/domain, displaying 'Welcome to the WORKGROUP workgroup.' with an OK button.

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.
Windows warning dialog about restarting the computer, alerting that other users are logged in and risk losing data. Options to continue with 'Yes' or 'No'.

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.

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
Windows Server Tags:DNS, Domain, Domain Controller, Microsoft Windows, Windows 10

Post navigation

Next Post: How to run the Cisco ASDM launcher

Related Posts

  • MBAM Replacement
    MBAM extended support ends April 2026: Find alternative solution Security | Vulnerability Scans and Assessment
  • article 1280x720.aa742702
    How to create a custom view in Windows Event Viewer Windows Server
  • needthetools
    Fix no BitLocker Recovery tab in Active Directory Windows Server
  • windows update 03
    How to target WSUS clients with the registry keys Windows Server
  • troubleshooting Active Directory Replication
    How to troubleshoot Active Directory Replication issues Network | Monitoring
  • Fixed Sysprep Generalize 1
    How to Fix The Virtual Desktop is Not Sysprep Generalized Virtualization

More Related Articles

MBAM Replacement MBAM extended support ends April 2026: Find alternative solution Security | Vulnerability Scans and Assessment
article 1280x720.aa742702 How to create a custom view in Windows Event Viewer Windows Server
needthetools Fix no BitLocker Recovery tab in Active Directory Windows Server
windows update 03 How to target WSUS clients with the registry keys Windows Server
troubleshooting Active Directory Replication How to troubleshoot Active Directory Replication issues Network | Monitoring
Fixed Sysprep Generalize 1 How to Fix The Virtual Desktop is Not Sysprep Generalized Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

veeaam100

Veeam Vanguard

  • Encapsulationset to Auto
    Error – Command rejected: An interface whose trunk encapsulation is “Auto” can not be configured to “trunk” mode Network | Monitoring
  • microsoft edge
    How to forcefully remove Microsoft Edge Browser the hard way from your Windows device Windows
  • MSSQLlicensing
    Microsoft SQL Evaluation period has expired: How to upgrade SQL Server instance Oracle/MSSQL/MySQL
  • images 7
    The plugin filter file/etc/ansible/plugin_filters(yml) does not exist – Skipping Configuration Management Tool
  • sdf
    Creating an offline local repository in Linux Linux
  • Delete Edit or Revert a Snapshot on vSphere
    Manage VMware Snapshots: Delete or Edit or Revert a Snapshot Virtualization
  • vmwarefrsd4
    CVE-2021-31693: VMware Tools for Windows update addresses a denial-of-service vulnerability Network | Monitoring
  • WPScan Banner
    How to scan WordPress Websites With WPScan For Security Vulnerabilities Security | Vulnerability Scans and Assessment

Subscribe to Blog via Email

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

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

Tags

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

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.