Creating a new subnet
Currently on our 2008 domain we have 1 subnet with address 192.168.20.x
we are fast running out addresses and i am looking to add a second subnet, and am looking at the best way to do this.
We have Dell 3448p Switches which support Vlans, and 2 Windows Server 2008 DC's, 1 of these DC's acts as the DHCP server.
The new subnet will primarily be for our voip phone system, all computers in the office connect to the phones but acquire their own IP addresses.
What would be the best setup to acheive this?
we are fast running out addresses and i am looking to add a second subnet, and am looking at the best way to do this.
We have Dell 3448p Switches which support Vlans, and 2 Windows Server 2008 DC's, 1 of these DC's acts as the DHCP server.
The new subnet will primarily be for our voip phone system, all computers in the office connect to the phones but acquire their own IP addresses.
What would be the best setup to acheive this?
fgasimzade
As far as I know Dell 3448 is not a Layer3 device, but you will need one to perform routing between subnets
Hi CaptainGiblets,
As you have 2 servers, gateway and a few switches I would suggest editing the subnet of your DHCP scope and replicating that new subnet on your servers. You can change the DHCP scope fairly easily using ntsh, a good guide can eb found here:
http://www.windowstricks.in/2009/06/how-to-change-subnet-mask-of-dhcp-scope.html
Once that is done add the new subnet into your server's addresses and DHCP will take care of your other clients. You will also need to make the same subnet change on your Gateway's internal side too.
As you have 2 servers, gateway and a few switches I would suggest editing the subnet of your DHCP scope and replicating that new subnet on your servers. You can change the DHCP scope fairly easily using ntsh, a good guide can eb found here:
http://www.windowstricks.in/2009/06/how-to-change-subnet-mask-of-dhcp-scope.html
Once that is done add the new subnet into your server's addresses and DHCP will take care of your other clients. You will also need to make the same subnet change on your Gateway's internal side too.
ASKER
@fgasimzade - i thought a layer 2 could do this? and wouldnt be much of an issue in a small network.
@monkeydaveX - Do you mean changing the subnet mask to a 255.255.0.0 and also make these changes manually to my servers, then just change the ip address's on the phones to say 192.168.19.x ?
@monkeydaveX - Do you mean changing the subnet mask to a 255.255.0.0 and also make these changes manually to my servers, then just change the ip address's on the phones to say 192.168.19.x ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That sounds simple enough, and if i changed it to say 255.255.253.0 that would give me .20 .21 and .22??
oops I forgot to add that you could then assign your phones IP's in the new range (192.168.21.1-254) leaving your current range intact and everything communicating on the new subnet quite happily.
ASKER
sounds good, also because they all have the same network id, am i correct in thinking that their would not need to be any sort of router and will be able to communicate as normal?
Hi Giblets,
Not quite, subnet's are a little confusing on that one, the decimal numbers we see (255 /254 /252) are directly related to a binary number. You will need to read up on subnetting or use a Subnet Calculator to check valid subnets.
A calculator with your initial IP saved: https://www.dan.me.uk/ipsubnets?ip=192.168.20.1
A good source of subnet information: http://www.techrepublic.com/article/ip-subnetting-made-easy/6089187
With this in mind the next possible increase in the subnet would be 255.255.252.0 providing you with a range from 192.168.20.1 - 192.168.23.254.
Not quite, subnet's are a little confusing on that one, the decimal numbers we see (255 /254 /252) are directly related to a binary number. You will need to read up on subnetting or use a Subnet Calculator to check valid subnets.
A calculator with your initial IP saved: https://www.dan.me.uk/ipsubnets?ip=192.168.20.1
A good source of subnet information: http://www.techrepublic.com/article/ip-subnetting-made-easy/6089187
With this in mind the next possible increase in the subnet would be 255.255.252.0 providing you with a range from 192.168.20.1 - 192.168.23.254.
That's correct, increasing the subnet will mean no router is required, however the new subnet must be contained on the internal side of your gateway device or nothing from the network will get outside. (sorry for repeating myself but I don't want you to be stuck!)
ASKER
Ok ill read up a bit more on subnetting later, i did go through it all on my MCP but it was years ago and not looked at it since.
So its just expanding the subnet, as long as the DHCP server or manual ip entries have the correct default gateway etc and are all connected to the same physical switches on same vlan it should all function normal?
Cheers for the swift responses.
So its just expanding the subnet, as long as the DHCP server or manual ip entries have the correct default gateway etc and are all connected to the same physical switches on same vlan it should all function normal?
Cheers for the swift responses.
Yes that's correct, all fixed IP's on your LAN network need the new subnet and then it's business as usual : ) VLAN's will continue to function as they did before the change (unaffected).
ASKER
Cheers for all your help. Will implement some time over the weekend.
appreciated thanks CaptainGiblets - this was my first answer here so thanks again!