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 ...
Nick_2021
Apr 12, 2021Aspirant
antinode wrote:>What is the IP address of the router's WAN/Internet interface?
ADVANCED > ADVANCED Home : Internet Port : Internet IP Address
108.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
antinode
Apr 12, 2021Guru
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.
- Nick_2021Apr 12, 2021Aspirant
>> ORBI is on V3.2.18.1_1.4.14 firmware.
>Hmmm. The latest I see is "V3.2.17.12_1.4.14".
I'm pretty sure it came with it OOB. I'm hesitant trying to go backwards. I doubt it's an issue with the new FW. As I mentioned, FiOS Gateway routers had the same issue. It does sound like an ISP block of some sort..
>1. Wrong external IP address
IP is correct from what you can see.>2. Bad port-forwarding rule
Also, as you see - it seems correct. Pretty straightforward setup...>3. Server not listening on the port-forwarding target system.
It's the default Plex port. It responds to it internally within LAN.>Can you access the server from a system on your LAN using the server's LAN IP address?
Yes, as stated above the Plex server is working like a charm on LAN. All devices on LAN can play media from it using their respective apps (ios/android) or straight via browser page (IP+port). They play directly & at original quality, with no transcoding necessary.
Devices outside LAN, however, can still connect to it via their apps, but they get the message you saw in the screenshot about 'connection is not direct blah blah' and end up getting a transcoded 720p feed of 2mpbs (plex limitation) that's routed through some proxy I guess. Plex standard behavior.>If that works, then, still from a system on your LAN, try using the router's WAN/Internet IP address. That should verify the port-forwarding rule(s) (and the "NAT loopback" feature of the router).
Tried that: "This site can’t be reached" timeout.>4. External influences:
>ISP blocking
All the ports? I tried a multitude of ports... I might try talking to their support again.
>other firewalls
I don't have any on LAN. Can't see any FW-related settings on ORBI either...sigh...
Thanks for your input.
If you have any other ideas - shoot.
- antinodeApr 12, 2021Guru
> Tried that: "This site can't be reached" timeout.
If you have all the addresses right, and the port-forwarding rule is
right, then, to me, that suggests a router firmware problem (port
forwarding, or NAT loopback) or a server problem.> [...] FiOS Gateway routers had the same issue. It does sound like an
> ISP block of some sort..Or a server problem.
> >4. External influences:
I would not expect external anything (ISP, or whatever) to affect
access from your LAN, even when using the router's WAN/Internet address.
Being largely ignorant/innocent of Plex, I might try running some
other server (Web, FTP, SSH, ...) on the same system, and see how port
forwarding for that service works. Or on a different system. (Is the
problem with the ISP or the local server?)> PC is a Win10x64.
And speaking of firewalls, does Windows see this network connection
as Public (bad) or Private (good)? Any other exotic Windows firewall
stuff?