Re: Domain users cannot logon to domain
- From: "Niv Raz" <nivraz00@xxxxxxxxxxx>
- Date: Mon, 19 Jun 2006 10:47:46 +0200
i sugesst you provide us more detail description about the structr...
--
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jorge de Almeida Pinto [MVP]"
<SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx> wrote in message
news:OA75Ai2kGHA.1324@xxxxxxxxxxxxxxxxxxxxxxx
DHCP configuration is not replication between servers, so I think
something else occurred here when you removed/add the role/scope
if you have multiple DHCP servers, clients don't care which DHCP server
will service them. Clients ask a question for an IP and the first DHCP
server to respond will service. It is basically on a "first come first
server basis"
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"MartinH" <nick@xxxxxxxxxxxxxx> wrote in message
news:80rb92hb8iliopbu5bbka40e6nsc013bn8@xxxxxxxxxx
Hi Jorge, It's me again :D
Problem 1...
On Site(1) there was a DHCP running with no scope on DC1 and a DHCP
with a scope on DC2.
I Removed the DHCP role from DC1 because there should only be 1 DHCP
per site in my opinion.
I just noticed that by itself the DHCP on DC2 was also removed. OOPS!
Not what i wanted. So i reinstalled the DHCP role on DC2 and to my
surprise there is no a identical DHCP with scope on DC1.
Problem 2...
Someting strange with the scope name. I created the DHCP role on DC2
with Child.Domain.net name. Scope names on both DC's are not
identical.
DC1 scopename: Child.Domain.net
DC2 scopename: Child
DC1 is the Rootserver and DC2 is the child.
I am beginning to think both DHCP's are identical and servicing
identical but i am not sure and better ask then sorry my mum says :D
What should i do now?
Kind regards, Martin
On Sat, 17 Jun 2006 11:03:15 +0100, "Jorge Silva"
<jorgesilva_pt@xxxxxxxxxxx> wrote:
Hi Martin
don't worry about anything the KCC does that automatically for you.
Just monitor on daily basis your replications you can use tools like:
- repadmin
- replmon
- dsastat
you can find these tools installing support tools from Windows cd
.
- Follow-Ups:
- Re: Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- References:
- Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- From: Jorge Silva
- Re: Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- From: Jorge Silva
- Re: Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- From: Jorge Silva
- Re: Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- From: Jorge Silva
- Re: Domain users cannot logon to domain
- From: MartinH
- Re: Domain users cannot logon to domain
- From: Jorge de Almeida Pinto [MVP]
- Domain users cannot logon to domain
- Prev by Date: Re: Cleanup CA rentries in AD (2)
- Next by Date: Re: Error message when adding user to group
- Previous by thread: Re: Domain users cannot logon to domain
- Next by thread: Re: Domain users cannot logon to domain
- Index(es):
Relevant Pages
|