DHCP Meltdown

[Guest]

I have a client that has maxed out their 192.168.0.x scope (with a Class C
subnet mask). Twenty IP's reserved for servers and nearly 230 workstations
now on line. As I see it, they can either go to a 172.16.x.y scope with a
255.255.0.0 subnet mask and have billions of addresses, but can they also
just keep the 192.168.0.x scope with a 255.255.0.0 subnet mask? It's not
classful, but where is that going to cause a problem? The domain controller
uses Windows 2K and Active Directory. The network consists of fibre between
Cisco 3500 XL switches. The only router in the system is a Linksys firewall
linking them to the Internet. I appreciate your thoughts.... they're a
Catholic parish/school and classes start Monday. If I need to make a major
shift, I need to do it soon. Thanks!

Jim Pandzik
(e-mail address removed)

 

[Mike Silverman]

Why not just extend the subnet to more than 254 devices like this:

192.168.0.x/23 (255.255.254.0)

That way they have 510 total devices in the subnet...

192.168.0.1 - 192.168.1.254

You'd need to change the mask on the static devices like the server and
switches and router, but thats fairly easy to do. And also modify the
DHCP scope.

Mike.

 

[Guest]

Thanks, Mike, I'll do that. I wasn't sure if a tweaked subnet mask would work.