Many people fix this issue by taking the system off the domain and then rejoining it. This can be a little painful since:
- It involves two reboots
- When you disjoin it you have to place it in a workgroup which will then create unwanted records in your WINS database
- It can have profile implications
netdom resetpwd /s:<domain controller>
Obviously the user specified must have the writes to join a computer to the domain (remember every user is allowed to do that 10 times, after that they willl need to be delegated that permission. Also, this must be run in an admin command prompt on the broken machine. Here is as example:
netdom resetpwd /s:mydomaincontroller /ud:mydomain\mick /pd:myawesomepassword
Notes: You will have to reboot the system once after this to straighten things out and on Vista/Windows 7/Windows 8 you may find that the 'Network and Sharing" center will show 'No Internet connectivity'. If it does then just tell the operating system to run diagnostics and it will burst into life. I have not been able to explain this last nuance.