Discussion Locked

dcpromo fails in existing domain

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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=,CN=servers,CN=,CN=sites,CN=configuration,DC= on please ensure credentials have sufficient access to add a replica. "could not find a domain controller for this domain"
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!

6 replies

by reference

DNS on member server is pointing to domain controller. should I have DNS running on member server?
dcpromo.log file from member server gives this info:
[INFO] Error - The Directory Service failed to create the server object for CN=NTDS Settings,......Please ensure
the network credentials provided have sufficient access to add a replica. (1908)
07/18 17:47:48 [INFO] NtdsInstall for ... returned 1908
07/18 17:47:48 [INFO] DsRolepInstallDs returned 1908
07/18 17:47:48 [ERROR] Failed to install to Directory Service (1908)
The dcpromoui.log files give this info:
dcpromoui t:0x5DC 00310 DcSiteName :
dcpromoui t:0x5DC 00311 ClientSiteName :
dcpromoui t:0x5DC 00312 Error 0x0 (!0 => error)
dcpromoui t:0x5DC 00313 Exit myDsGetDcName

by tduval

Answering just a small part of your pbm : slow connecting machines. As you attach to the domain, especially if you have an exchange server, all datas from c:\doc&setting\user are copied from station to server. This may take a while, with a vpn.

Check on the server, in profiles, you'll find all personnal documents, and, worse, all e-mails...

by reference

Whats the preferred way of configuring this environment? Have AD running at both sites, and configure replication to occur after hours? This is the intention, if I can just get past the promotion process, and/or fix the problem, I should be ok

by reference

I successfully got the server promoted to Active Directory by loggin in with alternate credintials (not administrator). The KB article you referenced appears to indicate that the administrator account could cause the problems I was having, but the scenario is completely different. (child domains, etc..) It still doen't make sense to me, but because of the profile issue I was experiencing, I figured it couldn't hurt to try alternate credintials...and it worked. Thanks for the input!

This discussion is closed to new replies.