Re: Login Authentication
- From: "Lucas" <lucaslafrance@xxxxxxxxxxx>
- Date: Wed, 22 Feb 2006 10:30:00 -0700
You are correct in assuming that we only have a few hosts in each site -
therefore dhcp is not useful to us. I have run the tools. I'll be putting
in a call to MS support soon. One question - could errors for the msdtc
event 53258 have anything to do with this? I worked on correcting this
yesterday but don't know if that could be the problem. I did run net diag
and dcdiag in verbose mode and did not find anything really interesting.
"Cary Shultz" <cwshultz@xxxxxxxx> wrote in message
news:OMqdyfnNGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
Lucas,
Just out of curiosity, why are you not using DHCP to handle the IPAddress
thing? Or, is it such that there are only a handful of computers in the
remote Sites?
And, you stated that all of the Domain Controllers are GCs as well.
Everything looks on paper to be correct....
Have you run dcdiag /c /v and netdiag /v on all of your Domain
Controllers? These are part of the Support Tools...
--
Cary W. Shultz
Roanoke, VA 24012
"Lucas" <lucaslafrance@xxxxxxxxxxx> wrote in message
news:ul3yjBjNGHA.740@xxxxxxxxxxxxxxxxxxxxxxx
Each site has it's associated subnet. All clients in this domain are
running XPsp2 totally updated or Server 2003SP1 totally updated. DNS is
setup to pull from the local domain controller then secondarily to the
domain controller at a remote site. I doubt that it makes any difference
but all of the clients have manually configured IP addresses. I have
verified that all TCP IP properties are correct for each host. We show
no problems with FRS or the Directory Service in the Event Logs.
"Cary Shultz" <cwshultz@xxxxxxxx> wrote in message
news:OIHv0dENGHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
Lucas,
This is in addition to your problem.
I would also want to know that all of my clients are authenticating
against the local Domain Controller.
I would also set up DNS so that in each of the Remote Sites each client
is getting first the local DNS Server information and then the DNS
Server information of the Main Site. In the Main Site I would make it
so that the clients are getting first the local DNS Server information
and then the DNS Server information from the remote sites.
No where would there be any mention of any ISP DNS Server information
(except where it belongs: in the Forwarders tab in the DNS MMC!).
So, to you problem:
All Domain Controllers are running Windows Server 2003 (SP1?) and what
are the clients running? Have you set up the Sites correctly in the
Active Directory Sites and Services? Have you created a Subnet and
associated each Subnet with the appropriate Site?
Like Paul stated, have you run dcdiag and netdiag? Seems like you have.
What is your DNS set up?
--
Cary W. Shultz
Roanoke, VA 24012
"Lucas" <lucaslafrance@xxxxxxxxxxx> wrote in message
news:OlYAVz9MGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
When my headquarters site domain controller goes down we are unable to
process domain logons in this site. We have three sites and one domain
controller in each site. Our AD is in windows 2000 native mode and all
domain controllers are Windows 2k3. All sites are linked together in
full mesh replication topology. The server that has gone down holds
the 3 domain level fsmo roles - PDC Emulator, Infrastructure Master,
and RID Master.
We are testing domain controller failover and when this domain
controller has gone down we are unable to authenticate against the
domain from within this site. Failover does not seem to be working.
Could this be because it holds the FSMO roles or do I need to
specifically configure and allow authentication to a different site?
.
- References:
- Login Authentication
- From: Lucas
- Re: Login Authentication
- From: Cary Shultz
- Re: Login Authentication
- From: Lucas
- Re: Login Authentication
- From: Cary Shultz
- Login Authentication
- Prev by Date: Question on certficates
- Next by Date: Domain rename problem
- Previous by thread: Re: Login Authentication
- Next by thread: Re: Login Authentication
- Index(es):
Relevant Pages
|
