K_Wilke

<div>
I would recommend you start subnetting - maybe separate by device type/function.<br><br>For example, create a subnet for Wireless devices.<br>Maybe one for Servers<br>Maybe one for Printers <br>etc.<br><br>If you must supernet, then I would expand it by 1 bit. &nbsp;If the network is already 192.168.2.x then by changing the mask to 255.255.254.0, you should be able to use 192.168.2.1 to 192.168.3.254 (usable).
</div>


<div>
From a technical perspective, yes, you can make that change. We've hit this a few times at one client site that was small to start with and no plans to grow. We are up to x.x.252.0 for their subnet setup now along with VLANs for devices that don't belong there.<br><br>It can be done. But, users need to be prepared for the change and what to do if "nothing is connected".<br><br>The main thing is to make sure to transition the domain controllers correctly, DHCP settings updated as needed, and any static IP assigned systems get the necessary change.<br><br>We would set up a temporary virtual machine on the old subnet to use as a jump server during this process.<br><br>PowerShell Remote can take care of most of the changes for the server static IP addresses as well as the IPConfig /Release &amp;&amp; IPConfig /Renew needed on the clients.
</div>


<div>
Resubnetting is the recommended procedure for increasing a DHCP scope when the current scope has entirely consumed the current subnet mask. However, this method requires you to change all subnet hosts and gateways. If you have an address range that has run out of available host addresses, you may be able to change the subnet mask to include a larger share of host addresses. However, simply changing the subnet mask requires that all routers and other statically assigned computers be reconfigured and all DHCP clients have renewed their lease obtaining the new parameters.<br><br>Additionally, the entire DHCP scope or scopes must first be deleted and then re-created using the new subnet mask. The potential for duplicate addresses exists during this period if you do not take steps to prevent leasing addresses that other clients may use. Despite all of the aforementioned caveats, resubnetting is still the recommended procedure. The resubnetting configuration creates no additional overhead on the subnet routers or gateways, and keeps all hosts on the same broadcast address.<br>If you use the resubnetting option, you need to delete and re-create the DHCP scope with the new subnet mask (it is not possible to change only the mask for a particular scope). If you are servicing existing clients within a portion of this range, you should turn on conflict detection until all your clients are migrated into the new scope. This action requires you to perform the following steps:<br>1. &nbsp; &nbsp; &nbsp;Configure the interface of each connected router and change the IP address for the connected interface, its subnet address, and its subnet mask.<br>2. &nbsp; &nbsp; &nbsp;Delete your current DHCP scope.<br>3. &nbsp; &nbsp; &nbsp;Create a new DHCP scope with the new subnet mask.<br>4. &nbsp; &nbsp; &nbsp;Enable the Conflict Retries option on the DHCP server (set to 1 or 2).<br>5. &nbsp; &nbsp; &nbsp;Force your DHCP clients to renew their DHCP leases.<br>6. &nbsp; &nbsp; &nbsp;Change the IP address, subnet mask, and/or default gateway on each statically-configured host.<br>7. &nbsp; &nbsp; &nbsp;The following example shows the result if you use the resubnetting option:<br>8. &nbsp; &nbsp; &nbsp;Subnet Address: 192.168.100.0<br>Subnet Mask: 255.255.254.0<br>9. &nbsp; &nbsp; &nbsp;You now have a network of 510 hosts with addresses from 192.168.100.1 to 192.168.101.254 (for scope 192.168.100.0), or 256 newly available DHCP addresses.
</div>


<div>
<div class="content wysiwyg-content fr-view">
<p>Hello all,</p><p>Please be gentle. &nbsp;It has been many, many years since I have had to change a client from one IP address scheme to another one.</p><p>A client of mine is using the IP address scheme of 192.168.2.x and it is a class C subnet mask of 255.255.255.0</p><p>They have run out of IP addresses.</p><p>So if I change the subnet mask to 255.255.192.0, then they should be able to use IP addresses of 192.168.1.1 - 192.168.63.254, correct?</p><p>I can do this with a 192.168 ip scheme and I don't have to change to a 10.10.x.x, correct?<br>Thank you,</p>
</div>
</div>



Hello all,
Please be gentle.  It has been many, many years since I have had to change a client from one IP address scheme to another one.
A client of mine is using the IP address scheme of 192.168.2.x and it is a class C subnet mask of 255.255.255.0
They have run out of IP addresses.
So if I change the subnet mask to 255.255.192.0, then they should be able to use IP addresses of 192.168.1.1 - 192.168.63.254, correct?
I can do this with a 192.168 ip scheme and I don't have to change to a 10.10.x.x, correct?
Thank you,

Changing IP LAN Adresses

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.