I’m having issues getting Remote Access to work. I have two LANs.
LAN 1: This LAN is from my ISP modem --> Router 1. (192.168.1.x)
LAN 2: This is a Cisco lab network that I use for my workstation, server, and other stuff. Initially started off as a test lab but I have grown to love everything about it and am now using it long-term. The router is a Cisco 1921 that gets its IP address from Router 1 on LAN 1. This is just so that the Cisco switch and its devices can reach the internet. It does not work without doing this. (10.0.0.x)
The Cisco 1921 (Router 2) connects to a Cisco 3750 switch that has my workstation, server, and other devices on it.
Plex Media Server lives on the server inside of a docker container. I host other docker containers that can reach the internet just fine, including multiple websites via reverse proxy.
On LAN 1, I’ve forwarded out port 32400 to the internet and tell it to use the local IP of the Cisco router according to Router 1 (192.168.1.x), because on the Router 1 network, it is not able to see the 10.0.0.x network.
However, LAN 2 is able to see LAN 1, and router 2 looks for traffic sent to 192.168.1.x (Router 2 IP on Router 1) and tells it to forward to the 10.0.0.x address of the device hosting the service on that port. It does this through NAT.
The problem is, I need a way to change the private IP in the Plex interface to the 192.168.1.x address, since the outside world cannot see the 10.0.0.x network. I can’t change that in Settings > Network > Preferred network interface, because the server is only tied to the 10.0.0.x network, not the 192.168.1.x network.
Long story short you doubled NATed using 192.168.1.0/24 for LAN1 and cascaded LAN2 using the Cisco 1921 ISR behind the ISP customer gateway with 10.0.0.0/24. Are you positive you have NAT configuration correct on the 1921 ISR?
Share the routing and NAT statements from each device. Or screenshots.
Cool! You’re your own ISP now.
Edit: You don’t need to change the private IP on the Plex Server. That’s used for same-subnet discovery, and … well, it’s on the 10.0.0.x subnet.
You can tell the Plex Server to consider IP addresses in the 192.168.1.x network to be “Local” from a bandwidth perspective, and from a “don’t require auth” perspective, but they’re not going to be local from a “casting” or device discovery perspective.
Playback should still work and traffic should still stay inside your network(s).
Hmm, disregard everything. I’ve been playing around with it. For some reason, when I select “manually specify port” and just leave it on 32400, it works? But if I un-select it, it doesn’t work? Weird. I know my server version is a bit older, maybe that’s why.
Edit: If you don’t manually specify a port, it picks one (not 32400) randomly. That works fine in a UPnP environment, and being a bit random has some (minor) advantages.
Because you’re configuring the translation manually on multiple devices, you definitely want to make sure that Plex uses the port you specify.
