NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6700 Port Forwarding Not Working
Hello, I have tried numerous times to get any of my ports to open on my router, and despite many different efforts to get them open, I have had no success. Things I have tried (In coalition with ea...
I tried redoing the bridging process today, and doing this miraculously fixed my problem. I guess something went wrong the first time I put the modem-router into bridge mode.
All is fixed and ports open normally.
> I have tried numerous times to get any of my ports to open on my
> router, [...]
Why? Which ports? What feeds "my router"? Is it something simple
(like a modem), or another router? (Is the WAN/Internet IP address of
the R6700 a private or public address? If in doubt, report at least the
first two octets ("a.b" out of "a.b.c.d").)
> [...] despite many different efforts to get them open,
That non-description conveys no useful information about what you
did, or what happened when you did it. Standard port-forwarding
preface: In my experience, people who talk about ports being "open"
often don't understand the problem. A port looks "closed" when there's
no server program (or device) listening at that port. All the port
forwarding in the world won't help you if, at the end of the line, no
one is listening at that port number.
> I have had no success.
"success" determined how, exactly?
> -Standard port forwarding
Actual port-forwarding rules? Are you doing something (like, say,
address reservation) to ensure that then target device has a reliable IP
address?
> -Restarting router
Probably wise.
> -Allowed access through firewalls
> -Disabled all firewalls
Allowed what, exactly, through which firewalls where?
> -Enabling a DMZ
Often a last-ditch option. Less access control that way.
> I also have run programs that require certain ports to listen while
> testing them so I know that is also not the issue in this case.
You lost me.
Assuming that you're running some server program on some system which
listens to the ports of interest, can you contact that server from a
system within the LAN? If local access fails, then access from the
outside world hasn't much of a chance.
Thank you for your response and I will try to address everything to the best of my ability.
> Why? Which ports? What feeds "my router"? Is it something simple
(like a modem), or another router? (Is the WAN/Internet IP address of
the R6700 a private or public address?
a. I am trying to run game servers from my PC and need the ports open to do so.
b. I have been trying to open ports 25565 (Minecraft) and also 9000-9004 (Far Cry 2)
c. My router is connect to a modem-router. My modem-router is bridged to my router.
d. I believe it to be private but I am not sure.
>In my experience, people who talk about ports being "open"
often don't understand the problem. A port looks "closed" when there's
no server program (or device) listening at that port.
I have been actively running my server programs while testing the ports so it should be listening.
>success" determined how, exactly?
I have not been able to open any given port.
>Actual port-forwarding rules? Are you doing something (like, say,
address reservation) to ensure that then target device has a reliable IP
address?
I have just been port forwarding through my router's configuration under the default gateway. As to this, I do not have an address reservation if you are speaking about a static IP. This has not been a problem on any of my previous routers.
>Allowed what, exactly, through which firewalls where?
I have Norton Security as well as the Windows Defender firewalls on my computer (running the most recent version of Windows 10 at this time). I have allowed access to the ports through both of these and also entirely stopped their functionality. Neither of these led to the ports being open.
>Assuming that you're running some server program on some system which
listens to the ports of interest, can you contact that server from a
system within the LAN?
I am not sure what you mean entirely here. Sorry for my ignorance. If you mean can I connect to said server locally (LAN), then yes I am able to.
> c. My router is connect to a modem-router. My modem-router is bridged
> to my router.
What, exactly, is this "a modem-router"? "bridged" is a specific
technical term. Do you mean that the R6700 (WAN/Internet port) is
connected to this "a modem-router" (LAN port), or that the "a
modem-router" is in bridge mode, so that it's acting as only a modem, or
what?
> d. I believe it to be private but I am not sure.
> [...] (Is the WAN/Internet IP address of the R6700 a private or public
> address? If in doubt, report at least the first two octets ("a.b" out
> of "a.b.c.d").)
For access from the outside world to work, you'd generally want the
port forwarding configured on the outer router (closer to the ISP), and
cascading a second (inner) router would make things more complicated
("double NAT").
To avoid cascading multiple routers, the two usual schemes are:
1) Configure the modem+router as modem-only (also known as "bridge
mode"), and do all the serious work on what had been the inner
router (R6700).
2) Use the modem+router as the main router, and configure the
R6700 as a wireless access point.
Either scheme leaves you with one router and one LAN. Port
forwarding is configured on the one (remaining) router, and there's no
second router to cause trouble. Which to choose may depend mostly on
which router has a nicer feature set.
> I have just been port forwarding through my router's configuration
> under the default gateway. As to this, I do not have an address
> reservation if you are speaking about a static IP.
You lost me. With two routers, "my router" is a little ambiguous.
Copy+paste of some actual port-forwarding rules would be clearer than
any explanation of what you think they're supposed to be doing.
Port-forwarding rules include a target (server) IP address. If your
server is not at that address, then port forwarding is doomed. The
server address can be static (assigned in the server's IP
configuration), or it can be a reserved dynamic (DHCP) address, so that
the router (DHCP server) always gives it the same address.
> [...] If you mean can I connect to said server locally (LAN), then yes
> I am able to.
Yup. That sounds good. The problem may be confined to port
forwarding. (And, perhaps, the cascaded routers which complicate port
forwrding beyond reasonableness.)>What, exactly, is this "a modem-router"? "bridged" is a specific
technical term. Do you mean that the R6700 (WAN/Internet port) is
connected to this "a modem-router" (LAN port), or that the "a
modem-router" is in bridge mode, so that it's acting as only a modem, or
what?I have the modem-router in bridge mode so it is only acting as modem. From now on I will just refer to it as the modem and the R6700 as the router. Sorry for the confusion.
>With two routers, "my router" is a little ambiguous.
Copy+paste of some actual port-forwarding rules would be clearer than
any explanation of what you think they're supposed to be doing.I have tried to copy and paste but it seems to delete my post so here is a picture.
If I have missed anything please let me know. Thank you.
I tried redoing the bridging process today, and doing this miraculously fixed my problem. I guess something went wrong the first time I put the modem-router into bridge mode.
All is fixed and ports open normally.