@will2021_597482666070088 I have the same issue with V8.12. Despite raising a ticket there is no solution. Where can I find V8.11 to have a working client again?

Hi,

A number of IP cameras are connected via 4 PoE switches to 4 camera ports of the RLN36, and they have been assigned IP addresses via DHCP of the NVR. The addresses are in the range 172.16.25.nn. The NVR camera gateway is 172.16.25.1 (mask 255.255.255.0). I have established a static route in the network router from my LAN gateway 192.168.0.200 to the camera network 172.16.25.0



However I cannot access the cameras behind the NVR from the LAN. I know the route is valid as I can access the NVR itself using its gateway address http://172.16.25.1. Is there a way to change the IP_forward flag in the NVR to be able to route through from the LAN to the camera segment?

A workaround would be to utilises another network adapter in the PC connected to a camera port on one of the PoE switches or the NVR, but that would only enable that one PC to access a camera GUI. What I need to be able to do is to enable an FTP feed from particular cameras directly to a NAS on the LAN. This is necessary for security reasons so that the NVR hard drive and NAS hard drive are physically separate.

My only other alternative would be to connect the cameras to the LAN segment instead of to the NVR camera ports, but then the camera network traffic on the LAN would become excessive.

Is there another solution to this network obstacle that the NVR does not allow routing from the LAN segment to the camera network segment?

@joseph_1979 Thank you - that explanation about P2P servers makes sense. I have now tried a direct connection using IP/Domain name and port 9000 (having forwarded port 9000 on the camera's router). This time the resolution starts at Mid but seems to stick at High once it has been selected, which is preferable for my installation.

A further question - if more than one camera is to be connected, should the service port on each be changed from 9000 to say 9001, 9002, 9003 etc? And then adjust the port forwarding accordingly to forward cam1:9001 fw to 9001, cam2:9002 fw to 9002, cam3:9003 fw to 9003 etc? Or is it better to keep the service port for each camera at 9000 but adjust the port forwarding so that cam1:9000 fw to 9001, cam2:9000 fw to 9002, cam3:9000 fw to 9003?

UID connected cameras always start Live View with Low Resolution. LAN connected cameras start with the resolution that was selected last. How can this behaviour be changed so that remote cameras Live View always starts with the last selected resolution? [Windows Client v8.12.1]

@joseph_1979 The missing files message was regarding DirectX libraries. I had previously updated DirectX so I knew the message was erroneous and was ignored.

@joseph_1979 the issue is when selecting some of my HD cameras I get "Loading failed - Retry". If I re-installed V8.11.0 the issue was gone.

I managed to get V8.12.1 to work by uninstalling the previous version first, through the Windows uninstall facility. However the new installation wanted missing files. I ignored the erroneous warning about missing files and had to insert all the camera passwords again, as well as re-add cameras from outside the LAN. V8.12.1 seems to be OK now.

@will2021_597482666070088 I have the same issue with V8.12. Despite raising a ticket there is no solution. Where can I find V8.11 to have a working client again?