External Access to NVR Camera System
Solved
Skarn_Kain
-
Skarn_Kain -
Skarn_Kain -
Hello everyone,
I recently set up an NVR camera system (Brand: szsinocam - https://www.amazon.fr/gp/product/B08JTXQM2P/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1)
It is well connected to my box (Freebox Pop) and recognized as a device on the network.
Everything works fine on the internal network (I can connect to the NVR via my PC without any issue), however, all the "external" functionalities (email sending, app connection, or even access via external IP address) do not work.
I have indeed set up a static DHCP lease and enabled port forwarding on my box, but nothing works.
What else could be blocking?
Thank you in advance to everyone who takes the time to respond.
(PS: I manage to handle computers, but I am not at all skilled when it comes to networks)
I recently set up an NVR camera system (Brand: szsinocam - https://www.amazon.fr/gp/product/B08JTXQM2P/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1)
It is well connected to my box (Freebox Pop) and recognized as a device on the network.
Everything works fine on the internal network (I can connect to the NVR via my PC without any issue), however, all the "external" functionalities (email sending, app connection, or even access via external IP address) do not work.
I have indeed set up a static DHCP lease and enabled port forwarding on my box, but nothing works.
What else could be blocking?
Thank you in advance to everyone who takes the time to respond.
(PS: I manage to handle computers, but I am not at all skilled when it comes to networks)
10 answers
Hello,
I initially followed the "simple" procedure outlined in the manual, without success, which led me to look for other configuration solutions on my own.
I initially followed the "simple" procedure outlined in the manual, without success, which led me to look for other configuration solutions on my own.
Hello again,
I'm getting back to you because even though the majority of the problems have been solved (my NVR is now successfully sending emails and I can access it via the dedicated app), I still have an issue.
I have finally enabled DHCP on the NVR, which is now automatically retrieving the connection information from the Freebox.
On the Freebox, via the Freebox OS, I have set up a static DHCP lease for the NVR.
I have also activated port forwarding on my Freebox, with the destination IP being the same as in the static lease, and on port 56666.
But despite this:
- The local connection (via IE browser, which is the connection method for my NVR) works fine by entering the local IP address defined in the static lease
- However, the external connection, by entering my Freebox's IP + ":56666" (so XX.XXX.XXX.XXX:56666) does not work. The response I get is that "XX.XXX.XXX.XXX does not allow the connection."
Furthermore, https://www.yougetsignal.com/tools/open-ports/ always indicates "Port 56666 is closed on XX.XXX.XXX.XXX"
I don't know if it's related, but in the configuration of my NVR, I have, in the "Port Setting" tab:
Http Port: 80 || Enable UPNP: No
Rtsp Port: 554 || Enable UPNP: No
I tried to enable UPNP (even though I don't know if it's related) but it doesn't seem to change anything.
Did I make a mistake? What did I not understand? Is there a configuration on the NVR that I potentially did not set up correctly (considering that as mentioned earlier, the NVR does send emails and I can view the cameras externally via the dedicated app, but not through the browser)?
Thank you in advance for your answers.
I'm getting back to you because even though the majority of the problems have been solved (my NVR is now successfully sending emails and I can access it via the dedicated app), I still have an issue.
I have finally enabled DHCP on the NVR, which is now automatically retrieving the connection information from the Freebox.
On the Freebox, via the Freebox OS, I have set up a static DHCP lease for the NVR.
I have also activated port forwarding on my Freebox, with the destination IP being the same as in the static lease, and on port 56666.
But despite this:
- The local connection (via IE browser, which is the connection method for my NVR) works fine by entering the local IP address defined in the static lease
- However, the external connection, by entering my Freebox's IP + ":56666" (so XX.XXX.XXX.XXX:56666) does not work. The response I get is that "XX.XXX.XXX.XXX does not allow the connection."
Furthermore, https://www.yougetsignal.com/tools/open-ports/ always indicates "Port 56666 is closed on XX.XXX.XXX.XXX"
I don't know if it's related, but in the configuration of my NVR, I have, in the "Port Setting" tab:
Http Port: 80 || Enable UPNP: No
Rtsp Port: 554 || Enable UPNP: No
I tried to enable UPNP (even though I don't know if it's related) but it doesn't seem to change anything.
Did I make a mistake? What did I not understand? Is there a configuration on the NVR that I potentially did not set up correctly (considering that as mentioned earlier, the NVR does send emails and I can view the cameras externally via the dedicated app, but not through the browser)?
Thank you in advance for your answers.
Indeed, the NVR listens on ports 80 and 554. You're right, by choosing port 80 as the "destination port" for redirection on Freebox OS, it seems to work because I can access the login page of my NVR by entering XX.XXX.XXX.XXX:56666 now.
Thank you for your help.
However, when entering the same username and password as locally, I get "Username or password is error" when connecting externally... Any idea?
Thank you for your help.
However, when entering the same username and password as locally, I get "Username or password is error" when connecting externally... Any idea?
I'm summarizing my ongoing problem here in case someone comes across it:
My NVR uses Internet Explorer to access it via PC, and I successfully get the same login page when connecting via external IP as I do via local IP (except that the Username is already pre-filled locally while it isn't externally)
However, when entering the same Username and password as I do locally (which works), I get "Username or password is error" when trying to log in via the external IP.
My NVR uses Internet Explorer to access it via PC, and I successfully get the same login page when connecting via external IP as I do via local IP (except that the Username is already pre-filled locally while it isn't externally)
However, when entering the same Username and password as I do locally (which works), I get "Username or password is error" when trying to log in via the external IP.
Would it be possible for the moderators to delete this thread? I will restate my question regarding the network in a clearer and more direct way.
Hello everyone,
I’ll summarize my ongoing problem:
I recently installed an NVR camera system (Brand: szsinocam - https://www.amazon.fr/gp/product/B0 [...] UTF8&psc=1)
It is properly connected to my box (Freebox Pop) and recognized as a device on the network.
I have correctly configured the NVR network side (I do receive automatic emails from the NVR and can connect to the NVR using the dedicated smartphone app - IP view).
I have also set up a static DHCP lease and enabled port forwarding on my box (Start port: 56666 / End port: 56666 / Destination port: 80).
My NVR uses Internet Explorer to access it via a PC.
The connection and use work without issue when connected to the local network (192.168.1.218).
However, when I connect remotely using the external IP (XX.XXX.XXX.XXX:56666), I get the same login page as with the local IP (so I am apparently reaching my NVR), but when entering the same username and password as in local connection (which work without issues locally), I get "Username or password is error" when I try to connect via the external IP.
What else could be blocking?
Thank you in advance to everyone who takes the time to reply.
I’ll summarize my ongoing problem:
I recently installed an NVR camera system (Brand: szsinocam - https://www.amazon.fr/gp/product/B0 [...] UTF8&psc=1)
It is properly connected to my box (Freebox Pop) and recognized as a device on the network.
I have correctly configured the NVR network side (I do receive automatic emails from the NVR and can connect to the NVR using the dedicated smartphone app - IP view).
I have also set up a static DHCP lease and enabled port forwarding on my box (Start port: 56666 / End port: 56666 / Destination port: 80).
My NVR uses Internet Explorer to access it via a PC.
The connection and use work without issue when connected to the local network (192.168.1.218).
However, when I connect remotely using the external IP (XX.XXX.XXX.XXX:56666), I get the same login page as with the local IP (so I am apparently reaching my NVR), but when entering the same username and password as in local connection (which work without issues locally), I get "Username or password is error" when I try to connect via the external IP.
What else could be blocking?
Thank you in advance to everyone who takes the time to reply.
The technical service finally got back to me, and surprisingly with a good solution. So it's working!
So I'm posting the solution here:
In addition to the "classic" access port redirection to the NVR (port 80), you need to redirect other ports on your box:
- to redirect the video stream, you need to enable a redirection for port 554
- And to allow access management by the NVR, you also need to enable a redirection for port 5540
So I'm posting the solution here:
In addition to the "classic" access port redirection to the NVR (port 80), you need to redirect other ports on your box:
- to redirect the video stream, you need to enable a redirection for port 554
- And to allow access management by the NVR, you also need to enable a redirection for port 5540
554, it was written higher up, I think, and it's quite classic,
but 5540, that doesn't just come out of nowhere :-(
but 5540, that doesn't just come out of nowhere :-(
If I understand correctly, RTSP (554) is for controlling the video stream, but not the stream itself, which is under RTP.
Yes, I read the manual, but unfortunately it is not very precise or comprehensive.
Through the app, I tried the recommended app (Danale) as well as the Onvifer and DMSS apps (which always returns a connection error).
For external access via public IP, through a web browser (as for access via internal IP).
I don't know if it's relevant, but I also checked if the port I enabled for redirection on my router was open (through https://www.yougetsignal.com/tools/open-ports/) and it is not ("Port 3333 is closed on XX.XXX.XXX.XXX").