NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6300V2 Bridge Mode Prevents Port Forwarding! Help!
I have spent over a total of 100 hours trying to get port forwarding to work on my network so that I can use the remote access feature on the Plex Media Server app. I've done all the basics, rese...
That's it!
Your internet port has a 100.x.x.x address. canyouseeme.org shows a 76.x.x.x.
That says that either your ISP's modem is doing its own NAT routing or that your ISP is using carrier NAT. On paper at least 100.x.x.x is reserved for carrier NAT.
See if you can find the manufacturer/model for that modem. You also might need to contact your ISP, and see if they have some way to keep that port open.
Another thought is that you could try changing the port number (say to 49152) in the R1 forwarding rule and also in the plex server configuration. It's possible that using a port in the "private use" range will work better.
SaintGrimm wrote:
EDIT: I do believe plex uses UPnP, and I have turned it on in R1.
I saw some guides talking about enabling DMZ, but I wasn't sure which IP to set it to, multiple guides just said to fill out the IP, without saying which one it should actually be... On R1 I tried enabling DMZ and setting the IP to R2's IP and also tried setting the IP to my office PC, but that also made no difference, so I turned DMZ off again last night after trying it.
Leave the DMZ off. You shouldn't need it, and I think it just confuses things. You might also try disabling upnp on the R1 - you can re-enable when you get things working.
Try going into the R1 admin screen, and look at the internet IP address. Check to see if it is the same 76.x.x.x address that you see in canyouseeme.org. I am wondering if your ISP device is also acting as a router. If it is, the R1 internet address won't be a 76.x.x.x address.
I'm not fully sure what you're wanting me to look at, is this right? I tried to block out anything that might be bad to show this time :P lol
That's it!
Your internet port has a 100.x.x.x address. canyouseeme.org shows a 76.x.x.x.
That says that either your ISP's modem is doing its own NAT routing or that your ISP is using carrier NAT. On paper at least 100.x.x.x is reserved for carrier NAT.
See if you can find the manufacturer/model for that modem. You also might need to contact your ISP, and see if they have some way to keep that port open.
Another thought is that you could try changing the port number (say to 49152) in the R1 forwarding rule and also in the plex server configuration. It's possible that using a port in the "private use" range will work better.
It's after hours today, but I'll call our ISP tomorrow. I really don't know where another modem could even be. When we have issues and they have to come fix it, they just screw around with the box that's on the outside of the house, it's not a modem/router or anything and goes from the side of the house down into the ground.
The plex "out" port HAS to be 32400 according to their website. I've tried putting the in port as different things and leaving the out as 32400 (as described as a possible option on their website) but that didn't change anything either.
Thank you for all of your help! Hopefully my ISP can take it from here. And if they can't or if what they want me to do ends up being just as much of a headache as getting this far, I think I'll just buy a raspberry pie and wire it directly to R1 at once it seems to work when connected to R1.
SaintGrimm wrote:
I really don't know where another modem could even be.It sounds like carrier NAT then. The IPv4 addressing system (x.x.x.x) was limited to a max of 4 billion addresses (and the overall framework didn't allow all of the addresses to be used). As the internet grew, we ran out of addresses. IPv6 is the long-term solution, but rollout has been very sluggish. Carrier-NAT is a stop-gap solution - and just like home NAT it does create some connectivity issues.
SaintGrimm wrote:
I think I'll just buy a raspberry pie and wire it directly to R1 at once it seems to work when connected to R1.
If the ISP is using carrier NAT the port might fail to open (or drop) from time to time, no matter which router you connect it to.
But if R1 turns out to be reliable, you might want to invest in running an ethernet cable from the bedroom to the office. That will get you better performance anyway (locally at least).
Anyway, let us know how it works out.