Not only did this help me solve my problem, it made me laugh at work -thanks to the underwear gnome reference

tyvm

Hi Luke, even though my situation is the same, the way I resolved the issue is as follow:
My first PC where I created the VPC was Vista x32. Somehow, the network admin deleted it because he thought it was just an unused PC. However, I created it again, and when I tried to login to the domain, thats when I the message above appeared. What I did was to check with the network admin to see if my VPC existed. Of course, I had renamed it just so it can be clear that it was needed. We checked and I noticed that my VPC was not registered on the domain. I simply then went to add it to the domain, restarted, and login without any problems. I simply right-clicked on MyComputer->Properties, and under the ‘Computer Name’ tab, I clicked on the ‘Network ID’ button and followed the wizard.

I double checked then with the network admin and whala … my VPC then appeared registered on the domain. I hope this helps someone else!!

Thanks a lot. It save me a lot of time.

AWESOME! Thanks for saving us a ton of work

I am not WORTHY! Thank you! You have saved me.

[…] tool may sometimes cause the stupid “Windows cannot connect to the domain” glitch that I described here. So far this only happened to a single machine I renamed this way – most were just fine. […]

Am not sure if the length of the computer name (FQDN) would cause this or play up so try and keep the length to a ‘meaningful’ minimum characters/alphabets!

I have the same issue. Can you remove and add Exchange, SQL servers from domain domain without causing other AD issues? Thanks

You just saved my weekend. I owe you a case of beer or something. Thanks

In my case computer account was disabled. Launched active directory searched for computer name R.click and enable. Done.