Discussion Locked

Aditional domain controller

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

Hi all
Can some one please tell me how to configure aditional domain controller to primary domain controller if primary domain controller fails.
Thank in advance

regrds
Ravi

8 replies

by thl0508

You may look at how to setup a BDC (Backup Domain Controller). It 's also depend on what kind of OS you are using too.

by cg it

NT dcpromo promote to PDC

W2k/2003 with AD [and they are within the same domain {ack configured to handle authentication for the zones} ]you don't need to worry about it as DCs are peers with each other.

by ravi_t

Iam using 2000server operating system in two systems Sys1 & Sys2. And one 2000professional
I configured Sys1 as parent.com & sys2 as additional domain controller for parent.com
Now Iam unable to logon to domain from professional system, when I make Sys1 down

by curlergirl

First, in Win2K with Active Directory, there is no such thing as a "PDC" or BDC" - all DCs are peers. I'm assuming this means that Sys2 right now is configured as a member server, not a domain controller. To make it a domain controller, you need to run dcpromo on Sys 2. To do this, simply open the Run command (Start/Run), and type "dcpromo" (without the quotes). This will open a GUI program that walks you through promoting the member server to a domain controller.

Hope this helps!

by cg it

hummm Once again as my first answer said, W2K with AD, all domain controllers are peers with one another PROVIDED that you setup your peer DC as Active Directory intergrated [or a standard secondary. Now if you'e dont all that, you also have to specify the second DC as a DC to go to if the first one isn't available in your TCP/IP properties on the W2K workstation. If you didn't list your second DC in the DNS section of TCP/IP properties, then your client won't look for it. IF you have DHCP running, you add in the second DC in the options. That way the client will always get the list of DCs in which to authenticate to.

by cg it

just because you created a DC and replicate Active Directory between the 2 doesn't mean that DHCP automatically changes to include the DC as authoritative for the zone. You have to add in the DC. If you run a static scheme, as I mentioned above, you have to specify the DCs IP address in TCP/IP.

This discussion is closed to new replies.