Resolve iVMS-4200 NVR connectivity and authentication issues

draft · equipment nvrfirewallnetwork

Generated by docuprocessor (prompt article/v3) · 2026-04-22 14:36

Source thread

thread_id: spaces/AAAA05BdS6s/threads/V__qaTaODqs · 26 msgs · first 2024-12-27 · participants: Tech ATech B

Tech A 2024-12-27 16:03

QQ; for Pediatric Dentistry of Bronx Ortho - PDS, trying to set up the iVMS-4200 camera, but when we are trying to log in to set it up, we are getting "incorrect password", we tried the one we have in bitrix tho.

Tech A 2024-12-27 16:03

(no text)

image/png image.png

**iVMS-4200 software login dialog is displayed on screen.** The user has entered the username "admin," a masked password, and CAPTCHA text "NAA2" (matching the displayed CAPTCHA image). The "I Agree Terms of Service and Privacy Policy" checkbox is checked, and the system is showing "Not Log..." status in the top toolbar, indicating the client is currently not authenticated.

Tech B 2024-12-27 18:00

who is this for? You should not be using admin's account to setup the software.

Tech B 2024-12-27 18:01

for each user, you should be setting up a separate account which can be deactivated if the user leaving the company etc.

Tech A 2024-12-27 18:52

Right, this SS was one of the Users out of 4 i tried to log in.

Tech A 2024-12-27 18:52

this is for Pediatric Dentistry of Bronx Ortho - PDS

Tech B 2024-12-27 19:26

the ip address of the NVR should be 172.17.184.148 but I cannot ping it

Tech B 2024-12-27 19:27

whats the status of it?

Tech A 2024-12-27 19:28

is not 172.17.184.88?

Tech B 2024-12-27 19:35

(no text)

image/png image.png

**WatchGuard Fireware Policy Manager** is displayed via a LogMeIn remote session, showing the firewall policy table for configuration file **PDS-BRONX-ORTHO.xml**. **Row 4 ("CAMERAS OUT")** is highlighted, configured as policy type with source **172.17.184.148**, destination **Any-External**, and ports **tcp:80, tcp:443**, with **App Control and Geolocation set to None**. Additional visible policies include NVR (tcp:8888), FTP (tcp:21), DR-BGP (tcp:179), HTTP-proxy (tcp:80), HTTPS-proxy (tcp:443), and BOVPN entries; rows 4, 9, 10, and 12 display a document/edit icon in the Action column indicating IPS or logging modifications.

Tech A 2024-12-27 19:35

Since we could not gett it work through the HIK-Connect log in, we tried the Ip/ domain option, did a SNAT and firewall policy for port 8000, but still not working

image/png image.png

The screen displays a device management interface with an **Edit dialog** open, showing the following configuration: **Adding Mode: IP/Domain**, **Name: Cameras**, **Address: 172.17.184.88**, **Port: 8000**, **User Name: operator**, and a masked password field. The background table shows a single device entry labeled "Cameras" with connection type **IP/Domain** and partial address **172.17.184.88.9...**, classified as **Encoding D...** device type. No error codes or indicator lights are visible; TLS is unchecked.

Tech B 2024-12-27 19:36

port 8000 is not even used. I believe its 8888 for mobile and 9000 for the web

Tech B 2024-12-27 19:36

are you able to login to the web interface?

Tech A 2024-12-27 19:37

this is the one i lgged in.

image/png image.png

The screen shows a **Hikvision NVR Web UI** (Live View) accessed via browser at **172.17.184.88:9000/doc/page/preview.asp**, labeled **"PDS-BRONX"** in the browser tab. The live view window displays a **black/blank feed** with a yellow border, indicating no active video signal is rendering. The left panel lists **6 active "IP Mini Dome"** cameras and **2 offline/unassigned channels** ("IPCamera 07" and "IPCamera 08"), with the PTZ preset panel visible on the right showing **Preset1 through Preset14**.

Tech B 2024-12-27 19:39

oh, yes, you are correct, i looked at the wrong policy

Tech B 2024-12-27 19:44

hm...

image/png image.png

**Administrator Command Prompt – Ping 172.17.184.88 -t** The screen shows continuous ping output to **172.17.184.88**, with intermittent successful replies (bytes=32, TTL=62, times ranging from **12ms to 2044ms**) interspersed with **"Request timed out"** messages and multiple **"Reply from 169.254.184.26: Destination host unreachable"** responses. The pattern indicates highly inconsistent connectivity, with several consecutive timeouts and occasional unreachable replies from a secondary IP (**169.254.184.26**) before successful replies resume.

Tech B 2024-12-27 19:45

is that IP within the DHCP range?

Tech B 2024-12-27 19:47

no, its outside. not sure why there is an issue with the ping

Tech B 2024-12-27 19:48

im pinging from the data center server. are you having the same issue when pinging locally?

Tech A 2024-12-27 19:50

Well earlier when i tried i could ping it fine from one of the PCs, but then it was unreachable even tho i was logged in on the Web GUI

Tech B 2024-12-27 19:52

i know for a fact it was working last week as I was able to set it up on the phone and also was able to access from my PC.

Tech B 2024-12-27 19:52

could be a damaged cable maybe? Have them reconnect it

Tech B 2024-12-27 22:12

Thsi is fixed, we rebooted the device and the switch

Tech A 2024-12-27 22:13

let me check

Tech B 2024-12-27 22:13

i checked already

Tech A 2024-12-27 22:36

had to set up a new encoding channel to set the live view but YEAH is G2G now. Thanks Sergey

image/png image.png

**iVMS-4200 NVR Client – Multi-Camera Live View** The system displays **"PDS BRONX ORTHO – BXORTHO-FD02 – Remote Control – Monitor 2"** in the title bar, running the **iVMS-4200** client software with **6 active IP Mini Dome camera feeds** timestamped **12-27-2024 Friday 05:35:12–05:35:22 PM**. All feeds are rendering in **night vision (IR monochrome mode)**; the top-left enlarged feed shows a hallway/door area, while the remaining five feeds show various interior spaces. The status bar shows **"Not Logged..."** in the upper right, ambient temperature reads **35°F Clear**, and no visible error codes or alarm indicators are active in the feed panels.

---
title: "Resolve iVMS-4200 NVR connectivity and authentication issues"
category: equipment
tags: ["nvr", "firewall", "network"]
source_thread_id: "spaces/AAAA05BdS6s/threads/V__qaTaODqs"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T14:36:53"
participants: ["Tech A", "Tech B"]
---

# Resolve iVMS-4200 NVR connectivity and authentication issues

## Problem

The iVMS-4200 camera client software was unable to authenticate to the Hikvision NVR at 172.17.184.88, returning "incorrect password" errors for multiple user accounts including admin. The NVR was experiencing intermittent network connectivity issues with inconsistent ping responses, timeouts, and "destination host unreachable" messages from secondary IP 169.254.184.26. While the web interface at port 9000 remained accessible and showed 6 active IP Mini Dome cameras, the iVMS-4200 client could not establish a connection for live view monitoring.

## Resolution

1. Reboot the NVR device and the network switch it connects to
2. Verify network connectivity by pinging the NVR IP address (172.17.184.88) from both local workstations and remote locations
3. Configure iVMS-4200 using IP/Domain mode with the following settings:
   - Address: 172.17.184.88
   - Port: 8000 (for iVMS-4200 client access)
   - Username: operator
   - Use the correct operator password from documentation
4. Set up a new encoding channel in the iVMS-4200 client to enable live view functionality
5. Verify all camera feeds are displaying properly in the client interface

The issue was resolved after the device and switch reboot restored stable network connectivity, allowing proper authentication and live camera feed access.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/V__qaTaODqs`
- Attachments:
  - ![image.png](../attachments/V__qaTaODqs.JtvzKuxtco8/image.png) — **iVMS-4200 software login dialog is displayed on screen.** The user has entered the username "admin," a masked password, and CAPTCHA text "NAA2" (matching the displayed CAPTCHA image). The "I Agree Terms of Service and Privacy Policy" checkbox is checked, and the system is showing "Not Log..." status in the top toolbar, indicating the client is currently not authenticated.
  - ![image.png](../attachments/V__qaTaODqs.NehnZf8KoC8/image.png) — **WatchGuard Fireware Policy Manager** is displayed via a LogMeIn remote session, showing the firewall policy table for configuration file **PDS-BRONX-ORTHO.xml**. **Row 4 ("CAMERAS OUT")** is highlighted, configured as policy type with source **172.17.184.148**, destination **Any-External**, and ports **tcp:80, tcp:443**, with **App Control and Geolocation set to None**. Additional visible policies include NVR (tcp:8888), FTP (tcp:21), DR-BGP (tcp:179), HTTP-proxy (tcp:80), HTTPS-proxy (tcp:443), and BOVPN entries; rows 4, 9, 10, and 12 display a document/edit icon in the Action column indicating IPS or logging modifications.
  - ![image.png](../attachments/V__qaTaODqs.QSTxq2exwHM/image.png) — The screen displays a device management interface with an **Edit dialog** open, showing the following configuration: **Adding Mode: IP/Domain**, **Name: Cameras**, **Address: 172.17.184.88**, **Port: 8000**, **User Name: operator**, and a masked password field. The background table shows a single device entry labeled "Cameras" with connection type **IP/Domain** and partial address **172.17.184.88.9...**, classified as **Encoding D...** device type. No error codes or indicator lights are visible; TLS is unchecked.
  - ![image.png](../attachments/V__qaTaODqs.f1pKM6NZ7eg/image.png) — **Administrator Command Prompt – Ping 172.17.184.88 -t**

The screen shows continuous ping output to **172.17.184.88**, with intermittent successful replies (bytes=32, TTL=62, times ranging from **12ms to 2044ms**) interspersed with **"Request timed out"** messages and multiple **"Reply from 169.254.184.26: Destination host unreachable"** responses. The pattern indicates highly inconsistent connectivity, with several consecutive timeouts and occasional unreachable replies from a secondary IP (**169.254.184.26**) before successful replies resume.
  - ![image.png](../attachments/V__qaTaODqs.gK-snHxUZMw/image.png) — The screen shows a **Hikvision NVR Web UI** (Live View) accessed via browser at **172.17.184.88:9000/doc/page/preview.asp**, labeled **"PDS-BRONX"** in the browser tab. The live view window displays a **black/blank feed** with a yellow border, indicating no active video signal is rendering. The left panel lists **6 active "IP Mini Dome"** cameras and **2 offline/unassigned channels** ("IPCamera 07" and "IPCamera 08"), with the PTZ preset panel visible on the right showing **Preset1 through Preset14**.
  - ![image.png](../attachments/V__qaTaODqs.hHx_NBLDv_E/image.png) — **iVMS-4200 NVR Client – Multi-Camera Live View**

The system displays **"PDS BRONX ORTHO – BXORTHO-FD02 – Remote Control – Monitor 2"** in the title bar, running the **iVMS-4200** client software with **6 active IP Mini Dome camera feeds** timestamped **12-27-2024 Friday 05:35:12–05:35:22 PM**. All feeds are rendering in **night vision (IR monochrome mode)**; the top-left enlarged feed shows a hallway/door area, while the remaining five feeds show various interior spaces. The status bar shows **"Not Logged..."** in the upper right, ambient temperature reads **35°F Clear**, and no visible error codes or alarm indicators are active in the feed panels.

Generated article

draft