Wi-Fi & Network
Device keeps changing IP address
Stabilize a printer, camera, NAS, or smart-home device that keeps getting a new local address — usually a DHCP reservation issue, not a hacked device.
Problem summary
Changing local IP addresses are usually a DHCP reservation issue, not a sign the device is hacked or broken.
Find the device in the router client list by name and MAC address.
ipconfig /all (macOS/Linux: ifconfig)
The current IP, MAC, and connection type are visible.
Stop before changing the whole subnet while important backups or work devices are active.
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.
Identify the device by MAC
Check: Use the router client list or device network page to record hostname, MAC, and current IP.
Expected result: You can identify the device even if its address changes.
If not: If it is not visible, fix power, Wi-Fi, or Ethernet first.
Remove device-side static conflicts
Check: Set the device back to automatic DHCP unless vendor docs require a static IP.
Expected result: The router leases an address cleanly.
If not: If the device cannot use DHCP, stop before changing subnet-wide settings.
Create a router reservation
Check: Reserve a unique address for the device in the router DHCP screen.
Expected result: The device returns to the same address after reboot.
If not: If not, check MAC randomization or duplicate DHCP servers.
Update saved paths
Check: Update printer ports, NAS paths, camera apps, bookmarks, and backup jobs to the reserved address or stable hostname.
Expected result: Apps stop chasing the old address.
If not: If one app still fails, isolate that app before changing the router again.
Document the reservation
Check: Record device name, MAC, reserved IP, owner, and purpose in your home network notes.
Expected result: The next router change can be rebuilt safely.
If not: If several critical devices are undocumented, pause and inventory before further edits.
Decision tree
If: The device appears with a new MAC each time.
Then: Private/random MAC or adapter changes are preventing stable reservations.
Action: Use a stable MAC for this trusted network or reserve the actual MAC shown.
If: The device has a manual IP outside the current subnet.
Then: Router replacement or subnet changes broke the path.
Action: Return the device to DHCP, then reserve the desired address on the router.
If: Two devices claim the same address.
Then: There is an IP conflict.
Action: Disconnect one device, clean old reservations, and assign unique addresses.
Safe stop: Stop before changing the whole subnet while important backups or work devices are active.
If: The router reservation exists but apps still fail.
Then: The network identity is fixed, but saved paths are stale.
Action: Update printer ports, NAS paths, bookmarks, and backup destinations.
If: A second router or extender was added recently.
Then: A duplicate DHCP server may be issuing addresses.
Action: Put the extra router into bridge/AP mode only if you understand its role.
Evidence table
| Symptom | Evidence to collect | Likely layer | Next action |
|---|---|---|---|
| Printer or NAS appears at a new address. | Router DHCP lease table with hostname, MAC, and current IP. | DHCP reservation | Reserve the device by MAC and update saved paths. |
| Reservation does not stick. | Device reports a different/private MAC for the home SSID. | Client identity | Use stable MAC for that trusted network. |
| Device vanishes after router replacement. | Old saved IP uses a different subnet than current gateway. | Subnet migration | Return device to DHCP and rebuild reservations. |
| Two devices intermittently fail. | Duplicate leases, static IP overlap, or ARP table changes. | IP conflict | Clean the conflict before application troubleshooting. |
Commands and settings paths
Client network details
ipconfig /all (macOS/Linux: ifconfig)
Where: On a Windows PC on the same home network.
Expected: The gateway and subnet match the router DHCP range.
Failure means: Wrong subnet or gateway points to another network or duplicate router.
Safe next step: Fix network attachment before reserving devices.
Router reservation screen
Router admin UI > LAN/DHCP/reservations/connected devices
Where: In the router admin UI.
Expected: The target device has a unique MAC and a documented reserved IP.
Failure means: No reservation or duplicate MAC/IP leaves discovery unstable.
Safe next step: Create one reservation and record it.
Neighbor table
arp -a
Where: PowerShell or Command Prompt on a Windows PC after reaching the device.
Expected: The target IP maps to the expected MAC address.
Failure means: A different MAC at that IP indicates a conflict or stale path.
Safe next step: Clean reservations and retest before changing app settings.
Hardware and platform boundary
Change only when
- Buy networking gear only after duplicate DHCP, subnet, reservation, and MAC-randomization evidence is clean.
Evidence that matters
- Router firmware quality, clear reservation UI, client list visibility, and exportable settings matter.
Evidence that does not matter
- A faster router does not fix stale printer ports, NAS bookmarks, or manually conflicting static addresses.
Avoid
- Avoid disabling DHCP for the whole network and avoid exposing local devices to the internet to bypass local discovery.
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, MAC identity, subnet changes, stale app paths, duplicate DHCP, and IP conflict stop points.
Sources/assumptions
- Assumes private home IPv4 addressing managed by a consumer router.
- Does not cover business VLAN, static routing, or public IP assignment.
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.