Networking Forums

Networking Forums > Computer Networking > Windows Networking > DHCP configuration error?

Reply
Thread Tools Display Modes

DHCP configuration error?

 
 
SA
Guest
Posts: n/a

 
      01-14-2008, 10:23 PM
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.
 
Reply With Quote
 
 
 
 
Ryan Hanisco
Guest
Posts: n/a

 
      01-15-2008, 03:58 AM
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.

 
Reply With Quote
 
SA
Guest
Posts: n/a

 
      01-15-2008, 02:52 PM
Ryan:

Thank you.

Bottom line (for me): I do need to have an exclusion for the .0 and .255
addresses.

Sven.

"Ryan Hanisco" wrote:

> 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.

 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      01-15-2008, 03:09 PM

"SA" <(E-Mail Removed)> wrote in message
news:761AEC49-31E7-4471-A882-(E-Mail Removed)...
> Ryan:
>
> Thank you.
>
> Bottom line (for me): I do need to have an exclusion for the .0 and .255
> addresses.


The Network ID and the Broadcast address do no go into the scope at all. The
full range for the scope would be:

x.x.x.1 -- x.x.x.254

The DHCP Server should complain and not even let you include .0 or .255.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP Error 64 - No static IP bound to this DHCP Server DHCP Firewall Windows Networking 0 02-02-2006 04:04 PM
Error in bluetooth configuration Ruben Wireless Networks 0 12-05-2005 09:18 PM
Wireless Configuration error message Mike Wireless Networks 0 09-22-2005 07:55 PM
Error: Network configuration has changed. Homer Simpson Windows Networking 0 12-17-2003 01:53 PM
IP configuration Fatal Error Kumar Windows Networking 1 09-13-2003 12:10 PM



1 2 3 4 5 6 7 8 9 10 11