anything that is on either subnet 1 or 8 should stream locally no matter what.
if it did not before, then the addition of those subnets to the ‘lan’ settings in plex should have helped.
if you do not want the desktop plex server to go out of the gateway 192.168.1.1 (no remote), then REMOVE the gateway ip from the windows settings (not plex). (you might need to change from DHCP to static on that ethernet interface)
this will still allow local 192.168.1.0 access, but windows will not attempt to route out to 1.1 gateway.
I’d still like to see debug logs from a time period showing a transition from 192.168.8.103 to 192.168.1.104 on the remote access screen. As far as I know, Plex Media Server should honor your preferred network interface setting; if it’s not, something is causing it to switch. It could be some network instability, and the logs may show that in the form of network status events. Something like:
I did not understand why you are enabling/disabling the Ethernet port in your Plex server.
I was suggesting that doing so with Plex running might be causing issues, as Plex sees interfaces going online/offline and it might get confused.
So the router for the 192.168.8.x network only supports WiFi connections?
And the address for the Plex server WiFi adapter is 192.168.8.104, correct?
How is the 192.168.8.103 Ethernet interface used on the Plex Server?
If the 192.168.8.103 Ethernet interface has no path to the Internet, then it should be disabled and not used. Using such an interface will confuse Windows and Plex, as they will not know which interface to use for Internet access.
How is this accomplished? Are you connecting via the 192.168.1.x network
Ok guys I’ve done some research to this issue and it’s unresolvable while I’m currently with Three Using their THREE UK 5G Home router. Apparently, this issue has become a problem for many others. There is no way around it without going through so much hassle. So I’m just gonna get a 4g router for the sim that allows me to do remote-play and lend my 5G router to family member.
I think you’ll find that with another (4G) router you’ll also be behind Carrier Grade NAT.
As far as I can see it’s not a hardware issue with the specific 5G router or 5G itself, it’s the decision of your mobile carrier to put their customers behind CG-NAT (where you can’t forward ports to accept incoming connections). Nearly all mobile carriers all over the world do this.
Behind CG-NAT you can do a few things for the server to be remotely accessible:
VPN into a remote server that can forward ports (fairly difficult to set up)
use ZeroTier (this is actually quite good - worth trying)
if you can get IPv6 (sometimes possible by choosing another APN on the 4G/5G router), there’s no CG-NAT, although your clients also need to be on IPv6.
Anyway stepping back to your issue: the dropdown where you choose your preferred network interface in the Plex Network settings is not to specify what interface to use for remote access, it’s the address that’s broadcast on your LAN for local clients, as per the description: “The network interface local clients will use to connect” As far as I know there’s no setting to force Plex to use one network interface for remote connections. Which interface is used, is left up to the OS. So the good news is, it’s not Plex fault here
If you’re interested how Windows determines what route your internet-bound traffic takes (ie what interface it uses for Plex remote access), read this.
A metric is a value that is assigned to an IP route for a particular network interface that identifies the cost that is associated with using that route. For example, the metric can be valued in terms of link speed, hop count, or time delay. Automatic Metric is a new feature in Windows that automatically configures the metric for the local routes that are based on link speed. The Automatic Metric feature is enabled by default, and it can also be manually configured to assign a specific metric.
It appears that you can set this “Metric” number manually for your interface in the Networking system settings of Windows, so if you set this for your WiFi interface a lower number than for your Ethernet one, Windows should prefer it and your frustrations should (?) be over.
For completeness and future reference, on macOS the routing preference order is set in Network preferences, click on the gear icon, “Set Service Order”. For Linux, there’s this solution.
