Remote access not sticking

Server Version#: 1.1.x
Player Version#: Smart TV app / Smartphone app

Ok I dunno what am doing wrong but here’s my setup.

I have a tiny Technicolor modem that provides my main router Internet through WAN port, all my devices as a result connect to the Internet through router not modem. I only use modem coz my router doesn’t have a phone line port (ADSL).

My Plex Server is on a PC running Linux Mint. I have enabled port forwarding on that router, Btw it’s a Linksys WRT3200ACM. As result I can locally watch my movies just not outside home.

Don’t forget everything is connected to that router coz it has Gigabit LAN which my modem doesn’t.

My problem is I can’t get Remote access to stick. It says fully accessible for a minute then goes red saying something about Double NAT which I don’t understand.

Now what I have gathered so far is, that my modem provides IP ranges of 192.168.1.x whereas my router 10.134.0.x which are two largely different ranges. I think that’s where my issue lies.

How can I fix it so Remote access sticks? Mind you I did read the double NAT FAQ but still do not understand anything.

Kindly note that I am a network noobs. I don’t know first thing about networking. So please help me in the simplest way possible.

I hope I explained my issue well enough.

You’ve explained very well.

Double NAT is when the internet (WAN) IP address given to your modem gets changed twice its way to your computer. The norm is to have it change only once.

The norm is:

111.222.333.444 (Public IP) -> Modem/router -> 192.168.0.x (Your LAN) -> PMS

Double NAT is:

111.222.333.444 -> Modem/router -> Something uncontrollable -> Modem/router -> 192.168.0.x

Since Remote Access is PMS talking directly to your modem/router, when in a double NAT configuration, PMS can’t reach it because of how networking works.

I can’t imagine the modem can only work in this mode.
Connect a device directly with a LAN cable to the modem.
Try to Connect to http://192.168.1.1 or http://192.168.1.254.
On the Configurationpage, search for a setting called Modem mode, the goal is that the router gets the public ip from the modem.

My situation is PMS is connected to router not modem coz modem is 10/100 whereas router is 10/1000…

Router IP : 10.134.0.x
Modem IP : 192.168.1.x

Where do.I find this modem.mode? Router or modem? So router has to be on the 192.168.1.x as well?

TechXero,
This is Double NAT because 10.x.x.x is a private LAN (NAT #1) and 192.168.1.x (NAT #2) is also a private LAN.

If you want Remote Access to work, you must perform the port forwarding manually and assign ports.

Like I said before, I did the port forwarding to 10.134.0.161:32400 which is Server IP + Port. Still ain’t working…

Where is the server? on the 192.168.1.x?

What is the toptology?

Internet -> router 1 -> 10.x.x.x -> modem/router -> 192.168.x.x -> PMS ?

Modem to router. PMS is on router not modem… So Internet (modem) -> router -> PMS (10.134.0.x)

so

INTERNET -> Modem (10.x.x.x) -> Router (192.168.x.x)-> PMS ??

Correct me if needed and please tell me the port assignments ? what goes to which port?

Modem is 192.168.1.x -> Router (10.134.0.x) -> PMS (10.134.0.161) port forwarding is done on 10.134.0.161:32400

Thank you.

Internet (port 32400) -> modem -> (32400) router (10.134.0.x) -> PMS (32400) … as example port.

And you “Manually specify port”, specifying port 32400 in PMS ?

I tried both manually enabled and disabled still same issue.

whenever you have manually specified forwarding , you must tell PMS.

The reason for this is to prevent it from trying to establish a port forwarding on the inner-most device.

Without getting in the devices (teamviewer) there’s nothing I can do except advise you. There must be a flag you’re missing. TCP inbound, No need for UDP. (Just stating the obvious in hopes of jogging something)

I shall give you TeamViewer access once am home. If that’s ok. Will finish work tonight at 7pm in 11 hours.

Btw thanks for all your help. See you tonight on TeamViewer :+1:

Edit : will be home soon hope to get this resolved

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.