DS-7616NI-K2 / 16P
I had setup this nvr for remote viewing for client using https and it was working fine for about a month.
They lost connectivity due to a cable modem issue, and the ip of the nvr changed due to DHCP being enabled and now mismatched with the port forwarding on router.
I set up a static ip address for the nvr and matched it in the router port forwarding.
I also generated a new self signed certificate, and the https seems to work fine until login, when it throws the "abnormal network" error.
It only throws the error while using https, and all works fine using unsecured 8080 http protocols.
I returned to DHCP and still received the error, so reinitiated static.
The cams are on the internal nvr switch using 192.168.254.XXX. The Nvr is on the 192.168.1.xxx network.
Everything seems to be properly functioning until https is used. The login page shows and functions, so I don't suspect the https protocol as being the issue.
I'm stumped at this point and curious as to why the issue did not occur on last setup, as all settings are the same as far as I can tell.
Hoping someone here has been through this and can provide a solution.
I had setup this nvr for remote viewing for client using https and it was working fine for about a month.
They lost connectivity due to a cable modem issue, and the ip of the nvr changed due to DHCP being enabled and now mismatched with the port forwarding on router.
I set up a static ip address for the nvr and matched it in the router port forwarding.
I also generated a new self signed certificate, and the https seems to work fine until login, when it throws the "abnormal network" error.
It only throws the error while using https, and all works fine using unsecured 8080 http protocols.
I returned to DHCP and still received the error, so reinitiated static.
The cams are on the internal nvr switch using 192.168.254.XXX. The Nvr is on the 192.168.1.xxx network.
Everything seems to be properly functioning until https is used. The login page shows and functions, so I don't suspect the https protocol as being the issue.
I'm stumped at this point and curious as to why the issue did not occur on last setup, as all settings are the same as far as I can tell.
Hoping someone here has been through this and can provide a solution.
