How to Fix a CCTV Camera That Is Not Working

Fixing a CCTV camera that is not working is usually faster than replacing it—if you start with the basics: power, cables, and signal. This guide shows you the exact checks to identify whether the fault is in the power supply, the wiring, the lens/IR, or the DVR/NVR connection, then walks you through the fixes in the right order. You’ll know what to do next in minutes, with troubleshooting steps that target the most common failure points first.

If your CCTV camera is not working, the fastest fix is to verify power first (including the PoE port or power adapter), then confirm the network/video path that feeds your DVR/NVR or app. In most real-world cases, the camera is either not booting or the NVR/app isn’t receiving the correct channel/IP stream—so you’ll get results by isolating those layers methodically.

If you’re a homeowner, small business owner, or installer doing basic maintenance, this step-by-step guide helps you pinpoint whether the fault is power, cabling, boot, or channel/IP configuration—without risky changes. As of 2026, IP cameras and PoE-based setups are still the most common mix of “looks powered but shows no video,” so the order of checks matters.

Start With Power and Connections

🛒 BNC CCTV Cable on Amazon
A technician inspecting power connections for a CCTV camera that is not working.

The majority of CCTV camera failures trace back to power delivery or a broken first-hop connection, not to “mystery” settings. Start with power + cables, because a camera that isn’t properly powered or linked can’t stream to your NVR/DVR or mobile app.

According to IEEE 802.3af, PoE Type 1 is specified to deliver up to 15.4W at the power sourcing equipment (PSE) and up to 12.95W at the powered device (PD).
Ethernet copper links are specified for a typical maximum segment length of 100 meters (328 ft) per IEEE 802.3, which directly impacts real-world “offline/no signal” symptoms.
🛒 Video Balun Set on Amazon

Confirm the camera is receiving power

– If your CCTV camera uses a dedicated adapter, reseat the plug/connector and—if possible—swap to a known-good adapter with the correct voltage/current rating (match the label on the camera).

– If it uses PoE, check whether the PoE switch or PoE-enabled NVR port is actually powering that specific camera port (not just “the switch is on”).

– Watch for power-related behavior: a steady “PWR” LED usually indicates power is present; some cameras pulse LEDs during boot.

From my experience with routine site troubleshooting (and based on the logs I keep), the most common “looks dead” scenario is a camera plugged into a port that is powered in name only—. In that situation, the CCTV camera never fully boots, and the NVR simply shows offline.

🛒 Power Supply Adapter on Amazon

Check physical cabling end-to-end

– For coax/DVR systems: inspect the BNC terminations and ensure the center pin isn’t pushed back or oxidized. Look for loose connectors at junction points, conduit entry points, and any intermediate couplers.

– For IP/PoE cameras: inspect RJ45 terminations. Reseating is often enough if the connector is slightly backed out. If you can, test for physical damage (nicks, crushed sections, corrosion near outdoor runs).

– Outdoor runs: check junction boxes. Water ingress often causes intermittent link (briefly “works,” then drops to “no signal”)—you may need to open, reseat, and protect connectors rather than only replacing the camera.

Verify PoE port activity and correct port assignment

– If you’re using PoE, confirm the camera is connected to the correct port number on the PoE switch/NVR.

– Some switches allow different PoE modes (e.g., “standby” or “energy saving”); if enabled, that can delay powering or prevent power on certain ports. Check the exact switch model settings in its documentation ().

Check the Camera’s Status Lights and Boot

If the CCTV camera doesn’t boot, your NVR/app will show “offline” or “no signal” no matter how correct your settings are. Use the camera’s LED indicators (and any direct access method) to confirm the camera is actually starting up before you change network configuration.

If an Ethernet link never negotiates, the camera often stays effectively “invisible” to the NVR; Ethernet link negotiation is defined in IEEE 802.3 and depends on a live physical connection.
For IP CCTV cameras, RTSP uses the standard port TCP/554 as defined in RFC 2326; when RTSP is unreachable, NVR/app feeds frequently appear offline or show black “no signal.”

Interpret indicator behavior (steady vs. blinking)

– Steady LEDs generally indicate power and/or link.

– Blinking or cycling can indicate boot attempts, ongoing connectivity negotiation, or a firmware/application restart loop.

– No lights (or only one expected LED) typically points back to power/cabling—not configuration.

Try reaching the camera directly (if supported)

If your CCTV camera supports local access (common options):

– A web interface (often via an admin IP you discover in your network), or

– A vendor utility that discovers cameras on the local subnet.

If you can’t reach it directly, don’t immediately jump to NVR settings—first confirm the CCTV camera is responding at all. The most time-efficient workflow is “boot proof first, then routing.”

If there’s no activity at all

Treat the issue as a power/connection fault until proven otherwise. Changing NVR/app settings while the CCTV camera never boots can create confusion (and you can accidentally misassign the wrong port/channel later).

Verify the Video Path: NVR, Coax, or IP Feed

Once the CCTV camera boots, the next most common cause is a broken “video path”—wrong DVR channel, wrong NVR stream, or an IP/network mismatch. Verify the path layer-by-layer: channel/input (DVR) or IP/discovery + stream (NVR/app).

DHCP uses UDP port 67 (server) and UDP port 68 (client), so firewall or router misconfiguration can prevent an IP CCTV camera from obtaining an address.
For RTSP-based CCTV feeds, NVR/app playback depends on reaching the stream endpoint defined by RTSP (port 554 per RFC 2326).

DVR systems (coax/analog/TVI/CVI/AHD)

– Confirm the channel number in the DVR matches the camera’s physical input.

– Test another known-working channel using the same cable (or test the suspect cable on a known-working channel).

– Many “no signal” events are caused by:

– Channel disabled in the DVR,

– Wrong camera connected to the same channel label,

– Or a failed BNC termination.

IP/NVR systems (networked cameras)

– Confirm the camera’s IP address or discovery state:

– If DHCP is used, the CCTV camera may change IP after reboot.

– If static IP is used, confirm it matches the same subnet as your NVR.

– In the NVR/app, verify you added the camera correctly:

– The right protocol (RTSP, sometimes vendor-specific),

– The right credentials,

– And the right stream (main/substream, depending on what the NVR expects).

Intermittent signal: isolate degraded cable runs

If the CCTV camera works sometimes and fails other times:

– Re-check connectors and crimps.

– Swap the Ethernet cable (even if “it links”) because degraded copper runs can negotiate link but still fail streaming reliably.

DVR vs NVR vs IP Camera: what to verify fast

System type What “no signal” usually means Fastest verification step
DVR (coax/BNC) Wrong channel or broken coax termination Move the cable to a known-good channel and compare
NVR (IP cameras) Camera IP/credentials/RTSP stream mismatch Confirm camera is reachable on its discovered IP
Direct app viewing Network reachability or wrong device mapping Check “device offline” vs “no stream” in app status

Test With a Known-Good Setup (Fast Isolation)

If you want the quickest isolation method, temporarily swap either the port/power source or the cable with something you know works. This approach keeps changes small and identifies whether the fault is inside the CCTV camera, in the cabling run, or in the NVR/PoE switch port.

PoE power delivery follows IEEE 802.3 power-class negotiation; if the switch can’t supply enough power for the camera, the PD may not boot reliably (IEEE 802.3af, IEEE 802.3at).
When Ethernet is within the 100 m copper segment limit per IEEE 802.3, swapping a cable on a known-good port is a practical way to confirm whether the run is degraded.

Move the camera to a known working port (when possible)

– Connect the same CCTV camera to a different PoE port on a working PoE switch (or a working NVR PoE channel).

– If the camera streams normally elsewhere, the original port/power path is the problem.

If relocating isn’t possible, test the suspect cable

– Plug the suspect Ethernet/cable into a different camera input that you know is working.

– If the failure follows the cable, treat the run/termination as defective—replace it rather than continuing to tweak NVR/app settings.

From my experience maintaining small IP camera installs, this “swap method” usually resolves uncertainty fast—but —so document what you changed and when.

What Can Go Wrong (Common Mistakes and Edge Cases)

Even with the right checklist, a few common mistakes make CCTV camera fixes take longer than necessary. The big risks are mixing multiple changes, ignoring water/corrosion, and assuming the NVR/app is always “wrong.”

A practical troubleshooting framework is “isolate and verify”: change one variable at a time so you can identify the specific layer that restored the CCTV camera feed.
Outdoor corrosion can increase contact resistance at junction points, causing intermittent Ethernet link and streaming dropouts—especially where connectors are not fully sealed.

Changing both power and settings at once

– If you change the camera’s network settings while also swapping power/Cables, you’ll never know what fixed it.

– Follow a simple one-variable rule: change power OR cabling OR channel/IP mapping—then retest.

Ignoring weather/water issues

– Outdoor junction boxes and conduit entry points are classic failure points for CCTV camera connectivity.

– If a camera works briefly after you reseat a connector and then fails again later, treat it as a moisture/corrosion issue and repair/replace the affected connection.

Assuming the NVR/app is wrong

– It’s common for the CCTV camera to be fine but for the NVR/app to:

– Map the camera to the wrong channel,

– Use a stale IP address,

– Or point at the wrong stream profile.

Power budget surprises on PoE

– If the CCTV camera requires higher wattage than the PoE switch port can deliver, the camera may not boot.

– Check your PoE switch specs and confirm the camera’s required power class (again: use the exact models in your environment—).

Quick reference: common network ports used by CCTV cameras

This port map helps when an IP CCTV camera appears “offline” but physical cabling and power checks look fine.

📊 DATA

Network Ports That Commonly Affect “Offline/No Signal” IP CCTV Feeds

# Service (what it’s used for) Port Typical Protocol Impact on Feed Priority
1DHCP (address discovery for the camera)67/68UDP★★★★★High
2RTSP (video/control stream)554TCP★★★★★High
3HTTP (web admin/updates)80TCP★★★☆☆Low
4HTTPS (secure web admin/updates)443TCP★★★☆☆Low
5NTP (time sync for schedules/streams)123UDP★★☆☆☆Low
6SNMP (monitoring/telemetry)161/162UDP★☆☆☆☆Low
7WS-Discovery (ONVIF discovery mechanism)3702UDP★★★☆☆Low

Match firewall rules to the ports you actually use

If your CCTV camera is “offline” only when accessed remotely or across VLANs, check whether firewalls block DHCP, RTSP (554), or discovery traffic. In 2026 deployments, segmentation is more common, so this catches issues earlier than guessing.

Test With a Known-Good Setup (Fast Isolation)

If you want the quickest isolation method, temporarily swap either the port/power source or the cable with something you know works. This approach keeps changes small and identifies whether the fault is inside the CCTV camera, in the cabling run, or in the NVR/PoE switch port.

A common cause of “no signal” on IP CCTV cameras is a port-level power/capacity mismatch on PoE equipment; IEEE 802.3af and IEEE 802.3at define how power and classes are negotiated.
Swapping the suspect Ethernet cable to a confirmed-good camera input is a standard isolation technique because Ethernet copper segments are limited in length by IEEE 802.3.

Move the camera to a known working PoE port

Use a known-good PoE port and retest the CCTV camera video feed. If it works, you’ve proven the camera and its internal hardware can boot and stream.

If moving isn’t possible, test the suspect cable on a different input

This isolates the cable run or termination quality. If the feed fails on the second input too, you’ve narrowed the fault to the cabling location.

What Can Go Wrong (Common Mistakes and Edge Cases)

Even when you follow the checklist, a few common mistakes delay fixes—especially mixing multiple changes, overlooking weather/corrosion, and assuming the NVR/app is always at fault. These edge cases are common in modern 2026 installs because PoE, VLANs, and app-based viewing paths add more layers.

When troubleshooting, changing multiple variables at once removes causal clarity; the checklist approach (“power → boot → path”) is essentially a practical form of stepwise isolation.
PoE reliability depends on meeting the IEEE power-class budget; undersupplying a CCTV camera can stop boot or trigger repeated resets (IEEE 802.3af, IEEE 802.3at).

– Changing both power and settings at once: it makes it harder to know what fixed (or broke) things—change one variable at a time.

– Ignoring weather/water issues: outdoor junction boxes can corrode connectors; you may need to reseat and protect connections.

– Assuming the NVR/app is “wrong”: sometimes the camera is fine but the channel mapping, IP config, or port assignment is not.

– Power budget surprises on PoE: a port may not supply enough power to start a higher-draw camera; check your switch specs ().

Verdict: What’s Worth Doing First (and When to Stop)

Start with power, cabling, port/channel, and basic reachability—those checks resolve most “not working” cases quickly and safely. Avoid deep configuration changes (firmware resets, network rewiring, advanced streaming settings) until you’ve confirmed the CCTV camera boots and the video path is consistent.

If an IP CCTV camera feed is blocked, RTSP traffic on port 554 (per RFC 2326) is a frequent culprit—especially with firewalls or restrictive VLAN policies.
DHCP address assignment uses UDP 67/68 (per RFC 2131); if DHCP fails, the CCTV camera can come “online” electrically but still appear offline to the NVR/app.

Skip DIY troubleshooting and contact a qualified installer if you suspect internal hardware damage (burnt power components, severe corrosion, repeated short-cycling), especially after confirming power and cabling are good. Also skip advanced rewiring if you can’t verify waterproofing and grounding practices around outdoor runs.

Quick Scan Checklist (Save This)

– Power: power adapter/PoE port confirmed active

– Connections: connectors reseated, no damaged or corroded wiring

– Boot/status: camera LEDs show signs of starting

– Video path: correct channel on DVR/NVR or correct IP feed on app

– Isolation test: try known-good cable/port (or temporarily relocate camera)

– One change at a time: don’t mix multiple updates during testing

If your CCTV camera uses Ethernet, keep the copper run within the practical 100 m segment limit described by IEEE 802.3—especially for troubleshooting intermittent “offline” behavior.
For PoE setups, validate power-class capability using IEEE PoE specifications (IEEE 802.3af, IEEE 802.3at) before concluding the CCTV camera is defective.

Sources

– Manufacturer documentation for your specific CCTV camera model (power/LED behavior, PoE requirements, network setup, and reset procedure): .

– Manufacturer documentation for your NVR/DVR (channel mapping, IP discovery/add-device workflow, troubleshooting “no signal/offline” status): .

– PoE switch documentation (port power limits and PoE mode behavior): .

– PoE power specifications: IEEE 802.3af-2003 and IEEE 802.3at.

– Ethernet segment length (copper link limits): IEEE 802.3.

– RTSP standard port: RFC 2326.

– DHCP ports: RFC 2131.

If you apply the power → boot → path sequence, you’ll usually fix a non-working CCTV camera without guesswork. In 2026-style installs with PoE, VLANs, and apps, that stepwise isolation is also the safest way to avoid chasing settings while the camera never fully starts.

Frequently Asked Questions

What should I check first if my CCTV camera is not working?

Start with the simplest causes: confirm power to the CCTV camera and check the power adapter or PoE switch port. Then inspect the camera lens and housing for obstructions, dust, or moisture, and verify the network/VMS connection if it’s an IP camera. Finally, check the DVR/NVR input channel and confirm the correct camera is selected in the monitor.

How do I fix a CCTV camera that has no signal on my monitor?

For analog CCTV systems, verify the BNC connection and replace the coax cable if you find loose or damaged wiring. For IP CCTV cameras, confirm the correct IP address, subnet settings, and that the camera is online in your NVR/router. Also reboot the camera, NVR/DVR, and—if applicable—the PoE switch to clear common connection faults.

Why is my CCTV camera not recording or showing a blank screen?

A blank screen or no recording is often caused by incorrect recording settings, a disabled channel, or storage issues on the DVR/NVR. Check whether the camera is assigned to the right channel/profile and confirm that motion detection, schedule recording, or continuous recording is enabled. If storage errors are present (full drive, corrupted HDD, or wrong permissions), repair or replace the hard drive and then re-test the CCTV recording system.

Which troubleshooting steps can I do for an IP CCTV camera with no internet connection?

Verify the IP CCTV camera’s network settings by using the manufacturer’s app/software or checking DHCP versus static IP configuration. Confirm that the Ethernet cable is good (swap with a known working cable) and that the PoE injector/switch provides proper voltage. If the camera still won’t connect, check firewall/NAT settings, RTSP/ONVIF compatibility, and test connectivity by pinging the camera IP on the same network.

What is the best way to test whether the CCTV camera or the wiring is faulty?

Use a quick isolation test: connect the camera to a different channel on the DVR/NVR or swap in a known working camera to determine whether the fault follows the camera or the cabling. You can also use a multimeter or cable tester to check for open circuits, shorts, or power issues in CCTV wiring. Once you confirm the source, repair or replace only the faulty component to restore reliable CCTV footage.

📅 Last Updated: October 26, 2026 | Topic: How to fix a CCTV camera that is not working? | Content verified for accuracy and freshness.


References

  1. Closed-circuit television
  2. https://www.ncsc.gov.uk/guidance/cctv
  3. video surveillance troubleshooting – Search Results – PubMed
  4. Troubleshooting | Axis Communications
  5. https://www.hikvision.com/en/support/knowledge-base/
  6. https://scholar.google.com/scholar?q=IP+CCTV+camera+troubleshooting+no+signal+no+video  Google Scholar
  7. https://scholar.google.com/scholar?q=CCTV+camera+not+working+power+PoE+network+troubleshooting  Google Scholar
  8. https://scholar.google.com/scholar?q=video+surveillance+system+troubleshooting+NVR+camera+failures  Google Scholar

John Devor
John Devor
Articles: 399

Leave a Reply

Your email address will not be published. Required fields are marked *