Re: Need DHCP Setup Clarification 2003 Std Svr

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Doug, you have steered me on an interesting journey.

I've discovered that DC1 has bindings to two connections!! One is
192.168.0.1 with no default gateway and aimed at this same address for DNS.
This must be a configuration mistake by my predecessor. This one is listed
at the top of the two connections. This connection is disabled in My Network
Places but it's IP is listed in DHCP.

The other is it's static IP of 192.168.1.2 and has all the correct gateway
and DNS entries. This one is listed at the bottom of the two connections.

DC2 has only one binding that is properly configured with it's static IP.
However, there is also a second connection here that is only partially
configured and disabled.

If I understand correctly, I should go into DC1 and remove the binding to
the bogus 192.168.0.1 connection, leaving the correct one in place.

I should then go into DC2 which lists it's proper static IP and activate it.

I have a total scope of dynamic IP addresses to assign on the network from
192.168.1.71 to 192.168.1.253 which is lets say 180 addresses. I should go
into DC2 and set up an assignable scope of about 20% of the addresses, call
it 36 of them.

Then I should go into DC1 and modify the assignable scope it has to 80% or
call it 144 addresses.

That splits the DHCP assigning about 80/20.

If I am correct so far, what will happen to DC1 when I delete the bad
binding? How will all the dynamic IP's assigned by DC1 be affected when I
change the scope it hands out to a reduced 80%?

Will I have to have all users restart their workstations to get new IP
addresses?

I already entered all the static IP exceptions into DC2 identicle to DC1.
Is it safe to assume the static IP's will be OK?

If you get me through all this you must have the patience of a Saint.
--
Thanks, Steve


"Doug Sherman [MVP]" wrote:

"Do I understand that DC1 should have it's static IP address there and not
192.168.0.1?"

Yes, check bindings per my previous post.

"That DC2 should have it's static address there (which it does)."

Yes.

"Then authorize DC2 as a DHCP server and the allready handed out dynamic IP
user addresses will replicate on DC2?"

No - DHCP servers do not replicate - that is the reason for split scopes.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"SteveP" <SteveP@xxxxxxxxxxxxxx> wrote in message
news:698A21DA-1C00-43A1-8C3B-0FBA1153639A@xxxxxxxxxxxxxxxx
Thanks for helping, Doug. I'm worried that if DC1 developes a problem I
will
really be in trouble.

Both domain controlers have one NIC each. I inherited this setup from my
predessor who had both servers configured identically. I am aware of
splitting the scope, but want to get DC2 back to it's original
configuration,
whiched worked fine, as fast as possible.

This brings me back to the question about what IP addresses should DC1 and
DC2 have directly under DHCP.

Do I understand that DC1 should have it's static IP address there and not
192.168.0.1?

That DC2 should have it's static address there (which it does).

Then authorize DC2 as a DHCP server and the allready handed out dynamic IP
user addresses will replicate on DC2?

I will deal with splitting the scope after all is functional again and I'm
out of the woods.
--
Thanks, Steve


"Doug Sherman [MVP]" wrote:

First of all, if you are going to run two DHCP servers serving the same
scope, you should split the scope:

http://support.microsoft.com/kb/280473/en-us

Second, possibly DC1 has more than one adapter. Check the binding -
DHCP
should be bound only to the 192.168.1.2 adapter and this IP must be
statically configured:

http://support.microsoft.com/kb/298490/en-us

Doug Sherman
MCSE, MCSA, MCP+I, MVP


"SteveP" <SteveP@xxxxxxxxxxxxxx> wrote in message
news:4F465790-3F22-4A5D-ABBA-EE276BA61412@xxxxxxxxxxxxxxxx
The network I work on is 2003 standard server SP1 and uses the IP
addresses
of 192.168.1.1 to 192.168.1.254. There are two domain controllers
that
handle AD, DNS, DHCP and WINS. They are named DC1 (192.168.1.2) and
DC2
(192.168.1.3) respectively and they are identicle.

I just had to recreate DHCP manually on DC2. After recreating DHCP on
DC2
I
noticed a discrepancy between the two domain controllers in DHCP. The
first
entry under DHCP on DC1 is "DC1.xxxx.local [192.168.0.1]".

In the same location on DC2 the entry reads "DC2.xxx.local
[192.168.1.3]".

1. Should these entries match?
2. If so should they both be 192.168.0.1 or something else?
3. DC2 has it's own static IP of 192.168.1.3 in this location and
that is
what is throwing me off. DC1 does not have it's own static IP in this
location.
4. When I finally authorize DHCP on DC2 will it pick up on all the
dynamis
IP addresses already assigned by DC1?

In short what IP address should be entered in DHCP in the first line
under
the heading for each server?

I am under time pressure to solve this one.

--
Thanks, Steve






.



Relevant Pages

  • Re: Jorge --- Re: root forest AD DC crashed
    ... Also install DNS, WINS and DHCP ... Give DC1 it own IP address ... As preferred DNS for DC1 enter the IP of DC1 ... As alternate DNS for DC1 enter the IP of DC2 ...
    (microsoft.public.win2000.active_directory)
  • Re: Need DHCP Setup Clarification 2003 Std Svr
    ... I'm worried that if DC1 developes a problem I will ... DC2 have directly under DHCP. ... Then authorize DC2 as a DHCP server and the allready handed out dynamic IP ... I will deal with splitting the scope after all is functional again and I'm ...
    (microsoft.public.windows.server.general)
  • Re: Need DHCP Setup Clarification 2003 Std Svr
    ... I've discovered that DC1 has bindings to two connections!! ... DC2 has only one binding that is properly configured with it's static IP. ... That splits the DHCP assigning about 80/20. ...
    (microsoft.public.windows.server.general)
  • Re: Domain users cannot logon to domain
    ... I Removed the DHCP role from DC1 because there should only be 1 DHCP ... I just noticed that by itself the DHCP on DC2 was also removed. ... surprise there is no a identical DHCP with scope on DC1. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD replication
    ... Assuming DC1 for the Root Domain, and DC2 for the child domain: ... NtdsSettings -> all tasks and choose check replication topology, ...
    (microsoft.public.windows.server.active_directory)