I have this one new Windows 7 desktop that (and it's clones (different network IDs)) looses domain trust relationship much more often than any other Windows 7 computers in the office.
We use 2003 as AD DC.
I have discovered this when and updated user logon script wasn't executing. Tried run gpupdate /force and received processing of group policy failed because of lack of connectivity to the domain controller
.
Anyone got ideas where to start troubleshooting? We recently moved from Sophos to Avira, so AV doesn't seem to have influence on it. It's a mint install, so I wonder what I could've screwed up...
When this happens, log into the computer using a local account and try to ping the domain name.
If you can't, start there (it could be anything from a bad cable to bad DNS settings to a routing problem).
If you can, the problem becomes more complex, but is generally still a DNS problem of some kind.
As a general rule, the authoritative nameservers for your AD domain should be domain controllers, ultimately. This means that all your hosts have to be using DNS controlled by you; if someone has managed to statically configure something like 8.8.8.8 in your DNS settings, or you are using public DNS resolvers as "secondary" DNS servers, you will get problems like this.
It's also possible, though unlikely, that some malware or something is trying but failing to man-in-the-middle traffic to the DC; the solution to that is generally to reimage the workstation. It's probably DNS though, and not this.