Solved

Windows 7 Workstations Trust Relationship Failed

Posted on 2014-02-21
15
429 Views
Last Modified: 2014-03-04
I have a mixture of Windows 7 workstations with Windows XP and after a power failure in my environment, all the Windows 7 workstations are coming up with the Trust Relationship Failed error.

I have tried removing them from the AD and readding them, but they still come up with a failed trust relationship each time we reboot.  Usually, removing and adding solves the problem when I've seen it in the past.

Any ideas?
0
Comment
Question by:ParadiseITS
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 2
  • 2
  • +4
15 Comments
 
LVL 19

Expert Comment

by:helpfinder
ID: 39876781
try to reset computer account in AD (Users and Computers > Reset computer account)
0
 
LVL 19

Expert Comment

by:Peter Hutchison
ID: 39876787
Check that all the relevant services on running on the DCS (how many DCs do you have) e.g.
Active directory domain services, Netlogon, DNS server etc. Run a DCDiag tool to check that it is working properly.
0
 
LVL 9

Author Comment

by:ParadiseITS
ID: 39876828
RE: try to reset computer account in AD (Users and Computers > Reset computer account)

We even did better than that and deleted the computer account all together, still no luck.
0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 9

Author Comment

by:ParadiseITS
ID: 39876829
RE: Check that all the relevant services on running on the DCS (how many DCs do you have) e.g.
Active directory domain services, Netlogon, DNS server etc. Run a DCDiag tool to check that it is working properly.

Two DCs -- can we run DCDIAG during the day?
0
 
LVL 19

Expert Comment

by:helpfinder
ID: 39876855
yes you can
0
 
LVL 4

Expert Comment

by:amclaughlin01
ID: 39876865
We have this issue crop up from time to time, and we have found running through the network wizard on the workstation 99% of the time resolves the issue.  We originally were doing the remove and readd to the domain, but the network wizard seems to work quicker and faster.  

Plus, if you remove and readd, then you need to recreate any permissions or group memberships.  The network wizard seems to reset the computer account/password and retains all group memberships, rights, etc...
0
 
LVL 9

Author Comment

by:ParadiseITS
ID: 39877402
Yes, that is usually the case.  But in this case it does not work.
0
 
LVL 9

Expert Comment

by:Zenvenky
ID: 39877423
Is this issue occurs with all the Win7 workstations or couple of machines?

Just take one corrupt machine for testing purpose and update NIC drivers, then join it to domain. I'm sure it will work this time. Also check for event ID netlogon 5719 in Win7 workstations, if it exists then you have to update the NIC drivers.

Netlogon Event ID 5719
0
 

Expert Comment

by:MortensonIT
ID: 39877500
Have you tried the NET DOM command?

netdom resetpwd /server:domaincontroller /userd:domain\USERNAME /passwordd: *

I use this instead of doing the disjoin/rejoin process.
0
 
LVL 9

Expert Comment

by:Zenvenky
ID: 39877703
Netdom meant for domain controllers not for workstations.

http://technet.microsoft.com/en-us/library/cc788073.aspx
0
 
LVL 5

Expert Comment

by:Mdlinnett
ID: 39880511
Have the DC's had graceful shutdowns or did they just go off too?

Using a Win 7 PC as a test, do a System restore to a point in time prior to the power loss then remove / re-add to the Domain.  See if that sticks.

It does sound AD related but it might be worth giving that a shot.
0
 
LVL 9

Author Comment

by:ParadiseITS
ID: 39880539
The power pulled them all down, no graceful shut downs.  We noted that the time was off on the DC -- we have set the time back to match and are going to try rejoining on Monday.
0
 
LVL 5

Expert Comment

by:Mdlinnett
ID: 39880696
Have the DCs since been given a graceful shutdown / restart? I have seen DCs behave erratically until they have been given a clean, graceful restart following an incident like this.
0
 
LVL 9

Accepted Solution

by:
ParadiseITS earned 0 total points
ID: 39886797
The issue was the time offset -- once that was corrected everything worked fine.
0
 
LVL 9

Author Closing Comment

by:ParadiseITS
ID: 39902798
We solved it ourselves.
0

Featured Post

Free Webinar: AWS Backup & DR

Join our upcoming webinar with experts from AWS, CloudBerry Lab, and the Town of Edgartown IT to discuss best practices for simplifying online backup management and cutting costs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
This article demonstrates probably the easiest way to configure domain-wide tier isolation within Active Directory. If you do not know tier isolation read https://technet.microsoft.com/en-us/windows-server-docs/security/securing-privileged-access/s…
This Micro Tutorial will give you basic overview of the control panel section on Windows 7. It will depth in Network and Internet, Hardware and Sound, etc. This will be demonstrated using Windows 7 operating system.
This Micro Tutorial will give you a introduction in two parts how to utilize Windows Live Movie Maker to its maximum editing capability. This will be demonstrated using Windows Live Movie Maker on Windows 7 operating system.

749 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