Server Version#: 1.18.4.2171-ac2afe5f8
Player Version#:
Old 2006 dell XPS 400 running windows 7 ultimate.
When remote access is enabled it will work fine for a while but then it’ll say not available outside your network. I will disable and enable several times with several reboots and then it will work again. I have checked everything possible using the troubleshooting guide.
The only issue I can see that is left is the double NAT. I currently have a Uverse modem / wireless router from AT&T and then have my ASUS wireless router connected to that which is what I connect my house too. I do this as my ASUS has a better distance and I get quicker speeds.
Is this truly my issue? Can I keep this setup and get it to work?
Also, I was having this same issue before I updated PMS. I just updated yesterday in hopes that that was the issue.
Do you keep those two networks separated on purpose?
You can configure the ASUS wireless router to act as access point or disable its DHCP component. This way, all network devices will receive their local IP addresses from the main router (Uverse modem) and you resolve the double NAT situation. If needed you should also be able to disable the Uverse’s WIFI.
Since you entertained the idea of double NAT are you certain this is the culprit causing the issue?
I guess the main reason I keep them separate is the fact I am rather magoo when it comes to networking. When I have issues with networking, I trouble shoot the issue until it’s resolved and works. I’m not certain on how to set the ASUS up as an access point or disabling the DHCP but I’m assuming either one of those processes can be easily found on google. My question to that would be, will that screw up all my static IPS I have setup for several of my devices? I would prefer to go in the direction that will be as little work and will be minimal interruption to everything.
With your comment of disabling the wifi on the Uverse (The route I’m considering if it will solve my issue), I am confused at how that would resolve the double NAT? If nothing is connecting to it wirelessly, which would mean it’s not being used by anything, how would disabling it change anything?
To your comment of time to move on; well, it came with windows XP SP3 when I originally ordered it from DELL. So… Ummmm… Yeah. LOL!!! I did move on.
You can get Plex remote access to work within a Double NAT situation… however this can be notoriously complicated and give your remote access some hiccups (e.g. ending up with an indirect/relayed connection which has a limited bandwidth). Some users have situations where they must live with a double NAT situation – e.g. if it is induced by their ISP. For users who got into such a situation because of a misconfigured home network it’s definitely worth to resolve that issue.
You can compare such a Double NAT setup to an old-day switch board… in order to communicate with the internet, your communication is first routed to the switch board… that router will then forward the communication to the actual target.
Your setup is a role model for such a scenario where apparently two network devices are acting as the masters of their own network. The most simple way to resolve it is indeed to disable the DHCP server on the 2nd (“slave”) component.
That being said… you’re right. If you have all your static IP assignments configured on that 2nd network device, you’ll need to re-establish those on the main network device.
In a common use case that should only impact few network clients as most devices don’t need their own static local IP address. Exceptions are devices like a local (Plex Media) Server.
Disabling the Uverse’s WIFI isn’t actually necessary. I considered that if you prefer the ASUS WIFI for its better performance and therefore don’t use the Uverse WIFI, you can also disable it.
Benefits could be reducing potential attack vectors (1 WIFI is offers less potential targets than 2 WIFIs) and power consumption.
As for the Win7 comment: Just another attack vector as it’ll no longer be supported and get patches from MS. As with all of the above… in the end it’s your call.
Ugh, not the answers I was hoping for but makes sense. Not sure when or even if I will attempt this. With 4 kids, 3 PS4’s and 1 XBOX one I would send them into a melt down if I dropped the internet for any length of time. Then on top of not being able to play fortnite they would still be unable to watch plex for an unknown period of time??? That would easily knock 10 years off my life LOL!!!
Thanks for the info as I do appreciate your knowledge.
I don’t think it’s going to be that big of an effort – and it also shouldn’t take overly long.
You can minimize the time of move by double-checking upfront what devices actually need a static IP address. That way you can speed up re-assigning them a new static one.
All in all, most of your devices (such as Playstations, phones, notebooks…) don’t need a static IP address anyway. Also… Plex within your home network should be playing just fine with or without a static IP address.
