Netgear R8300 Port Forwarding
I am sorry if this is already solved, but I cannot find any support for this issue. I cannot configure port forwarding for any port with the exception of 3389 and 8443. I have set up custom port forwarding in the advanced section of the router setting to go to a range of different port numbers still no luck. I have two desktops I would like to access remotely without third party software (TeamViewer). I have set up static IP’s for the PC’s that I am working on and I have a DDNS configured to the router, which-ever PC is configured to port 3389 works without any problems. However, when I create a new port to run the other PC on, it will not open up to the internet. I have confirmed this using port checker tools. I have also restarted the router several times with no change. I am using the latest firmware (30). I cannot seem to access the firewall setting on the router, there is no selection for it under the Advanced - Security tab, this is what I can see:
I have confirmed that internally the port works. I guess ultimately what I need is to know how to open different ports to the internet.
Re: Netgear R8300 Port Forwarding
> [...] I cannot configure port forwarding for any port with the
> exception of 3389 and 8443. [...]
"cannot" is not a useful problem description. It does not say what
you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
"3389 and 8443" are Microsoft Remote Desktop and the router's own
"Remote Managment", or what?
> [...] I have set up custom port forwarding in the advanced section of
> the router setting to go to a range of different port numbers still no
> luck. [...]
That's nice, I'm sure, but, with my weak psychic powers, I have no
idea what your actual (failing) port-forwarding rules are.
> [...] I have set up static IP's for the PC's [...]
Terminology: A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address. Which do you mean? (Either way should
give a device a reliable/fixed address, but it's nice to know what's
actually happening. Using static addresses requires more care in the
configuration of the DHCP server.)
> [...] which-ever PC is configured to port 3389 works without any
> problems. [...]
That's a good sign. Now, if anyone else knew what your failing
port-forwarding rules were, then we might have some chance of figuring
out what's wrong.
Are you doing any special Remote Desktop configuration on the
individual Windows systems (like, say, which port it uses)? (None
should be needed; port forwarding on the router should be able to do the
> [...] when I create a new port to run the other PC on, [...]
I also have no idea what "create a new port" means to you.
> [...] I am using the latest firmware (30). [...]
"30"? Do you mean "V220.127.116.11_1.0.99", or what?
> [...] I cannot seem to access the firewall setting on the router,
There is no "firewall setting on the router".
> I have confirmed that internally the port works. [...]
How, exactly, did you "confirm" what, exactly? See "As usual,
> [...] what I need is to know how to open different ports to the
Port forwarding is the likely answer, but, in my experience, people
who talk about ports being "open" or "closed" often don't understand the
But, in this case, if your (invisible) port-forwarding rule for port
3389 works as expected, then I'd guess that the likely problem is in
your (invisible) port-forwarding rule(s) for other the other port(s).
(Which, so far, I can't see. Because they're ...)