Re: Unable to authenticate users in windows 2003 SP1 secondary DC
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 22 Jan 2007 09:10:40 -0600
"MS" <lmathew@xxxxxxxxxxxxxxxxxx> wrote in message
news:ukXxdOjPHHA.320@xxxxxxxxxxxxxxxxxxxxxxx
Hi Paul,
Thanks for the info. I have the DC's setup exactly as you have mentioned.
Single domain, both DC's are GC, both DC's are DNS AD Integrated and
client able to ping both servers using IP and hostname.
On a second thought, is it because my PDC hosts user folders and apps
folders mapped to drives names, whereas, BDC also do contain these
folders for redundacy purpose, however they are not shared and mapped.
Could this create authentication issues like not being able to map the
drives(since it is trying to map the the share on the failed PDC) from
netlogon script and eventually authentication failing
Well sure. If you are mapping to a share on the down DC it will fail.
It is NOT due to authentication* but due to the missing sharepoint.
If you want both DCs to be able to offer the files then research DFS
(perhaps with automatic replication).
*Authentication is when the user (or computer) proves his/her/its identity
and receives security credentials.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- Unable to authenticate users in windows 2003 SP1 secondary DC
- From: MS
- Re: Unable to authenticate users in windows 2003 SP1 secondary DC
- From: Paul Bergson [MVP-DS]
- Re: Unable to authenticate users in windows 2003 SP1 secondary DC
- From: MS
- Unable to authenticate users in windows 2003 SP1 secondary DC
- Prev by Date: Re: 32bit to 64bit AD upgrade
- Next by Date: Force kerberos to use TCP and consequences
- Previous by thread: Re: Unable to authenticate users in windows 2003 SP1 secondary DC
- Next by thread: Re: Unable to authenticate users in windows 2003 SP1 secondary DC
- Index(es):
Relevant Pages
|
Loading