Solved

Trust relationship between this workstation and the primary domain failed

Posted on 2011-09-22
5
478 Views
Last Modified: 2012-05-12
We currently have a windows 2003 domain and 8 Domain Controllers spread out in the organization. The setup is as follows:-
- HQ - 3 Domain Controllers
- Site 2 - 2 Domain Controllers (FSMO role holders)
and 3 other branch sites have a Domain Controller each.

An issue started cropping up on machines getting the Trust relationship issue when users try to login to them. The machine accounts seem to be alive and well on AD when it gets this trust issues and need to be re-added. Even after re-adding the machine to the domain some machines get the same error again a week or so after. We have yet to isolate it to a certain Operating System or maybe a culprit GPO. Right now it seems to be randomly happening across the domain. Is there any way of actually pinpointing the cause of this error that occurs on the machines??
0
Comment
Question by:itc_sysadmin
5 Comments
 
LVL 39

Accepted Solution

by:
Krzysztof Pytko earned 167 total points
Comment Utility
By default each computer in a domain changes its password every 30 days. When PC is not restarted at least once in this time or it's problem wth accessing DC then next time computer cannot log on into domain. Then you will see that error message which you posted here.

To be sure that everything is OK, schedule frequent workstations restart.

Additionally, please run on your DC in command-line

dcdiag /e /c /v
and
repadmin /showrepl /all /intersite /verbose

and review output to see if there are no errors in your domain environemnt (i.e. with replication)

Regards,
Krzysztof
0
 
LVL 9

Assisted Solution

by:Lester_Clayton
Lester_Clayton earned 167 total points
Comment Utility
Frequent causes of Trust Relationship Failed:

There is another computer in the same domain with the same name
Somebody is deleting the computer object
People are reverting to an earlier stage of the computer's life (System Restore, Snapshots, etc)

0
 
LVL 7

Assisted Solution

by:ComputerBeast
ComputerBeast earned 166 total points
Comment Utility
Hi all,

Take the PC out of the domain. Delete the workstation object from the domain (if it remains). Add the PC back into the domain

Hope it works.

Thank you
Anil
0
 

Author Comment

by:itc_sysadmin
Comment Utility
Thanks everyone for the replies. I have a feedback that this issue maybe happening to windows7 machines.

The exact issue is that after the machine is installed with win7, after about a week or so the machine gets kicked out of the network with that error. Re-adding to the domain works but a week later the same issue arises again.

Does anyone else face similar issues with win7 machines and was able to resolve it? Is this a vulnerability? And if so has MS released a patch yet on this issue?

Itc admin
0
 

Author Closing Comment

by:itc_sysadmin
Comment Utility
have done some research on the issue and found that it seems to be a vulnerability with win7 machines. didn't really get a confirmation on whether it was or not. may need to research some more.
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

My last post dealt with using group policy preferences to set file associations, a very handy usage for a GPP. Today I am going to share another cool GPP trick, this may be a specific scenario but I run into these situations frequently in my activit…
I'm sure that every Windows systems administrator has written, or at least used, a batch or VBS login script at some point in their career, whether it is to map network drives, install printers, or set some user preferences.  No more! With Window…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now