Networks

Ask something
Discussion Locked

One domain, 2 subnets

0 helpful
2 replies

by adamtechpro 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I currently have a Windows 2000 networked environment within my companies network. We have 10 servers to handle various tasks, one domain controller with a single NIC that handles the 192.168.3 subnet. The 150+ users and 60-70 devices are all assigned into the 192.168.3 subnet (users on DHCP and devices statically assigned). We have a cisco 1720 router that connects us to our T1 for internet connectivity. The scope we have set up for the 192.168.3 subnet is currently nearing capacity and I am looking into a second subnet to alleviate the soon to be lack of IP adresses. Id like to set up a second subnet, 192.168.5.0. I want to know what exactly I will need to do in order for these subnets to communicate with eachother. Off the bat I know i will have to add the new subnet scope into DNS and DHCP on my domain controller, and im assuming I will need to configure some static routes on the router and possibly a relay agent on the domain controller(if not a second NIC for the domain controller. I simply need a checklist of what needs to get done in order for me to allow both subnets to communicate. Essentially id like to have it so the 192.168.3 is reserved for clients, and the 192.168.5 addresses for the static adresses (printers,wireless devices etc), and the client loses no networked functionality from the 192.168.3 subnet (printers, shares etc..) if they need to get to devices on the 192.168.5 subnet. Thanks for any help, it is definetly appriciated. I am open to any other plan of attacks as well

2 replies

by bfilmfan

I am slightly confused on your design, but here goes.

Are you planning to use a variable length subnet mask on the existing network? It read as if you plan to have 192.168.3 and 192.168.5 subnets on the same wire. Was this your thought?

If that was the plan, I'd simply subnet a class B address space with whatever number of bits I felt I needed. An example would be to break 172.16.0.1 with a 24 bit mask, would give you 256 subnets with 254 hosts each. You could then proceed with your 192.168.X.X address plan.

You will need to add the amended subnet to AD:

http://technet2.microsoft.com/WindowsServer/en/Library/94728c86-c7cf-4d03-9b43-91c67e0b09d61033.mspx

by bobtheitbuilder

If you have only one network segment then you may have to change to a Private Class B address range "172.16.x.x 255.255.0.0" which could be subnetted if you plan to have more subnets, 254x254 devices. 192.168.3.0 /24 can only give you at most 254 hosts per the one subnet. If you were to subnet a 192.168 range you may get more subnets but the amount of hosts drops considerably. Using a 172.16 range will give you plenty of host addresses for many years to come and your windows dhcp server can then easily cope with your scope. You would have to ament the router LAN IP address to a 172.16 one and then change all your static devices to the 172.16 range but only amend the scope on the dhcp server and the dhcp clients net a /release /renew. Good luck

This discussion is closed to new replies.