Re: Authentication doesn't fail over to additional DC's
- From: "Danny Sanders" <DSanders@xxxxxxxxxxxxxxx>
- Date: Thu, 27 Mar 2008 09:48:35 -0600
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?
.
- Follow-Ups:
- Re: Authentication doesn't fail over to additional DC's
- From: Kimberly Pace
- Re: Authentication doesn't fail over to additional DC's
- References:
- Authentication doesn't fail over to additional DC's
- From: Kimberly Pace
- Authentication doesn't fail over to additional DC's
- Prev by Date: Authentication doesn't fail over to additional DC's
- Next by Date: Re: Raising domain/forest functional level by command line
- Previous by thread: Authentication doesn't fail over to additional DC's
- Next by thread: Re: Authentication doesn't fail over to additional DC's
- Index(es):
Relevant Pages
|
Loading