NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nick_2021
Apr 12, 2021Aspirant
Issues opening a port on AX4200 ORBI RBR750
Hello,
I have a Plex server app running on a QNAP NAS on a network. Everything works great on LAN, but I can't make other devices connect to it directly from the outside (over internet). Supposedly Plex/QNAP should open whatever ports they need on router via UPNP, but they don't. And no matter what port I'm trying to open manually (and force Plex/QNAP to use it) - it's not accessible from the outside.
Setup is the following: Verizon FiOS 1Gbps fiber >> UTP-Cat5E-wired >> AX4200 ORBI RBR750 router >> UTP-Cat5E-wired >> QNAP NAS (static IP).
I had an hour long session with QNAP technician and he said "the port is not getting opened, so it's a router issue"...
To be fair, I initially used FiOS default router (Gateway FiOS Router FiOS G-1100-FT-FRONTIER) trying to make this work. I had a remote session with a Verizon tech and he couldn't figure it out either and blamed the router, so we ended up replacing the router with the same one. The issue remained.
So I then went ahead and got the ORBI mesh hoping that a router swap would help. It didn't. So I don't think it's a Netgear issue per se, but there's clearly something preventing my setup from being avail from the outside, and I'd REALLY appreciate if some bright mind can help me solve it.
Router is 192.168.1.1 (no double-nat)
NAS is 192.168.1.212 (static)
By default Plex tries to use port 32400. I tried it (and a dozen other ports).
ORBI is on V3.2.18.1_1.4.14 firmware.
PC is a Win10x64.
Thank you,
Nick
8 Replies
> Router is 192.168.1.1 (no double-nat)
"Router" has _two_ IP addresses.
That looks like the IP address of the router's _LAN_ IP interface,
which proves nothing. What is the IP address of the router's
WAN/Internet interface? If you're worried about revealing secrets, then
the top half of the address, "a.b" out of "a.b.c.d", would satisfy most
of my curiosity.
ADVANCED > ADVANCED Home : Internet Port : Internet IP AddressIs that the address which you're using for remote access?
Plug that address into the form at: https://whois.arin.net/ , and see
if it is a public or private address.> NAS is 192.168.1.212 (static)
Terminology: A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address. Either one should fix the address of a
device, but some implications are different.> [...] no matter what port I'm trying to open manually (and force
> Plex/QNAP to use it) - it's not accessible from the outside.Actual port-forwarding rule? Actual error message when you do what,
exactly?For the usual problems with port forwarding, see:
- Nick_2021Aspirant
antinode wrote:>What is the IP address of the router's WAN/Internet interface?
ADVANCED > ADVANCED Home : Internet Port : Internet IP Address108.56.x.x - verizon's public adress. Rotates pretty often.
antinode wrote:>Is that the address which you're using for remote access?
>Actual port-forwarding rule? Actual error message when you do what, exactly?
yes, plex dynamically picks up the public address (while using it's own port (with checkbox unchecked) or with the one I force it to). In the pic below I'm manually assigning port 32400 (Plex's default):
https://drive.google.com/file/d/1GCrAIfG2acmEpVPIspv3QKAQrarB6Z8B/view?usp=sharing
this is the port forwarding rule from ORBI setup:
https://drive.google.com/file/d/1z6DKDwJ7d6DdgbQ23byrzp1I-HxKPjca/view?usp=sharing
antinode wrote:>A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address. Either one should fix the address of a
device, but some implications are different.NAS has this IP set as static and ORBI has it reserved for NAS as well:
https://drive.google.com/file/d/1nh64MuKZoH_ByHXaSg7IYKc94dgHikqT/view?usp=sharing
this is https://canyouseeme.org/ trying to ping the port:
https://drive.google.com/file/d/1XV2GN1WEwVQM0lA3DHTRTCdQ_m7xrgzA/view?usp=sharing
Thank you for your input,
Best regards,
Nick
I didn't spot any obvious problems in your configuration.
> https://community.netgear.com/t5/x/x/m-p/1859106
Did you try the tests in that list (particularly in item 3)?
> ORBI is on V3.2.18.1_1.4.14 firmware.
Hmmm. The latest I see is "V3.2.17.12_1.4.14". Normally, if
everything seems right except the actual behavior, I'd suggest a
different/older firmware version, but I'd hesitate if I couldn't return
to the starting place.
You have posted your message in the section of this community given over to DSL Modems and Routers. (This is easily done, given Netgear's complicated community structure.)
Many questions apply to different types of device, so you might get informed responses here, but modem/routers and Orbi devices are very different product lines and technologies, with few people using both, so you might get more help, and find earlier questions and answers specific to your hardware, in the appropriate section for your device. That's probably here:
Orbi - NETGEAR Communities- Nick_2021Aspirant
Hello Michael,
Thank you for your input. I'll try posting in ORBI community.
Though I don't believe the issue is specific to modem-vs-Orbi differences..
Best regards,
Nick
Nick_2021 wrote:
Though I don't believe the issue is specific to modem-vs-Orbi differences..
No, but people over there are more used to the ways of the Orbi technology and you will find a lot more message traffic there.
DSL modem routers are a small and shrinking business for Netgear. Just count the number of messages.