Server Version#: 1.16.1.1291
Player Version#: multiple.
This is a pseudo repost after a moderator suggested I move it here from from player section
It seems I cannot get my devices (in this particular troubleshooting case, my firestick) on my LAN to connect directly to my PMS.
On the plex client on my firestick, I have the “info” overlay on. When I try to stream at high bit rates it says something to the effect of - connecting thru the WAN not enough bandwidth, limited to 7200 kbps. I have unlimited set in both the client and on the server.
To confirm the plex client is indeed connecting thru the WAN, I disabled remote access on PMS. After doing this, my firestick cannot connect at all anymore.
My router is a DD-WRT router. I whitelisted plex.direct (as shown above) and after that didn’t work; I also disabled “No DNS Rebind” in DDWRT… no change.
The only working theory I have at the moment is that is this somehow related to the fact that the devices that are wireless are showing this problem (namely, they appear to plex as “remote”. My LAN plugged in devices don’t seem to have this problem (only tested a few though).
Here is an example… the “android TV” device is the fire stick… the .140 device is my “plugged in” desktop PC.
If the dd-wrt is also handling your wireless, do you have ‘client isolation’ activated?
It prevents all wireless clients from accessing other devices on your subnet, so all they can do is going through the WAN interface.
Also in Plex:
Settings - Server - Network - ‘Show Advanced’ - “Treat WAN IP As LAN Bandwidth”
Hmmm… well this is interesting… I am unable to connect to my plex server directly (using http://name:port) when I am on wireless…
Well, that tells me I got a router config problem. With wireless clients unable to access my wired lan (on certain ports anyway). I can ping wired IPs from wireless but can’t seem to access via the plex port.
I know this is outside the scope of being a “plex” problem but I’ll take any advice you may have. Otherwise I will run down that rabbit hole to get that resolved and see if it fixes my problem.
Thanks for getting me to think in a different direction about this problem :-).