Hikvision NVR and hikvision camera on the same subnet...

[Pierrick]

I recently received my Hikvision hardware:
1 NVR DS-7604NI-K1 / 4P(B)
1 Camera DS-2CD2185FWD-I

My lan is 192.168.0.1 to 192.168.0.254.
The gateway is 192.168.0.254

I have connected my NVR on my LAN with the LAN port and I'm able to sign-in on NVR (IP address of the NVR: 192.168.0.39).
I have also connected the IP camera on the LAN1 POE port of the NVR and I can see that the camera is connected and online in the NVR camera status page.
But it seems that the camera has IP 192.168.254.6
I now would like to change IP address of the camera in order to be able to reach it on my LAN but always connected on the LAN1 POE port of the NVR.
Is it possible? (NVR acts as a switch?)
If possible how to change it? I've tried to modify the camera settings by clicking modifiy button on the NVR menu.
Then I disable plug and play an select manual settings and configure IP adress(192.168.0.170), password, etc...
But after this configuration, the camera is no more in online status but in network error...

So, to conclude, Can you explain me how to configure both NVR and camera in the same subnet (my LAN subnet) with the camera connected on a NVR POE port...
Thank you for your help.

 

[TonyR]

Read this: Hitting cameras web pages with a laptop in an NVR with POE

@Shockwave199 made a how-to video here.

 

[alastairstevenson]

I now would like to change IP address of the camera in order to be able to reach it on my LAN but always connected on the LAN1 POE port of the NVR.
Is it possible? (NVR acts as a switch?)

The easiest, and supported, method, is to enable 'Virtual host' in the NVR web GUI advanced network settings.
When you have done that - the camera web GUI will be directly accessible from the LAN-connected PC by using the links showing in the far right column of the 'Camera Configuration' page of the NVR web GUI.

 

[Pierrick]

The easiest, and supported, method, is to enable 'Virtual host' in the NVR web GUI advanced network settings.
When you have done that - the camera web GUI will be directly accessible from the LAN-connected PC by using the links showing in the far right column of the 'Camera Configuration' page of the NVR web GUI.

Great!
I can now access the login page of the camera...
But a new question... Which login/password use????? I try user admion with the passwors set on NVR but no result....

 

[alastairstevenson]

But a new question... Which login/password use?????

On a new camera - it will be 'Inactive', requiring that a new, strong password must be set.

When you added it to an NVR PoE port in Plug&Play mode - the NVR will do that task.
Normally, the NVR will use it's own password to activate the camera, unless the option to use a different password has been enabled.
As far as I know - that option can only be set in the VGA/HDMI interface to the NVR.

Check out the NVR VGA/HDMI configuration pages to see how the NVR has been configured for camera passwords.
From what I remember - there is also an option to show the password.

 

[Valiant]

The easiest, and supported, method, is to enable 'Virtual host' in the NVR web GUI advanced network settings.
When you have done that - the camera web GUI will be directly accessible from the LAN-connected PC by using the links showing in the far right column of the 'Camera Configuration' page of the NVR web GUI.

Alastair, This feature is interesting, The web camera GUI may be accessible but are the LAN IP addresses on the same network or in a different range ?. I'm interested in understanding further how it works and what the real use case is for it ?. Does traffic pass across the Linux kernel ? (I think I may have read something similar here sometime ago), if so perhaps performance wouldn't be the same as a regular switch.

Do the NVR ports effectively appear on the same layer 2 network and receive broadcast traffic like DHCP ?. If the NVR auto allocates IP addresses to the cameras, then how do you ensure you don't get duplicate IP's on the network ?. I'm wondering if there are any negative outcomes ?

 

[alastairstevenson]

what the real use case is for it ?

The proxied access to camera configuration items provided by the NVR only covers a subset of all the camera configurations needed, so direct access for some detailed configuration is a user requirement.

are the LAN IP addresses on the same network or in a different range ?

The NVR with built-in PoE-support has 2 network interfaces, the LAN interface and the PoE interface.
These are, and must be, on separate network address segments.

Does traffic pass across the Linux kernel ?

Yes, the Virtual Host facility makes use of the Linux kernel 'IP_forward' (not to be confused with port-forwarding) capability as part of it's operation.
In effect, it provides a NATed access to the camera IP address HTTP port.

Do the NVR ports effectively appear on the same layer 2 network and receive broadcast traffic like DHCP ?.

No, these are on a separate broadcast domain, separate network segments.

If the NVR auto allocates IP addresses to the cameras

It's not so much auto-allocating network addresses as managing the camera configuration. There is no DHCP as such.

how do you ensure you don't get duplicate IP's on the network ?

The NVR PoE interface is on a separate network segment from the NVR LAN interface.
Typically, the LAN router/gateway has no knowledge of that network segment, though that can be changed if there is a need for the cameras on the NVR PoE ports to be directly accessible from the LAN, or for them to be able to communicate out to the LAN or the internet.

I'm wondering if there are any negative outcomes ?

Maybe the fact that the cameras can be made accessible from the LAN, and can potentially communicate outside their own segment.

 

[Searay]

The easiest, and supported, method, is to enable 'Virtual host' in the NVR web GUI advanced network settings.
When you have done that - the camera web GUI will be directly accessible from the LAN-connected PC by using the links showing in the far right column of the 'Camera Configuration' page of the NVR web GUI.

 

[Searay]

This is EXCELLANT and should be pinned!

Thank You!

I copied the url shortcut to desk top and it works GREAT!!!

Thank You AGAIN!

 

[klauscla]

Hi, I have exactly

The proxied access to camera configuration items provided by the NVR only covers a subset of all the camera configurations needed, so direct access for some detailed configuration is a user requirement.


The NVR with built-in PoE-support has 2 network interfaces, the LAN interface and the PoE interface.
These are, and must be, on separate network address segments.


Yes, the Virtual Host facility makes use of the Linux kernel 'IP_forward' (not to be confused with port-forwarding) capability as part of it's operation.
In effect, it provides a NATed access to the camera IP address HTTP port.

No, these are on a separate broadcast domain, separate network segments.

It's not so much auto-allocating network addresses as managing the camera configuration. There is no DHCP as such.

The NVR PoE interface is on a separate network segment from the NVR LAN interface.
Typically, the LAN router/gateway has no knowledge of that network segment, though that can be changed if there is a need for the cameras on the NVR PoE ports to be directly accessible from the LAN, or for them to be able to communicate out to the LAN or the internet.

Maybe the fact that the cameras can be made accessible from the LAN, and can potentially communicate outside their own segment.

Hi I have exactly the same issued of the OP. Now with virtual host I can access the cameras, my problem is that I use the stream of the camera that are now attached to the LAN-POE of the NVR for BlueIris and Home Assistan use, which are in the same network of the NVR

SO the NVR is 192.168.1.40
My Home assistant is 192.168.1.10
BlueIris server is 192.168.1.20

Now the NVR put all the cameras in the 192.168.252.xxx range, so now they are not accessible from Blueiris and Home Assistant with the rtsp stream
(rtsp:/admin:xxx@192.168.254.2:554/Streaming/Channels/101 is not accessible and should be
rtsp:/admin:xxx@192.168.1.xx:554/Streaming/Channels/101


Is there a way I can have the stream in 192.168.1.xxx or any other workaround

 

[klauscla]

I can access the weUI of the cameras using ports 6500x

http://192.168.1.77:65001/

will access port on POE number 1, but how to get the stream? Usually I would use 554for rtsp, but now?

 

[alastairstevenson]

If it's purely for RTSP streaming - use the NVR IP address in the URL instead of the camera address.
Adjust the channel for each camera needed.