Hi  @aashishvanand ,

I had a very similar problem just over the weekend.

My solution was to use only the NVR Web Interface, I used the "cameras/add manually" option and specified the IP address - it also did NOT allow me to select the protocol (was set to ONVIF and greyed out.)

After I added the camera's - they worked fine.

(When I tried this using the Vigi PC Client - it did not work.)

Regards, Bill.

OzzyBill wrote

Hi  @aashishvanand ,

 

I had a very similar problem just over the weekend.

 

My solution was to use only the NVR Web Interface, I used the "cameras/add manually" option and specified the IP address - it also did NOT allow me to select the protocol (was set to ONVIF and greyed out.)

After I added the camera's - they worked fine.

 

(When I tried this using the Vigi PC Client - it did not work.)

 

Regards, Bill.

  @OzzyBill So, How did you manage to add it? Using ONVIF, both ports 2020 and 443 don't work.
Did you add the camera first and then move it to the other subnet? 

Hi  @aashishvanand ,

The web interface just says "ONVIF" which I assume is port 2020.

The camera's had to be left on their original subnet which they had originally been installed on.

The NVR had been moved to another subnet - it was straightforward to log into it's web interface and update it's networking to use DHCP (although I notice that all my Vigi cameras and NVR appear to switch back to "Static IP".)

With the NVR on the new network I was able to use "Settings->Add manually" to specify the IP Address of each camera on the old subnet.  As I added them, the NVR then asked for the password - which I then added, clicked OK, and then I was given the opportunity to re-specify the IP Address - which I could then give as the new subnet (which the camera was actually not connected to you!)

I then physically moved the camera over onto the new subnet - and the NVR was able to connect to it still and capture the video.

I had tried multiple different methods before without success including using libonvif/onvif-gui - but the C300HP proved very stubborn (Packet traces shows it kept booting up with it's old IP and ignoring the DHCP server of the new subnet.)