Solved: Dahua N41bk22 not showing up on config tool or router, even after physically resetting camera

F

Foneman1

n3wb
Oct 24, 2018
6
7
Missouri
I have 3 brand new N41BK22 cams, and installed 2 onto my existing Dahua NVR, one cam was replacing an existing 720P cam, and the other was going on an unused channel.
The first cam I installed was picked up by the NVR immediately, but the other just showed "invalid" username password on the screen.

I power cycled the NVR, deleted and re-added the offending camera,and eventually had to reset the entire system, still to no avail. I swapped the offending camera with the 3rd cam, still in it's box, and the 3rd worked as it should.

I opened up the problem camera, and held the reset button for 30 seconds (while plugged directly into my Ubiquiti router's POE port) multiple times. I used a short patch cord between cam and router, cable tests good. Router shows the camera on the POE port is drawing power. Router does not show the cam in the list of clients I even unplugged the camera from the router after resetting, and plugged it back in.

Config tool refuses to see it, even when both my PC and the cam are plugged directly into a separate POE switch. Typing the default cam IP into a browser does nothing either.
 
I had this. You need to adjust the range of IP's in the Network settings to include the cameras IP range.

See the instructions for setting up Dual NIC cards to see how to add IP address ranges to the network card settings. Once this is done, the PC should see them once more and they should be available to the Config App.
 
  • Like
Reactions: bigredfish
Foneman1 said:
Ok, solved. I went and disabled wifi on the laptop, and set ethernet to static IP, and assigned a range in the subnet of the cam, and it found the camera.

I don't mess with static IP's much, so that's what had me lost.
Click to expand...

I was going to ask if the PC was on a 192.168.1.XXX subnet because the cam's default IP when reset is 192.168.1.108 and I was't sure if the Config Tool would find cams that are on a subnet different from the PC.

I don't use Config Tool, just the PC and a browser so I wasn't sure.
 
  • Like
Reactions: CCTVCam and bigredfish
PC was on 192.168.0.x. Sounds like it won't work with different subnet settings. I've used other config tools for IOT devices that do work across subnets, so didn't know about Dahua tools
 
  • Like
Reactions: TonyR
Leaving it plugged into the NVR and manually resetting should accomplish this. On brand new reset it will get a 10.1.1.x address from the NVR Poe switch. If it doesnt t see the NVR then it will default to 192.168.1.108
 
Yep I don't know why cameras are doing this lately. Resetting the camera should only reset the camera but somehow it seems the subnet is disappearing from windows network card settings with a reset. Maybe one of the Windows updates has introduced some kind of redundant subnet address cleanup. Very annoying though and potentially very confusing unless you happen to use the same subnet for your pc by default, which then leaves you unsecure from the cameras being network accessible / phoning home.
 
Last edited:
bigredfish said:
Leaving it plugged into the NVR and manually resetting should accomplish this. On brand new reset it will get a 10.1.1.x address from the NVR Poe switch. If it doesnt t see the NVR then it will default to 192.168.1.108
Click to expand...

It was a brand new (old stock) camera, and the NVR was being stupid and saying the username/password was invalid (it wasn't) The other identical camera was picked up by the NVR immediately, and provisioned. I ended up resetting the entire NVR, and using a 3rd identical camera.

It's all working now.
 
  • Like
Reactions: CCTVCam and bigredfish
You must log in or register to reply here.
Top Bottom