Heres a interesting one, maybe someone who has been around AD a bit might see what ever it is that Im missing.

On a client site, The client has built a server and a domain, called the domain domain.dns...name changed to protect the client... (why .dns?? I dont know...)

they set up AD with thier tech who "kinda knew about windows2000" UGH.
Then the same person took the same CD and key to another machine and built another server (yep thats called piracy in my book, but not my call) but did not make this one AD, just joined it to the domain.
Heres the problem I run into.
the client wants to install AD on the second server, making it a "secondary" domain controller, if you will. No problem, just run teh wizard right? <sarcasm> RIGHT </Sarcasm>

The wizard states that the domain does not exist or the Domain controller can not be contacted.

Now I can ping it, browse it, connect to it any other way I need to, so there is definately a connection from computer a to computer b. I tried putting the main servers DNS as teh ONLY DNS entry on the secondary, I tried adding the IP to the host file. I tried NSLOOKUP to see if I could talk to it, I cant. Im not sure where to turn next, a search on google produces some things, but most of it points to all Ive tried already. A search on microsoft is a copy of what I found on google.

Anyone out there up on the AD?
TIA
Avenger