Ip conflict

[lloydchristmas]

Hi all,

I have a 4 channel hikvision NVR with 3 cams connected. They've been connected and running fine, connected to internet so viewable through the app.

The way I had it set up was a ethernet cable from the router straight to the nvr. My WiFi has been dogshit recently so I thought I'd set up my 16ch switch and feed all the cat6 cables I have running to different rooms in the house. I took out the internet feed from the nvr and put it in the switch, then had an ethernet going from the switch back to NVR. Worked fine, cameras back online. Then the dreaded beeping started. "Ip conflict". I assume there is more than one device trying to use the same IP but I have no idea about IP addresses. Then two of the cameras dropped out. I played around a bit and then two cameras were working and one wasn't, all very frustrating. Anyway I decided to go back to how it was and connected internet straight back to it, but I'm still getting the same error IP conflict. All cameras are working, and viewable online the app.

I have some screenshots of IP addresses and model numbers.

NVR
ds-7604ni-k1/4p

2 of the cameras are
ds-2cd2363g0-1

Appreciate any help.
Had to switch it off for now as there's no way to mute the annoying beeping. Last time I had this issue the harddrive was fried.

 

[David]

Hi all,

I have a 4 channel hikvision NVR with 3 cams connected. They've been connected and running fine, connected to internet so viewable through the app.

The way I had it set up was a ethernet cable from the router straight to the nvr. My WiFi has been dogshit recently so I thought I'd set up my 16ch switch and feed all the cat6 cables I have running to different rooms in the house. I took out the internet feed from the nvr and put it in the switch, then had an ethernet going from the switch back to NVR. Worked fine, cameras back online. Then the dreaded beeping started. "Ip conflict". I assume there is more than one device trying to use the same IP but I have no idea about IP addresses. Then two of the cameras dropped out. I played around a bit and then two cameras were working and one wasn't, all very frustrating. Anyway I decided to go back to how it was and connected internet straight back to it, but I'm still getting the same error IP conflict. All cameras are working, and viewable online the app.

I have some screenshots of IP addresses and model numbers.

NVR
ds-7604ni-k1/4p

2 of the cameras are
ds-2cd2363g0-1

Appreciate any help.
Had to switch it off for now as there's no way to mute the annoying beeping. Last time I had this issue the harddrive was fried.

Are the cameras connected to the Ethernet ports at the rear of the NVR?

David

 

[lloydchristmas]

Are the cameras connected to the Ethernet ports at the rear of the NVR?

David

Yes mate. 3 cams plugged into 4 of the available channels on back of the box.

And one in the internet port

 

[David]

Yes mate. 3 cams plugged into 4 of the available channels on back of the box.

And one in the internet port

When cameras are connected direct to the NVR they are on a IP subnet for the cameras only. Try restarting your NVR.

David

 

[lloydchristmas]

When cameras are connected direct to the NVR they are on a IP subnet for the cameras only. Try restarting your NVR.

David

Yea I rebooted it a few times but still getting same error and beeping as soon as it starts back up. All cameras working though

 

[lloydchristmas]

Should the camera and NVR be closer range? Box is 192.168.4..... cams are 192.168.254....

Would putting the box on 254 help

 

[David]

Should the camera and NVR be closer range? Box is 192.168.4..... cams are 192.168.254....

Would putting the box on 254 help

No, when cameras are connected to the NVR rear ports the NVR manages the IP addresses. If you look at your NVR network settings you should see a setting for the IP address used for cameras connected to the rear ports like 192.168.254.nnn. Leave this as it is.

The NVR gets an IP address from your router and takes care of routing information to and from the cameras / internet. On the NVR camera management page how is that camera setup? It should be plug and play, I suspect the camera with the problem does not have DHCP enabled and has a fixed (wrong) IP address. You could delete and re-add the camera to see if that solves the problem. You could also access the camera direct via the virtual host and check the camera settings.

David

 

[David]

@lloydchristmas this should you with virtual host setup

Enable virtual host nvr 4.0

Struggling to find the enable virtual host setting on the nvr gui V 4.0 software via web browser. I have accessed configuration/ system / channel management tab where this lists each camera its IP settings etc and at the right hand side of the page each camera has an edit tab in the operation...

www.use-ip.co.uk

 

[lloydchristmas]

No, when cameras are connected to the NVR rear ports the NVR manages the IP addresses. If you look at your NVR network settings you should see a setting for the IP address used for cameras connected to the rear ports like 192.168.254.nnn. Leave this as it is.

The NVR gets an IP address from your router and takes care of routing information to and from the cameras / internet. On the NVR camera management page how is that camera setup? It should be plug and play, I suspect the camera with the problem does not have DHCP enabled and has a fixed (wrong) IP address. You could delete and re-add the camera to see if that solves the problem. You could also access the camera direct via the virtual host and check the camera settings.

David

Yes I when I had a look they were set to plug and play.

Ok I will try delete and re-add them when I get home later.

 

[David]

Yes I when I had a look they were set to plug and play.

Ok I will try delete and re-add them when I get home later.

is there any more detail on the IP conflict error? Post anything you see, even a hex error code (like 0x1a2b03.....) can be helpful.

Dont forget to try the virtual-host as well.

David

 

[sportster]

A few comments / observations to compliment what David has pointed out:

1. can you hand draw a diagram (& post a pic) of how you would like it cabled ? Be sure to clearly differentiate how the NVR's LAN port is cabled vs the NVR's 4 x POE ports and, if used, how the switch & router are cabled in.
2. on the NVR's Network General config page, you're showing a network mask of 255.255.252.0. Can you confirm 2 items:
   • mask 255.255.252.0 is intentional and not a typo (most use 255.255.255.0, but 255.255.252.0 is a valid network mask too). Whether or not HIK's firmware behaves well with "252" is another question. Lol ! Stranger things have happened.
   • this LAN interface is "really" using DHCP ? (thus the network info is / was assigned by your DHCP Server (usually your router.))
3. mask 255.255.252.0 indicates IP address ranges:
   • for LAN port --> 192.168.4.1 - 192.168.7.254
   • for NVR POE ports --> 192.168.252.1 - 192.168.255.254 (again, whether HIK's firmware honors this range might be in question. I've certainly never tested it.)
   • Is this what you want ?
4. can you provide a NVR screen shot of the network config showing the "Internal NIC Address". I'm guesing it shows the default 192.168.254.1 BUT ??

 

[David]

@sporster,
All valid points, I did wonder about the SNM. Only 4 devices connected, I sense I’m missing something. I suspect the camera with dhcp disabled but the NVR camera management PnP should deal with that.

David

 

[sportster]

@David ..... yeah, I'm still scratching my head about the 4 devices connected..... when the initial post indicates 3 cameras. Figured a diagram might fill in the blanks.... and help sort out those pieces missing from this puzzle. Cheers!

 

[David]

@David ..... yeah, I'm still scratching my head about the 4 devices connected..... when the initial post indicates 3 cameras. Figured a diagram might fill in the blanks.... and help sort out those pieces missing from this puzzle. Cheers!

Yes, a diagram helps. Switch uplink ports not being used correctly, loop protection from spanning tree protocol…..

 

[lloydchristmas]

No, when cameras are connected to the NVR rear ports the NVR manages the IP addresses. If you look at your NVR network settings you should see a setting for the IP address used for cameras connected to the rear ports like 192.168.254.nnn. Leave this as it is.

The NVR gets an IP address from your router and takes care of routing information to and from the cameras / internet. On the NVR camera management page how is that camera setup? It should be plug and play, I suspect the camera with the problem does not have DHCP enabled and has a fixed (wrong) IP address. You could delete and re-add the camera to see if that solves the problem. You could also access the camera direct via the virtual host and check the camera settings.

David

Yes I when I had a look they were set to plug and play.

Ok I will try delete and re-add them when I get home later

Yes, a diagram helps. Switch uplink ports not being used correctly, loop protection from spanning tree protocol…..

Thanks for responses guys, sorry been at work so haven't been able to check properly. But here's a sketch. First image is original set up (was working fine), then second image the new setup with the switch box (ip conflict), and now I am back at original set up but still with IP conflict.

 

[sportster]

Not seeing anything obvious. To keep the conversation going, I'll offer this up:

a) the 2 sketches are a good start. Thanks for that.

b) can you address #2, #3, #4 from my earlier post ? Your responses may indicate what needs to be looked at next.

c) I'm not seeing anything unusual in your sketches, until I get to the wall socket. What exactly is going on there ? Do you really have 4 ports in one wall socket ? What port is cabled to what port ? Maybe take a pic to educate me/us. If necessary, can you temporarily bypass this wall socket ?

d) re: the IP conflict message. The NVR should "log" additional info about which IP Address(es) are problematic. Can you review the log records and identify which IP address(es) is/are in conflict ?

e) in pic 1, where are the other household devices ? are they connected via wireless in the pic 1 scenario ? or ?

 

[lloydchristmas]

Not seeing anything obvious. To keep the conversation going, I'll offer this up:

a) the 2 sketches are a good start. Thanks for that.

b) can you address #2, #3, #4 from my earlier post ? Your responses may indicate what needs to be looked at next.

c) I'm not seeing anything unusual in your sketches, until I get to the wall socket. What exactly is going on there ? Do you really have 4 ports in one wall socket? What port is cabled to what port ? Maybe take a pic to educate me/us. If necessary, can you temporarily bypass this wall socket ?

d) re: the IP conflict message. The NVR should "log" additional info about which IP Address(es) are problematic. Can you review the log records and identify which IP address(es) is/are in conflict.

e) in pic 1, where are the other household devices ? are they connected via wireless in the pic 1 scenario ? or ?

B) yes will do mate, wasn't able tonight as I get home late and kids were asleep. As soon I turn the nvr on I get those loud beeps. Seems mad that you can't mute alerts... Unless there is a way?

Sorry I should have explained the sketches a bit better...

C) So the router is downstairs. I have an ethernet cable going from router to a wall socket, which is patched to upstairs to a comms cupboard and goes straight into the nvr in pic 1. I also have an indoor camera near the router which also plugs into the wall socket patched to the Comms cupboard straight into Nvr Chanel 3. So to answer your question, no it's not 4 ports in 1 wall socket, more like 2 daisy chained to extend and reach the Comms cupboard.

D) will check in the morning

E) The comms cuoboard basically has loads of ethernet cables which are run to different parts of the houses which are either for cameras or option to provide internet to via the switch. Up til now I've been using WiFi for 99% of devices, but I'm getting crappy connection recently hence why I decided to start hardwiring the devices I could using the switch, but got this hiccup straight away.

 

[sportster]

As soon I turn the nvr on I get those loud beeps. Seems mad that you can't mute alerts... Unless there is a way?

I don't have your model of NVR nor that version of firmware, but if you can find this panel (see pic) in your firmware, chances are you can turn off the annoying buzzer.

Failing that, you might try disconnecting Ethernet cables.

 

[David]

@lloydchristmas,
As @sporster says we need more detail on the IPConflict, as I said earlier, post all the detail shown.

This seems to be on the NVR's internal IP network which is isolated (ish) from your internet network. If you have a PoE supply or a dc supply can you disconnect the camera from NVR D4 and connect it to your router / switch? Use the sadp tool to identify the camera by MAC address (usually on camera label), check the status of DHCP and enable if necessary. Before posting a screenshot of the sadp screen black out the camera serial numbers.

David

 

[JB1970]

IP conflict error generated by the NVR is telling you that another device on the network has the same IP as the NVR. It won't be anything to do with the cameras. It's easily sorted just change the IP of the NVR. Unless you know what other devices on your network use static IP address just select DHCP and let the router assign it. If you don't want the address to change, once done login to your router and add a DHCP reservation so that it's always assigned the same address.

If you must have a static IP address then first check the routers settings to see the range of IP addresses in it's DHCP pool and give the NVR an address outside of that range and having checked that nothing else is using it (I always run a network scan with IP Scanner ultra to see what devices are present and their IP addresses). Depending on the router you may have to adjust the DHCP pool range, as some (Virgin Media hubs for example) allocate the entire subnet to DHCP.