the trust relationship between the workstation and the primary domain failed

This error message keeps popping up when we try to log on to a work PC?

"the trust relationship between the workstation and the primary domain failed"

Our server is Win 2003

Does anyone know what this means and how it can be fixed?

IP4IT StaffAsked:
Who is Participating?

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

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.

Don S.Commented:
It means that the machine account in the directory has lost synch with the workstation.  This can happen if one or the other was restored recently or there is another machine named the same in the domain.  If it is the later issue,  change the name on the machine,  join it to a work group,  restart, then rejoin it to the domain and restart once again.
Muhammad MullaSystems AdministratorCommented:
This normally happens if the password for the computer account in the domain database doesn't match the one that is local on the computer itself, or the computer account has the incorrect role in AD.

There is a Micorsoft KB for this issue here:

You can also reset the password from PowerShell V3 using

Reset-ComputerMachinePassword [-Credential <PSCredential>] [-Server <String>]

Open in new window

Benjamin VoglarIT ProCommented:
Hi. Make rejoin to the domain. This could happened if you have problem with the time.
Make sure that all clients and domain controllers have the same time.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Mal OsborneAlpha GeekCommented:
I have always found this problem easiest to fix by just rolling the machine out and in to the domain.

Before you do anything though, check the clocks on the CD and workstation are correct. If they differ, this is one error you are likely to see.

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
IP4IT StaffAuthor Commented:
Thank you for all the replies.

Sorry that I have not responded.

I will try these today.

Hopefully none of them will cause a secondary issue such as causing issues between the relationship of MS Outlook on the PC and MS Exchange on the server.
Danny ChildIT ManagerCommented:
Most of the solutions above achieve the same thing, in terms of resetting the **PC** password on the account (which is not visible to users) - it's just used for authentication.

If you choose to take the PC out of the domain, make sure you know a -local- admin password for it first.  You'll need that to log into it once it's removed from the domain.

If it is this kind of problem, it will have no effect on the Outlook/Exchange setup.  They're all based around user passwords, not PC AD accounts.
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.