We are trying to troubleshoot a scope overlap problem. We have multiple device types we wish to give all different ranges of a 16 bit subnet. IE. X device we wish to give 192.168.2.1-192.168.2.254/16, Y devices we wish to give 192.168.3.1-192.168.3.254/16. We are trying to accomplish this by creating different scopes and using the 60 class identifier. The problem is DHCP won't allow us to give these scopes with 16 bit masks because of the potential overlap. We aren't overlapping the address pool so why does DHCP care and can we work around this?
If this isn't possible, how can i assign specific ranges by device type without creating multiple scopes?
Any thoughts would be helpful.
UPDATE:
Entire Scope is 192.168.0.0/16
Gateway is 192.168.1.1/16
Device Hardware A – 192.168.20.1-192.168.20.254/16
Device Hardware B – 192.168.26.1-192.168.26.254/16
Device Hardware C – 192.168.85.1-192.168.85.254/16
We tried to setup multiple scopes for each device type (A,B,C) but couldn't specify a 16 bit mask as Scope A could technically overlap Scope B even thought our start and end addresses don't.
I hope this makes more sense.
Thanks for your thoughts.
Best Answer
Because windows counts the "scope" as 192.168.0.0/16. Without a router of some sort, you are basically creating a huge singular subnet.
I think what you are actually trying to create is what windows calls an "address pools". You can create one for each group, but unless you do static reservations, windows will simply assign the next available address to each device as it requests an IP.