log time to log on to network with master dc down

hello all
we have a win2000 network. two dc. The first dc (master) went down
and we are working on it now. But the problem is the users are trying to log
on to the network and its very slow..... like 7 to 10 min. Also let me add
that these users are loging on to a terminal server. So what am i missing
or need to recofigure so that the terminal server see that there is another
dc. The first dc is the Catalog and im sure its the master for all roles.

In addition to redundant DCs, you also need redundant AD/DNS. All machines
(*all* machines including the DCs) in the system need to point to *all* the
AD/DNS Services in their network settings. There will probably always be
some delay because they would try the first DNS listed and it would have to
"timeout" before it tried any subsequent DNS's listed.

In other words just redundant DCs isn't enough,..all the required services
needed for normal operation must be redundant, ...and all the machines need
to know where those are located.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"James" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> hello all
> we have a win2000 network. two dc. The first dc (master) went down
> and we are working on it now. But the problem is the users are trying to
log
> on to the network and its very slow..... like 7 to 10 min. Also let me add
> that these users are loging on to a terminal server. So what am i missing
> or need to recofigure so that the terminal server see that there is
another
> dc. The first dc is the Catalog and im sure its the master for all roles.
>
>