My question is does anyone know a work around for my router port overlap issue?
Basically i have a new router that is a DDW36C ubee cable modem supplied by TWC. I have 3 plex servers. I am trying to program the router to take external port 32400 to internal 32400 (@192.168.0.3) on one machine and it works fine. Taking the second server and pointing 32401 to internal 32400 (@192.168.0.6) informs me there is a port overlap and i am unable to apply the setting.
On my last router the software did not prevent me from putting whatever i wanted in the settings so it worked but after an upgrade in speed they replaced my router and now i’ve faster but lost 2 plex servers essentially in the deal.
You’ll have to find the manual for that router and see if you can map an internal port to a different external port. Also, I don’t recommend using 32400 or 32401 for external ports - move up to 40000. Things seems to work better that way for some reason.
If you can’t, then AFAIK you really don’t have much choice - you have to use just one Plex server for remote access.
Thanks for the response. That is kinda where i was with probably just stuck to one plex server. I looked into the manual and couldn’t find a way around it. I even have the technician password for the device from TWC and i have access to more features then the “normal” admin password and still nothing. I think my only real option at this point if i want to continue using it is if i put the modem in bridged mode and purchase a router capable of using the same internal port. I wonder why plex is so insistent on not changing the internal 32400 port?
You could enable UPnP on the router, and then have one Plex server let UPnP pick a port, and have the other Plex server set up with manual port forwarding for port 32400.
curious, but why not manually set the port on the other servers and use those instead of the default 32400 on each server? You should be able to set server 2 to use remote access port to 42400, port forward that, and the 3rd server to 52400 and port forward to that.
@Merlinium said:
curious, but why not manually set the port on the other servers and use those instead of the default 32400 on each server? You should be able to set server 2 to use remote access port to 42400, port forward that, and the 3rd server to 52400 and port forward to that.
His router does not allow internal and external ports to be different. Since Plex Server requires 32400 (it can’t be changed), he can only use his router to map one path to one server. Other routers allow you to do this:
192.168.1.50 - internal port 32400, external port 40000, protocol TCP
192.168.1.51 - internal port 32400, external port 41000, protocol TCP
Actually my router allows me to manually set external to internal port but when i use the 32400 as the internal port on both 192.168.1.50 and on .51 it informs me i have a port overlap. Which is stupid. I actually tried the exact settings you listed with {external ip} :40000 to internal 192.168.1.3:32400 and {external ip} :41000 to internal 192.168.1.6:32400 and i am told that is a port overlap and it even highlights in red (and blinks) the 32400 piece.
I see this as a software mistake in that there should be ZERO issues with that setup however i found a solution that works although it is a terrible idea.
I can list a dmz zone ip and give my 192.168.1.6 machine access directly to the internet and testing proves it works. So i should get a separate router of some kind plug that into my main modem and plug the computer only into that device and set that router as a dmz zone.
192.168.1.1 (main router) points dmz to 192.168.1.2 (load balancing tp link with firewall) then plug in plex server and set static 192.168.1.6 and it would effectively isolate 1.6 from the rest of my network but achive my goal with multiple plex servers running. not elegant but effective in testing so far.
ok maybe I am missing something here, but from what i can tell, you can set up remote access manually with a different port #. Default mode is 32400, but manually you can select a different port number like 40000. then use the router to port forward to that servers IP and port number.
@Merlinium said:
ok maybe I am missing something here, but from what i can tell, you can set up remote access manually with a different port #. Default mode is 32400, but manually you can select a different port number like 40000. then use the router to port forward to that servers IP and port number.
No, you can’t change the Plex port. It is always 32400.
@Merlinium said:
ok maybe I am missing something here, but from what i can tell, you can set up remote access manually with a different port #. Default mode is 32400, but manually you can select a different port number like 40000. then use the router to port forward to that servers IP and port number.
No, you can’t change the Plex port. It is always 32400.
Later tonight when everyone is off of my server I will test this, but i can swear that I had changed the port # before when I was building the new server and testing access to it while still running the original server.
@Merlinium said:
ok maybe I am missing something here, but from what i can tell, you can set up remote access manually with a different port #. Default mode is 32400, but manually you can select a different port number like 40000. then use the router to port forward to that servers IP and port number.
No, you can’t change the Plex port. It is always 32400.
Later tonight when everyone is off of my server I will test this, but i can swear that I had changed the port # before when I was building the new server and testing access to it while still running the original server.
Nope, there’s no setting or switch or modification of the internal port that Plex uses. You can pick any external port (if your router supports it) and send it to the IP address of the Plex server at port 32400, which allows you to have multiple servers with remote access.
If the cable company router is failing at so basic a task the best solution would be to get a “good router” and put theirs in bridge mode. I’m sure everyone here can suggest their own personal “good router”. Though clearly a Netgear Nighthawk R7000 running DD-WRT(Kong) is the best choice.
If you don’t want to do that though you still have other options, for instance you could port forward all the external Plex ports to one machine and then redirect them from there on to the correct machines. On linux you’ve got iptables, or windows netsh & portproxy, on either you could install nginx (or similar).
I like the high end ASUS routers myself but the Netgear Nighthark is a very good router as well.
Basically your way around it is to either set the cable companies router in bridge mode or if you can’t do that then just use NAT (on by default) with your own router behind it using a different IP range. For example your default router will probably use the default space of 192.168.1.x and you would setup your own 2nd router with any other IP range such as 192.168.2.x. This setup will also work well with multiple servers if you can’t do bridge mode.
Apparently i never closed this post…
Ultimately i did as Cayars suggested only through my work i was able to get a Fortinet device called a fortigate. I put the modem in bridged mode and was able to set up my servers after a couple rebuilds. Took a couple of months to work out and in that time i stopped monitoring this thread it seems…
