NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi port forwarding not working
Hi, I am trying to set up port forwarding on my Orbi AX4200. The purpose is to set up remote access to my Plex server running on a Synology NAS, which is connected to one of the satellites of my...
synology has it's own plex server. it designates 32400. Both with and without Upnp, 32400 is not showing as being reached no matter what external port I designate. 32400, 32500, 32600, 32605 etc. The reason you change the external port is because I have two plex servers in my home (for different reasons like transcoding ability). One on a pc running unraid and another on the synology nas. my PC has external port 32600 forwarded to 32400 at the IP of the PC. My synology has external port 32605 as my external forwarded to my plex app on the nas. forwarded to 32400. Plex uses as a standard port of 32400. So, to designate which server plex is pulling data, you change the external ports to point to each source. All this is explained in the support area of plex.tv. The plex app on the synology NAS does see external connection (green check in plex). I am just wondering why canyouseeme does not when I check port 32605.
yes, my public IP matches. no double NAT
Aggie94 wrote:
The reason you change the external port is because I have two plex servers in my home (for different reasons like transcoding ability). One on a pc running unraid and another on the synology nas.
Thanks. That makes perfect sense. So, both Plex servers are reachable from the internet using the Plex Media app, but canyouseeme does not show the port open. Very interesting question.
Would it be convenient to try a few other web test sites? Gibson Research "SheidsUp!", for example. https://www.grc.com/shieldsup
It could have something to do with the method the Plex server uses to connect. I don't know if this question is worth a lot of your time (since both Plex servers are working). Maybe Plex only accepts a connection that contains specific information? My approach would be to use the Orbi debug capability of "Enable LAN/WAN Packet Capture". Begin the capture, then try some "can you see me" web sites. Then connect using the Plex Media app. Save the debug file to your PC and then use Wireshark (or a similar pcap utility) to open both the LAN.pcap and WAN.pcap files.
The LAN capture will be the easiest because Wireshark can use a display filter to show only the packets going to/from the media server(s). (ip.addr == 192.168.1.11) What I suspect might happen is that there will be TCP packets going from the Orbi router to the Synology, but no responses going back to the router. Then, when Plex Media connects, there will packets going to the Synology and packets going back to the router (the router being the gateway to the internet).
The WAN side will be more difficult because all incomming packets are addressed to the Orbi router and Network Address Translation hides the internal IP address.
the shieldsup is green for port 32605 to my NAS port forward. it didn't say open, rather stealth. on a whim, I disabled the firewall on the nas for a few seconds and it passed. so, the issue is not the netgear router and I'm sorry if I mucked up this guys thread. thanks for all the help.
Aggie94 wrote:
the shieldsup is green for port 32605 to my NAS port forward. it didn't say open, rather stealth.
Thanks for taking the time for this other test. SheldsUp! defines a port as
- Open - when a connection attempt is accepted
- Stealth - when the connection request just 'disappears'. No response of any kind.
- Closed - when a port responds to the connection request with a denial.
There is an interesting discussion in the FAQ about why Gibson uses the terms he does when other sites use other terms.
Not having much luck finding a reference for the Plex client/server TCP handshake.
This post says it is an http header:
https://www.reddit.com/r/PleX/comments/g7yge1/how_does_plex_serverclient_handshake_work/