Dual WAN Server - Remote Issues sometimes

Server Version#: Latest
Player Version#: Latest

Hi there,

I have Dual WAN at home, one is a Static IP traditional connection and plex remote works perfectly fine over that when it’s the only connection plugged in.

My second WAN is double natted LTE Modem, it’s configured as Load Sharing because I can get 300-400Mbit downloads over LTE here where I live, and only 100Mbit over the fixed line.

When both are plugged into the router Plex Remote is green “Fully Accessible” showing the IP of the fixed line. However, every so often it switches over to the LTE IP and then becomes inaccessible.

Unplugging and plugging the modem from the router fixes this issue only temporarily.

Is there a way to force PMS to only the Fixed line IP? I assume this is what “Custom Server access URLs” was for and have a Domain name linked to my Static IP Fixed line. However that doesn’t seem to do anything.

Any advice would be great, thanks.

Since the connection is one device upstream from the server (in the router / at the WAN entry point), there is nothing PMS can do.

PMS can favor one ethernet adapter over the other on the host itself but if you have two traffic streams, your only solution is to write some route table rules to favor / adjust the metrics.

in your dual wan router, look for something where you can bind a port to a particular wan.

basically you want the router to only use wan1 for plex traffic (unless of course wan1 is actually down). essentially disabling load balancing for plex traffic.

I have a problem similar to yours, and I have tried everything to get around the problem. My current setup is as follows. The PC running PMS is dual-homed. Here is the routing table.

Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.2.1    192.168.2.106     30
          0.0.0.0          0.0.0.0     192.168.30.1    192.168.30.73     40
    99.80.231.223  255.255.255.255      192.68.30.1    192.168.30.73     21
    99.80.242.242  255.255.255.255      192.68.30.1    192.168.30.73     21
    99.81.213.165  255.255.255.255      192.68.30.1    192.168.30.73     21

(I hope that looks OK.) Those three 99.8x IPs were plex.tv when I tried this last gasp. (I call it last gasp because I tried everything else. Before the above route table, I just had two entries. I tried ‘Preferred network interface’ and then restarted PMS. That did not work – insisted on going to 192.168.2.1. When I gave 192.168.30.1 a lower metric, it worked. However, I do not want 192.168.30.1 to be the go-to gateway for normal Internet traffic. I also tried setting the URL. Nothing seems to work.) So the last gasp above is based on looking up plex.tv (which I assumed is where PMS tries to go when establishing an outside connection). Notice the route table says when those IPs are used, use the 192.168.30.1 gateway, which is what I want. It just doesn’t do what I want – always uses the 192.168.2.1 gateway (lowest metric).

I have probably tried things not listed here. Does anyone know how to get this to work? I notice there’s some configuration file somewhere that has IPs in it, but it is unclear what those parameters are for.

(To make something clear: NIC1 and NIC2 in the one PC are connected to separate LAN1 and LAN2 (do I have to say respectively?) routers , which each router connected to its own ISP. I want (almost) all traffic in or out of the PC to be on LAN1 connected to ISP1. This includes LAN PLEX traffic. I want WAN connections to PLEX to come in from ISP2. I have not been able to get this to work without removing lower-metric LAN1 from the equation. One simple way to get this to work would be allowing me to specify the external URL to use to get to my PMS. That URL Settings parameter doesn’t seem to do it.)

This topic was automatically closed after 90 days. New replies are no longer allowed.