Регистратор hiwatch коды ошибок

Столкнулся с проблемой на регистраторе Dahua.

имеем продвинутый гибридный видеорегистратор Dahua. Регистратор находится в здании №1, локалка 192.168.2.0/24, в качестве шлюза Mikrotik.На этом микротике поднят vpn-client l2tp/ipsec на второй микротик (VPN-сервер), находящийся в здании №2.

На втором микротке локалка 192.168.1.0/24.

Между собой микротики устанавливают VPN-канал, внутри которого IP 10.20.30.0, и там и там прописаны встречные статические маршруты. Компы из обеих сетей видят друг друга без проблем.

На регистратор Dahua из локалки заходит без проблем, а вот из удаленной сети зайти не получается. SmartPSS видит серийник устройства, видит количество портов, но подключиться не может.

То же самое с доступом по www, из локалки все ок, а из удаленной сети страница web-service загружается, но ни одна учетная запись не подходит, ругается что “пользователь не существует”. Пробовали разных пользователей, создавали новых, пробовали режимы tcp/udp/lan/wan – безрезультатно.

Открывать порты наружу не вариант. Во-первых, роутер все-равно за NAT провайдера, т.е. без белого реального IP. Во-вторых, открывать порты наружу не комильфо, т.к. сеть получится не защищенной и сам дахуа потенциально может содержать дырки.

У кого какие идеи и мысли?

Get the error codes via OpenSDK_GetLastErrorCode and get the error code information via OpenSDK_GetLastErrorDesc. The API only returns 0 and -1 by default (except some special API). The error code of SDK is listed according to modules. Major and frequently-occurred error codes are shown below.
error code is defined in the header file of OpenNetStreamError.h.
return via information callback function, refer to header file of INS_ErrorCode.h for details.

Hikvision DS7608-NXI-I2/8P/4S

• deepskydiver
• hikvision

  hikvision accessories

  network

  network cameras

  networking

So I’ve had some quite random success ignoring the switch and port 5 on the NVR started working.
The labels I’m using are:

1 2 3 4
5 6 7 8

For these 8 ports I still can’t get a camera to work in ports 6 or 7, but port 5 has started working.

1A 2B 3C 4D
5F 6- 7- 8E

I have one camera, G with no way to connect.

Here are some other clues:
When the ports indicate there is traffic to a camera it always show up on the NVR itself – but not always on the Windows App and sometimes when it does the label doesn’t match. I noticed the cameras have two names. I had used the Windows app prior to the cables being scrambled so this may be a clue.

As a result I connected the camera matching the name the Windows app had for that port/connection. Hoping that might help me connect everything correctly.

But the camera in port 8 doesn’t show up at all in the windows app, but it does when looking directly at the NVR.
The error I get is “Reconnecting .. The stream type is not supported by the device. Error code: OpenSDK StringError(110)”.
I’ve checked and from what I can find it’s set to H264 and Auto in terms of resolution – just like the other cameras. Incidentally, that’s the same error i get for the camera when it isn’t physically connected – and the other camera which isn’t currently physically connected.

Here are some other clues:
When the ports indicate there is traffic to a camera it always show up on the NVR itself – but not always on the Windows App and sometimes when it does the label doesn’t match. I noticed the cameras have two names. I had used the Windows app prior to the cables being scrambled so this may be a clue.

But the camera in port 8 doesn’t show up at all in the windows app, but it does when looking directly at the NVR.
The error I get is “Reconnecting .. The stream type is not supported by the device. Error code: OpenSDK StringError(110)”.
I’ve checked and from what I can find it’s set to H264 and Auto in terms of resolution – just like the other cameras. Incidentally, that’s the same error i get for the camera when it isn’t physically connected – and the other camera which isn’t currently physically connected.

I think I understand, are your camera cables A, B, C etc?

You can also remotely configure the NVR using IVMS4200, see attached screenshot from the maintenance & management tab

Administrator

I believe I know the company it was purchased through and have given them that. I’ve had no response from that company. It’s only small and might not be trading now. I’ll keep my fingers crossed. But will that allow me to resolve the problem?

Find and update company information – GOV

Free company information from Companies House including registered office address, filing history, accounts, annual return, officers, charges, business activity

we haven’t yet had our hands-on one of these AcuSense NVRs and the network setting your describing does not appear to be available on other models, do you have a screenshot of where you are seeing this setting?

Sorry, I thought you meant you had a particular network address box in the NVR settings that was empty and I couldn’t figure out which address your description related to, the information you describe should be easily visible in the NVR network settings.

IPv4 Subnet Mask – 255.255.255.0
Internal Network Card IPv4 – 192.168.254.1 (this is the IP range that the PoE ports use to activate directly connected cameras)

I’ve resolved the issue with the cameras. And for those who find themselves in a similar position: here’s how:

I certainly don’t know what I’m doing but it’s clear the company who installed it did not either. The hikvision switch is a red herring. It’s not needed.
I remembered that in experimenting I’d changed a setting on port 5 – to make it plug and play rather than manual. This is why it started working. When I made the same change to ports 6 and 7 they worked too – all ports work as you’d expect.

I then found out that for both the Windows and Android app the cameras need to be sequential or the ones after the gap do not appear. With no camera in port 7 the last camera could be seen in some settings but not the live views or alarms.

So that was it: set the ports via the monitor on the NVR to be Plug and Play and make sure the cameras are in contiguous ports. It’s not the first issue I’ve had with the house. There were dozens of meters of cables and other devices in the cabinet that I gradually cleaned up when they weren’t needed. And now that switch can go too and everything is working as it should be.

Thanks for your help everyone. I got a reply on the password from Hikvision too – but the file they supplied gave me error 2022. So I’ve asked again.

Similar threads

5/7 cameras have successfully been added, not sure why the other two are giving this error as the settings/configuration appear identical for all of them.

Have you tried adding the remaining cameras directly to your Hik-connect account through the Hik-Connect portal?

Hi Dan, thanks for the suggestion. I tried adding the cameras directly in the portal, after entering the serial number it tells me the camera has been added. But the camera is not visible in the hik connect portal.

But I now have six cameras on the Hik Connect app on iOS, and five on the portal.

I also tried adding the camera through the iOS Hik Connect app and it tells me that the camera has been added but doesn’t appear.

I’ve tried refreshing multiple times and logging out and back in.

For the camera that says it has been added, I think you are going to have to try unbinding the device using SADP and then try adding it to the Hik-connect portal.

Thanks Dan, I’d like to give that a try. But since I upgraded SADP I can’t get any of my cameras to show. They are all accessible through IVMS-4200 and direct via IP on the same computer.

I’ve ran sc query “npf” in the command line and it shows that it’s running, I’ve also tried uninstalling and reinstalling to no joy.

I”ve also tried installing Npcap: Windows Packet Capture Library & Driver and win10 cap but

I”m pretty sure it’s an issue with having the right NPF but haven’t been able to get it to work.

We have seen issues previously, not just with Hikvision’s software, where the software has to be added to the firewalls safe software list and be given permission to pass & receive data through the firewall, So I would recommend trying to add the SADP tool to that safe software list.

Xe0000105 is an error occur when your Hikvision Device (IP Camera, NVR, DVR) does not connect with Hik-Connect Server. when Hikvision Device fails to establish a correct communication protocol with Hikvision Hik-Connect Server this error occur on android phone screen.

Simillar issue occur when you see these errors Offline (0Xe0000104), Offline (0Xe0000108), Offline (0Xe0000105)

How to Solve Offline (0Xe0000104), Offline (0Xe0000108), Offline (0Xe0000105)

First go to your Hikvision Device Network settings. you can use a windows pc to access hikvision device and change the network setting.

Here is the the path to enter into network settings:

Input This DNS Setting in your Hikvision Device

Preferred DNS Server: 8.8.8.8Alternate DNS Server 8.8.4.4

After setup the DNS Severs please save setting and restart your Hikvision Device.

After restart check the Hik-Connect Online Status.

if all configuration is correct, Hik-Connect Status will be Online and you can smoothly run all your Cameras on Hik-Connect APP.

Downlaod Hik-Connect APK App

Приветствую всех. Я в камерах самоучка и дилетант, но тк развернул уже не одну сеть видеонаблюдения в клубах, какой-то опыт появился и хочу поделиться, тк сам мучался от этой ошибки 153 в программе просмотра для iOS Ivms 4500. 

Нашёл одну из причин ошибки 153. Регистратор Hikvision dsn108p, камеры тоже родные. Все проверил, порты открыты извне, но все равно писало эту ошибку. Оказывается, причин может быть две:

1) Не проброшен внутренний айпи регистратора во внешнюю сеть. Оказывается он может сам слетать в роутере микротике, если верить нашему провайдеру. Но странно что порты не слетели проброшенные. Проверить можно — вбив внутренний айпи регистратора в программу просмотра и подключившись по вайфай к тому же роутеру. Если показывает в этой внутренней сети — значит слетел проброс внутреннего айпи или портов. Насчёт портов не уверен что номер ошибки тот же. Порты можно проверить на внешних сайтах.
2) Много раз был введён неправильный пароль в программе удаленного просмотра (ivms4500 для ios). При этом регистратор блокирует все аккаунты с данного айпи. Придётся подождать пока не разблокируется. Или зайти с другого айпи.

Так как в поиске по этой ошибке выносит сюда, написал здесь, чтоб не плодить темы. Модератор может перенести.

На чтение 5 мин. Просмотров 147 Опубликовано 15.12.2019

The Hikvision code error 153 is generated when there are too many attempts to login into the Hikvision camera or DVR/NVR by using the wrong password through the iVMS-4500 smartphone app.

Sometimes the password is incorrectly typed into the smartphone and the app sends it to the device more than once and that counter backs with an error that locks the camera for (usually) 30 min to protect against a possible hacker attack. To solve error code 153, you need to the device or wait 30 minutes.

This error shows when the device is hit with the wrong password many times via the iVMS-4500 phone app. Eventually, it enters into lockdown to protect the user credentials. You’ll just see there [Code error: 153] (as shown in the picture below).

Try the following suggestions to fix the problem.

Reboot the device

In many cases, this is the easy solution for code error 153. Simply reboot or restart the camera or the DVR/NVR. Once the machine is back on, try to enter the username and password again, hopefully, there will be no mistake this time.

Wait 30 minutes

Another way to solve code error 153 is by waiting at least 30 minutes until the camera is ready again to let the app authenticate again.

As we mentioned before, this error shows up when someone is using the wrong password to access the security device. By waiting 30 minutes, you’re allowing the camera’s protection layer to time out.

Access your device from a computer

You can unlock the device by accessing it through a computer that uses a different IP address. Go to Remote configuration > System > Login Security to unlock the IP used by the smartphone.

Update the firmware

It has been reported that, sometimes, the issue is solved by updating the firmware on the IP camera or the NVR/DVR in question, especially if you’re units are old products. Additionally, make sure the phone app (iVMS-4500) is up-to-date.

Does this error mean that someone knows your password?

Security-wise, should you be concerned when you get this type of message? What if you’re using the right password but you’re still getting code error 153?

That means that perhaps someone else is trying to access your camera/Hikvision system by sending a different combination of username and password (trying an incorrect account). You never know.

However, the IP camera or Hikvision DVR/NVR will lock itself for 30 minutes in order to prevent this type of situation. It’s recommended to check your network security or ensure that your password is not compromised (use a combination of letters, numbers, and special characters).

How to fix error code 153 in LTS cameras

Hivkison sells its products to other companies that rebrand them and resell them to end-users (these products are called OEMs).

And, since it’s the same software, error 153 may show up on various camera brands that are not directly labeled as Hikvision, for example, the LTS cameras.

To fix error code 153 in LTS cameras, navigate to the Security Service configuration section and uncheck the box that says “Enable Illegal Login Lock”. If the issue still persists, contact the LTS and update the firmware on your device.

в оборудовании Hiwatch ошибка при воспроизведении «ПОТОК ЗАШИФРОВАН»

При попытке просмотра в реальном времени устройства Hiwatch, которое поддерживает доступ к платформе Hik-Connect, появляется сообщение об ошибке «поток зашифрован».

Это означает, что

Включена функция шифрования потока.

Для решения проблемы

требуется ввести пароль по следующему пути в iVMS-4200 и перезапустить режим просмотра в реальном времени:

Управление устройствами -> Группа -> Выберите устройство -> Изменить -> Введите ключ

На веб-интерфейсе устройства:

Настройки -> Локальные -> Ключ шифрования -> Введите ключ

Ключ шифрования — это код подтверждения устройства, который вы можете найти на устройстве. Если устройство не имеет кода подтверждения, пароль по умолчанию — ABCDEF.

Вы можете изменить пароль или отключить функцию шифрования потока через веб-клиент Ezviz или мобильное приложение Hik-Connect.

Как отключить функцию шифрования потока через учетную запись Ezviz:

1) посетите сайт www.ezvizlife.com и войдите в свою учетную запись

2) Перейдите по следующему пути: Управление системой-> Управление устройствами-> Мое устройство. Перейдите в настройки устройства и отключите шифрование потока.

3) Код для отключения функции будет отправлен на ваш телефон или по электронной почте.

4) Введите полученный код, чтобы отключить шифрование потока.

Как отключить функцию шифрования потока через приложение Hik-Connect либо Ezviz:

1) Запустите приложение Hik-Connect и войдите в свою учетную запись.

2) Ваше устройство-> щелкните на устройстве-> Конфигурация-> отключить шифрование потока.

3) Код для отключения функции будет отправлен на ваш телефон или по электронной почте.

4) Введите полученный код, чтобы отключить шифрование потока.