Quick answer: Read the exact channel message and check its meaning for that recorder and firmware. A missing Ethernet link points you toward physical connection and power checks; an offline channel can also involve addressing, access or configuration. Record the current state, protect required recording and change one variable at a time. A lit LED or one successful swap does not clear the entire cable, PoE supply or camera.
On this page
No Link vs Offline: which layer is failing?
Start with the recorder message, port diagnostics and camera identity. Labels and the conditions behind them vary by model and firmware; “offline” is not a universal guarantee that the physical link is healthy. Use the evidence to choose the next check rather than assigning a cause from a single word.
| Observed result | Possible area | Next controlled check |
|---|---|---|
| No reported link or dark indicator | Connection, power, port policy, device or indicator behavior | Check model-specific indicator meaning, power and link diagnostics |
| Intermittent link or reboot | Cable/termination, power/heat, negotiation or device fault | Correlate logs and actual load; test the permitted path and PoE |
| Link present but channel offline | Address/mapping, credentials, protocol, permissions, capacity or remaining physical errors | Compare actual device identity and channel error with network and application records |
| Explicit authentication error | Stored credentials, account permissions, lockout or supported method | Confirm the approved account and integration settings without repeated guesses |
Channel capacity and physical PoE ports are different limits. CS-N110 P8H-AI lists 10 video channels and eight PoE ports; CS-N220 P16H-AI lists 20 and 16. More channels than ports means an additional network/power path may be needed, but does not prove that channel number 9 or 17 is permanently tied to one topology. Confirm the actual channel-to-device/port mapping and supported recorder configuration.
How do you run the swap test on port and cable?
A controlled comparison can narrow the fault, but only for the load and conditions tested. Obtain permission for interruption, preserve the required recording and record the original port, device, credentials and mapping. Check compatible power and a safe connection before moving anything; keep other cameras and the PoE budget in view.
- Use a documented compatible test camera and short known-good cable on the suspect port, within its approved power policy. Record link, power and relevant diagnostics.
- Compare the suspect camera on a permitted known-good compatible path. A successful short-cable test narrows the problem but does not prove the camera works at its maximum/night load.
- Test the field path with appropriate cable and PoE instruments and the required device/load. Compare termination, length, losses, environment and actual link errors.
- Restore the approved mapping and verify live view, required events and recorded playback. Record what the tests establish and what remains untested.
Read indicators according to the exact hardware instructions and corroborate them with diagnostics. A steady light does not certify cable performance, adequate PoE at peak load or an error-free link. Avoid treating “camera fails on every test” as automatic RMA approval: record the controlled tests and let support confirm the next service step.
What does the PoE check tell you?
A device without adequate power may not establish or retain Ethernet link. Test power type/class, negotiation and delivered power under the actual load using suitable instruments. A passive voltage indication alone does not establish that all pairs, data performance, PoE negotiation and device operation are correct. The PoE camera troubleshooting guide covers the controlled power checks.
- If source and camera-end results differ, inspect and test the whole permitted path, including connections, cable and source policy. Do not automatically reterminate the far end before locating the fault.
- Compare the camera’s full power requirements with the individual port and the shared available budget. Zero current can have more than one cause; do not immediately condemn the camera.
- Correlate a night failure with the actual lighting, heater, environment and load. A higher load is one possibility, not proof that the last illuminator to turn on is the failing port.
- For a conventional twisted-pair Ethernet channel, 100 m is a channel design limit, not a universal long-distance PoE guarantee. Verify cable topology, patch cords, temperature and power losses. CS-H1108PLS lists 100 m standard / 250 m Extend Mode; confirm supported speed, cable, power and load before selecting it.
- Confirm the required standards-compliant cable and local installation requirements with the responsible designer. Cable material, resistance or damage needs actual examination/test; do not label a cable from a symptom alone.
Use PoE camera not working: budget, cable length and switch class for the power checks, and PoE max distance and PoE extenders for the design options. CS-H1108PLS lists -20°C to +55°C and a non-condensing environment; enclosure, actual ambient and other equipment limits still need checking. An external switch must also fit the approved network design.
Link is up but the camera is offline: IP and credentials
A reported link is the starting point for further checks, not permission to rule out cable or power. Read errors, speed and load alongside addressing and authentication. Confirm the actual recorder camera/uplink architecture and supported discovery/access method; the number of PoE ports does not establish its DHCP or subnet behavior.
The camera kept a static address from somewhere else
Compare the configured channel target with the actual device IP, mask, gateway and identity. A bench or replacement camera may retain an old address. Use the supported discovery/configuration tool on an authorized path and coordinate changes with IT; do not bridge an isolated camera network or change a production address merely to make discovery work.
Two cameras share an address
Duplicate IPv4 addressing can cause missing or intermittent access, but symptoms and a changed MAC are not conclusive by themselves. Corroborate identity, DHCP/neighbor evidence and the approved topology before a controlled correction. IP address conflicts between cameras covers that process.
The channel holds the wrong credential
Compare the channel’s approved stored credentials and supported authentication method with the camera and any lockout/account state. Correct a confirmed mismatch through the authorized process; avoid repeated guesses or an unnecessary reset. How to reset a CASE camera or NVR password covers recovery when it is genuinely needed.
The channel is simply pointing at nothing
A channel may point to an obsolete or incorrect address or have the wrong protocol/settings. Confirm actual device identity and supported integration, then update the approved mapping. Discovery alone is not acceptance: verify recording and playback. NVR not showing cameras: check IP addresses, DHCP and PoE first provides the addressing workflow.
Channels, PoE ports and bandwidth: the printed limits that look like faults
Review channel capacity, PoE power, per-port network capability and aggregate recording/output/decode/AI limits separately. A capacity mismatch may prevent the required operation, but it is not diagnosed from a channel label alone. Use the exact revision’s definitions and current stream settings.
| Catalog model | Video channels / PoE ports | Bandwidth rows | Design note |
|---|---|---|---|
| CS-N105 P4H-AI | 5 / 4 | 100 Mbps in / 80 Mbps out | 4+1 RJ45 10/100 Mbps |
| CS-N110 P8H-AI | 10 / 8 | 100 Mbps in / 80 Mbps out | 8+1 RJ45 10/100 Mbps |
| CS-N220 P16H-AI | 20 / 16 | 160 in (AI on120) / 80 out Mbps | Gigabit uplink;16×100 Mbps PoE |
| CS-N440 P16-H-AI (catalog spelling) | 40 / 16 | 400/400; AI on200/200 Mbps | Confirm ordering identity against actual P16H-AI revision before quoting |
Confirm how any external camera reaches the recorder and receives compatible power; do not assume channel numbers map permanently to built-in ports or every camera belongs on the customer LAN. Budget required aggregate streams, events and clients with headroom and test the actual load. A 100 Mbps port is not proof that any camera stream, codec or configuration fits, and link presence does not exclude intermittent physical errors. The IP camera bandwidth calculator supports that aggregate traffic assessment.
What to tell your customer
We will record the channel error, compare the actual device, port and cable/power path, and check the channel settings. After an approved correction we will test the required recording and playback and document the result. If support or RMA is needed, we will provide the evidence rather than assume a failed test guarantees replacement.
FAQ
What is the difference between No Link and Offline on an NVR?
A missing Ethernet link directs physical/power checks; an offline channel can have physical, addressing, authentication or other application causes. Confirm the exact model/firmware meaning and corroborating diagnostics. A label alone cannot identify the faulty part.
Why does a camera show No Link only at night?
Lighting, heaters or environment may change the load, but a night-only failure needs correlated logs and actual power/link tests. Check source/port/shared budget, cable losses, compatible power and the device under relevant conditions. Any redistribution or switch change needs an approved design and recording test.
Can I use a PoE extender or an extend-mode switch on an NVR PoE port?
Use only a documented compatible extender or PoE switch arrangement after confirming source/PD compatibility, cable, speed and power under load. CS-H1108PLS’s 250 m Extend Mode row is not a universal recorder-port extension guarantee. Agree the actual external network and recorder integration before changing the path.
Channel 9 on my 10-channel NVR is offline. What should I check?
Confirm the actual mapping and power/network path. CS-N110 P8H-AI lists 10 video channels and eight PoE ports, but the channel label alone does not tell you which port or network a device must use. Check identity, address, approved credentials and supported configuration, then recorded playback.
The link LED is steady but the channel says offline. Is the cable still a suspect?
Yes. A link indicator does not certify the cable or guarantee adequate power under all loads. Check negotiated state, errors and actual-load behavior while also checking address, identity, account and integration settings. Use the evidence to narrow the fault; do not infer an old static address without confirming it.
References
- Anabon: model and revision documents
- Anabon Technical Support
- Fluke Networks: channel, permanent link and MPTL distinctions
- Ethernet Alliance: PoE source/device power classes
