In our first domain join failure case, we looked at the scenario when the local computer name was corrupted https://chentiangemalc.wordpress.com/2012/07/27/case-of-the-domain-join-failure/
Now we look at this scenario: Joining a computer to a domain, we are told “Object already exists” Even though it doesn’t!
Searching AD Users & Computers we find:
So I start a Network Monitor trace, configured to use Windows Parsers. Network Monitor is here http://www.microsoft.com/en-us/download/details.aspx?id=4865 and the latest parsers are available here http://nmparsers.codeplex.com/
Parsers are selected in Tools –> Options
I then set the network monitor filter to monitor NetLogon traffic. From this could see a specific domain controller was the culprit for saying the object already existed:
Sure enough, when connected Active Directory Users & Computers to the specific domain controller in question computer account was found.
Computer account could not be deleted. Ultimate cause was Domain Controller had run out of free disk space…
This issue could also be caused by delays in replication. When joining to domain, all DCs are checked against…Network Monitor will easily tell you why your domain joins are failing in most cases. And on Windows 7 and later you can just netsh trace start capture=yes report=yes persistent=yes to get the required logging, even if a reboot occurs in-between, just netsh trace stop to finish your trace, then open the .ETL file in Network Monitor.