Additional Domain Controller Failure

[Guest]

I have a W2k domain controller with a few client workstations. I recently decided to add an addtional domain controller to the domain for better availability and of course for backup.

I can make changes on either domain controller and the chnages are automatically replicated to the other domain controller.

But when the first/original domain controller is down or offline, the second one does not rise up to its responsibilties and users cannot logon to the domain.

Any suggestions will be most welcome and many thanks in advance
AK

 

[Cary Shultz [A.D. MVP]]

AKZ,

Make the other, newer DC a DNS Server as well as a Global Catalog Server.
This will help. However, it could be a problem that one of the five fsmo
roles is not available ( as I presume that the first DC holds all five of
the fsmo roles ).

HTH,

Cary

I have a W2k domain controller with a few client workstations. I recently

decided to add an addtional domain controller to the domain for better
availability and of course for backup.

I can make changes on either domain controller and the chnages are

automatically replicated to the other domain controller.

But when the first/original domain controller is down or offline, the

second one does not rise up to its responsibilties and users cannot logon to
the domain.

 

[Guest]

Hi

Thanks cary for the response.

I tried to make the second DC a DNS server. but when domain users try to login while the first DC is offline, the logon fails. The error message is that the domain could not be found

I have a feeling that the solution could be in fsmo settings? How do you make fsmo available to the second DC

Also, Do I need to make the second DC also a DHCP server?
Supposing this this will work, what about user profiles and home drives which are on the first DC? How do you replicate them to the second DC

Many thanks in advanc
Akz

 

[Jimmy Harper [MSFT]]

One thing to note is that we need to be able to contact a Global Catalog
server when a user logs on. Try making the second DC a Global Catalog.
Instructions for this can be found at
http://support.microsoft.com/default.aspx?scid=KB;EN-US;313994.

Also, if the second DC is running DNS, make sure the client machines point
to it for their secondary DNS in TCP/IP properties (this can be configured
through DHCP).

If your clients are Win2k or XP, they should still be able to logon when the
FSMO role holder is down (although if it is going to be down for a while,
you should transfer the roles before shutting it down).

--
Jimmy Harper [MSFT]
Directory Services
This posting is provided "AS IS" with no warranties, and confers no rights

Hi,

Thanks cary for the response.

I tried to make the second DC a DNS server. but when domain users try to

login while the first DC is offline, the logon fails. The error message is
that the domain could not be found.

I have a feeling that the solution could be in fsmo settings? How do you

make fsmo available to the second DC?

Also, Do I need to make the second DC also a DHCP server?
Supposing this this will work, what about user profiles and home drives

which are on the first DC? How do you replicate them to the second DC?