Re: Authentication doesn't fail over to additional DC's

What error do the users get trying to log in when this DC is down?

hth
DDS

"Kimberly Pace" <KimberlyPace@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:05A07E59-5579-42D1-A131-80734BAD2E48@xxxxxxxxxxxxxxxx
Each DC at the six sites are GC's. The 2nd server in the DC is a global
catalog. I have played with changing roles and moving the GC from one
server
to the other. I have split the roles between the two and have put all the
roles on one server, etc. Also, I've adjusted the logon cache settings in
group policy, thinking the workstations would try to re-authenticate with
the
last DC that logged them on.

"Danny Sanders" wrote:

Which server is the global catalog?

hth
DDS

"Kimberly Pace" <KimberlyPace@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D879F63-002D-4621-A135-C39BF0F6644B@xxxxxxxxxxxxxxxx
Hi,

I have 8 domain controllers in our enterprise. 6 are located at other
geographical sites and 2 are located in our central datacenter. All
domain
controllers are handling logon requests through the enterprise. I
assumed
I
should be able to shut down one of the DC's in the datacenter without
causing
logon issues, but that doesn't seem to be the case -- even if I
transfer
the
PDC emulator role to another DC. Users start calling the HelpDesk
saying
they can't log on but more importantly, our BizTalk server won't
authenticate
and all users are denied access to our intranet site which relies on
BizTalk.
Once the DC controller is back on line, everything goes back to normal.
I've talked with the team controlling the BizTalk server and they
assure
me
that don't have any dependencies written into the server configuration
requiring that one DC to be online. I can shut down other DC's with no
interruption to authentication. Any ideas?





.

Relevant Pages