Just build a new subnet in the existing site (192.168.0.0/23) and delete the “192.168.1.0/24″ subnet. Nothing else needs to be changed (other than you’ve mentioned), since you’re not changing IPs.

I’m happy I found this article, it’s very close to what I’m planning for my network. Actually, response #4 touches on what I would like to do.
I’ve got 3 subnets connected by VPN. 2 of the subnets are not very populated but the 3rd is near capacity. I have a lot of static addresses on that subnet and would like to increase the size of the subnet without changing any of them.

I have 192.168.5.0 /24 (has one DC)
192.168.3.0 /24 (has one DC)
and 192.168.1.0 /24 (has two DCs).

I’m considering changing the subnet mask of the 1.0 network and turning it into 192.168.0.0 /23.
My thinking behind this is that I won’t have to change the IPs of the servers and devices, just their subnet masks (aside from the necessary configuration changes to my firewall and to active directory). I can let a change in DHCP configuration take care of my client machines.

In the 5th step of the original article you discuss creating a new subnet in sites and services. So, I’m wondering if it’s possible to do what I’m suggesting. I’m not giving my DCs (or any of my other servers for that matter) different addresses, I just want to change the subnet mask. If it is possible, what steps would be different?

Thanks,
Thomas

thanks , hope you can help.

john disano
Jdisano@hotmail.com or john.disano@ppsd.org

thanks , hope you can help.

john disano
Jdisano@hotmail.com

We have a LAN of ~22 WinXP computers with a single Win2K Server DC acting as DHCP/DNS Server, File & Print Server. I finally buckled down last week to change over from public IP addresses (don’t ask )to 192.168.11.0/24. I’d planned *most* of your points and found that I had no trouble connecting clients to the domain or to the Internet after the changes.

BUT I now find I have two WinXP clients which cannot access any resources on the File/Print Server: if I drill down through My Network Places to Microsoft Windows Network, the domain name appears but after an unusual delay; when I then click on the domain name I get “nnnn is not accessible. you might not have permission…. no path to network resource” where nnnn is the domain name.

I’ve already spent a “long day/night” fiddling with things, making sure the DC’s DHCP, DNS etc. is clean & correct… shutdown the two clients after connecting them to a DUMMY Workgroup, removed them from the DC’s DNS Forward Lookups, DHCP list and AD list of computers… followed by a fresh connect to the domain from each client which succeeds as normal.

The clients appear to be joining the domain just fine and can be seen in the domain browse list from the DC and other clients and can be connected to – they just cannot connect to the domain themselves. If I enter the domain name in an Explorer Address Box on the client I get the default content page for the HTTP Server on the DC.

Over the weekend it’s occurred to me that the common element here is that those two clients are the only ones which had/have printers attached (USB) which are shared and had entries in the Active Directory list.

I’m now hoping that if I remove those dangling(?) printer shares from AD it’s going to help. Other than that I’ll be following every clue in your article in detail to see what I might have missed, when I get to the office. If you have any thoughts or suggestions I’d appreciate hearing back. Thanks.

Fantastic articles- thanks!

We are just planning on changing our subnet mask- it’s currently 255.255.255.0 and we need more addresses on our static range. What’s the best way to do this?

Many thanks!