ploughingon
Technical User
Hi
I'm kinda the only one that approaches an understanding of tcp/ip at my work place, but i'm a very long way from being an expert. We're running out of IP's in our address space, I've got an idea on how to sort it out and I'd like to run it past the more experienced folks on this forum.
we use 172.16.4.0 / 255.255.252.0 at the moment. Gives us 1024 address's
of this range 172.16.4.0 - 172.16.5.254 is managed by dhcp and
172.16.6.0 -172.16.7.254 is the range we assign to servers printers , switches etc.
I've been looking for an easy way to expand this range. So i figured that changing the subnet mask to 255.255.248.0 bringing 172.16.0.0 - 172.16.3.255 into the range. Would be the best thing to do for us.
I'm kinda nervous as I've never managed a broadcast domain of this size before and i dont really know what to expect.
Am i mad or is there a gotcha?
I'm kinda the only one that approaches an understanding of tcp/ip at my work place, but i'm a very long way from being an expert. We're running out of IP's in our address space, I've got an idea on how to sort it out and I'd like to run it past the more experienced folks on this forum.
we use 172.16.4.0 / 255.255.252.0 at the moment. Gives us 1024 address's
of this range 172.16.4.0 - 172.16.5.254 is managed by dhcp and
172.16.6.0 -172.16.7.254 is the range we assign to servers printers , switches etc.
I've been looking for an easy way to expand this range. So i figured that changing the subnet mask to 255.255.248.0 bringing 172.16.0.0 - 172.16.3.255 into the range. Would be the best thing to do for us.
I'm kinda nervous as I've never managed a broadcast domain of this size before and i dont really know what to expect.
Am i mad or is there a gotcha?