Dahua - Unauthorised
Completed
I have two Dahua cameras that were working fine and after some work on the system, powering down and up the network I am getting problems with these two cameras.
HDW3549-AS-PV-S3 - Firmware V2.840.0000000.18.R
HDW3589-AS-PV-S3 - Firmware V2.840.0000000.18.R
NXWitness is running 5.0.0.36410
In the left hand side the cameras have a red padlock next to them and if you try and load them the error where the image should be reads "UNAUTHORISED Please check authentication information"
I have taken the RTSP stream and added that directly with the same login credentials I am using and that works fine.
I have checked the date/time settings on the camera and NXWitness match which they do.
I tried to create a separate ONVIF user for NX Witness and that has not helped.
I can connect to the camera Web UI through the NX browser interface and it connects to the camera fine and I can login with the credentials I am using.
I deleted one of the cameras from NX to then try and add it back in, but NX is not finding the camera on a direct IP search or a subnet search.
-
Hi Liam Parker,
Lucky guess from my side. The camera uses time-based authentication.
Assure the timezone is set identical to the timezone of the server. It might be that daylight saving time wasn't configured correctly in the cameras and the issue corrected itself when the wintertime started.
-
Hi Liam,
I believe there is an issue we have discovered recently with Dahua cameras, when the timestamp is incorrect, it may cause issues with authorization token.
It has been resolved in the past with the Date & Time / timezone being corrected to match the server time.Can you check this for the cameras? If there are still issues - we can check the Onvif initialization via Wireshark, when the camera is added to the system (not as RTSP).
-
I have had this issue quite often lately. Unfortunately the only fix has been to go into the Dahua camera settings and "Default" the settings. Not "Factory Default" just "Default" that will retain the network configuration and user/password so it will reconnect again after you delete and re add it to the system. May not even have to delete and re add, I just always do as its faster than waiting to see if it authorizes.
-
Calvin Wientjes, thanks that has worked for me also and I remember having to do that when I had problems at another site a while ago, however that problem seemed to stop when the clocks changed in Oct and been ok at that site.
Derek Mangasarian, I still have one problematic camera on the system if you want to do a screen share to try and get to the bottom of the issue. The server is running Ubuntu and happy to let you take control of that machine over a Remote Desktop session. -
Norman - Nx Support - As per my initial post I have already checked that the timezones match, so it's not that.
-
So after some further testing after getting a new NX Witness server and having the same problem, it looks like the problem is to do with having DST enabled on the camera. Video link below shows DST being enabled and the search not finding camera with the UI open and IP address of 172.16.5.139, then after disabling DST and re-searching it finds it, then enabling it again and re-searching it fails to find it.
For now I will leave DST disabled and hopefully because I have NTP enabled the time will stay correct.
Perhaps Nx Witness can talk to Dahua and try and figure out what is happening here anyway.
Please sign in to leave a comment.
Comments
8 comments