IP conflict is persisting after deleting cameras. But the camera's have unique IP's outside of NX?
CompletedI'm having odd issues with one server, where several cameras seem to be "locked" into the same IP address. I can check the camera's MAC address in our Firewall and Network Monitor, and they are all working properly with unique IP addresses.
But after I delete a camera, it is automatically detected again with the same incorrect IP as before.
Is there a way to renew or set the IP address of a camera to resolve this issue? This server has ~45 cameras, and 5-6 are having this issue. They are showing the same IP and feed.
-
Hi Luke McFadden,
Do you use the "Auto-discovered" or "Manually search" to add the cameras?
I assume you use the "Auto-discovered" to have the camera discovered then you disabled the function, am I correct?Once you disable the auto-discovered, the Nx Witness will not be able to refresh those information inside the resource database, so it looked like they were locked.
Even though you delete then re-add the camera, since the camera has been recognized already, the camera identifier will remain the same in the database(that is why you can see the old recording associate to it). So the mediaserver will bring the same detail.
It is suggested that you might be able to use the auto-discover to find the camera, and leave the option enabled next time, then it is likely the issue could be solved.
Thanks.
0 -
Ichiro Thanks for the reply. No, we keep auto-discover on. So when I delete the cameras, they are being re-added... but still with the incorrect IP address. Is it possible to purge these cameras from the database? I understand we would lose it's archive, but at this point we need to do something as nothing is being recorded right now from multiple cameras. We have multiple systems across countries, and this is the only one having this issue?
0 -
Greetings, we are still having this issue. To confirm, these two cameras by MAC address have unique IP addresses in the camera when connecting directly, and through our network monitor. Only NX is having the IP conflict.
Here are some screenshots showing this issue Ichiro
Can we escalate this to a support ticket? I can provide logs and wireshark capture that way.
I'm running NX 5.0.0.35.270


0 -
Hi Luke McFadden,
Yes, my manager has created a support ticket for you. Please check you inbox and we will discuss further on the ticket. Thanks.
0 -
Currently, under investigation by our developers.
JIRA-VMS-37266
Update: customer patch applied, issue resolved.
0
Please sign in to leave a comment.
Comments
5 comments