New firmware for Hik NVR's 76 77 96 NI-I

[alastairstevenson]

Have you tried this on your 78x??

I must admit I haven't tried the tftp updater on an NVR for ages - it's been easier and more effective just hooking up to the serial console. Especially when you can get directly to the bootloader by bypassing the captive update dialogue.

 

[Rebem]

Upgrade went well here on a DS-7608NI-I2 / 8P but I have a few issues with Chrome and RSTP viewing on a Raspberry Pi seems to be broken. In Chrome I can't view LiveView - keeps bringing up an error about "Multiscreen mode only accepts Liveview and Playback at sub-stream" which it's set for. Also, I can't view any "Local" configuration items - they're all blank. However it seems to work just fine in IE.

Not sure what's going on with RTSP - just about to investigate it but it just crashes the Raspberry Pi 3 (running Kodi and the Surveillance Room addin). Maybe sub-streams are handled differently now??

 

[monaro]

"Have you tried this on your 78x??"

I tried it on my box but found it didn't recover it. I'm going to use another computer to try again.

 

[whoslooking]

what do you mean didn't recover?? 15 bleeps boot loop?

 

[monaro]

The tftpserve program just keep saying something like initialise-success or something similar. Left in running for a hour or so.

 

[alastairstevenson]

The tftpserve program just keep saying something like initialise-success or something similar.

What did it say for the IP address that it initialised on?

Left in running for a hour or so.

It doesn't do anything apart from responding to any requests it gets.
Like the probe for its existence that a Hikvision device does when the device is powered on.

 

[monaro]

I couldn't get it to initialize with the ip address I configured it (the one you said I needed to use) with hence why I will use another computer.
Cheers

 

[alastairstevenson]

I couldn't get it to initialize with the ip address I configured it (the one you said I needed to use)

What address did it say was in use?
It does need to be 192.0.0.128 to be available as an updater, that's the address the the Hikvision devices probe on power-on.

 

[tangcla]

Help required please, @alastairstevenson - I went from 3.4.93 to 4.1.50. Genuine Australian unit from a distributor.
Flashed via web interface, system seems to have rebooted but I was unaware because it wasn't responding to pings on my network (192.168.1.50)
Did some investigating and turns out the system had reset to 192.0.0.64 as it was visible via SADP when connected directly to my desktop via LAN bypassing my (managed) switch.
Tried to use TFTP Server to reflash 4.1.50 but it never gets to success:

[2018-05-25 17:04:35] Connect client[192.0.0.64] success
[2018-05-25 17:04:35] Start file [C:\TFTP\digicap.dav] transmitting
[2018-05-25 17:06:41] Connect client[192.0.0.64] success
[2018-05-25 17:06:41] Start file [C:\TFTP\digicap.dav] transmitting

This loops for a few times, it takes about 2 minutes before it loops, and I never see any confirmation that the file is completed.

I also occasionally get a string of "Resend required" messages too.

Please, any suggestions would be greatly appreciated.

 

[alastairstevenson]

[2018-05-25 17:04:35] Connect client[192.168.0.64] success

That's an odd IP address - usually the probe for the tftp server comes from 192.0.0.64
A tftp update of the same firmware should clear the configuration back to defaults and fix the problem.
But how to get the tftp update to work if it's misbehaving? Without resorting to a serial console connection.
Long shot suggestion : Change the PC subnet mask to 255.255.0.0 and see if the tftp updater behaves any better.
Presumably the PC IP address is 192.0.0.128

 

[tangcla]

That's an odd IP address - usually the probe for the tftp server comes from 192.0.0.64
A tftp update of the same firmware should clear the configuration back to defaults and fix the problem.
But how to get the tftp update to work if it's misbehaving? Without resorting to a serial console connection.
Long shot suggestion : Change the PC subnet mask to 255.255.0.0 and see if the tftp updater behaves any better.
Presumably the PC IP address is 192.0.0.128

Oops. That was my mistake. I hand-typed it.
Device IP is 192.0.0.64 and desktop IP is 192.0.0.128, 255.255.255.0 (but will try it again later with 255.255.0.0)

 

[tangcla]

That's an odd IP address - usually the probe for the tftp server comes from 192.0.0.64
A tftp update of the same firmware should clear the configuration back to defaults and fix the problem.
But how to get the tftp update to work if it's misbehaving? Without resorting to a serial console connection.
Long shot suggestion : Change the PC subnet mask to 255.255.0.0 and see if the tftp updater behaves any better.
Presumably the PC IP address is 192.0.0.128

Actually, before I attempt that, I did request a password reset using SADP.
If I power cycle the NVR, will the password reset request be invalidated?

 

[alastairstevenson]

but will try it again later with 255.255.0.0

That was only valid based on the (incorrect) IP address.

If I power cycle the NVR, will the password reset request be invalidated?

Yes, the start time is part of the request data.
The tftp updater can be troublesome on a direct connection to a PC - best to have both connected to the switch as normal.

 

[tangcla]

Thanks. I might wait until say Tuesday for the reset file from Hikvision (it's Friday night now) and attempt this again if no response .

 

[Joel Fennah]

Hi Guys, I have the same issue with a NVR. After the American FW was installed on a genuine Australia NVR. Let me know if you have any success.

 

[tangcla]

Seems like us Aussies have some issues here!!

 

[Joel Fennah]

I've just tried to do TFTP update but the NVR didn't appear to attempt to talk to the TFTP server, I want to try talking to the NVR via serial port but had no success, possibly because it's dodgy cable, going to try and get a new one from work tomorrow.

 

[marku2]

4.1.50 should have been done at the nvr with a screen hooked up as it’s that new format