RE: DHCP configuration error?



Hi SA,

In a High Availability configuration mode you will generally configure a
single overlapping scope with reciprocal exclusions to avoid NAK problems.

For simplicity I'll change the scopes, but you'll get the idea.

If you want the range of your addresses to be 10.1.0.0 - 10.2.254.254 with a
/16

DHCP 1
Scope 1 10.1.0.1 - 10.1.254.254 /16
Scope 2 10.2.0.1 - 10.2.254.254 /16
Exclusion 10.1.128.0 - 10.1.254.254
Exclusion 10.2.128.0 - 10.2.254.254

DHCP 2
Scope 1 10.1.0.1 - 10.1.254.254 /16
Scope 2 10.2.0.1 - 10.2.254.254 /16
Exclusion 10.1.0.1 - 10.1.127.255
Exclusion 10.2.0.1 - 10.2.127.255

In this case, I have created two scopes to allow me to manage VLANs or the
like and have split the addresses across the two servers. Whichever server
responds first will give the address, but I have to be sure to specify the IP
Helper line in the switch/ router config. The exclusions are there to
prevent a server for issuing a NAK on a lease renewal telling the client that
the range is invalid. You want it to see that the lease is excluded and
request a new one, not give up or just keep using the expired IP Address.

I could have specified one single scope for the whole range, but I prefer
not to do this as then I have to exclude the 0 and 255 addresses (you don't
have to, but I like to avoid potential inter-op problems). Normally you
would only do this in the case where you allow your network to summarize so I
prefer to break them.

Finally, you could assign one scope to each server and make it responsible
for that only. This gives you a split in load, though not actually High
Availability -- especially if your subnets have meaning for VLANs, equipment
type or something like that.

Hope this helps.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"SA" wrote:

All:
I have two DHCP servers running on our network. We have been assigned
10.12.0.x through 10.12.7.x by the network admin.
For load balancing, I set up two servers (Windows Server 2003 R2 SP 2) with
DHCP. I set up a single scope on each server. One server assigns 10.12.0.1
through 10.12.5.255.
I noticed the other day that my server assigned 10.12.1.0 to a client. The
client is working fine... but I am surprised that that IP address was
assigned. Did I make a mistake by having only scope? I.e. should I have a
scope for each third octet and have them assigned from 10.12.x.1 to
10.12.x.254?
(Our subnet is 255.255.248.0).
Thanks,
SA.
.



Relevant Pages

  • Re: Application Hang
    ... Do not run 2 DHCP servers together, that will create conflicts for the client. ... Under DNS management console is the server listed under Forward lookup zone, if yes with how many entries and which ones? ... I hope this is what you were looking for by way of scope options: ...
    (microsoft.public.windows.server.networking)
  • Re: SBS Reinstall
    ... In DHCP when I select the server it shows 192.168.16.2 and when I expand it ... "The wizard cannot set the DHCP scope options" error message when you run ... Ethernet adapter local area connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: ...OS is Win 2003 Std...
    ... Microsoft Small Business Server Support ... >> The scope I have defined is identical to what you have listed, except for>> the range of the scope; ... but the message in the system error log>> indicates that it is not servicing clients because there is no NIC with a>> static IP assigned. ... >> The messages can be produced at will currently by simply restarting the> DHCP>> server service. ...
    (microsoft.public.windows.server.sbs)
  • Re: No DHCP Leases Available - SBS2K3
    ... delete scope 192.168.1.240 dhcpfullforce (command ... scope with two suggested options; stopped DHCP service; ran CEICW again - ... same message as above; started DHCP service; opened Change Server IP Address ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem With Joining XP Computer to Windows 2003 Domain
    ... One, if the DC is connected directly to the Internet, DISCONNECT IT by ... I have assigned the server to Domain Controller ... > seem to be pointing to DHCP scope possibly on the server's configuration ...
    (microsoft.public.windowsxp.network_web)