Ability to set default camera password for autodiscover
Answered
This is mostly for Hik's (and maybe Dahua too now) that require activation and password change before any config changes like IP address can be made. (you may already be working on this).
It'd be handy if i could global set the default password for auto-discover by system. Many times I pre activate and configure cameras in batches prior to install. This way when they're installed, they should be auto-discovered and be available for aiming on the mobile app. Problem is, the default password is still '12345' and auto-discovery adds the camera but then the camera locks until I update the PW in settings and power-cycle the camera.
Sure, if i batch activate/configure on site, I can disable auto-discovery and manually add the cameras with the correct password, but that is one more step and I'm lazy.
The default value is stored somewhere but nowhere to change it in the GUI, I checked the API, maybe there is a 'hack' in the meantime you could share with me that i could apply during server build/setup. All camera passwords will be the same for that system.
-
Official comment
Hi Paul,
Please make sure that there's no third-party services online which could lock the camera. We've run extra tests in the isolated environment when only Spectrum Server was running with Hik cameras online. In this situation cameras didn't lock.
But as soon as we confirm that under some circumstance Server makes cameras to lock we'll make its fix our top priority.
So instead of making possible to edit "default" passwords pool we'd like to resolve the blocking issue itself. Just FYI, the password pool extension will definitely cause significant increase of the discovery/failover time.
-
Thank you, Paul.
When auto-discovery option is on, once our software discovers a new device, it's automatically trying to submit default passwords/logins according to device's manufacturer. We keep default credentials per brand in our DB, which gets consistent update every once in a while. Once you change credentials manually and update the same info in our Desktop Client, our software no longer submits default credentials, only the ones replaced by you.
If you experience issues with cameras getting locked, it's more likely specific cameras issue and cannot be resolved on our side.
0 -
Yes, I am referring to changing the default password in the database that would apply to NEW discoveries, not individual cameras that have already been discovered.
Let me explain it better as it relates to the latest Hikvision firmware version as an example.
Hik cameras no longer have a 'default' password of '12345' (which is likely what is in your db).
A new camera needs to be activated via SADP or the web interface before anything can happen. During activation, a password must be entered (min 8 characters). Then the camera IP can be changed from the default of 192.0.0.64.
Now comes the issue... once the camera is activated with its new password and IP address and available to be discovered, Nx will try connecting to it using the old default of 12345. After x failed attempts, the camera locks for 30 minutes or until reboot.
What I would like is a way to change the default password in your db. Or, perhaps a more elegant solution would be to add a "Default Discovery Camera Password" field to the System Admin page. If field is not null then use that value as default for all brands, else, use the defaults by brand in your db.
3 -
Paul,
What version of our software are you currently using, please?
0 -
DW 3.1.0.16975 for both server (ubuntu 16.04) and client (Win10)
Hik/LTS Camera FW version V5.4.5 build 170718
You ask that like this behavior is unexpected, its always been that way for me.. am i missing something?
I can re-create with screenshots if you like...
0 -
The behavior is really unexpected, since we've implemented Hikvision API in 3.1 and this type of issue should not occur.
Please, open a support ticket here and describe the issue you currently have with the screenshots attached.
Thank you.
0 -
I know I'm late to this discussion, but I can back up Paul's claims here. It is an annoyance that we had to engineer a way around. Here is what we do Paul:
1) Using SADP or the Batch Config Tool, setup your camera on a separate test network, or simply with a laptop and PoE injector.
2) Create a secondary Operator account so that you can login with another credential when the admin account gets locked out.
3) Physically install the camera on the permanent network and allow Nx to discover it.
4) Change the credentials in Nx to match the Hikvision admin account.
5) Log into the Hikvision camera using the secondary credentials (since the admin account will be locked) and reboot the camera.
When the camera boots back up, it will be presented with the correct admin credentials and should work properly.
1 -
Jon, you feel my pain.
All I want to do is activate the cameras and set IP's at the shop, take them to the job-site, install them and have Nx discover and add them so I can aim them with the remote app "on-the-fly".
I hadn't considered adding a second user to the camera, maybe for some reason I though a lockout was global, never tried it. Thanks for that tip.
Still a pain in the a$$.
What I do now is just add one more step at the job-site. I use a temp switch to connect the cameras about to be installed to the camera network and do a manual add for the block of IP's. I then place them in a view called "install" so they are easier to find in the mobile app when there are a lot of cameras already.
Smaller jobs where I can preconfigure the server and the cameras at the shop is no big deal. But when adding cameras to an existing job, it could be made easier I think.
I don't even bother with the autodetect anymore and disable it by default.
Have a safe Memorial Day.
1 -
Has there been any progress or further discussion on this topic?
I have a customer saying they get locked out of Hikvision cameras with auto discovery still. They have to disable auto discovery because cameras lock after several attempts with default credentials in the database.
If there were a way to change default credentials that are tested, or edit a line of text to do so, it would be great to avoid the confusion it causes onsite when installing a large number of cameras that suddenly stop responding.
Thanks
Matt
1 -
Matt, not to my knowledge. We only use the auto discover feature on smaller installs. We simply turn this off on our larger systems.
0 -
Hi Matt,
What models and firmware versions does this happen to?
I have in my lab several servers and several Hikvision cameras and they won't lock due to the build-in login limitation.
If I remember it from the top of my head we do 3 attempts and then stop the attempts. The Hik camera allows 5 login attempts before they get locked.
As my colleague, Sergey Yuldashev mentioned, please assure that there are no third-party services online that could lock the camera.
0 -
Thank you Norman.
I will wrangle some details from the customer and see if we can replicate.
I will get back if I can get the details. And share your reply.
0 -
What about a way to store custom credential sets to have Nx test on cameras? We use Auvik for our network manager, and it has the ability to store credential sets that are filtered based on SNMP info pulled from the device.
0 -
-
Hi @...,
You can change the credentials in the device, and when the device is auto-discovered in Nx, you can select them all (hold Ctrl en click on each device you want to select, or hold Ctrl, click on a device, release, hold Shift and click below the selected device and all devices in between are selected) right-click and select Camera Settings and in the General tab you can edit the credentials for all selected devices at once.
0 -
Ok... I am just going to bump this feature request.
It is very common for my clients to add more cameras. Today I am preconfiguring 12 new cams for an existing system. Since all the cameras on the system use the same password, it would be incredibly convienent to be able to mount the camera and have it autodiscovered and viewable (with the right password) while I am up in the air. Now it takes the extra step of "bench" connecting them all, and adding them manually. That does not take that long... but certainly much longer than it would if i could specify a default autodiscover password. There is a whold table somewhere with mfg default passwords... all I need is one, or at least be able to override the mfg default.0 -
I'll go one better.. imagine a scenario where I have to replace a bad camera. I go out, climb the ladder and check for power to make sure. I install the new one, climb down, add it to the system. If I did not get the aim just right I have to climb back up and fix that. Two trips up the ladder instead of one. The life you save... (might be mine)
0
Please sign in to leave a comment.
Comments
16 comments