We have a network made of two local ranges: 192.168.1.0/23 and 192.168.1.0/23.
So far I have been using a Linux DHCP Server; I would create a pool of ip addresses from the first range and could set it to deny all clients except the static ones that I placed there myself. Then I also had a ip pool for guests - ip's that were issued to devices not in that list who received from the second range.
I am moving to Windows Server DHCP. I know how to create a pool, but how do I deny requests for a certain pool and only allow registered ip's there?
I have found I can reserve the pool by adding the same range to the exclusion range and the server won't hand these out; I can still manually add devices here, though.
So, I'm thinking now that I need to use a superscope with scopes underneath with the ranges I want. And now I get hung up a little; Windows tells me the second scope has addresses already in a known pool.
Our network has a range of
Say I want these ranges:
- scope1 = 192.168.1.0 - 192.168.1.10
- scope2 = 192.168.1.11 - 192.168.1.20
- scope3 = 192.168.0.0 - 192.168.0.255
What do I put for the netmasks? Normally, I would think to use
255.255.254.0 for the mask to allow the entire ranges of both networks. But don't I need a smaller number for the scopes? In The New Scope Wizard, I have to specify both the
netmask and the