The Trust relationship between the workstation and Domain Failed -Win7

Hello,

You need to start doing some trouble shooting within Active Directory.

What is the OS of the Server? Has any recent changes been made? Have you migrated to another server? How many servers? If more than one, are they replicating?

Please provide an ipconfig /all of the problem PC and an ipconfig /all of the Server.

On the Server open CMD and type Dcdiag to diagnose the domain state. If its windows Server 2003 or earlier then you will have to download the windows support tools found here:
Download: Windows Server 2003 Service Pack 2 32-bit Support Tools - Microsoft Download Center - Download Details


Dave

It doesn't appear to be a domain issue. Why look there all of a sudden? I have a simple 2008R2 domain in native mode - no replication, no changes in weeks. All of a sudden a windows 7 pro 64bit machine that was joined in, "crashes" or whatever. User reboots it and no more trust relationship. I assume it was trying to install updates since there are pending updates on the login screen that didn't finish, but now local accounts nor network accounts work. This is a dell computer. I will have to boot from CD and try to reset local account passwords to get in and chkdsk the things and pull logs to be sure, but from what I can gather in this thread, these aren't people with domain issues!

If the trust relationship between a PC and the domain controller fails its because it isn't authenticating correctly. You can't rule out a DC problem without looking into it.

There are a lot of reasons for why this happens. I had one a few weeks ago which was cause due to a duplicate Computer name on the network. Two PC's tried to authenticate with AD which caused the trust to fail.

Do the Dcdiag and post the results

Hi all,

I re-imaged a whole floor (140) Windows PCs with a fully updated image with the latest windows patches on it. All were done last week. Just today i've had reports that out of 12 randomly checked PCs, 8 of them came up with the trust relationship error............AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

Ok, need to get to the bottom of this, can anyone help troubleshoot this, can post any logs or stats if needed.

Hello,

Please start a new thread for your question.

If its only 8 PC's then I would re-join the domain to see if that sorts it. Check the Computer names to make sure they are not the same.

If it doesn't fix it then you need to look at the DC's event logs.

Thats 8 randomly today!!!! Over the past month we have MANUALLY rejoined the said PCs back into the domain, and then again they fall again a few days later.

We are regularly having to rejoin the SAME PCs back into the domain, so I need a fix for this which is permenant not something that we have to keep fixing on a daily basis.

Have you checked the PC names? tried renaming the PC and then joining it back onto the domain?

Are they all connected to the same switch? - Frequent disconnections could cause the problem.

the pc name is correct, and yes we've joined the pc back to the domains 100's of times.... that is no joke, we are sick and tired of keep having to do this.

I am sat next to two PCs, both with same image, one has the trust error, the other doesn't. Identical image, same DNS/DHCP settings. Ipconfig is the same. The PCs are both in the same switch as well.

On the broken one, in the event log under system there is event 3210's...

This computer could not authenticate with \\******* , a Windows domain controller for domain *******, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.

I can login locally into the broken PC, internet access is fine etc, so what the hell can this be?????

Maybe the TechNet solution will help. This one has to do with the Certification Authority services.

The trust relationship between this workstation and the primary domain failed

Tried that link, but not relevant to what I have happening here.

Also set the Machine Password Maximum Age to 999 using GPO
Since then it was quiet, but surely enough we've had another 10 fail today...

Surely I can't be the only experiencing this...