I’ve been using Plex for over 4 years and just recently have run into an issue with remote access. My ISP changed their routers which no longer have a bridge mode but do offer a DMZ plus mode (still NAT). Anyway, I can’t get direct access remote to work now and I’m running out of places to look. I’ve hunted the forums but nothing suggested seems to mesh either. Here’s the details … external modem has an IP, my router (in DMZ mode) gets an IP assigned in the 172.x range. On my router I have a static route for anything coming in on 32400 to send to my internal media server on my 192.168.x range so yes potentially dual NAT … that being said Plex is the only thing that doesn’t work with this schema. Plex locally shows Private 192.168.69.169:32400 (green arrow) Public 104.152.x.x:32400 (ugly red X) Internet.
I’ve manually specified 32400 as my port and have a forwarding rule which does in fact forward all incoming on 32400 on the external IP address to my internal 192.168 address. To test I just did a simple telnet:
$ telnet 104.152.x.x 32400
Trying 104.152.x.x…
Connected to 104.152.x.x.
Escape character is ‘^]’.
^]
telnet> quit
Connection closed.
I can also connect to it via web browser going to the external address hitting http://104.152.x.x:32400/web but when I load that it still spins at looking for servers than says it’s unreachable.
Any ideas on what to check next?? I have a friend who has basically the same set up (same ISP etc) and it finds his no problem. The only difference is that I’m using DynDns as a service but it does resolve the external IP and I can connect to all my other port forwarded devices with no issues.
Any ideas?
Something else I’ve noticed … MyPlex: Sending Server Info to myPlex (user=my_user_id, ip=, port=32400)
The ip is not being submitted properly (or at all) to myplex from the server. Any ideas why this would happen??
OK everything is working now … I went through tons of forum posts and errors and found people having issues with jumbo frames enabled so I checked every single damn device I had and *NOTHING had it enabled … until I did a friggn ifconfig on the interface on my server … yup … MTU 9000 smacks head … I have no idea when I may have changed this although I had been testing JF on my internal network at one point … odd that it just started impacting me after my external modem was upgraded.
Anyway … set the MTU back to 1500 and magically everything works!
COMCAST USERS: If anyone else comes here looking for problems with this, but doesn’t have the same issue as you (like myself) - here is another possible fix. If you have one of the newer Comcast routers PLUS a separate router (and don’t care about Comcast’s wireless capabilities), log into the Comcast router (http://10.0.0.1 - username and password are admin/password by default), change to Bridge Mode. Just another possible solution that worked for me and might work for others.
@rdfrancis516 said:
COMCAST USERS: If anyone else comes here looking for problems with this, but doesn’t have the same issue as you (like myself) - here is another possible fix. If you have one of the newer Comcast routers PLUS a separate router (and don’t care about Comcast’s wireless capabilities), log into the Comcast router (http://10.0.0.1 - username and password are admin/password by default), change to Bridge Mode. Just another possible solution that worked for me and might work for others.
yeah smart move as comcast routers are junk.
