• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 522
  • Last Modified:

Trust relationship between this workstation and the primary domain failed

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
itc_sysadmin
Asked:
itc_sysadmin
3 Solutions
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
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
 
Lester_ClaytonCommented:
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
 
ComputerBeastCommented:
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
 
itc_sysadminAuthor Commented:
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
 
itc_sysadminAuthor Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now