NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
port forwarding doesnt work with PR60X router and M4300-48X switch
I am unable to get the public IP to forward to an internal IP. I've setup port forwarding many times, but I can't get it working on this equipment. I'm using a PR60X router and a M4300-48X switch. ...
My custom ports forwarding works fine on my end, though I am only using it for Windows RDP:
Have no issues with the port forward working on both my main (10 gig WAN) internet and backup internet when I had to use failover.
Have you tried doing a factory reset of the router to see if that would help out? That would probably be the last thing I would do.
ShadowMario3 wrote:
Have no issues with the port forward working on both my main (10 gig WAN) internet and backup internet when I had to use failover.
One port forwarding active magically on two WAN interfaces?
Would you mind to tell us more about failover - no word of this in the user manual.
With an eye on community know-how: We're keen to know why and how you have to RDP port forwardings configured. Are these the same RDP ports forwarded from both WAN connections?
ShadowMario3 wrote:
Have you tried doing a factory reset of the router to see if that would help out? That would probably be the last thing I would do.
Suspect more a problem with ports already in use for the router own local/internal usage, like for the Web UI, when the OP does talk of http and port 80. Not the first Netgear (and other brands) router struggling over these basics. I would try some alternate port forwarding, assuming the router can deal with PAT, e.g on some random port like 80123 for example.
Yeah, from the last time I had a failover occur, I was able to use RDP through the second IP with no issues at all. I can do another test tonight to confirm this.
FWIW, my setup is I have a GoNetspeed (regional fiber company) with a static IP as my main WAN, connected to the WAN2 port. I have Comcast as my backup internet connected to WAN1, which, while dynamic, doesn't use CGNAT. Since OP mentioned that the port forward is working through another router, I assume that they are not behind a CGNAT.
As for how I did the port forwarding on the PR60X, I didn't need to specify which WAN ports it would apply to, I just made sure that External IP Address was set to "Any". First, you need to make a new rule under Service Management that specifies the ports.
Once they are added (or if you want to use one of the pre-defined ones), then you can go to the Port Forwarding page and they will appear in a list of rules when you add a new entry:
I have never used the predefined ones myself, so I was never able to check if port 80 had the issue like you mentioned.
As for why I have two RDP ports connected to the same internal IP, it's because that device is my Netgear RS700 router, which I have all of my computers hooked up to. I know that I am in a double NAT situation, but I don't mind this setup since I am still able to set up a VLAN through the PR60X so I have the RS700 dedicated for my main network and another router that is used for my Guest and IoT WiFi.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
