DHCP scopes

Here is the situation:  I have a network.  The network spans 3 floors in a building.  I want each floor to have its own subnet (ie: 1st floor =, 2nd floor =, etc..).  Each floor is separated by its own router/gateway.  The DHCP server is on the 3rd floor (  All routers can forward DHCP packets.  How do I configure DHCP in Win2k to have clients from each floor obtain IP configurations from a certain scope?  -- ie:  clients from the 1st floor obtain the IP configurations from the scope.  Thanks in advance.
Who is Participating?
rcasteelConnect With a Mentor Commented:
It is this simple...

Create a scope for each subnet.

Tell your routers to forward DHCP packets to your DHCP server.

The DHCP server will use the IP address of the Router's interface that recieved the DHCP REQUEST to determine which scope to pull from.

You are done.
matt023Author Commented:
is it simply adding an ip address from each subnet on the dhcp server, and the dhcp server will use a certain scope based on the router determined source request?  
DHCP source is driven by DNS, WINS and yes.. DHCP servers.  These settings can be found on 2K, Control Panel, Administrative Tools, Network ...., within Network choose PROPERTIES from Local Area Network.  Adjust DNS and WIN to the server in sequence. Don't forget to press good old advance button.

Good Luck
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

matt023Author Commented:
sorry that I have to reject your answer, but I don't quite understand your explaination.  How do DNS and WINS effect the way a DHCP server give out IP configurations from a certain scope or the way clients request for IP configurations from a certain scope?  May be I'm not being clear with the question.  
I want to configure a DHCP server with 3 different scopes of IP addresses.  I want clients from each floor/subnet to get an IP configuration from a certain scope.  Note:  I also have DNS server running on the same DHCP server.
As long as you have a different gateway for each level of the DHCP scope you are fine, but here in lies the problem with the different gateways the seperate floors may not talk with each other as quick unless you have routers for each level,

Here is a few tips:  Use the Ipconfig /setclassid for each level

then with tracert you can determine the path on which its taking, but in reality unless you have a BDC in 2 floors and 1 PDC you really wont be able to get the seperate scopes.

The way I suggest to do this is:

Create a scope that excludes the other two scopes you want to create along with it.

So create scope 127.0.1.* and exclude within that one 127.0.2.* and 127.0.3.* within it.
scope 2 on the BDC1 would be 127.0.2.* with exclusions on 127.0.1.* and 127.0.3.*
then on BDC2 would be 127.0.3.* with exclusions on 127.0.1.* and 127.0.2.*

Connect the BDC's to the PDC via seperate DNS, WINS and Gateway,Subnets. But then the will all accept the same underlayed protocol's  

Thats my 2 cents worth and it dont sound like much.  Personally I would make the NETBIOS/NETBEUI names with the floor level and machine id something like 1stflr12 (depends on how many systems total you have)to keep the Names under the required size.

Hope this gives you some ideas at least.
On your DHCP server create a Superscope that includes the three networks.
For the 192.168.1 network exclude the address range of 192.168.2 and 192.168.3
For the 192.168.2 network exclude the address range of 192.168.1 and 192.168.3
For the 192.168.3 network exclude the address range of 192.168.1 and 192.168.2
This works by giving addresses to the stations that are requesting a new lease only from their own network.
matt023Author Commented:
so basically, the DHCP server will give out the addresses within a certain scope based on the requestor's subnet.

slang9, instead of creating a superscope, can I just create 3 different scopes.  I also don't quite understand why would I need to exclude scopes within a scope.  If I create a scope of to, why would I need to exclude 192.168.2.x?  It's not even a part of the scope -- please explain.  thanks so far.
matt023Author Commented:
Also related to this question, look at my recently posted question about migration DHCP to win2k DHCP.  you can earn lots more points!!!
There is a migration wizard for pre-2k systems, not sure what it all has but here is the link(s)


The reason for the exclusion is the fact that the scope, even with the limit is part of the same subnet and gateway, so it will ROUTE through to the fast link thats why you create the exclusions to the individual scopes. its Hierarchy based will see the 192.168.1.* as the top level and work its way down Thus placing the scopes of the addresses outside that range. Essentally doing what rcasteel has said in plainer language.
matt023Author Commented:
thank you all for you comments.  rcasteel gave me the most "right to the point" and accurate comment.  Thanks again.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.