I am trying to install active directory on a member server in an existing domain. The existing Domain Controller is located accross a WAN link setup via a VPN connection (box-to-box)solution. The two networks see each other fine, I can ping back andforth, and the promotion runs through most of it’s process successfully, then gives and error “Directory service failed to create the server object for CN=NTDS,CN=
I have spent hours checking the domain controller, and everything looks fine there.
It appears to be failing in the sites and service establishment. But I can’t figure out why.
The other side to all this is that the member server and several other 2k pro machine’s on this remote end take 10 to 15 minutes to load personal settings. some of the 2k pro machine at this remote end logon fine. I have checked DNS on domain controller, all looks ok and shows the remote member server. WINS is running on the domain controller, and setup in member server to look for on domain controller. What am I missing?
Is there a special way of doing this across wide area networks? Why the long logins if DNS is running fine? The promotion to DC was intended to solve the login problem, but I can’t get it to finish successfully, and must indicate a problem with the existing DC…?
Thanks in advance for any help!