HIKVISION nvr DS-7608NI-SE/P - brick

MacPlus

MacPlus

n3wb
Dec 8, 2014
7
2
Hello!,
I have nvr DS-7608NI-SE/P.

Recently installed: Baseline Firmware_NVR (76NI-SE)_En_V3.0.10 141125
from website: http://overseas.hikvision.com/en/download_89.html

"Support models:
DS-7600NI-SE, DS-7600NI-SE/N, DS-7600NI-SE/P, DS-7600NI-V, DS-7600NI-VP"


After update, my NVR does not respond...?
- after a power on only seems sound "bip bip".
- cameras are properly powered by PoE.
- program SADP does not see the device.
- Tx/Rx LED are blinking
- power LED is ON, status OFF

I tried the program tftpserv, ... does not see the device...

Please help solve the problem.

greet,
in despair,:frown-new:
Maciej
 
Possibly dumb question, in which case apologies:
Did you
4. Modify the PC address to: [FONT=Calibri,Calibri][FONT=Calibri,Calibri]192.0.0.128[/FONT][/FONT][FONT=Calibri,Calibri][FONT=Calibri,Calibri][/FONT][/FONT][FONT=Calibri,Calibri][FONT=Calibri,Calibri][/FONT][/FONT], mask: [FONT=Calibri,Calibri][FONT=Calibri,Calibri]255.255.255.0[/FONT][/FONT][FONT=Calibri,Calibri][FONT=Calibri,Calibri][/FONT][/FONT][FONT=Calibri,Calibri][FONT=Calibri,Calibri][/FONT][/FONT]. (Fig. 8). This step is very important because this tool sets the server IP address to: 192.0.0.128.
Click to expand...
 
Yes, i have done according to the instructions of the program...does not see the device... :-(

edit:
which cable rj45 I must use?

cross?..
 
Last edited by a moderator:
OK... I have a crosscable.

and unstable connection, take a look:

attachment.php


[2014-12-09 20:49:45] TFTP server[192.0.0.128] initialized
[2014-12-09 20:51:08] TFTP server[192.0.0.128] initialized
[2014-12-09 20:52:08] Device[192.0.0.64] test tftpserver
[2014-12-09 20:52:52] Connect client failure,0
[2014-12-09 21:05:52] TFTP server[192.0.0.128] initialized
[2014-12-09 21:07:06] Connect client failure,0
[2014-12-09 21:07:32] TFTP server[192.0.0.128] initialized
[2014-12-09 21:08:27] Connect client failure,0
[2014-12-09 21:09:07] TFTP server[192.0.0.128] initialized
[2014-12-09 21:09:37] Device[192.0.0.64] test tftpserver
[2014-12-09 21:10:21] Connect client failure,0
[2014-12-09 21:11:43] TFTP server[192.0.0.128] initialized
[2014-12-09 21:13:16] TFTP server[192.0.0.128] initialized
[2014-12-09 21:13:40] Device[192.0.0.64] test tftpserver
[2014-12-09 21:27:24] TFTP server[192.0.0.128] initialized
[2014-12-09 21:28:20] TFTP server[192.0.0.128] initialized
[2014-12-09 21:28:54] Connect client failure,0
[2014-12-09 21:29:28] TFTP server[192.0.0.128] initialized
[2014-12-09 21:29:42] TFTP server[192.0.0.128] initialized
[2014-12-09 21:29:59] TFTP server[192.0.0.128] initialized
[2014-12-09 21:30:10] Connect client failure,0


firewall is off.

ideas?
 

Attachments

  • ping.png
    ping.png
    87.5 KB · Views: 899
We (or at least I) kinduv assumed you were following that procedure, without success.
For the benefit of the community, as it may help others in a similar situation, what did you do differently that gave a successful outcome?

On the face of it from what you have shown - the NVR was communicating OK with the TFTP server. Did you assume that it simply tries continuously to connect to the TFTP server, as opposed to trying for a while, moving on down the boot cycle, failing for some (unknown reason) and restarting and continuing the cycle?
 
Ive got the same problem with bricked hikvision, same model. Does it matter - cross cable or not?
The problem is the same, firewall is off.
[2014-12-09 21:09:07] TFTP server[192.0.0.128] initialized
[2014-12-09 21:09:37] Device[192.0.0.64] test tftpserver
[2014-12-09 21:10:21] Connect client failure,0
Maybe try via switch? Because while its booting up -windows show many times cable connected/disconnected.

 
I I had cross cable (computer > NVR)




- Connect the cable via computer - nvr
- Turn on the NVR

- In the windows "RUN" enter the text ping 192.0.0.64 -t
If the ping will show one or more result of "reply from 192.0.0.64..." > the connection is correct (the cable is good)

- Start "TFTP server" (you need to have the firmware file "digicap.dav" in the same directory as the program)
and see the program...

program will display "failure" or nothing within a 15 seconds or more... go to restart NVR (2 seconds off)
and again
program will display "failure" or nothing within a 15 seconds or more... go to restart NVR (2 seconds off)
and again..

you do not need to restart the program


I did a 4 time - restart NVR


program will display"
[2014-12-20 16:59:51] Device[192.0.0.64]test tftpserver
[2014-12-20 16:59:59] Connect client success [192.0.0.64]Success
[2014-12-20 16:59:59] Start file transmitting[C:\Auto Update\digicap.dav]
[2014-12-20 17:00:44] Completed file[C:\Auto Update\digicap.dav] transmit
[2014-12-20 17:01:05] Device[192.0.0.64]system update completed!"

good luck!!

Maciek
 

Attachments

Last edited by a moderator:
  • Like
Reactions: alastairstevenson
Hey MacPlus, I did the exact thing you did here, upgrade to a baseline firmware and now I can't even log into the web GUI. I am using the TFTP Auto Update program but it is not detecting the NVR. I have a constant ping going to it and the pings are responding. The only thing that is different from your procedure is my laptop is not connected directly to the NVR. Although, my NVR and my laptop are connected to the same switch within the same subnet of 192.168.0.xxx.
 
Tried, but still had Connect client failure,0
IP settings was exactly how they should, device was pingable for some time.
 
I down loaded the latest firmware 3.0.10 and installed it using a USB drive per the user manual instructions on page 102. Simple! No cables to mess with. Took about one minute to update and maybe another minute to reboot. Up and running, no problems so far.

Only thing I noticed so far was a rather large exclamation point in the lower left corner of the monitor. Apparently some settings get reset. Had to go to the Configuration, Exceptions screen and unselected some items, such as alarm input triggered and motion detection. I still get the little bell and recording symbols in the upper right corner of each view, but now the large exclamation point does not keep popping up. :)

Recordings still there, all cameras show up.
 
You cant if unit it bricked.
Tried via switch, update went fine! dont know what was the problem, tried different cables even cross.
 
Last edited by a moderator:
You must log in or register to reply here.
Top Bottom