Dahua NVR and Camera Setup - Best Practice

Here is what I would do. This is with the idea you might be using Win11,
Press CTRL and R together then in the box type in ncpa.cpl then right click your Network connection, Then click Properties, then click on IPV4, Then Properties, Then first i would setup a Static IP for your PC, Then I would click the Advanced, then in the top part click on the add and add in the IP range of the camera and make it something other then what your camera has in my case I have my main static IP as 10.0.0.129 and my extra IPs I have setup as things like 192.168.1.119 and so on with a good few IPs in my extra area.. Screenshot (3784).png
 
Revo2Maxx said:
Here is what I would do. This is with the idea you might be using Win11,
Press CTRL and R together then in the box type in ncpa.cpl then right click your Network connection, Then click Properties, then click on IPV4, Then Properties, Then first i would setup a Static IP for your PC, Then I would click the Advanced, then in the top part click on the add and add in the IP range of the camera and make it something other then what your camera has in my case I have my main static IP as 10.0.0.129 and my extra IPs I have setup as things like 192.168.1.119 and so on with a good few IPs in my extra area.. View attachment 209449
Click to expand...
Thank you so much for your reply!! I tried this, but I suspect I executed it incorrectly. In my case, my DHCP range is 10.0.0.X, and the problematic camera is showing up on my router as 192.168.1.251 (?). So I configured my Windows PC with a static IP address of 192.168.1.252 or 192.168.1.2, and a default gateway of 192.168.1.1. And then the subnet mask and DNS server were as you have it. When I did that, and then I used 192.168.1.251 in my browser, it wouldn't find the camera. Any obvious I'm doing wrong?
 
Well sounds like you might have locked your self out of your own network. My static ip is 10.0.0.129 because that is my normal lan range, then 10.0.0.1 as my default gateway and 255.255.255.0 for my subnet mask.
Then in my extra ip area I have added 10.1.1.129, 192.168.1.119, 192.168.0.119, and others that I may use added. All ending with .119. Anyway all subnet mask used 255.255.255.0. Then with my case I can access my local network, then connect camera with static ip of 192.168.1.108 to my Cisco switch and going to my browser enter that cameras ip address and I can access the cameras webui to make changes to camera. At same time I can surf web and access my other cameras or network ip ranges with out issue. If you are unable either network issue or might be blocked by your current network router setup. Even with direct cable from your computer to camera still no access going to its listed ip? Sure it's good ip and not a ghost wifi ip. I mean on some of my cameras I get ghost ip of range set by factory but not setup or have access to reboot camera make sure ip scan or other method you use to find your cameras and make sure it's still showing. If it is, then press ctrl and r same tim, type cmd press enter, then type ping cameras ip address -t and see if your able to ping the camera. After 10 tries press ctrl c to stop ping request. If all ping request fail then camera isn't reachable.
 
No I think we miscommunicated somehow. My LAN's DHCP range is 10.0.0.1 - 10.0.0.254. And all my cameras have IP reservations inside the range. My network and all the cameras (and my Blue Iris) have been working swimmingly for several years. What I don't understand is why, after a short power outage last week, just one camera came back with an IP address (according to my router, which is a Unifi UDM Pro) of 192.168.1.251. I can't figure out how to connect to this camera since it's IP address is outside the range. I'd like to follow your suggestion above to reconfigure the network settings of my Windows PC but I'm unclear which of the IP addresses in your example are the analogues for my DHCP range and the out-of-range IP address. Can you kindly clarify?

Also I haven't tried plugging the laptop directly into the camera because the camera is being powered by POE. If plug my laptop (which is Mac) into the camera directly, will it even get power?

Thanks again!
 
Ok yes my network is 10.0.0.xxx normally as well. So in my setup my main static ip is 10.0.0.129. My main router is 10.0.0.1 and so all other ips I am adding are for my many other connected devices with switches and their own ranges. So if I move camera from my Dahua POE nvr to my poe switch then I can access the camera by accessing its static ip making access faster then having to worry about ip tools or EZTools.

About connecting to your laptop no power unless you connect to external power supply.

So your router shows this cameras IP outside your normal network range? Can you confirm that it really is your camera? By name or mac address? Or just guessing missing camera must be with rogue ip? Does your camera manual state its normal static ip is the one in your pool outside scope? Seems like strange ip address
 
So this video is unlisted and will only be found by the link here. Just wanted to show what I am talking about. Pulled a good few cameras to make some changes to the Gel Packs that are in them.. A step that many don't do and one of the reasons I have very old cameras still running on my network. I normally have them all down and returned before winter but had some health issues this year that kept me from doing a lot of things I normally would have done lol. So thought while I had this camera on my desk I would show what I am talking about. In the Video it shows my Alibi NVR on 10.0.0.96 as that is my normal IP range. Then I show the Turret Zoom camera that is connected on my NVR POE port with a 192.168.0.13 IP and then I show that I am connected to the camera over the NVRs Virtual Host this means when you click on connect or the e on the Amcrest or Dahua devices I also have it will open the NVRs IP address and a port or in the Alibi case a few ports and access camera WebUI over NVRs ip with ports.. Then I remove the camera from the POE port of the NVR and connect to my switch and show that I can now access my camera and NVR at the same time on different IP ranges..

 
Revo2Maxx said:
Ok yes my network is 10.0.0.xxx normally as well. So in my setup my main static ip is 10.0.0.129. My main router is 10.0.0.1 and so all other ips I am adding are for my many other connected devices with switches and their own ranges. So if I move camera from my Dahua POE nvr to my poe switch then I can access the camera by accessing its static ip making access faster then having to worry about ip tools or EZTools.

About connecting to your laptop no power unless you connect to external power supply.

So your router shows this cameras IP outside your normal network range? Can you confirm that it really is your camera? By name or mac address? Or just guessing missing camera must be with rogue ip? Does your camera manual state its normal static ip is the one in your pool outside scope? Seems like strange ip address
Click to expand...
Thanks again for your reply. All my IP cameras are wired via ethernet to my Dahua POE switch (which is then connected to my Unifi network infrastructure). That's how it's always worked and it's always worked fine. I haven't made any changes to the physical topology.

I'm certain I have correctly identified the camera because (1) I know it's MAC address; and (2) in my Unifi router, I previously reserved a static IP address and named the device, both of which are correspond to the camera in question.

My bugaboo continues to be that the camera, even after a reset, boots up with an IP address (192.168.1.251) outside of my range. Lke you, my network is 10.0.0.X, and the rouge camera has a static IP of 10.0.0.206. Even the router's UI shows the static IP should be .206, even though it's actual IP is 192.168.1.251.

So, to answer your questions (thank you again!): yes, my rotuer shows this camera's IP outside my range. Yes, I'm sure it's the rogue camera (if I disconnect the camera physically from the poe switch, the camera goes away in my router UI) by both name and MAC address. Not to mention IP reservation as well. So, no, I'm not guessing. When I first installed this camera 3-4 years ago, it booted up as 192.168.1.108, like all (?) my dahua cams do.

Stymied!
 
Revo2Maxx said:
About connecting to your laptop no power unless you connect to external power supply.
Click to expand...
Sorry I don't understand what you're saying here. I'm trying to connect to my camera, but the camera is powered via POE, so when I take my laptop and physically connect to the camera from my laptop, does the camera get power from the laptop somehow.

Because when I did connect physically to the camera with ethernet, my browser won't connect to it when I type 192.168.1.251 as the URL. I even tried the reserved IP, 10.0.0.206. Still nothing.

Wonder if the camera is getting power when I have it connected this way?
 
Finally.... I did remove the camera's ethernet cable from the poe switch and connected it to my main network switch. I tried both a poe port and a regular port, and neither way makes the camera accessible.

BTW I'm using Blue Iris as my NVR.
 
Revo2Maxx said:
Here is what I would do. This is with the idea you might be using Win11,
Press CTRL and R together then in the box type in ncpa.cpl then right click your Network connection, Then click Properties, then click on IPV4, Then Properties, Then first i would setup a Static IP for your PC, Then I would click the Advanced, then in the top part click on the add and add in the IP range of the camera and make it something other then what your camera has in my case I have my main static IP as 10.0.0.129 and my extra IPs I have setup as things like 192.168.1.119 and so on with a good few IPs in my extra area..
Click to expand...
So here's what I did. Since I already have 10.0.0.89 as my reserved IP address for my Windows machine, I used 10.0.0.89 / 255.255.255.0 / 10.0.0.1 as my IP4 properties. Then under advanced, since my router is saying my rogue camera is 192.168.1.251, I created two IP addresses: 192.168.1.250 and 192.168.1.252.

Then I went to my browser and tried 192.168.1.251. Still nothing. Am I not following your instructions correctly?
 
I am sure you tried all these things. But here is an idea, Seeing you said that you reset camera, I would remove from router static pool and reboot camera again. Don't reset again just reboot Remove from power wait 10 or 20 seconds and restore power and see if the IP info changes? If that don't change then it almost sounds like the camera might have an issue with the ethernet chip/circuit? I have many Dahua and Dahua OEMs that I have on a router pool static ip and never had any that has gone rogue like this.. Had one that took wrong info from camera because it was a Wifi/Ethernet camera and the connection was pulling wifi data and not connected cable data. Firmware glitch.. After I removed from static it came up and setup and has work correctly since. So just an idea.
 
You must log in or register to reply here.
Top Bottom