GW5508NP cannot connect to remote viewing

[pebble...@gmail.com]

I am having issues connecting with the remote view app. I have the RXCamView app that was working  for quite some time and then stopped for some reason. I rebooted the system and still could not connect would either say password error or network error. I then rebooted my router/modem to be safe and still the same errors, I logged in using the WEB GUI to make sure I could connect with a PC directly connected to it and changed the password and still could not connect. I then updated the firmware to see if that would fix it since it was said to have improvements to P2P connections and after the full reboot I still could not connect. I also tried downloading the APP's that are on the software page and on the GWCAMVIEW app I was able to connect to it once and could not connect again. I downloaded the RealView Pro and still nothing. I must also note that the APPs also would not recognize the QR code, the APPs would just continue to say make sure its the right one etc. etc. the RX APP would recognize the QR but I couldn't connect. Any advice would be appreciated. 

[GW Security Q&A forum]

The Realview Pro app is for the other NVR line we have (the 22, 24, 32, 34 series NVR); it will not work with your GW5508NP.

The connection worked for you one time? Were you using your mobile data or wifi when the connection worked for you?

[pebble...@gmail.com]

The connection worked for months without issue then stopped suddenly. Connected via Wi-Fi seemed to be the only way it would work I could never get the cameras to load when on mobile data, I even tried connecting to the Wi-Fi network the device is currently hardwired to without much luck. It did come up once when I tried to use the add online device but after the app closed it would not find it again.

[thomasr...@gmail.com]

same here let me know what you find out. can only view on wifi not data.

[pebble...@gmail.com]

So, I have been going through the forums and this seems to be a reoccurring issue with little to no success in any of the suggested work-arounds. This needs to be addressed either through a firmware update or App overhaul....