Windows 7 Workstations Trust Relationship Failed

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?
LVL 9
ParadiseITSAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

helpfinderIT ConsultantCommented:
try to reset computer account in AD (Users and Computers > Reset computer account)
Peter HutchisonSenior Network Systems SpecialistCommented:
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.
ParadiseITSAuthor Commented:
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.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

ParadiseITSAuthor Commented:
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?
helpfinderIT ConsultantCommented:
yes you can
amclaughlin01Commented:
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...
ParadiseITSAuthor Commented:
Yes, that is usually the case.  But in this case it does not work.
ZenVenkyArchitectCommented:
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
MortensonITCommented:
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.
ZenVenkyArchitectCommented:
Netdom meant for domain controllers not for workstations.

http://technet.microsoft.com/en-us/library/cc788073.aspx
MdlinnettCommented:
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.
ParadiseITSAuthor Commented:
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.
MdlinnettCommented:
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.
ParadiseITSAuthor Commented:
The issue was the time offset -- once that was corrected everything worked fine.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ParadiseITSAuthor Commented:
We solved it ourselves.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.