That is the way it is.
DCs have different Roles.
It takes all the DCs together to make things happen properly.
The purpose of multiple DCs is not so that the network will keep "zipping"
along if one does down because that won't happen. But what it does do is
keep you from losing the Active Directory Database, which then allows you,
in the event the DC is going to be dead for a while, to transfer all the
FSMO Roles from the dead one to the remaining DC,...then things will keep
going,...but "no promises" about minor delays and hickups until the Domain
fully replicates and "settles in" with the new config.
When the dead DC is brought back to life, the FSMO Roles can be transfered
back to it and after a period of replication and "settling in" [again]
things will be back to normal.
Been there,..done that,...it's happend here.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"boba" <(E-Mail Removed)> wrote in message
news

464ECAA-1B1F-4E5E-8E57-(E-Mail Removed)...
>I have DC1 on VMware on SAN and DC2 standalone on same network (not on
> VMware). My DC1 was down on SAN and it took 15-20 minutes for users to
> login
> to network. What can I do that if DC1 is down DC2 picks up login quickly
> instead of 15-20 minutes. I would appreciate any help.
>
> Thanks!