Whats the deal with wireless and authentication

I have a large number of users who use wireless to connect their laptops, windows based tablets and other devices.  They do not physically connect to the network.  Every few months from most of these users I get a "The Trust Relationship between the workstation and the primary domain failed."

What do I need to turn on, or turn off, for proper authentication to happen so that they no longer get this message.  I also get this at one of our remote sites on physically connected hardware which connects via vpn, which does not have an AD server onsite.  All of our domain servers are 08+.  The domain/forest level is 2008.
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.

Joseph MoodyBlogger and wearer of all hats.Commented:
We saw the same issue in our environment though no where near as widespread as what you are reporting. We increased the machine password change interval and haven't see the problem since. According to MS, this should not have had anything to do with it though:


Here is some information I documented when troubleshooting this problem: http://deployhappiness.com/the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/
Craig BeckCommented:
It's not a wireless or config issue.  As Joseph says, it's related to the machine password.  For some unknown reason though Microsoft don't seem to acknowledge the fact.

This link will help you sort the problem...


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
CoffeeBlackAuthor Commented:
Thanks guys, it seems as though there are a number of ways this issue can be recreated.  And a couple of ways to quick fix it.  The quick fix I had down one of the two ways.  Log in as an admin, take it off the domain, add it back in.  I didn't have the command to basically fix it.

For us it has almost always been where there wasn't a MS dns/dhcp/ad server, and separately with wireless devices.  All relating back to the machine passwords it sounds like.  Thx all.
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
Active Directory

From novice to tech pro — start learning today.