A Solution to the 5722 Problem on W2K3 Server *if* You Did Something Silly
by Zube (zube@stat.colostate.edu)
Created: May 28, 2010
Updated: May 28, 2010
http://www.stat.colostate.edu/~zube/docs/5722.txt

[Additions, suggestions, corrections or thoughtful discussion always welcome.]

I set up a set of XP machines, but the very last one was giving me
fits.  After adding it to the domain, the Windows 2003 server would
show the following in the logs:

The session setup from the computer WIN10 failed to authenticate.
The name(s) of the account(s) referenced in the security database is
WIN10$.  The following error occurred: Access is denied.

I found the error in an MSKB document:

http://support.microsoft.com/kb/216393

The first suggestion in the document is to use netdom.exe to reset the
security channel.  Unforunately, netdom.exe is not installed by default
on Windows 2003.  It is part of a group of programs that are on the
2003 CD and downloadable, but they aren't installed by default.
Wonderful.

Once installed, I tried the suggestion:

netdom reset WIN10 /domain:mydomain

which resulted in the incredibly helpful "error 67, the network name
cannot be found".  I tried everything I could think of including the
/pleasemicrosoftIloveyou and /Ibelievethatactivationreallythwartspiracy
options, but tens of attempts yielded no solution and no useful data.

Useless.

It turns out that in my haste to set up the last two machines, I 
had named them identically.  So I removed each in turn from the
DOMAIN, renamed one, then added both back.  The errors stopped.

So, if you get this error shortly after adding machines to a DOMAIN,
see if you've named two identically by mistake.  It may save you
from the pain and frustration of Microsoft's KB articles and netdom.exe.