• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 58
  • Last Modified:

Changing network subnet

Hi Experts,

We are merging with another company and need to change our private subnets to theirs.

We have DHCP scopes created for the clients We will change server IP's to the new subnet. My concern is we have 2 VLAN's  on our switches that need to be changed along with the IP for management.

Is this the correct order and approach.

Routers are complete(not using them as gateways.

1) Change Switch management IP
2) Change VLAN IP's leave VLAN ID the same.
3) Change all servers to new IP and Gateway.
4) Activate new workstation scopes

1 Solution
John HurstBusiness Consultant (Owner)Commented:
1, 3, and 4: Yes.
2: I think so. There is no need to change the VLAN ID.
5: Change printers as well.
nociSoftware EngineerCommented:
There is slightly more to it.....
Don't forget other networked equipment. (esp. the ones without DHCP).

Network services (Printing, LDAP, DNS, log servers, ...) are also changing. So you will also need to update policies (Windows) or config files that address those services. Part of them (Like DNS) might be supplied in DHCP.
Check the configuration for use of hard IP addresses in stead of names.

Check DNS service records (Like MX, that require IP addresses and not names).
talltreeAuthor Commented:
Thank you John and Noci.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now