Synology Surveillance Station cannot find camera in different subnet

S

shawnwong.au

n3wb
Oct 3, 2024
6
0
Australia
First of all, thanks for reading this thread.

Things started by Im getting thousands of useless notification by motion detection since my cameras are not capable to do AI stuffs and few days ago I browse on reddit saying Synology Surveillance Station can do some AI work to analyze the image and send REAL notifications.

But I encounter some problem during setting up Synology Surveillance Station. It cant find any cameras but only the NVR....
Here's my device.

DevicesModelIP Address
Cameras x4Dahua DH-P40A2-PV10.1.1.65-68
NVRDahua DH-NVR1104HC-P-HDS4192.168.50.252
NASSynology 416play192.168.50.18
RouterAsus TUFAX3000192.168.50.1

NVR & NAS are connected to Router. Cameras are connected to NVR having IP assigned automatically by NVR from 10.1.1.65-68.

Camera are accessible through Web GUI (192.168.50.252:1896) of NVR by pressing the IE icon, but can not be accessible by typing in the IP address with port(192.168.50.252:10081-10084).

Is there any workaround to make those cameras visible in Synology Surveillance Station? The only thing visible on there is my NVR with the IP 192.168.50.252:1896.

After spending days googling, I think those camera are not visible there because the devices are in different subnet. However I find it is quite difficult to me to make it work:|

One of my friends suggested that I should just simply buy a POE switch, connect it to NAS and avoid messing around the network. But before buying another device (save money), I want to give it a shot here and learn how to solve this problem. Thank you guys.
 
First, I don't use a POE NVR or NAS, I use Blue Iris VMS on a PC.

But if you put a gun to my head and insisted on my thoughts, I'd do as your friend suggested: put the cams on a POE switch, assign them all unique, static IP's on the same 192.168.50.XXX subnet as the NVR's LAN (but outside of the router's DHCP pool if there is a router) and add them to the NVR and to the NAS. A good Netgear 5 port POE switch with 4 POE+ ports is less than $65, A TP-LINK with same specs, $50.....less than lunch for 4 at a fast food chain restaurant. :cool:
 
Last edited:
  • Like
Reactions: looney2ns
In many nvrs you have the option to bridge the Poe ports to the NVR wan port.
Not sure if yours does but it probably can.

What this will do is make the Poe ports act like a Poe switch on your 192 network and the 10 network will cease to exist.
You will still need to manage the network addresses of the cameras either statically as above or via dhcp.

Once you have the Poe ports bridged and the cameras on the 192 network, the Nas will be able to see them.

If your NVR wasn't dahua you could also try using a static route on your router.
This tells devices on the 192 network that if they're trying to get to the 10 network that they will find if they go to the 192.168.50.252 address of your NVR.
It works with other brands but I'm told it doesn't work with dahua.
 
  • Like
Reactions: TonyR
TonyR said:
First, I don't use a POE NVR or NAS, I use Blue Iris VMS on a PC.

But if you put a gun to my head and insisted on my thoughts, I'd do as your friend suggested: put the cams on a POE switch, assign them all unique, static IP's on the same 192.168.50.XXX subnet as the NVR's LAN (but outside of the router's DHCP pool if there is a router) and add them to the NVR and to the NAS. A good Netgear 5 port POE switch with 4 POE+ ports is less than $65, A TP-LINK with same specs, $50.....less than lunch for 4 at a fast food chain restaurant. :cool:
Click to expand...
Assigning cams to specific IP eg 192.168.50.x first before plugging in to NVR can force the NVR to not assigning 10.1.1 IP to cameras once it plugged in? If that so it worth trying.
 
looktall said:
In many nvrs you have the option to bridge the Poe ports to the NVR wan port.
Not sure if yours does but it probably can.

What this will do is make the Poe ports act like a Poe switch on your 192 network and the 10 network will cease to exist.
You will still need to manage the network addresses of the cameras either statically as above or via dhcp.

Once you have the Poe ports bridged and the cameras on the 192 network, the Nas will be able to see them.

If your NVR wasn't dahua you could also try using a static route on your router.
This tells devices on the 192 network that if they're trying to get to the 10 network that they will find if they go to the 192.168.50.252 address of your NVR.
It works with other brands but I'm told it doesn't work with dahua.
Click to expand...
1. Search through internet and quite sure my NVR does not have the bridge mode, there's only option of IP Address, Subnet Masks, Default Gateway:facepalm:

hq720.jpg


2. Unfortunately it is a Dahua NVR, I did try setting up route in router like this. But the problem still exist... Am I setting it wrong?

2024-10-05 13_34_25-Window.jpg
 
Make sure you are using Internet Explorer (yeah we know lol) to log into NVR gui. It should have that option.

The NVR acts as a firewall/router, so trying what you did in your router won't work lol
 
wittaj said:
Make sure you are using Internet Explorer (yeah we know lol) to log into NVR gui. It should have that option.

The NVR acts as a firewall/router, so trying what you did in your router won't work lol
Click to expand...
ummm.... Yeah I can login the webgui both in chrome and palemoon with current settings.

Its the Synology surveillance station cannot find cameras even manually adding those cameras using IP (192.168.50.252:10081-10084), cant get through Authenticate using username and password of NVR's
 
I don't know the NVR side well but maybe try turning off ONVIF authentication and see if it then can get to them via 192.168.50.252:10081-10084.
 
shawnwong.au said:
1. Search through internet and quite sure my NVR does not have the bridge mode, there's only option of IP Address, Subnet Masks, Default Gateway:facepalm:

hq720.jpg
Click to expand...
Well that's the location you would normally find the bridge mode setting.
But if yours can't do it you will need to buy a separate Poe switch (unless you already have one) in order to put the cameras on the 192 network.
 
shawnwong.au said:
Assigning cams to specific IP eg 192.168.50.x first before plugging in to NVR can force the NVR to not assigning 10.1.1 IP to cameras once it plugged in? If that so it worth trying.
Click to expand...
Perhaps you misunderstood what I stated.

That IS the intent if NOT plugging cameras into the POE ports of the NVR......if plugged into a POE switch that is connected to the NVR's LAN then you MUST assign the cameras the static IP's, as the NVR's private server on it's POE ports cannot do it because you're not connecting to them.:cool:

Re-stated:
  • Cams to NVR POE ports = cams assigned IP's by NVR in 10.X.X.X subnet
  • Cams and NVR LAN port to POE switch = you assign static IP's to cams and NVR LAN in 192.X.X.X subnet
 
  • Like
Reactions: looney2ns
TonyR said:
Perhaps you misunderstood what I stated.

That IS the intent if NOT plugging cameras into the POE ports of the NVR......if plugged into a POE switch that is connected to the NVR's LAN then you MUST assign the cameras the static IP's, as the NVR's private server on it's POE ports cannot do it because you're not connecting to them.:cool:

Re-stated:
  • Cams to NVR POE ports = cams assigned IP's by NVR in 10.X.X.X subnet
  • Cams and NVR LAN port to POE switch = you assign static IP's to cams and NVR LAN in 192.X.X.X subnet
Click to expand...
So I should buy a POE switch after all?
 
shawnwong.au said:
So I should buy a POE switch after all?
Click to expand...
Because you stated that you wanted to connect the cameras to your SSS unit, that was my suggestion in post #2.
 
And if your NVR is lacking the ability to bridge mode out the cameras connected to the built-in POE.
 
You must log in or register to reply here.
Top Bottom