{"id":245,"date":"2018-02-01T22:16:59","date_gmt":"2018-02-02T05:16:59","guid":{"rendered":"https:\/\/csispecialist.com\/?p=245"},"modified":"2018-02-01T22:16:59","modified_gmt":"2018-02-02T05:16:59","slug":"error-trust-relationship-between-workstation-and-primary-domain-failed","status":"publish","type":"post","link":"https:\/\/csispecialist.com\/index.php\/2018\/02\/01\/error-trust-relationship-between-workstation-and-primary-domain-failed\/","title":{"rendered":"Error “Trust Relationship between Workstation and Primary Domain failed\u201d"},"content":{"rendered":"

The Error “Trust Relationship between Workstation and Primary Domain failed\u201d does not come up often but it is scary when it does.\u00a0\u00a0 <\/span>The quick explanation for this error is that the Active Directory stores a password for the computers connecting to it and the machine that has this error somehow did not sync correctly while using that password.\u00a0 <\/span>Microsoft knows about this problem and made these tools specifically to fix it.<\/p>\n

Most sites tell you to un-register the computer with the domain, then re-register it.\u00a0 <\/span>This, in most cases, will create a new user profile. You will then need to rebuild and copy files and configurations from the old user directories to the new. Fortunately, there is a simpler and easier way of doing this.<\/p>\n

Both the above method and the one I am about to describe require you to login to the local machines\u2019 admin account.\u00a0\u00a0 <\/span>Here is a good time to point out that you should retain the username and password for all of your workstations administrator type account just for this purpose.<\/p>\n

Up to Windows 2012<\/h4>\n

Up to Windows Server 2012, you can use the Netdom command from either an elevated PowerShell or command prompt.\u00a0 <\/span>In windows 10 and Server 2016 they dropped this command and instead use the Reset-ComputerMachinePassword in PowerShell to accomplish this.\u00a0 <\/span>Windows Server 2012 can use either method.<\/p>\n

To use the Netdom command you will need to first\u00a0login as a local administrative user.\u00a0\u00a0 <\/span>If you forgot the password there are methods of recovering it but I won\u2019t discuss them in this article.\u00a0\u00a0 <\/span>After logging in you will need to open the command prompt with Administrator privileges.\u00a0 <\/span>Then run the command as follows:<\/p>\n

netdom resetpwd \/server:DC_NAME \/<\/strong>userd:USERNAME \/password:PASSWORD<\/strong><\/p>\n

You will want to change the following to match your system:<\/p>\n

    \n
  1. DC NAME<\/strong> to the name of your Domain Controller.<\/li>\n
  2. USERNAME<\/strong> to a domain user that has rights to join new computers to the Domain.<\/li>\n
  3. PASSWORD<\/strong> to either the above USERNAME<\/strong>\u2019s password or use an * to have the computer prompt you for it.<\/li>\n<\/ol>\n

    After this completes you can just reboot your computer and login again under your Domain.\u00a0 <\/span>Everything should work as normal.<\/p>\n

    Windows 2012 to current<\/h4>\n

    For Windows 2012 and beyond the same method is accomplished in PowerShell using the Reset- ComputerMachinePassword commandlet<\/p>\n

    Again, you will need to login with a local Administrator privileged account.\u00a0 <\/span>Then Open PowerShell with Administrator Privileges.\u00a0 <\/span>Once PowerShell is open you will use the following commandlet\u00a0:<\/p>\n

    Reset-ComputerMachinePassword -Server “DC01” -Credential Domain01\\Admin01<\/strong><\/p>\n

    You will want to change the following to match your system:<\/p>\n

    DC01<\/strong> to the name of your Domain Controller.<\/p>\n

    Domain01\\Admin01<\/strong> to your domain before the \\ and a user that has rights to join new computers to the Domain after the \\.<\/p>\n

    This will then prompt you for the Password for the user you specified.<\/p>\n

    Afterwards exit PowerShell and reboot your computer and login in again under your Domain.\u00a0 <\/span>Everything should work as normal.<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    The Error “Trust Relationship between Workstation and Primary Domain failed” does not come up often but it is scary when it does.   The quick explanation for this error is that the Active Directory stores a password for the computers connecting to it and the machine that has this error somehow did not sync correctly while … <\/p>\n

    Continue reading “Error “Trust Relationship between Workstation and Primary Domain failed\u201d”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[63,64],"class_list":["post-245","post","type-post","status-publish","format-standard","hentry","category-windows-general","tag-domain-error","tag-domein-trust-error"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t