Help with Hilook NVR and Cameras - factory reset NVR

Have you tried resetting the cameras back to factory default, through the push button inside of the camera?
 
  • Like
Reactions: Flintstone61
Is your NVR running DHCP? If your NVR has POE ports, I would set the cameras back to factory default and then let the NVR find the cameras and assign them the IP address. If you are running the cameras through a POE+ Switch, then you could make the cameras static with an IP address of your own choosing.
 
  • Like
Reactions: Flintstone61
doesn't he need about 12 vdc @ 1.0 Amp to power that device?
 
So....you already tried using the previous owners Admin Password? And can you log into the NVR at all? If his password works at all you might need that to get in the NVR and let it assign that to the cameras?
 
Smilingreen said:
Is your NVR running DHCP? If your NVR has POE ports, I would set the cameras back to factory default and then let the NVR find the cameras and assign them the IP address. If you are running the cameras through a POE+ Switch, then you could make the cameras static with an IP address of your own choosing.
Click to expand...

I am running them directly from the NVR. How do I set the cameras back to default factory? I thought that is what the tftp software does?
 
Flintstone61 said:
So....you already tried using the previous owners Admin Password? And can you log into the NVR at all? If his password works at all you might need that to get in the NVR and let it assign that to the cameras?
Click to expand...

Yep. The NVR appears to be working fine, as I factory re-set it, and then updated to the latest Firmware. I thought this was the best thing to do, being a second hand system.... apparently not!
 
Jayson H said:
Is it normal to have no internet connection when I change the IP address?
Click to expand...
Yes, the PC IP address is now on a different address range than your internet router, so internet traffic isn't able to flow.

Jayson H said:
PC is plugged into LAN 1, camera is in LAN 2 on the router/modem.
Click to expand...
That's fine.

Jayson H said:
Still, the camera isnt being picked up on tftp.
Click to expand...
The Hikvision tftp updater can can be a bit variable in how it responds.
The address the camera normally probes to find the tftp updater, 192.0.0.128 , is set in an environment variable in the bootloader, and has been that standard value for quite a few years.
There have been occasional reports of devices using a different target address, 192.168.1.128 , so it would be worth trying that to see if the camera connects with the PC set to that, assuming there isn't another device on your LAN already using that address..

You will be able to gain access to the cameras and get them connected to the NVR, but it may be necessary to spend some more time if you are willing to do this.

A slight long shot - with the PC network using it's normal settings and the camera on the LAN, powered with 12v, the 'forgot password' link in SADP will export a password reset request XML file, which if sent to Hikvision technical support might get them to send the response file which when imported into SADP will reset the camera password.

An easy enough next step if you want to have a go :
Immediately after power-on, the camera should probe for the availability of the tftp updater on the network.
The traffic associated with that probe can be captured and the details checked with a network capture tool running on the PC, which will see any broadcasts from the camera.
Wireshark is such a tool, very widely used and easy enough to use.
www.wireshark.org

Wireshark · Download

Wireshark: The world's most popular network protocol analyzer
www.wireshark.org www.wireshark.org
 
alastairstevenson said:
Yes, the PC IP address is now on a different address range than your internet router, so internet traffic isn't able to flow.


That's fine.


The Hikvision tftp updater can can be a bit variable in how it responds.
The address the camera normally probes to find the tftp updater, 192.0.0.128 , is set in an environment variable in the bootloader, and has been that standard value for quite a few years.
There have been occasional reports of devices using a different target address, 192.168.1.128 , so it would be worth trying that to see if the camera connects with the PC set to that, assuming there isn't another device on your LAN already using that address..

You will be able to gain access to the cameras and get them connected to the NVR, but it may be necessary to spend some more time if you are willing to do this.

A slight long shot - with the PC network using it's normal settings and the camera on the LAN, powered with 12v, the 'forgot password' link in SADP will export a password reset request XML file, which if sent to Hikvision technical support might get them to send the response file which when imported into SADP will reset the camera password.

An easy enough next step if you want to have a go :
Immediately after power-on, the camera should probe for the availability of the tftp updater on the network.
The traffic associated with that probe can be captured and the details checked with a network capture tool running on the PC, which will see any broadcasts from the camera.
Wireshark is such a tool, very widely used and easy enough to use.
www.wireshark.org

Wireshark · Download

Wireshark: The world's most popular network protocol analyzer
www.wireshark.org www.wireshark.org
Click to expand...

Thanks, I am willing to put as much time as needed into this.

I have downloaded Wireshark and run a capture.

I can see references to Hikvision in the capture, such as:

No. Time Source Destination Protocol Length Info
26 18.637065 192.168.254.6 224.0.0.251 MDNS 342 Standard query 0x0000 ANY HIKVISION IPC-T240H - F28661071._http._tcp.local, "QU" question ANY HIKVISION IPC-T240H - F28661071._psia._tcp.local, "QU" question ANY HIKVISION IPC-T240H - F28661071._CGI._tcp.local, "QU" question ANY IPC-T240H20201222AAWRF28661071.local, "QU" question ANY IPC-T240H20201222AAWRF28661071.local, "QU" question SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local A 192.168.254.6 AAAA fe80::2ea5:9cff:fe03:e711
27 18.637340 fe80::2ea5:9cff:fe03:e711 ff02::fb MDNS 362 Standard query 0x0000 ANY HIKVISION IPC-T240H - F28661071._http._tcp.local, "QU" question ANY HIKVISION IPC-T240H - F28661071._psia._tcp.local, "QU" question ANY HIKVISION IPC-T240H - F28661071._CGI._tcp.local, "QU" question ANY IPC-T240H20201222AAWRF28661071.local, "QU" question ANY IPC-T240H20201222AAWRF28661071.local, "QU" question SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local A 192.168.254.6 AAAA fe80::2ea5:9cff:fe03:e711
28 18.996897 192.168.254.6 224.0.0.251 MDNS 342 Standard query 0x0000 ANY HIKVISION IPC-T240H - F28661071._http._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._psia._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._CGI._tcp.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local A 192.168.254.6 AAAA fe80::2ea5:9cff:fe03:e711
29 18.997117 fe80::2ea5:9cff:fe03:e711 ff02::fb MDNS 362 Standard query 0x0000 ANY HIKVISION IPC-T240H - F28661071._http._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._psia._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._CGI._tcp.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local A 192.168.254.6 AAAA fe80::2ea5:9cff:fe03:e711
30 19.337088 192.168.254.6 224.0.0.251 MDNS 342 Standard query 0x0000 ANY HIKVISION IPC-T240H - F28661071._http._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._psia._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._CGI._tcp.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local A 192.168.254.6 AAAA fe80::2ea5:9cff:fe03:e711
31 19.337306 fe80::2ea5:9cff:fe03:e711 ff02::fb MDNS 362 Standard query 0x0000 ANY HIKVISION IPC-T240H - F28661071._http._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._psia._tcp.local, "QM" question ANY HIKVISION IPC-T240H - F28661071._CGI._tcp.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question ANY IPC-T240H20201222AAWRF28661071.local, "QM" question SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local SRV 0 0 80 IPC-T240H20201222AAWRF28661071.local A 192.168.254.6 AAAA fe80::2ea5:9cff:fe03:e711

What do I do now?
 
Jayson H said:
What do I do now?
Click to expand...
You are doing quite well so far!

Jayson H said:
I have downloaded Wireshark and run a capture.
Click to expand...
That's a bit hard to examine - attaching the capture file (probably have to zip it up) would be easier - however :

There is nothing in that capture where the camera probes for the tftp updater, immediately at power on, so no info can be gleaned about the target address it's looking for.
It's just a set of broadcasts post boot-up.

The steps would be something like :
It shouldn't matter much what IP address is set on the PC, but setting 192.0.0.128 might be the best choice.
With no programs running on the PC except Wireshark, not yet in capture mode, and the tftp updater.

With the camera powered off, and both camera and PC connected to the router LAN ports, click the 'start capture' button in Wireshark.
Immediately power on the camera.
Stop the Wireshark capture after about 20 seconds, use File | Save As, zip it up and attach here.
 
Jayson H said:
There you go!
Click to expand...
Yes indeed! That's much easier.

The capture file has 4 instances of a Hikvision device trying to find a device at the IP address 192.168.1.128
That's very likely your camera doing the initial part of probing for the tftp updater.

As that target doesn't exist - the rest of the probe doesn't take place.

So now, a suggestion:
Set the PC IP address to 192.168.1.128
With the camera powered off, and both PC and camera connected to the router LAN ports, start the tftp updater.
Ensure the digicap.dav firmware file is in the same folder as the tftp updater program.
It would be useful to run Wireshark with a view to capturing the probe attempt.
Click the 'Start capture' button in Wireshark.
Immediately power on the camera, observe the tftp updater window.
Cross your fingers for a connection and download and update!
 
That's looking good. The handshake completes and the file is successfully transferred.
But no 'Update successful' message to indicate the file has been validated and applied.
That's the usual result when the version of firmware isn't a match.
The 'resend' messages should not ideally happen but can be ignored.

What's needed now is to find a valid firmware version.
 
alastairstevenson said:
That's looking good. The handshake completes and the file is successfully transferred.
But no 'Update successful' message to indicate the file has been validated and applied.
That's the usual result when the version of firmware isn't a match.
The 'resend' messages should not ideally happen but can be ignored.

What's needed now is to find a valid firmware version.
Click to expand...

Excellent! so go back to some of the links you provided earlier?
 
You must log in or register to reply here.
Top Bottom