How? Configure NVR to permit iVMS-4200 access to the 254.n IP

[kingdaddy]

I notice the NVR has a "internal NIC" of 192.168.254.1. I think that
is how the PoE ports are made private. (?) explain?

MY NVR is DHCP and has IP from my router 192.168.1.1, and gateway of 192.198.1.1
All is well with the 254.n cameras.

If I attempt to change internal NIC to 192.168.1.1, I get warning "IP address (NVR) and internal NIC conflict."

If I change camera IP to the 192.168.1.n of my network, and the internal NIC to (?), will that work?

Can I get some elaboration regarding this environment. I can't even ping the NVR cameras, and SADP is also affected. Browser access is neutered. I have no router ports opened for public network access.

 

[alastairstevenson]

I notice the NVR has a "internal NIC" of 192.168.254.1. I think that
is how the PoE ports are made private.

Yes, it's a separate network segment, only accessible via the internal routing of the NVR.
Loads and loads of posts on that topic - try a search for "poe cameras access routing" or similar.
Do you have 'Virtual Host' on your NVR? Network | Advanced settings | Enable virtual host.
That would be the easiest way to gain direct access to the cameras on the PoE ports.

 

[kingdaddy]

When I set Virtual Host check-box, I get window: "port", has 65001. Is that ok? Camera uses port 8000.
The check-box has empty space above, labeled Multicast IP. What is the significance?
So far, Ping, and SADP, and net scanner does not see the PoE port.

 

[alastairstevenson]

Camera uses port 8000

That's the 'media port' for the cameras, it's not related to the port that the Virtual Host provides.
Ping and SADP will not see the cameras - they are on a separate network segment, only accessible by default via the NVR, such as via the Virtual Host facility.

To access the cameras via Virtual Host once it is enabled, in your browser simply click the link in the right hand column on the camera configuration page.

 

[kingdaddy]

That works! great! Thank you.

I found a useful post by you Oct 2014, https://www.ipcamtalk.com/showthread.php/1604-Hikvision-POE-LAN-segment-access-to-cameras-without-virtual-host-or-extra-wiring?highlight=ip_forward
and trying to use router to define 'Static Route" as per description. I probably have not got it right yet. The example has a parameter " ,2" that is not accepted.

I would think 'Static Route' will make ping and SADP work. Is that correct? Can you elaborate?

Carl

 

[alastairstevenson]

Destination network 192.168.254.0, mask 255.255.255.0, gateway 192.168.1.100, some metric such as 2.

What metric if any is needed will depend on the specific way your router is configured for static routes, and even if it can do that at all.
So the metric of 2 may not even be needed.
SADP will not work, but ping will, and direct browser access will also work.
But with Virtual Host you don't really need any more, at least for the detailed camera configuration.

 

[kingdaddy]

(Happy Face!) SADP is now working, but I had to manually add the device.

 

[kingdaddy]

Sorry, I was so excited, I did not get my fingers in gear with my joy! It is iVMS that is working, not SADP.

 

[alastairstevenson]

Well done for getting there!