Wi-Fi & Network
Router changed IP addresses
Recover printers, shares, NAS, and smart-home devices after a router changes the home address range, breaking saved paths and manual IP settings.
Problem summary
A new or reset router can change the local subnet, breaking saved paths, manual IP settings, and device reservations.
Record the current router LAN IP and DHCP range.
ipconfig /all (macOS/Linux: ifconfig)
You know the new subnet, gateway, and address pool.
Stop before changing subnet or DHCP range on a network with work equipment.
Layer path
Step-by-step runbook
Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.
Write down the new network
Check: Record router LAN IP, DHCP pool, gateway, and DNS.
Expected result: You have a current baseline before editing any saved device paths.
If not: Do not chase individual devices until the new range is known.
Find critical devices by lease
Check: Use the router client list to identify printer, NAS, cameras, and backup targets by name or MAC.
Expected result: Each critical device has a current address or clear offline state.
If not: Check device power and old manual static IP settings.
Reserve before updating apps
Check: Create DHCP reservations for devices that need stable paths.
Expected result: The router owns the stable address plan.
If not: Avoid random manual IP edits; record any router limitation.
Update one saved path at a time
Check: Update printer ports, mapped drives, bookmarks, and backup destinations to the reserved address or stable hostname.
Expected result: Each service returns without changing the router range repeatedly.
If not: Test direct IP and name resolution separately.
Check for duplicate routers
Check: If devices land in different ranges, inspect mesh/extender/old-router DHCP or AP mode.
Expected result: One LAN range serves the trusted home network.
If not: Stop before subnet work if managed gear, VLANs, or work devices are involved.
Safe stop: Stop before changing subnet or DHCP range on a network with work equipment.
Decision tree
If: Working devices show a new subnet but saved paths use the old subnet.
Then: The router changed local addressing.
Action: Create reservations and update saved paths rather than changing the subnet repeatedly.
If: A device is missing from the router list.
Then: It may be offline or using a manual old-range IP.
Action: Reset only that device's network setting to automatic/DHCP if safe.
If: Two devices claim the same address.
Then: There is an IP conflict.
Action: Disconnect one, remove duplicate manual settings, and let the router assign/reserve addresses.
If: Addresses change unexpectedly after adding mesh or another router.
Then: A second DHCP server or double NAT may be active.
Action: Check AP/bridge mode and DHCP status on secondary gear.
If: Work gear, VPNs, VLANs, or managed switches are involved.
Then: Local changes may break managed policy or routing.
Action: Stop and document current ranges.
Safe stop: Stop before changing subnet or DHCP range on managed networks.
Evidence table
| Symptom | Evidence to collect | Likely layer | Next action |
|---|---|---|---|
| NAS bookmark stopped working. | Bookmark points to old IP; router client list shows NAS at new IP. | Saved path | Reserve new NAS IP and update bookmark/share path. |
| Printer offline after router swap. | Printer port uses old IP while printer has new lease. | Printer port or reservation | Reserve printer IP and update port. |
| Camera or smart device absent. | Device has manual static IP outside new subnet. | Device IP configuration | Set device back to DHCP or update to a planned reserved address. |
| Some devices get a different range. | ipconfig shows gateway from old router or mesh/extender. | Duplicate DHCP or double NAT | Disable secondary DHCP or use AP/bridge mode if supported. |
| Backup job fails after router change. | Backup destination path contains old IP or old hostname lease. | Backup destination identity | Update backup path after reservation and run a test backup/restore. |
Commands and settings paths
Working client baseline
ipconfig /all (macOS/Linux: ifconfig)
Where: Command Prompt or PowerShell on a working Windows PC.
Expected: IPv4, subnet mask, gateway, DNS, and DHCP server match the new router.
Failure means: The PC may be on guest Wi-Fi, VPN, old router, or wrong adapter.
Safe next step: Reconnect to the trusted LAN before updating devices.
Router LAN and DHCP
Router admin UI > LAN/DHCP settings > gateway, DHCP pool, reservations
Where: In the router or gateway app.
Expected: There is one clear DHCP pool and a place to reserve critical devices.
Failure means: Old reservations may not have migrated.
Safe next step: Create fresh reservations for printer, NAS, and backup targets.
Local neighbor view
arp -a
Where: Command Prompt or PowerShell after contacting local devices.
Expected: Known local IPs appear in the current subnet.
Failure means: The device may not be reachable or may be in another subnet.
Safe next step: Use router client list as the source of truth before app edits.
Name resolution check
nslookup HOST
Where: Command Prompt or PowerShell on the client PC.
Expected: The host resolves to the current local address if local DNS supports it.
Failure means: Hostname shortcuts may lag behind DHCP changes.
Safe next step: Use a reserved IP or update local name settings.
Hardware and platform boundary
Change only when
- Replace the router only after DHCP reservations, duplicate DHCP checks, and stable device paths still fail.
- Add managed networking only if you can maintain VLANs, DHCP scopes, and documentation.
Evidence that matters
- DHCP reservations, clear client list, stable firmware, useful logs, backup/restore of router config, and AP/bridge mode for mesh.
- For NAS and printer homes, good local DNS/reservation behavior matters more than top speed.
Evidence that does not matter
- Headline Wi-Fi speed does not fix stale printer ports or backup paths.
- Complex VLAN features are irrelevant if you only need stable home reservations.
Avoid
- Avoid repeated subnet changes while devices are reconnecting.
- Avoid exposing local services publicly to bypass local addressing.
Related tool/checklist
Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.
Device setup troubleshooterRelated problems
Last reviewed
2026-05-07 · Reviewed by HomeTechOps. Reviewed for DHCP reservations, saved local paths, duplicate DHCP risks, and conservative subnet-change stop points.
Sources/assumptions
- Assumes a single-router home network using private IPv4 addresses.
- Managed business networks, VLANs, and ISP-specific gateways may need expert handling.
Source-backed checks
HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.