How should I move our network to new subnets without losing domain access?

November 18, 2026 4 answers
Asked by _n57!frostmaraca.3

I'm the sole IT administrator and need to move servers and workstations off 192.168.33.0. The proposed networks are 10.10.3.0 for servers and VMs and 10.10.13.0 for workstations.

The domain controller runs as a Hyper-V VM, and we have an HP ProCurve switch and a Zyxel USG Flex gateway. Where should I start, and how can I avoid breaking domain access during the move?

Answers

n.573~velmora

First, check whether both groups really have to be renumbered. If the goal is separation, you could leave the servers on the existing subnet and move workstations to a new VLAN and subnet. That avoids changing the domain controller address during the first phase.

Build the new network alongside the old one, configure routing, DHCP and DNS, then move a test workstation. Check sign-in and the applications people actually use. Once that works, add and test firewall rules that permit the required traffic between networks. Separate subnets alone don't restrict access if traffic is freely routed between them.

q.752!orbitfob:

If both address changes are mandatory, the workstation move can still be a separate phase. That gives you a working path between networks before touching the servers.

Reply to this answer
t.694+plivaro

Lab this before changing production. Recreate enough of the setup to practice VLANs, gateway interfaces, routing and a domain client reaching DNS. Then write down the exact cutover and rollback steps for each component.

Schedule a maintenance window and move things in stages rather than changing every address at once. Have a way to reach the switch, gateway and Hyper-V host if the network configuration locks you out. A rollback plan needs to cover how you will restore access, not just which old addresses to put back.

Reply to this answer
Vexlori-2g

Map the dependencies before moving any server. Workstations need to reach domain DNS and the domain controller, but applications may also have hard-coded addresses or use broadcasts to find a server. Broadcast discovery in particular may stop working across subnets.

Inventory static addresses, DNS records, DHCP settings and firewall rules, then test each service from a workstation on the new network. Pay special attention to the domain controller move and verify name resolution and domain sign-in after it changes.

_n57!frostmaraca.3:

I'll make an application inventory part of the plan. Checking sign-in alone wouldn't catch a service that relies on broadcast discovery.

Reply to this answer
8h!vexmori_625

Draw out where each VLAN lives and which device will route between the old, server and workstation networks. Confirm the switch ports and the connection to the gateway carry the intended VLANs before moving clients.

Also settle on subnet masks and gateway addresses, not just the network numbers. Test routing, DHCP and DNS on each new network first. The gateway and switch configuration depends on how your ports and VLANs are currently set up, so don't assume a generic device walkthrough will fit as written.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions