Start Here: Can You See the Cameras on Your Local Network?
A router change breaks cameras in one of two very different ways, and the fix depends on which one you have. Before working through the seven fixes below, check whether the cameras are reachable at all from inside your own home. Open your camera or NVR app while connected to your home Wi-Fi, not on cellular data. If the live view loads, the cameras are fine on the local network and the problem is purely remote access – continue to Fix 1. If the live view fails on your own network too, work through this section first, because none of the remote-access fixes will help until the cameras are back on the network. Power the system down and back up. A new router hands out fresh local IP addresses, and equipment that stayed powered on through the swap can hold onto an address the new router no longer recognises. Unplug the NVR and any PoE switch, wait thirty seconds, then power the router first, the switch second, and the NVR last. Give it two or three minutes to settle before checking again. Check whether a device is stranded on the old address range. This is the most common reason a camera stays invisible after a router change. If you gave the NVR or a camera a fixed IP address on the old network, say 10.0.0.50, and the new router hands out addresses in a different range such as 192.168.1.x, that device is still answering on an address that no longer exists on your network. It will not appear in the new router’s device list, and the app will never find it. Connect to it directly and set it back to automatic (DHCP), or give it a new fixed address inside the new router’s range. On most NVRs this sits under Network settings; on cameras it is usually done through the manufacturer’s app on a phone joined to the same network.Reconnect Wi-Fi Cameras to the New Network
A new router usually means a new network name and password, and wireless cameras have no way to guess them. Battery cameras, Wi-Fi cameras and video doorbells all have to be re-paired by hand, one at a time, through the manufacturer’s app. Wired PoE cameras are not affected – they follow the NVR. If you kept the old network name and password exactly as they were, most Wi-Fi cameras find their way back on their own within a few minutes. If either one changed, expect to re-pair every wireless device. Once the cameras are visible on your local network again, continue to Fix 1 to restore access from outside the house.FIX 1: Find Your NVR’s New Local IP Address
When you replace a router, every device on your network gets a new local IP address assigned by the new router. Your NVR had an address on the old network – something like 192.168.1.105 – and the new router may have assigned it a completely different address. Any remote access configuration (port forwarding, app settings) that referenced the old address is now pointing at nothing. Start by finding the NVR’s current local IP address on the new network. The easiest way is through the NVR’s own display: go into the NVR’s Network settings menu and look for the IP address listed there. Alternatively, log into your new router’s admin page (usually at 192.168.1.1 or 192.168.0.1 in a browser) and look at the connected devices list – your NVR should appear there with its current address. Write this address down. You’ll need it for the port forwarding step.FIX 2: Give the NVR a Static IP Address
Before setting up port forwarding, assign the NVR a fixed (static) local IP address so it doesn’t change again the next time the router restarts or a lease expires. If the NVR’s address keeps changing, your port forwarding rules will periodically stop working without any warning. You can do this two ways. The first is through the NVR itself: go into Network settings, switch from DHCP (automatic) to Static, and manually enter an IP address outside the range your router hands out automatically (check your router’s DHCP range in its settings – pick an address above the upper limit of that range). The second method is through the router: most modern routers let you reserve a specific IP address for a specific device by its MAC address, so the router always hands out the same address. Either method works – the goal is that the NVR always has the same local address.FIX 3: Set Up Port Forwarding on the New Router
Port forwarding is what allows your camera app to reach the NVR from outside your home network. Your old router had port forwarding rules set up – those rules don’t transfer automatically when you change routers, so you need to recreate them on the new one. If you’re not sure how to do this for your specific model, a port forwarding guide for your router walks through the exact steps brand by brand. Log into your new router’s admin page. Find the Port Forwarding section (it may be under Advanced, NAT, or Firewall depending on the brand). Create a new rule with these typical settings for most NVR systems: the internal IP address is your NVR’s static address from Fix 2; the ports to forward are usually TCP 80 (or 8080), TCP 554, and UDP 37777 – but check your NVR’s manual for the exact ports your brand uses, as these vary. Set the external port to match the internal port for each rule. Save and apply. After setting up port forwarding, test it using a port-checking tool (search “port check tool” online) to confirm the ports are open and reachable from outside your network.FIX 4: Update Your DDNS Settings
Your home internet connection has an external IP address – the address the internet uses to reach your home. Most residential internet plans don’t give you a fixed external IP address; it changes periodically, and it almost certainly changed when you switched providers or reset your router. If you were using a domain name to reach your NVR remotely (something like yourhome.ddns.net), that domain needs to point to your new external IP address. If your NVR has a built-in DDNS service (most brands like Hikvision, Dahua, and Reolink offer their own), go into the NVR’s Network settings, find the DDNS or P2P section, and confirm it’s enabled and active. The NVR updates the domain name automatically when your IP changes – but only if DDNS is enabled and connected. If you set up a third-party DDNS service (like No-IP or DynDNS) on the old router, you’ll need to either re-enable that service on the new router or reconfigure it on the NVR directly. If you were using your internet provider’s P2P service or your NVR brand’s cloud service (serial number-based connection), go into the NVR’s network settings and confirm the P2P or cloud connection status shows as online. These services often reconnect automatically once the NVR has internet access, but a router change can require reauthorization.FIX 5: Reconnect the App to the NVR
After updating port forwarding and DDNS, the camera app on your phone may still be trying to connect using the old configuration. Most apps cache the last known connection settings, and those settings are now stale. Open the app and find the device or camera settings for your NVR. Delete or edit the existing connection and re-add the NVR using its current external address (your DDNS domain name, or your current external IP if you’re not using DDNS) and the same port numbers you set up in Fix 3. Enter your NVR username and password when prompted. If the connection still fails, double-check that the ports are actually open (Fix 3) and that the DDNS domain is resolving to your current external IP (Fix 4) before assuming the app settings are wrong.FIX 6: Check the New Router’s Firewall and Security Settings
Some routers – especially those provided by internet service providers – have aggressive default firewall settings that block incoming connections even when port forwarding rules are in place. ISP-provided routers in particular sometimes run in a mode that prevents any inbound traffic regardless of your forwarding rules. Check whether your new router has a firewall setting that may be blocking inbound connections on the ports you forwarded. Also check whether the router is in “double NAT” – a situation where your router is connected behind another router or modem-router combo from your ISP. Double NAT prevents port forwarding from working correctly because the incoming connection hits the ISP device first and never reaches your router’s forwarding rules. If you’re in a double NAT situation, either put the ISP device in bridge mode (it becomes a modem only, and your router handles all routing) or set up port forwarding on the ISP device as well.FIX 7: Consider Switching to a VPN-Based Remote Access
If port forwarding is consistently unreliable – whether because your ISP changes your external IP frequently, your router’s firewall is difficult to configure, or you simply don’t want open ports on your home network – a VPN-based remote access setup is a more secure and often more stable alternative. Rather than forwarding ports to the NVR, you connect your phone to your home network via VPN, and the camera app connects as if you’re sitting at home. Some routers have a built-in VPN server (WireGuard or OpenVPN). Setting it up once means your remote camera access works without any port forwarding, and it’s more secure because no camera ports are exposed to the internet. Many NVR brands also support direct VPN tunnel connection from their apps – check your NVR’s documentation for supported remote access methods.Still Have Security Cameras Stopped Working After Router Change? What to Check
If your security cameras stopped working after router change and you’ve worked through all seven fixes but still can’t access the NVR remotely, the most common remaining culprits are: ports that are showing as closed despite forwarding rules (usually a double NAT or ISP firewall issue), a DDNS domain that isn’t resolving to the correct external IP (log into your DDNS account and verify), or an app that’s cached old credentials and needs to be fully deleted and reinstalled rather than just edited. A factory reset of the NVR’s network settings, followed by a clean reconfiguration, resolves cases where the NVR’s own network stack has gotten into a confused state after the router change. Start here: Fix 1 (find the new IP address) and Fix 3 (set up port forwarding on the new router) resolve the majority of remote access failures after a router change. Get those two right before adjusting anything else.Frequently Asked Questions
Why did my cameras stop working after changing routers?
The new router assigns different IP addresses and often a new Wi-Fi name and password, so the cameras and NVR can’t reconnect. Re-pair them and update the Wi-Fi credentials.
How do I reconnect cameras to a new router?
Reconnect the NVR by cable or update its network settings, re-enter the new Wi-Fi name and password on wireless cameras, and re-pair the P2P or app connection.
Should I use the same Wi-Fi name and password as my old router?
If you can, yes — setting the new router to the same SSID and password lets most cameras reconnect automatically without re-pairing.
Why is remote viewing down after a router change?
P2P and any port forwarding were tied to the old router. Re-link the system in the app, and redo port forwarding or DDNS if you used them.
About the author
This guide was written and reviewed by the GuardSourceHQ Editorial Team, drawing on more than three decades of hands-on construction and service experience, along with practical experience installing and troubleshooting modern home-security systems. We judge a system three ways: how it performs, how it’s likely to fail, and how hard it will be to service later. We trace problems to the real cause instead of swapping parts and buying the same problem twice. We’re upfront about trade-offs, the limits of what we’ve tested, and what we’d trust in our own homes.