So this is working now and I'm not exactly sure why - What I did was connect the second NIC and assign it a static IP of 10.2.1.251 - I watched the FW and where I was seeing no traffic coming from NIC1 when I was trying to add the camera and failing, I saw the expected traffic coming over NIC2...
Correct. I add the RTSP feeds back to the old DVR and stream video without issue and I can view the RTSP feeds in VLC from workstations on the 10.2.1.1 subnet. Basically the only device unable to communicate with the camera at 10.3.1.60 is the ENR-130 at 10.2.1.240 and there are no firewall...
I am unable to ping the NVR (10.2.1.240) from the 10.3.1.1 subnet or access the NVR web console. I am able to ping any other device on the 10.2.1.1 subnet from the same device on the remote (10.3.1.1) subnet. I see the traffic pass on both the 10.3.1.1 firewall and the 10.2.1.1 firewall but...
The cameras are Reolink cameras - I've got 3 of the same make/model camera in use already - they are all just on the 10.2.1.1 (local) subnet. It's just the remote camera that I'm unable to connect to from the ENR-130. I am able to connect to the RTSP feed in an alternate DVR.
ENR-130...
The router at each location sets up the VPN and everything on the 10.2.1.1 subnet is able to access everything on the 10.3.1.1 subnet and vice versa.
RTSP is enabled - I've got several RTSP feeds connected to the NVR on the 10.2.1.1 subnet, it's just the sources on the 10.3.1.1 subnet that are...
I've got a remote site that is connected to the main site via a site-to-site VPN. I can access the camera at 10.3.1.60 from my local subnet 10.2.1.0/24 and can view the RTSP feed in our old NVR (on the same subnet as the new Acti ENR-130), but the camera does not connect when I add it to the...