The trust relationship between this workstation and the primary domain failed

[Chuey]

Hello,

I have a slew of computers running BootCamp with OS X 10.9.5 and Windows 7 for a STEM lab. Recently I've been having the same few computers losing their trust relationship to our domain every other day. The error I believe is:

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

Microsofts KB describes how to fix, which i already knew. I'm just wondering why this is happening so frequently and if anyone else has this issue. If so, is there something you did to stop it from happening so often? I'm sure it has something to do with BootCamp but not 100% sure, it seems to be the same computers each time.

Thanks in advance

[thoule]

Are you binding the Mac and PC side with the same name? Sounds like they are stepping on each other's accounts. When you bind a computer, it establishes a trust with a hidden password. If you bind a computer to the domain with the same name (computer account), then it'll reset that password for the new bind and thus break the trust relationship for the old bind. Hope that made sense - I haven't had coffee today.

[Chuey]

I'll have to double check the names when I get a chance. I'll let you know if that was it.

Thanks @thoule

[emily]

The times that we've seen this have been times when the machine doesn't check in to the domain after x amount of days (I think for us, 30?) on the LAN and the domain decides its an inactive object and that trust relationship is broken. If you unbind/rebind it should fix it.

[jarednichols]

Time may also have something to do with it. Check that both Windows and Mac are doing time against your domain controller.

[Look]

We have had the same behaviour as @emilykausalik on occassion, machines that are not booted in one OS for more than a month or two often end up unbound when they do.

[Josh_Smith]

We see the domain trust break on Windows 7 machines if they run Startup Repair....W7 can trigger Startup Repair on boot after a non-graceful shutdown. We saw that issue frequently until we disabled Startup Repair.