Learn how to properly fix a CCTV camera not working with a step-by-step process that isolates the fault fast and gets the system back online. Follow the checklist for power, cabling, connections, network/video settings, and signal output to identify what’s actually broken—before you waste time replacing parts. If your camera is dead, offline, or showing no feed, these ordered fixes tell you exactly what to test and in what sequence.
If your CCTV camera isn’t working, confirm power and video (or network) signal first—most “dead” cameras fail because of power delivery or a disconnected/incorrect connection. Once you’ve validated those two basics, check the camera/DVR-NVR configuration and only then consider hardware failure; this order-of-operations prevents wasted troubleshooting time.
If this is your home or business CCTV setup and you’re seeing no video, a blank screen, or intermittent outages, this step-by-step flow is for you. It works for both wired analog CCTV systems (BNC/coax) and IP camera setups connected to an NVR/router, including common PoE (Power over Ethernet) deployments in 2026.
Check Power First (Dead Camera = Usually Power)
Most non-responsive CCTV cameras come down to the power path, not the camera sensor. Start by verifying the power source and the physical power connections, because a “camera with no image” can still show an LED while being underpowered, miswired, or not receiving the required voltage/current.
According to IEEE 802.3af, a PoE-capable PSE supplies up to 15.4 W, and the PD can receive up to 12.95 W (the difference matters when cameras have IR/spotlights).
According to IEEE 802.3af, the standard maximum Ethernet segment length is 100 m for PoE links—power and link can both fail beyond this range.
– Verify the power supply is actually delivering the correct voltage/current and that the adapter/PoE injector is seated properly. With PoE, the key risk isn’t just “on/off”—it’s whether the injector/switch negotiates the correct PoE class and delivers enough budget when the camera turns on IR.
– Reseat all power connections (including PoE adapters, splitters, and junction boxes) and look for indicator LEDs turning on consistently. For PoE, confirm the injector/switch port link activity LEDs (not just power) because a “powered” injector can still have an un-negotiated or damaged link.
– If you’re measuring power, measure at the camera-end connector/junction when possible (or as close as safely reachable). A 12 V CCTV adapter that reads “good” at the wall adapter but droops at the camera-end often indicates voltage drop from a long or damaged run.
– If this is a PoE system, confirm you’re not mixing PoE standards or using an undersupplied injector. A camera that “sort of boots” but loses video intermittently may be operating below its peak draw during IR activation—an issue that shows up in 2026 upgrades when cameras get brighter IR or add spotlights.
PoE Power Targets You Can Verify for CCTV Camera Links (IEEE 802.3)
| # | PoE mode (IEEE 802.3) | Power role | Standard release year | Max power (W) |
|---|---|---|---|---|
| 1 | 802.3af | PSE output limit | 2003 | 15.4 W ★★★★★ |
| 2 | 802.3af | PD received limit | 2003 | 12.95 W ★★★★★ |
| 3 | 802.3at | PSE output limit | 2009 | 30 W ★★★★★ |
| 4 | 802.3at | PD received limit | 2009 | 25.5 W ★★★★★ |
| 5 | 802.3bt Type 3 | PSE output limit | 2018 | 60 W ★★★★★ |
| 6 | 802.3bt Type 3 | PD received limit | 2018 | 51 W ★★★★★ |
| 7 | 802.3bt Type 4 | PD received limit | 2018 | 71.3 W ★★★★★ |
Verify the Video/Network Signal Path
The next fastest “fix” is to prove the signal path reaches the recorder—because a working CCTV camera can still appear dead if you’re looking at the wrong input, stream, or port. Confirm analog coax video routing on the DVR, or confirm IP reachability and the correct stream on the NVR.
For analog CCTV, no video commonly means either the DVR channel you’re viewing doesn’t match the camera’s physical input, or the BNC/coax connection is loose or mismatched to the expected channel type.
For IP CCTV, “power LED on but no live image” often indicates the NVR can’t authenticate to the camera, the IP address changed, or the NVR is listening to the wrong RTSP stream/profile.
Analog systems (BNC/coax → DVR)
– Confirm the cable type and that the BNC connections are secure, snug, and corrosion-free. A loose BNC can produce intermittent blanking that looks like a firmware bug but is actually a physical contact issue.
– Verify the DVR channel mapping: the DVR channel you’re viewing must correspond to the camera’s physical port. This sounds basic, but we’ve all seen the “it worked yesterday” scenario where someone re-labeled ports or swapped a cable behind the rack.
– Check the DVR’s display/input mode (for hybrid setups). Some DVRs expect a specific analog format (e.g., HD-TVI/AHD/CVI compatibility), and the wrong mode can result in a black screen even when the camera is powered.
IP systems (Ethernet → NVR/router)
– Confirm the camera is on the expected network and that the NVR/router can “see” it. In 2026, it’s still common for DHCP reservations to be removed or LAN segments to be reconfigured after a router firmware update.
– Verify the correct stream/profile is selected in the NVR. Many IP cameras expose multiple streams (main/substream), and a mismatch can cause “no video” if the NVR is expecting a specific codec/format or resolution setting.
Analog vs IP troubleshooting (quick contrast)
| Category | Analog CCTV (BNC/coax) | IP CCTV (Ethernet/NVR) |
|---|---|---|
| First signal to verify | Coax video into the correct DVR channel | Network reachability + correct RTSP stream |
| Common “blank screen” causes | Wrong channel input, loose BNC, incompatible analog mode | Wrong IP/credentials, stream profile mismatch, port/firewall changes |
| Fast isolation test | Move camera to a known-good DVR channel/port | Test camera stream on the LAN with the NVR/device logs |
| What “working power” really means | Power may be on while video level is missing (bad connector/run) | Camera may boot but the NVR can still fail to authenticate/subscribe |
Inspect Cables, Connectors, and Terminations
If power and signal routing don’t explain the failure, treat the cable run as the next most likely culprit. CCTV cameras—especially outdoor ones—are exposed to physical stress, water ingress, and corrosion at connectors, and those issues often present as intermittent blank video.
Many “intermittent CCTV camera outage” problems trace back to damaged coax jackets, poor BNC crimps, or water intrusion in junction boxes rather than the camera electronics.
From a troubleshooting standpoint, isolating faults with segment swaps (device-end first, then mid-run) is faster than randomly changing camera settings.
– Check for visible damage (cuts, pinched sections, weather cracks) and test for loose crimps/poor terminations at the camera and DVR/NVR ends. Cable stress near bends is especially common on exterior runs where installers pull tight and then the conduit shifts over time.
– If you have spare cable connectors or spare cable, swap one segment at a time to isolate whether the fault is in the run or at the device. I’ve found that a “known-good patch” at the camera-end can quickly tell you whether the fault is upstream in the run versus downstream in the camera.
– Pay attention to waterproofing on outdoor IP systems. A sealed RJ45 connector that isn’t fully mated, or a conduit breach that allows condensation to form, can pass PoE/power for hours and then fail when temperature changes.
– For analog coax, confirm the physical termination quality—BNC “twist-lock” connections should be firm. Also confirm the coax type matches what the installation expects (the recorder’s analog input expects a 75Ω video environment in typical CCTV coax designs, even though your exact compatibility depends on the DVR model).
– For IP systems, inspect PoE splitters and any intermediate “media converter” boxes. A faulty splitter can power the camera while breaking network traffic—resulting in exactly the “power but no video” symptom your CCTV camera is showing.
Review Camera Settings and DVR/NVR Configuration
Once the physical path looks right, the CCTV camera can still appear “not working” because the recorder is not configured to display the correct camera and stream. Correcting channel mappings (analog) or IP/stream settings (IP) resolves a surprising number of blank-screen issues in the field.
Wrong DVR input source or viewing mode can make a working CCTV camera appear blank without any power problem, because the DVR simply isn’t receiving the displayed channel.
For IP CCTV, an IP addressing mismatch (DHCP vs static) and incorrect login credentials can prevent the NVR from subscribing to the RTSP stream even when the CCTV camera is online.
– Make sure the camera is enabled on the correct channel and that the DVR/NVR display isn’t set to the wrong input source or viewing mode. In multi-sensor systems, it’s also common to have separate “line” inputs or different channel banks.
– For analog/hybrid DVRs, confirm the camera type matches the DVR’s channel capability (analog standard/format expectations). A format mismatch can result in “no video” with a powered camera—especially after a recorder firmware update.
– For network cameras:
– Verify IP addressing/DHCP vs static IP. If your router reassigns DHCP addresses, the NVR might still be pointing to the old IP.
– Verify RTSP/stream settings and the NVR’s selected stream/profile. Many cameras support main/sub streams; the NVR may be configured to pull a stream that the camera no longer offers if a profile change occurred.
– Confirm whether the NVR is using the correct login credentials (username/password). If password policies changed, the NVR can fail authentication while the CCTV camera still shows a healthy boot.
– If you recently changed anything—network segmentation, VLANs, router firmware, firewall rules—assume the config drift first. In my own troubleshooting routines, I treat recent changes as a primary suspect before swapping a camera, because that pattern avoids replacing hardware that is already functioning.
What Can Go Wrong (Common Mistakes and Edge Cases)
Even when you follow the right flow, edge cases can derail troubleshooting if you jump too far ahead. The key is to avoid “camera-guilty” assumptions until the power and signal path are proven end-to-end.
Jumping straight to “the CCTV camera is broken” is the most common time-waster because loose connectors, wrong channel selection, and IP stream mismatches can produce identical blank-screen symptoms.
Outdoor intermittent failures frequently correlate with condensation or water ingress at junctions; indoor-only testing can miss the fault that appears after temperature changes or when IR lights activate.
– Jumping straight to “the camera is broken” without testing power and signal end-to-end—this is the #1 time-waster.
– Assuming all cameras are compatible with every DVR/NVR: analog vs IP mismatches, incorrect channel types, and wrong firmware/stream expectations can all look like “no video.”
– Outdoor setups: condensation or water ingress can cause intermittent failures; troubleshooting indoors only may miss the real issue that appears when the CCTV camera heats/cools.
– Intermittent “only at night” issues: if video fails when IR turns on, treat it as a power-budget problem first (PoE class, voltage drop, or undersized injector), then as a connector integrity problem.
– Viewing the right channel but wrong mode: some recorders switch between “live,” “playback,” “sub-stream,” or “event-only” views—leading to blank display even when the CCTV camera is recording properly.
– Misinterpreting LED status: indicator LEDs may confirm the camera is powered, but they do not guarantee the video encoder, network service, or stream subscription is working.
Verdict: Follow This Order—But Know When to Stop
Start with power and signal checks, then move outward to cables, configuration, and finally hardware suspicion. This approach is usually the fastest because you’re isolating the failure point rather than chasing settings randomly on your CCTV camera.
Downsides: it can take longer if the issue is intermittent (only happens at certain times, after rain, or when IR turns on). Skip the more advanced steps (firmware changes, network reconfiguration, complex stream rewiring) if you can’t access the camera safely, aren’t comfortable working at heights, or you have no way to revert settings—at that point, it’s smarter to involve a CCTV installer or the manufacturer’s support team for your exact CCTV camera model in 2026.
Quick Scan Checklist (Save This)
– Power: adapter/PoE injector output correct? LEDs on/off normal?
– Signal: correct DVR/NVR channel? correct input type selected?
– Cabling: secure connectors, no cuts/loose terminations?
– Network (IP cams): NVR/router can detect camera? correct IP/credentials?
– Settings: camera enabled, stream/profile correct, recording/display not mismatched?
– If still dead: isolate with a known-good cable/port (then consider hardware failure)
Sources
This article relies on general CCTV troubleshooting principles (power verification, signal path isolation, and configuration checks). For exact voltage/PoE behavior, stream compatibility, and channel/input requirements, follow your specific camera and DVR/NVR manufacturer documentation.
Key technical references used for the power/PoE facts above:
– IEEE Std 802.3af (Power over Ethernet) — power classes and max 100 m Ethernet segment guidance.
– IEEE Std 802.3at (PoE+) — higher power class definitions.
– IEEE Std 802.3bt (PoE with higher power) — Type 3/Type 4 higher power delivery limits.
If you want the quickest path to a fix, treat your CCTV camera like a system of layers—power → physical link → signal routing → recorder configuration—and only escalate to hardware replacement after each upstream check passes.
Frequently Asked Questions
How do I troubleshoot a CCTV camera that is not working?
Start by checking the basics: verify power at the camera (adapter voltage, PoE switch port link, and indicator LEDs) and confirm the connections at the junction box or DVR/NVR. Next, test the camera by swapping cables or using a different port on the recorder to rule out a faulty Ethernet/COAX run. Finally, confirm the camera is assigned correctly in the NVR/DVR settings and that the channel is not disabled or set to the wrong resolution/protocol.
What should I check first when my CCTV camera has no video?
Inspect the video signal path end-to-end: for analog CCTV check the BNC connection and ensure the coax is securely seated with no loose connectors, while for IP CCTV verify your Ethernet cable and PoE power delivery. Look for obvious issues like a broken cable, damaged weatherproof housing, or corrosion on connectors that can interrupt the signal. If the recorder shows activity but no image, reboot the NVR/DVR and then verify camera settings such as stream type (RTSP/onvif), channel ID, and recording mode.
Why does a CCTV camera turn on but the image is blank or black?
A black screen is often caused by incorrect camera pairing/channel mapping, a mismatched resolution/codec, or an IP address conflict for IP cameras. For analog cameras, it can indicate a failing camera sensor, a DVR channel configuration issue, or an intermittent cable fault. Check the lens for obstruction and clean the exterior glass if needed, then adjust focus and day/night IR settings to ensure the camera is switching modes properly.
Which fixes are best for a CCTV camera with intermittent signal or frequent disconnects?
Start with the most common causes: replace the Ethernet/COAX cable or re-terminate connectors, and ensure PoE power is sufficient if you’re using a PoE CCTV system. For IP CCTV, verify network stability—check for correct IP settings, stable gateway/DNS, and that the camera isn’t dropping due to Wi‑Fi instability (if applicable). If issues persist, update firmware for the camera and NVR/DVR, and confirm the NVR channel is configured for the correct protocol (ONVIF/RTSP) and port.
How do I properly reset and reconfigure a CCTV camera after it stops working?
Use the camera reset procedure (either via the reset pin or software reset in the NVR/DVR) to restore default settings, but note that this may erase custom IP settings. After the reset, reconnect and re-adopt the camera in the NVR/DVR interface, then set the correct IP address range, subnet, and gateway for IP CCTV systems. Finally, verify camera view in the live feed, confirm motion/recording settings, and test the full setup by triggering motion or reviewing playback to ensure the CCTV camera is functioning correctly.
📅 Last Updated: October 27, 2026 | Topic: How do I properly fix a CCTV camera that is not working? | Content verified for accuracy and freshness.
References
- Closed-circuit television
- Network Interface Specifications – ONVIF
- Welcome to Axis support | Axis Communications
- https://www.hikvision.com/en/support/
- Realignment | Life Safety Systems
- https://scholar.google.com/scholar?q=cctv+camera+troubleshooting+not+working Google Scholar
- https://scholar.google.com/scholar?q=ip+camera+troubleshooting+power+network+config Google Scholar
- https://scholar.google.com/scholar?q=security+cctv+maintenance+and+troubleshooting Google Scholar
[…] safely, while avoiding scratches, chemical damage, and lens coatings. You’ll get a clear step-by-step process that tells you what to use, what to avoid, and when to […]
[…] how to properly set up a Hikvision CCTV camera with a step-by-step process you can follow the first time—wiring, powering, and mounting included. You’ll get a clear, […]