Support

How to Find the IP Address of a CCTV Camera

If you need the IP address of a CCTV camera, the cleanest path depends on how that camera is connected. A camera plugged into an NVR PoE port is not the same as a camera living on the wider LAN through a normal switch or router.

CCTV Networking Support

Summary

Use this guide when you need to locate a camera on the network for setup, login, password recovery context or troubleshooting.

Applies to

IP cameras on NVR PoE ports
IP cameras on standard switches and routers
Mixed-brand CCTV networking jobs

Difficulty and time

Difficulty: Moderate

Estimated time: 10 to 30 minutes

What you will need

Access to the NVR or router if possible
Camera model or brand where known
PC or laptop for discovery tools if needed
One known cable path

What this guide covers

The difference between NVR PoE and normal LAN cameras
Using the NVR camera management page
Using the router DHCP list or discovery tools
How to test directly without creating IP conflicts

The mistake we often see is people scanning the wrong network. If the camera is sitting behind an NVR PoE interface, it may not appear where they expect in the router list.

So the first real question is: where is the camera plugged in?

Before you start

Work out whether the camera is plugged into the NVR directly or into a normal switch.
Note the brand if possible so you know which discovery tool may help.
Do not assign random new IPs until you know what network the camera is already on.
If the site is live, avoid creating conflicts on the production network.

Step 1: Check the NVR camera management page first

If the camera is connected to an NVR, the recorder is often the fastest place to find it.

Open the NVR camera-management or channel-management page.
Look for the camera IP, channel status and activation state.
Remember that cameras on an NVR PoE backplane may sit on a different subnet from the main LAN.
If the camera is visible there, record the IP before making any changes.

Step 2: Check the router DHCP list if the camera is on the LAN

If the camera is on a normal switch or directly on the router LAN, the DHCP client list is often a good next step.

Open the router DHCP or client list.
Look for the camera hostname, MAC prefix or unknown device that appeared at install time.
If the site uses reserved IPs, check those reservations too.
Do not assume every camera advertises a friendly name.

Step 3: Use discovery tools or a network scan where appropriate

Manufacturer tools and safe network scanning can help when the NVR or router view is not enough.

Use the brand discovery tool where relevant.
If needed, use a network scanner on the correct subnet, not a random PC on the wrong network.
On mixed-brand jobs, ONVIF visibility does not always tell you the login path or exact configuration state.
If the camera was never activated properly, discovery may find it but normal login may still fail.

Step 4: Direct test path if the network is still unclear

If you still cannot find the camera, isolate the path rather than guessing across the live site.

Test the camera on a known short patch lead and known-good PoE source if possible.
Put your laptop on the correct subnet for direct discovery where appropriate.
Keep notes of any temporary IP changes so the site can be returned cleanly.
Do not create IP conflicts by assigning addresses blindly.

Worked example

Camera not visible in the router list

Situation: A customer could not find a camera IP in the modem because the camera was actually sitting behind the NVR PoE ports.

Solution used: The installer checked the NVR camera-management page first and found the internal camera subnet there.

Why this was chosen: The router was never the right place for that camera path.

Installation notes: This is one of the most common reasons people think the camera is "missing" on the network.

Common mistakes

Scanning the wrong subnet.
Forgetting that NVR PoE ports may use an internal camera network.
Assigning new IPs before documenting the old state.
Assuming discovery means the password and activation path are also correct.

Related support guides

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.