An IP camera that works perfectly during installation can sometimes appear offline on the NVR later, even though the camera is still powered and connected to the network.
One of the first things to check is the camera's IP address. If the camera was configured to use DHCP, it may later receive a different address from the network. If the NVR was manually configured to connect to the old address, it can keep looking for the camera at that old IP and report the channel as offline.
This guide explains why that happens, how to diagnose it quickly, and how to prevent it with a properly planned static IP setup or DHCP reservation.
What is DHCP?
DHCP stands for Dynamic Host Configuration Protocol. A DHCP server, normally a router or other network device, can automatically provide a device with network settings such as its IP address, subnet mask, gateway and DNS information.
That is convenient for phones, laptops and temporary devices. CCTV systems are different because an NVR may be configured to find a camera at a specific address every day. If that address changes, the NVR entry can become incorrect.
Hikvision's network camera documentation confirms that when DHCP is enabled, the camera automatically obtains IPv4 parameters from the network. The same documentation also provides a manual IPv4 mode where the IP address, subnet mask and default gateway are entered directly.
A real-world example
Imagine a small CCTV system with the following addresses:
| Device | IP Address |
|---|---|
| Router / Gateway | 192.168.1.1 |
| NVR | 192.168.1.10 |
| Camera 1 | 192.168.1.101 |
On installation day, Camera 1 is discovered at 192.168.1.101. You add that camera to the NVR and the picture comes online.
Later, the DHCP server gives that same camera another address, for example 192.168.1.105. The camera is still on the network, but the NVR may still be trying to connect to 192.168.1.101.
The result is that the existing NVR channel shows Offline. If you run the NVR camera search again, the same physical camera may appear at the new address, which can make it look like a new device has appeared.
Why can a DHCP address change?
DHCP supports dynamic address allocation. A client receives an address from the DHCP server under the network's allocation and lease policy. In many cases a client renews and keeps the same address, but it should not be assumed that a dynamically assigned address will always remain identical after network changes, lease events, device resets or DHCP-server changes.
For a CCTV channel that has been manually added to an NVR by IP address, the important point is simple: the NVR entry and the camera's current address must match.
DHCP vs Static IP for CCTV
DHCP
- Fast initial setup.
- Automatic network configuration.
- Useful during discovery or temporary installation.
- The address is controlled by the DHCP server and can be less predictable unless a reservation is used.
Static IP
- The camera uses a deliberately assigned fixed address.
- The NVR always knows where that camera should be found.
- Troubleshooting and documentation are easier.
- Each address must be unique and planned correctly to avoid IP conflicts.
Example static IP plan for a CCTV system
For a network where the router is 192.168.1.1 with a subnet mask of 255.255.255.0, a simple installation plan could be:
| Device | IP Address | Location / Purpose |
|---|---|---|
| Router / Gateway | 192.168.1.1 | Main network gateway |
| NVR | 192.168.1.10 | Recorder |
| Camera 1 | 192.168.1.101 | Front Door |
| Camera 2 | 192.168.1.102 | Shop Floor |
| Camera 3 | 192.168.1.103 | Rear Door |
For Camera 1, the manual settings might be:
- IP Address: 192.168.1.101
- Subnet Mask: 255.255.255.0
- Gateway: 192.168.1.1
For the NVR:
- IP Address: 192.168.1.10
- Subnet Mask: 255.255.255.0
- Gateway: 192.168.1.1
These addresses are examples only. Always match the customer's actual LAN design, make sure every device has a unique address, and ensure a manually assigned static address will not be handed to another device by the DHCP server.
How to fix an IP camera that is offline because its IP changed
Step 1: Search for the camera
Use the NVR camera search, the manufacturer's device discovery utility, or the camera's web interface to locate the camera on the network.
Step 2: Check the current network settings
Record the camera's current IP address, subnet mask and gateway. Compare the current IP with the address saved in the NVR channel.
Step 3: Disable DHCP if you want a manually fixed address
Open the camera's Network or TCP/IP settings and disable DHCP. Menu names vary by manufacturer, but Hikvision cameras commonly provide DHCP and Manual modes under the TCP/IP settings.
Step 4: Assign a suitable static IP
Enter a unique address that belongs to the correct subnet. For example:
- IP Address: 192.168.1.101
- Subnet Mask: 255.255.255.0
- Gateway: 192.168.1.1
Before saving, make sure the address is not already being used by another device.
Step 5: Update the NVR
Edit the existing camera channel or re-add the camera using the correct IP address, username, password and protocol settings. Refresh the camera status and confirm that the channel returns online.
Important: built-in PoE NVR ports can use a different camera network
Do not automatically assume that every camera should use the same LAN subnet as the router. Some PoE NVRs maintain a separate internal network for cameras connected directly to the recorder's built-in PoE ports.
Before changing addresses, identify the topology:
- Camera → network/PoE switch → LAN → NVR
- Camera → NVR built-in PoE port
The correct IP range can be different between these two designs. Check the NVR model's network and PoE settings before changing camera addresses.
Other reasons an IP camera can show offline
1. Wrong subnet
If an NVR is 192.168.1.10 and a camera is 192.168.0.101 on a normal /24 network, they are on different subnets and may not communicate without routing.
2. Duplicate IP address
Two devices using the same IP address can create an address conflict. Every camera, NVR and other network device must have a unique address.
3. Incorrect username or password
The NVR can discover a camera but still fail authentication. This is common after a camera reset, password change or replacement.
4. PoE power problem
Check the PoE budget, port status, camera power requirement and cable condition. A camera that loses power will disappear from the network entirely.
5. Can poor Ethernet cabling make a PoE camera go offline?
Short answer: Yes. A PoE IP camera receives power and data through the same Ethernet cable. Copper-clad aluminium cable, a broken conductor, excessive pulling or a tight bend, rodent damage, moisture, and a loose or poorly terminated RJ45 plug or keystone jack can cause voltage drop, link errors, intermittent restarts or a complete offline condition.
Why low-quality cable causes PoE faults
- Copper-clad aluminium, also called CCA: aluminium has higher electrical resistance than copper. Fluke Networks reports approximately 55% higher DC resistance for aluminium of the same diameter. In a PoE circuit, higher resistance means more voltage is lost in the cable and more heat is produced. The camera can become unstable even when the Ethernet link appears to work.
- Excessive pulling, tight bends, crushing or kinks: these can distort the cable geometry and reduce electrical performance. Severe strain can also damage a conductor or pull a termination partly out of contact.
- Rodent damage: mice and rats can damage the outer jacket, insulation and copper conductors. A partly damaged pair may work intermittently before failing completely, and a damaged outdoor jacket can also allow moisture to enter.
- Loose keystone jack or poor RJ45 termination: a conductor that is not fully seated in the IDC contact can create an open circuit or an intermittent connection. Movement, vibration or cable tension can then make the camera repeatedly connect and disconnect.
Common signs of a marginal PoE cable
- The camera goes offline when infrared LEDs, a white light, a heater or another higher-power feature starts.
- The link LED drops or the picture returns when the cable or keystone is moved.
- The camera works on a short known-good patch lead but not on the installed cable run.
- The camera repeatedly restarts, shows packet loss or negotiates a lower link speed.
- A cable tester reports an open conductor, short, split pair, excessive length or abnormal resistance.
How to test and fix the cable fault
- Connect the camera with a short, known-good, factory-made full-copper Cat5e or Cat6 patch lead.
- Try a known-good PoE port and confirm that the NVR or switch has enough total PoE power budget.
- Inspect the complete route for tight bends, flattened sections, staples, cuts, tooth marks, water ingress and strain at both ends.
- Test the permanent link. A basic tester can find wire-map faults; a professional certifier can also measure length, insertion loss, DC loop resistance and resistance unbalance that matter for PoE.
- Re-terminate both ends to the same T568A or T568B scheme, keep pair twists close to the contacts, fully seat every conductor and secure strain relief.
- Replace CCA, damaged or unreliable cable with standards-compliant, solid full-copper Cat6. Use external-grade or suitably protected cable where the route is outdoors, damp, exposed to sunlight or vulnerable to rodents.
Installer note: HawkVision Pro has encountered internal conductor breaks, CCA cable with excessive resistance, rodent-chewed runs and loose keystone terminations in real installations. Do not hide a splice inside a wall or ceiling as a permanent repair. If the cable has been physically damaged or is CCA, replacing the full run is normally the more reliable solution.
6. Incorrect port or network interface
On recorders with multiple network interfaces or integrated PoE ports, make sure the camera is configured on the network that actually reaches the NVR.
Static IP or DHCP reservation?
A manually configured static IP is not the only way to keep a predictable camera address. Another professional option is DHCP reservation, sometimes called Address Reservation.
With a DHCP reservation, the camera can remain configured for DHCP while the router is instructed to always give that camera the same address, normally based on its MAC address.
- Manual static IP: the address is configured inside the camera.
- DHCP reservation: the router/DHCP server controls the fixed assignment.
For small standalone CCTV systems, a documented static plan is straightforward. On managed networks, DHCP reservations can make central administration easier.
Professional installation tip: keep an IP allocation sheet
Before leaving a site, document every permanent device:
| Channel | Device | IP Address | Location |
|---|---|---|---|
| CH1 | Camera 1 | 192.168.1.101 | Front Door |
| CH2 | Camera 2 | 192.168.1.102 | Shop Floor |
| CH3 | Camera 3 | 192.168.1.103 | Rear Door |
| — | NVR | 192.168.1.10 | Office |
Months later, if Camera 2 fails, the engineer immediately knows which address should belong to that camera and can compare the expected configuration with the current network.
Quick troubleshooting checklist
- Confirm the camera has power.
- Check Ethernet link and cable condition.
- Search for the camera on the network.
- Compare its current IP with the IP stored in the NVR.
- Confirm the camera and NVR are on the correct subnet.
- Check for duplicate IP addresses.
- Verify the camera username and password.
- Check PoE port status and total PoE budget.
- Use a static IP or DHCP reservation where predictable addressing is required.
- Document the final configuration.
Frequently asked questions
Can DHCP make an IP camera go offline on an NVR?
Yes, in a setup where the NVR is configured to connect to a specific camera IP. If the camera later uses a different DHCP address while the NVR continues trying the old address, that NVR channel can show offline.
Should CCTV cameras always use static IP addresses?
Not always. DHCP is a valid network configuration method. The key requirement for a permanent CCTV system is predictable addressing. A manually configured static IP or a properly managed DHCP reservation can both achieve that.
Why does the same camera appear as a new device in NVR search?
Often because the camera is being discovered at a different IP address from the address currently saved in the NVR channel.
Does the NVR need a static IP?
For many permanent installations, a predictable NVR address makes management, remote access and troubleshooting easier. The exact design depends on the customer's network.
Can a faulty cable cause the same offline symptom?
Yes. IP addressing is only one possible cause. CCA cable, high resistance, a broken pair, moisture, rodent damage and a loose RJ45 or keystone termination can interrupt both PoE power and network data.
Why does a PoE camera go offline when night vision turns on?
Night-time infrared or white-light modes can increase the camera's power demand. If the cable has excessive resistance, the run is too long, a termination is poor or the PoE budget is marginal, the additional load can expose the fault and the camera may restart or disconnect. Confirm this by testing with a short full-copper patch lead and a known-good PoE port.
Conclusion
If an IP camera works during installation and later appears offline, do not immediately assume the camera has failed. Check whether its IP address has changed and compare the current address with the one stored in the NVR.
For permanent installations, a planned static IP scheme or DHCP reservation provides predictable addressing and makes future maintenance much easier.
Trusted references
- Hikvision — Network Camera User Manual: TCP/IP, DHCP and Manual IPv4 configuration
- Hikvision — Network Video Recorder User Manual: Network Configuration
- TP-Link — DHCP Reservation / Fixed IP Address guidance
- RFC Editor — RFC 2131: Dynamic Host Configuration Protocol
- Fluke Networks: why CCA cable increases resistance and risk in PoE links
- Axis Communications: network camera troubleshooting and cable checks
- Panduit: Category 6 full-copper cable, PoE compliance, pull tension and bend radius
- Leviton: cable pulling tension, bends, kinks and termination practices
- Leviton: termination faults, open conductors and poor connections
- Belden: armoured Category 6 cable for IP cameras exposed to rodents, crushing and cut-through hazards
Network menus and exact configuration steps vary by camera, NVR, router and firmware. Always confirm the actual network topology and avoid assigning duplicate IP addresses.