Dahua CCTV system "failed to find host network"
- Thread starter ashking11
- Start date
bigredfish
Known around here
Could be a bunch of things
- Check cables to those cameras are plugged in and not damaged somewhere
- Temporary glitch in your PoE switch, try reboot of the NVR
- Failing internal PoE switch
- Log into NVR and see what they camera registration page is showing
- Any recent construction or critters in the attic?
Last edited:
Thanks for your reply, the system hasnt been used for a while - would a factory reboot help?
bigredfish
Known around here
bigredfish
Known around here
Mark_M
Known around here
As said implied by bigredfish, 'unable to find network host' means the NVR cannot find the camera and connect to it.
Compared to bigredfish's photo.... you have NVR GUI 4.0 version (red bell for TiOC function). So your camera status web UI will look like this:
In the corner of your camera, you will notice a little RJ45 port symbol.
This means the NVR recognises this channel is a camera connected directly to the NVR's built-in POE switch.
No RJ45 symbol means the camera is powered off and/or not responding to data.
My guess is your installer setup each camera manually rather than letting the NVR handle DHCP leasing and automatic plug & play.
So the NVR thinks each camera has a static IP address (the numbers shown on each channel) but it cannot find a camera on that address.
Try searching for devices and see if the NVR finds them all.
If your NVR does find all the cameras; delete all the un-connected entries first, then select all the found cameras and add them back.
Compared to bigredfish's photo.... you have NVR GUI 4.0 version (red bell for TiOC function). So your camera status web UI will look like this:
In the corner of your camera, you will notice a little RJ45 port symbol.
This means the NVR recognises this channel is a camera connected directly to the NVR's built-in POE switch.
No RJ45 symbol means the camera is powered off and/or not responding to data.
My guess is your installer setup each camera manually rather than letting the NVR handle DHCP leasing and automatic plug & play.
So the NVR thinks each camera has a static IP address (the numbers shown on each channel) but it cannot find a camera on that address.
Try searching for devices and see if the NVR finds them all.
If your NVR does find all the cameras; delete all the un-connected entries first, then select all the found cameras and add them back.
DHI-NVR4232-16P-4KS2/L ,please my 32 channel NVR is displaying failed to connect to network host . The first 16b cameras connected direct to the NVR and additional 8 cameras connected to an external Netgear 24 port POE switch. All working but after 2 years this error message came up and all cameras went off with the failed to find network host being displayed on all 16 channels and service returned message error on the channels of the cameras on external Netgear switch displayed on the CCTV monitor.
Who can assist
Who can assist
I recently had this happen to me, and I checked a few things to diagnose the issue.
Firstly, I opened the NVR and checked the connection for PoE power (the location and connector will vary by NVR). In my case, the connection was good, but I disconnected it and reconnected just to be sure.
Secondly, I went to the Camera section of the menu, as @Mark_M posted in his first photo, then I selected PoE from the left hand menu. At the top of that screen, I saw that the power draw was 0 W.
This is how I verified that the internal PoE Switch had failed (which is one of the suggestions from @bigredfish). Not great news, but I hope this helps.
Firstly, I opened the NVR and checked the connection for PoE power (the location and connector will vary by NVR). In my case, the connection was good, but I disconnected it and reconnected just to be sure.
Secondly, I went to the Camera section of the menu, as @Mark_M posted in his first photo, then I selected PoE from the left hand menu. At the top of that screen, I saw that the power draw was 0 W.
This is how I verified that the internal PoE Switch had failed (which is one of the suggestions from @bigredfish). Not great news, but I hope this helps.
Last edited: