emslan said:
Hi to all,
We have 4 dc but when our primary DC is not online the client can't logon.
How can we make sure that all dc is in load balance in authentication. Thanks
a lot in advance..
Chance are it is the DNS. Either not enough DNS
servers (e.g., only one on the down DC OR perhaps
not all of the DCs are "DNS clients" of the internal
DNS server set and thus never registered).
Make sure you have at least one DNS available all
of the time (one on each DC probably makes the
most sense) and...
Check these:
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server

C-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]