TFTP and password will 12345 or correct use original algorithm
All is work.
There are just differences in the use of the algorithm for the IPC and DVR, NVR!
TFTP and password will 12345 or correct use original algorithm
All is work.
There are just differences in the use of the algorithm for the IPC and DVR, NVR!
I have just tried a firmware update with the Hikvision TFTP tool, however get the error
[2015-05-11 18:53:11] Open file failure[C:\Auto Update\econt_Vision-AV2000]
The firmware file in the directory is digicap.dav, so I am unsure where this filename is coming from. A quick Google search lists others with the same issue but no immediate solution.
I may be best to wait for the reset code from the seller.
Nevermind about it. It's after correct boot your NVR.
This mean that your NVR doesn't catch TFTP Server sowtware via 69 UDP port!!!
Make sure that you have one LAN adapter with correct IP and of couse check firewall and etc.
Last edited by a moderator:
alastairstevenson
Staff member
That's not an error - it's just a loose end lying around in the firmware that appears after it's fully booted.
Did you follow the Hik instruction pages on the use of their TFTP tool?
You should see a log entry in TFTP when you start the NVR showing the NVR 'testing' the TFTP tool. If that doesn't show, something in your setup is not correct.
It's important that both the PC, with its IP address of 192.0.0.128, and the NVR, are both connected to live ports on a switch or router for the whole process.
Олег!
Да. Почему-то не срабатывает у него через tftp и его смущает ареконовская надпись и сбросить пароль не может через опубликованный алгоритм.
Вообщем всё как обычно
Как сам?
Last edited by a moderator:
Да, это я в курсе, но тут как всегда вопрос задают без каких либо подробностей о деле. Вот я про что!
Потому и написал, что нужно указать корректный ip адрес на ПК.
Пусть трахают мозг техподдержке и продаванам чинайским, может что-то дойдёт до них и до тех и до других
Олег!
Раньше да и задачи интересные ставились, хоть было с чем разбирать, а сейчас каждый мнит себя якобы хакером отломившем хик
Но всё итак просто, как и полтора года назад
Ничего особо не поменялось. а они всё плетуться в хвосте.Да и знания, которые он и тут якобы делятся, они путают с информацией, которую реально валят друг на друга, да и обижаются всякий раз на то, что что-то им не рассказываешь. Думать-то не научены!!! Им только фаст-фуд подавай искусственный, чтобы только глотали, а желудку переваривать не нужно т.к. оно само раствориться
alastairstevenson
Staff member
iTuneDVR - any useful suggestions to fix this problem in a camera bootup. mtdblock11 holds initrd ramdisk. Why does not the 5.2.5 firmware try initrd format instead as it usually does?
alastairstevenson
Staff member
That makes sense. During camera and NVR startup, the LAN interface changes state a couple of times, so anything on the other end of the crossover cable would react to the 'link down' in various ways, the very least of which would be a delay in getting back to the configured settings, and missing the packet from the camera or NVR.
alastairstevenson!
What the problem?
There did you catch this message log?
What did you do?
alastairstevenson
Staff member
It was from this thread here:
http://www.ipcamtalk.com/showthread.php/3500-Hikvision-DS-2CD2132F-IS-bricked-in-search-of-help
There are kernel log attachments and some files.
Any insight into the cause or solution would be welcome.
http://www.ipcamtalk.com/showthread.php/3500-Hikvision-DS-2CD2132F-IS-bricked-in-search-of-help
There are kernel log attachments and some files.
Any insight into the cause or solution would be welcome.
alastairstevenson!It was from this thread here:
http://www.ipcamtalk.com/showthread.php/3500-Hikvision-DS-2CD2132F-IS-bricked-in-search-of-help
There are kernel log attachments and some files.
Any insight into the cause or solution would be welcome.
I have this fresh IPC DS-2CD2132F-IS( manuf. after 2015) and all work fine!
Hardware region change or software patch - all work perfetly in my solution.
TFTP with 5.2.5 work and i can't see any problem with it!
What can i say?
Of course i open this IPC and connect to TTL and watch boot log and etc...
I think it's RAM trouble and need to return this IPC to seller, get money back and forget about it!
Last edited by a moderator:
alastairstevenson
Staff member
OK, thanks for the comments.
Could be faulty RAM, I haven't thought of that.
Could be faulty RAM, I haven't thought of that.
So you've figured out which byte range is now being used for the hardware descriptor block checksum? Or are you just adding here and subtracting there?
astairstevenson!
This question has long been settled and I'm not going back to him.
And if you add and subtract, then we must do it correctly and in the right places!
I think that soon the Chinese will close these loopholes, or a change algorimty at least! No need to disclose something as it soon will not help!
So the risk to buy goods in China so why not return the defective goods. Chinese hope that will not be returned.
This question has long been settled and I'm not going back to him.
And if you add and subtract, then we must do it correctly and in the right places!
I think that soon the Chinese will close these loopholes, or a change algorimty at least! No need to disclose something as it soon will not help!