Currently we have a 24 bit subnet at each site.
The problem:
We are running out of IP addresses rapidly.
The ranges set for different device types was inadequate and my predecessors then used any available IP address and reserved it for that device (eg. Printers)
VLANs were implemented but for the wrong reasons and so will be removed to flatten it out again and won’t be implemented again unless necessary.
The solution I’m proposing:
We implement a new 16 bit subnet at each site.
For example 172.16.0.0/16
Servers and Core Devices will go in the range 172.16.0.1 – 254
Printers will go in the range 172.16.1.1 – 254
Thin Clients will go in the range 172.16.2.1 – 172.16.3.254
Windows Workstations and Laptops will be put in the range 172.16.4.1 – 254
VPN clients and dial in clients will be allocated an address in the range 172.16.5.1 – 254
Future plans include quaranting clients at risk / devices plugged in to our network that are not under our control into the range 172.16.6.1 – 254
The Implementation:
This is where I am a bit of a loss. The first DHCP scope I created worked fine (10.0.0.1 – 254 / 16 bit subnet mask)
When I tried to implement a second scope of 10.0.1.1 – 254 DHCP refuses and claims that the scope overlaps.
So my question is, how do I configure DHCP on Server 2003 to auto assign devices into specific ranges based on their Vendor ID?
We have Cisco 2900 series switches for now and I am somewhat loathe to put in VLANs and make it too complex as I’m a Windows Sys Admin and would be a bit out of my depth if I went too hard core on the Cisco side.
I’ve done a bit of reading on Vendor ID’s and classes but come away with no real steps for testing it out and how to implement it.
Any advice would be greatly appreciated.
