NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAXE500 custom port forwarding is not working, Parsec unable to see unless connected to via VPN
I just recently got an RAXE500, and it's on the latest (V1.0.9.78_2.0.38) firmware. I am no longer able to use Parsec outside of my home network. UPnP is enabled on Parsec (though I don't see any rules created by it in the UPnP tab on the Nighthawk). So I followed Parsec's instructions and reserved the local IP on my PC and forwarded the ports to no avail. It doesn't seem that the port forwarding is working at all. Parsec still fails to connect unless I use a VPN to access my local network, which is not ideal (the VPN introduces additional latency on top of the latency of Parsec). I have tried switching to open NAT and turning off DoS and portscan protection, and neither have solved the issue.
(Sidenote: the VPN function on the RAXE500 is not working for me, even though VPN and DDNS are both enabled. I am using the VPN on my NAS to access Parsec.)
1 Reply
My NAS is successfully opening ports via UPnP, but none of the port forwarding rules I create (like those screenshotted above) are working. I'm pretty sure this is also why the router-based VPN isn't working as well (the VPN ports, like other custom rules are reading as closed on portchecker.co).