Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DHCP

Status
Not open for further replies.

xKhai

IS-IT--Management
Jun 13, 2007
3
CA
Hello,

I have a situation that needs to be planned and implemented very soon. Any help will be greatly appreciated.

Is it possible to use 1 range (ie 192.168.246.1 - 192.168.246.160) and carve it into 2 different scopes? I cant really use any other subnet range as were running out right now.

Then use those two scopes for different lease times. Each scope will be used for a different PC's based on the location. (ie. Floor one will be used for Scope A and floor 2 will be used for Scope B). Also how do i make computer located in floor A to only receive IP's from scope A)

Thanks in advance!
 
Is it possible to use 1 range (ie 192.168.246.1 - 192.168.246.160) and carve it into 2 different scopes? I cant really use any other subnet range as were running out right now.
Don't really know what your range is, you have not supplied the Subnet Mask You are using. I'll Assume 192.168.246.0/24 (255.255.255.0) Assuming this is the SM:
1. Only one scope per DHCP Server for 192.168.246.0/24
2. Yes you could carve it up into 2 scopes if using two DHCP servers. One server could have an address pool of 192.168.246.1 - 192.168.246.80. The second server pool could be 192.168.246.81 - 192.168.246.160

Then use those two scopes for different lease times. Each scope will be used for a different PC's based on the location. (ie. Floor one will be used for Scope A and floor 2 will be used for Scope B). Also how do i make computer located in floor A to only receive IP's from scope A)
You can only set the lease time per scope. So, in a sense you could set each dhcp servers with differn't lease times, but it would not provide a solution for your requirement. Splitting scopes on multiple DHCP servers was designed for redundancy. The problem here, Since both scopes are actually scope A (not really A and B) you are not able to insure that a DHCP client gets an address from a set server. Both servers listen for requests and are able to send offers.

The only way to insure which floor talks to which DHCP server is to set up an IP helper address on the Network Hardware to Direct DHCP requests. For Example, two DHCP servers (192.168.246.161 with scope set to 30 minutes, 192.168.246.162 with scope set for 3 days). Any DHCP request from Floor 1 gets directed to 192.168.246.161 via IP helper. Requests from Floor 2 -> 192.168.246.162...

I would only suggest doing this as a TEMP solution to assist in resolving your issue of running out of IP's. After you reconfigure your network to allow for more IP's I would go back to using a split scope as intended, for redundancy.

For more info on DHCP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top