Difference between revisions of "The trust relationship between this workstation and the primary domain failed"
Jump to navigation
Jump to search
m (Robot: Cosmetic changes) |
|||
| Line 26: | Line 26: | ||
Also check the timezone is correct. | Also check the timezone is correct. | ||
| − | Fixes a Potential problem where kerberos and the AD server get out of sync. | + | Fixes a Potential problem where kerberos and the AD server get out of sync. Has failed to permanently resolve the problem on sliceyToo, but did make it go away for a day while rebooting failed. |
== Reset Machine Password == | == Reset Machine Password == | ||
| Line 37: | Line 37: | ||
Reference: [http://www.implbits.com/about/blog/tabid/78/post/don-t-rejoin-to-fix-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/default.aspx DON'T REJOIN TO FIX] | Reference: [http://www.implbits.com/about/blog/tabid/78/post/don-t-rejoin-to-fix-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/default.aspx DON'T REJOIN TO FIX] | ||
| − | I have tried rejoining the computers to domain. | + | I have tried rejoining the computers to domain. It didn't fix. |
== Remove Stale Entries to the Old Domain Controller from ldap == | == Remove Stale Entries to the Old Domain Controller from ldap == | ||
| − | The previous Domain Controller with all the FSMO roles was named vm. | + | The previous Domain Controller with all the FSMO roles was named vm. It died a sudden death and was not cleanly demoted from the domain. |
Revision as of 05:00, 19 July 2014
The Issue
Some of the computers on the network display this error:
The trust relationship between this workstation and the primary domain failed.
No user is able to log in.
Potential Solutions
Reboot
Sometimes rebooting clears the error as a workaround
Setup Time Sync
w32tm /config /manualpeerlist:bob.ad.pumpingstationone.org,0x8 /syncfromflags:MANUAL w32tm /config /update net stop w32time net start w32time w32tm /resync
Also check the timezone is correct.
Fixes a Potential problem where kerberos and the AD server get out of sync. Has failed to permanently resolve the problem on sliceyToo, but did make it go away for a day while rebooting failed.
Reset Machine Password
netdom RESETPWD /Server:bob /UserD:PS1\hef /PasswordD:*
Attempted on sliceyToo, has not yet been attempted elsewhere.
Reference: DON'T REJOIN TO FIX I have tried rejoining the computers to domain. It didn't fix.
Remove Stale Entries to the Old Domain Controller from ldap
The previous Domain Controller with all the FSMO roles was named vm. It died a sudden death and was not cleanly demoted from the domain.