klsphotos
asked on
Super Scope, DHCP
Hi experts,
I hope you can help me with this.
We are running out of ip addresses fast. We have a class c 192.168.1, 255.255.255.0 scope.
I read that I could add a superscope on the DHCP scope to add a 192.168.2, 3, 4 etc scope.
My question is, once I do that, does the new network 2,3,4 or whatever I make it then connect with no issue to the .1? We are also getting a second isp line for traffic for some of our high intensity servers and they will need to communicate with out network and active directory as well so I am trying to figure out how this is all going to do this.
Subnetting is not my strong skill set, so I hope that made sense.
Thank you,
Karen
I hope you can help me with this.
We are running out of ip addresses fast. We have a class c 192.168.1, 255.255.255.0 scope.
I read that I could add a superscope on the DHCP scope to add a 192.168.2, 3, 4 etc scope.
My question is, once I do that, does the new network 2,3,4 or whatever I make it then connect with no issue to the .1? We are also getting a second isp line for traffic for some of our high intensity servers and they will need to communicate with out network and active directory as well so I am trying to figure out how this is all going to do this.
Subnetting is not my strong skill set, so I hope that made sense.
Thank you,
Karen
"My question is, once I do that, does the new network 2,3,4 or whatever I make it then connect with no issue to the .1?"
You'll need to change your subnet mask to accommodate the new networks. Since you're using 192.168.1/24 now, just adding "2,3,4 or whatever" will just give you new networks, not expand the one you already have.
If you change your subnet mask to /23 (255.255.254.0), you'll go from 254 hosts to 510 on a network that runs from 192.168.0.0 - 192.168.1.255. Changing your subnet mask to /22 (255.255.252.0) doubles that number again to 1022 and a range of 192.168.0.0 - 192.168.3.255. Here's a handy calculator should the issue arise again.
You'll need to change your subnet mask to accommodate the new networks. Since you're using 192.168.1/24 now, just adding "2,3,4 or whatever" will just give you new networks, not expand the one you already have.
If you change your subnet mask to /23 (255.255.254.0), you'll go from 254 hosts to 510 on a network that runs from 192.168.0.0 - 192.168.1.255. Changing your subnet mask to /22 (255.255.252.0) doubles that number again to 1022 and a range of 192.168.0.0 - 192.168.3.255. Here's a handy calculator should the issue arise again.
you can also add extra pools.
this requires a gateway per pool.
your existing equipment will route the traffic between the pools and allow hosts to communicate.
may be easier, maybe not depending on the software
--
if you want to broaden the mask, you'll need to change the mask on all the existing hosts in the .1 network ( and obviously the gateway ) or there will be no communication between them and the .[234] networks
this requires a gateway per pool.
your existing equipment will route the traffic between the pools and allow hosts to communicate.
may be easier, maybe not depending on the software
--
if you want to broaden the mask, you'll need to change the mask on all the existing hosts in the .1 network ( and obviously the gateway ) or there will be no communication between them and the .[234] networks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We are going to change the subnet mask, our vpn ip address pool was .5 so we had to change that before we could change the subnet mask. Thank you.
If you have a configured network, just create the IP interface for the new IP segment at your router/switch. No additional routing needed depends on your network.
Kindly please post your details configurations/diagram and etc