need help on this problem

donnexx

n3wb
Joined
Apr 27, 2015
Messages
19
Reaction score
0
my problem is that my nvr wont display anymore after i update the firmware from 3.7.10 to i don't know what firmware given from techsupport of hikvision.
when i tried to ping the ip add of nvr is okey i mean i getting reply without time out.
i also tried to open it using ivms 4200 using my laptop and thur IE but failed


here some info

laptop and nvr connected using straight rj45 connector i also try cross connection but same result


laptop ip add, 192.168.1.32
sub net. mask 255.255.255.0
gateway 192.168.1.1




nvr ip add 192.168.1.42
subnet mask 255.255.255.0
gateway 192.168.1.1


hope anyone could help me regarding on this


 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,986
Reaction score
6,806
Location
Scotland
What happened using the TFTP recovery method as suggested by @bp2008?
What is the exact model number of the NVR?
What firmware have you downloaded and tried via TFTP?
What happens if you try a telnet connection to the NVR IP address?
What shows using the VGA/HDMI interface?
 

donnexx

n3wb
Joined
Apr 27, 2015
Messages
19
Reaction score
0
What happened using the TFTP recovery method as suggested by @bp2008?
What is the exact model number of the NVR?
What firmware have you downloaded and tried via TFTP?
What happens if you try a telnet connection to the NVR IP address?
What shows using the VGA/HDMI interface?


What shows using the VGA/HDMI interface?[/QUOTE]
black display after showing the logo og hikvision
What happened using the TFTP recovery method as suggested
im still looking to find way cause i cannot pin the nvr using 192.0.0.64 (ip of my laptop 192.0.0.128)
What happens if you try a telnet connection to the NVR IP address?
not yet try this one
What is the exact model number of the NVR?
model DS-7604NI-SE/p


HOPE U CAN HELP ME WITH THIS.

can u give me the exact step on using TFTP
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,986
Reaction score
6,806
Location
Scotland
Agreed, and generally the NVR would only use 192.0.0.64 for a few seconds during the boot process while it tests for a listening TFTP server, after which it moves on.
This can be demonstrated by watching a continuous ping (eg ping -t 192.0.0.64) whilst powering on the NVR.
 

donnexx

n3wb
Joined
Apr 27, 2015
Messages
19
Reaction score
0
guys thanks response #alastairsteveson #bp2008


as today i using the TFTP server to update the server
in 30 mins. that is the view in my screen

how long this could be done is updating via TFTP



the nvr is directly connected to my laptop using cross cable and the ip of my laptop 192.0.0.128

the TFTP folder also is in root. located at C:?TFTP auto update
the date firmware is in the folder of TFTP



any comments guys
 

Attachments

aster1x

Getting the hang of it
Joined
Jul 8, 2014
Messages
400
Reaction score
88
It is better to use any switch or hub to connect the NVR and the laptop alone (nothing else in the switch and with static IP assignment in the laptop LAN port configuration) in order to maintain the LAN port of the equipment alive. Otherwise, when you use a cross cable and the NVR switches its LAN port OFF and ON, the laptop assumes that there is no network and assigns a local IP to the laptop port (127.0.0.1) and by that time the NVR boot has skipped the TFTP server detection in the laptop, and therfore the is no upgrade.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,986
Reaction score
6,806
Location
Scotland
That's good advice - it solved someone else's similar problem. The switch can just be your normal switch. No need to disconnect anything.
 
Top