NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi rbr 50 Port forwarding issues
I am trying to add ports 80, 8000, and 554 to my orbi so i can remotly see my truvision camera system. Router Firmware Version V2.5.2.4. I install these systems regularly but this is the first time...
Yes, they are going directly to the recorder it is a turvision nvr 10s.
Peace2u3 wrote:Yes, they are going directly to the recorder it is a turvision nvr 10s.
About UPnP, you are referring to page 79 of the user manual?
https://static.interlogix.com/library/1072766D%20TruVision%20TVN%2010%20user%20manual-EN.pdf
and the port forwarding information on page 139?
Could you please clarify the comment " I can view the cameras locally via the IP address in the app but not on a computer and not on data."
I did not find mention of an "app" in the user manual. If a web browser on a local computer will not connect to port 80 on the NVR, then an external web browser certainly will not be able to. What software is being used to connect on ports 554 or 8000?
Just generally speaking, the steps I use to diagnose port forwarding issues is (a) test the setup locally using the LAN IP of the server, then (b) verify ports are open using something like http://canyouseeme.com or www.grc.com, and (c) test remotely using a "Hot Spot" from my cell phone.
About the upnp, I was just mentioning that I tried it, both the router and the recorder have upnp and it didn't work.
There is a TVR mobile app that works in conjunction with the recorder, I can type in the IP address of the recorder, the port number, and the user name and password and it allows you to view the cameras (the recorder) while your on the local network like wifi. You can also use the app to view them remotely as long as you have ports forwarded by using their ezDDNS servers. As far as not being able to see them on my computer, I'm referencing typing in the ip address into the url bar with the port number and it not bring the recorder up as it does on all other systems I've installed. The company recently closed their doors and their customer service is only open mon-fri at times when I am at work. I have also used them a good deal before and most of their assistance is "ah yes, I see your ports arn't opened, you need to get them open then it should work." which in their deffence is correct. Also, not that it matters but I changed the ports to 8300, 8302, and 8304. The 554 (8304) port was the RTSP service port and the 8000 (8300) port was the Server port and for the sake of saying it the 80 (8302) port is the HTTP port.
As far as your last point, I have tried using the WAN IP to view the cameras and it didn't work but it doesn't really matter because I've been using portchecktool and they keep saying closed no matter what I change in the router. And yes, I've also used my cellular data to test the "remote access".
I would love to contact NG support but I'd really rather not pay for $90 for 1 phone call.
Peace2u3 wrote:I would love to contact NG support but I'd really rather not pay for $90 for 1 phone call.
From some of the recent posts, it is not clear to me that contacting GearHead support would be successful. Unless they would refund the money if they can't solve the problem, I'd be reluctant as well. (At this point, I would gladly pay $90 to get the problem "behind me", but would be furious to be out the money and still have no solution.)
Let's see if I undersand now:
The app works locally, but does not work remotely. Which port does the app use?
HTTP access to the system does not work locally, which implies that it cannot possibly work remotely.
How do you verify that their DDNS resolves to the public IP of the Orbi router?
(The Orbi router itself works only with a couple of DDNS providers, ezDDNS is not one of them. So, the recorder must connect to their system periodically to update the public IP independently of the router?)
My understanding of port forwarding is that services such as portchecktool only report ports open if they get a response from a connect request. They do not connect to the router, but to the end device. Is there another system that can be opened (temporarily) to test port forwarding? I have a couple of systems that contain web servers (my printer, Pi-Hole, etc.) How about opening port 80 on something else and see if it checks out as "open"?
My cameras stream over rtsp. Does VLC stream from this system locally?
Might not answer all your questions my dad has an orbi as well and the same company of recorder using the ezDDNS and it works fine for him. I have facetimed with him while we were both loged onto our routers but I can't see any differences. When he gets home today I may try again with what I've learned sence friday but don't know if I'll find anything.
The app uses port 8300 for local viewing, and the 8304 port for remote viewing.
On the recorder, you actually "apply" for a DDNS host name, there can be no copies and such. It will tell you if the name has been accepted. I'm not 100% if theres a way for me to see if the DDNS resolves with the public IP.
I agree that if I can't see port "80" open then theres no chance that I will view it remotely. Thats where I'm stuck at. If the ports showed open then I don't believe I would have an issue.
Also, I was not part of my dads set up as far as how they got it working and nobody that was remembers the details. (its been a few years)
This also streams over RTSP and I don't belive the recorder uses VLC at all unless its on a base level I haven't had to use.
I can try to see if I have anything else that I can open port wise. But this is the only thing that I know of.
Canyouseeme showed this
Error I could not see your service on ######## on port (8304)
Reason: Connection timed out
