This Remotely Access IP Camera on Different Subnet is a process is typically used when cameras cannot be detected by standard applications because their IP addresses (e.g., 192.168.254.x) differ significantly from the NVR’s address (e.g., 10.0.21.81).
HOW IS THE PROCESS?
This method is an option if you don’t have a technician on site. Sometimes it works, sometimes it doesn’t. First, we need to locate the cameras. If we see that the cameras have a very different IP address from the NVR, for example NVR: 10.0.21.81 and Camera 192.168.254.1, the applications we use, such as SADP or another application, will not find these IP addresses. Therefore, we must access the NVR and verify the IP address of the cameras in this example. Since they have a completely different IP address from that of the NVR, even if they are connected to the same device, they will not be detected.
We must follow the process shown in the image:
We must use the command The command “netsh routing ip enable” is used to enable IP Security Camera routing in Windows 10.
Then we must use the netsh command, which is used to configure and monitor Windows-based computers. In this case, we must name the ipv4 so that it shows us the available links.
Once we have identified the locations (IDX), we will display the link that says Ethernet and select its IDX, which, as the image shows, is port 9 in our case. To do this, we use the command: netsh interface ipv4 set interface 9 forwarding=Enabled.
This will allow you to select and activate this card for use or modification.
Here we will briefly show you how to teach the card that there is a link via the public IP where the cameras are located, which in our case, as we gave in the example, would be 192.168.254.0. We set it as 0 so that this is its connection.
Let’s run the command: route add 192.168.254.0 mask 255.255.255.0 10.0.20.81 (the latter IP is the IP of the NVR we want to access to add the IP mentioned above).
When you run this command, it will create the link via the IP address, which will allow us to access the IP address of the cameras without generating an error, and we will be able to restart the camera and/or activate ANTI-FICKER.
WHY IS THIS REMOTELY ACCESS IP CAMERA ON DIFFERENT SUBNET PROCESS MPORTANT?
Accessing IP security cameras on a different subnet is a critical technique for managing complex security networks, especially when physical access to the site is restricted. This configuration serves several vital functions in both security and operational efficiency.
Enables Remote Maintenance
The most immediate benefit is that you can manage hardware without a technician on-site. This configuration allows you to:
- Fix detection errors: Standard applications often fail to find cameras if their IP addresses differ significantly from the NVR.
- Control camera functions: You can remotely restart cameras or activate specific features like ANTI-FLICKER.
- Modify settings: The process lets you select and activate network cards for modification or use
Bridges Mismatched IP Ranges
In many setups, cameras and NVRs have completely different IP addresses. For example, an NVR might use 10.0.21.81 while the cameras use 192.168.254.1.
- This manual process “teaches” the computer’s network card that a link exists between these two separate zones.
- By creating a link via the IP address, you prevent errors when attempting to access the cameras.
Provides a Reliable Alternative
Standard automated tools often miss cameras on different subnets.
- This manual configuration provides a necessary “option” for administrators when automated tools fail.
- Even when devices connect to the same physical hardware, they remain invisible to each other without this specific routing.
