Server Version#: Don’t know
Player Version#: Don’t know
NAS is MyCloudEX2Ultra; using Plex Media Server app for the EX2, not the Premium Plex.
Router is Linksys EA6900
Continue to get the “Not available outside your network” message. I’ve been through all the Troubleshooting steps as far as I can understand them. My Router says it is set to NAT and the MyCloud NAS remote access is set to “on.” Although I’m probably missing something, just not sure what to try next. Grabbed a couple of screen snips if you want them.
I did not do anything to my router until I got some direction here - afraid I’ll screw something up. It does not have UPnP and NAT is enabled. Wondered about enabling a static route???
Enabling NAT should not be relevant when it comes to activating remote access.
The static routing means that you can assign a static IP address to the machine running your Plex Media Server within your home network. While it does not „enable“ remote access itself, you should definitely have such a static (local) IP for your Plex!
Can you find any settings towards „port forwarding“ in your router administration?
All the settings in my router are the defaults. I had just seen a reference to the router using NAT-PMP to establish the connection and didn’t know if that was the same thing.
Hmmm… Interesting in the admin section that now I see UPnP is enabled there.
Probably a stupid question, but I have the NAS and I have the Plex app on my Samsung TV through which I’d like to access my NAS media. The troubleshooting refers to the “computer” running my Plex server. Can I assume that my Windows 10 computer which I’m using to access my NAS and my Plex server settings is said computer? Sheesh… I build computers and troubleshoot them for other people, but this stuff makes my brain hurt! I think I need a beer.
You should be aware that you’re dealing with sensitive settings that can significantly impact the security of your home network.
The article you followed might have referred to how to enable remote access in a NAT environment. That doesn’t mean you need to enable NAT in the first place.
As for articles… the 2 links I added above should do
Before blindly checking further checkboxes… please test if you can access your public IP address using the port 32400 (tcp) from outside your network. You can do that e.g. using a service such as canyouseeme.org
I know! That’s why I was hesitant to do anything. I haven’t checked any boxes in my router settings at all. Although I’ve been using it for at least 2 years, those are all the default settings. I will use that canyouseeme link to see what happens. I know when I manually set the 32400 in the Plex settings, I still get the “Not available…” message.
I’ve been through both those links more than once, and nothing seemed to help. But I will give it another shot.
I really appreciate the help… Troubleshooting networking issues drives me nuts.
EDIT: So I checked the “manually set port 32400” and then it with the canyouseeme link. It said, " Error: I could not see your service on xx.xx.xxx.xxx on port ( 32400 Reason: Connection refused." (X’s added by me.)
I’m going to try to manually set it in my router. This is what the PortForward.com link said to do in the Linksys Router. Second screen is Plex…
Now that you have the port forwarding setup. Try shutting down the PMS server, reboot the router and wait a minute then start the PMS back up and then check to see if Remote Access is working. If not may have to toggle it off and back on (the Disable Remote Access button).
Ha! Saw the green “available” for a split second and then it went back to the red “network not available.”
Question… in my ipconfig command prompt, it lists my device IP as 192.168.1.1 which Linksys will not accept. I used the Device IP listed on the Plex Remote Access page which was 192.168.1.142. Is that correct?
In my screen snip above, it shows a red “X” next to my public IP. Does that have anything to do with this?
Plex communicates through port 32400.
From the port forward configuration you showed above, it seems your setup is ok and should pass those requests through.
Unless you have some other router in your home network that might “interfere”, you might want to check with your ISP if they block that port (and if they can open it for you).
No other routers. I’ve thought that I might check with my ISP too when I saw the connection refused message. I have wireless broadband from a local company out here in the country.
So, in desperation, I rebooted my router and then rebooted my NAS… now I’m getting a double NAT error message. I did send my ISP a tech ticket.
My setup is: Wireless broadband from a tower to a dish on my roof. Ethernet into the house to my Linksys EA6900 wifi router. That’s all, no modems etc. NAS is directly connected to the router with an ethernet cable.
I think my brain hurts again and I think I need more beer.
So, just an FYI. I finally heard back from my ISP last night. This is definitely something they will need to enable for me. So, thank you for all your help, but none of it was going to work! I am definitely double natted according to them. This is a small company called Wisper Internet which just acquired my even smaller local ISP. The two are still somewhat separate according to the tech, so it might be tricky, but he is working on it.
Oh, the joys of living out in the country! At least I’m not subjected to the horror that is HughesNet.
