NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Port Forwarding Intermittently Fails on RAXE500
After using the RAXE500 for a period of time, some of the port forwarding rules randomly stop working. If I edit and re-apply the affected rule, it starts working again. Has anyone experienced this issue or found a way to fix it?
7 Replies
Be sure uPNP is disabled on the router.
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?Be sure uPNP is disabled on the router. = yes already
netgear raxe500 v1.2.14Thank you for your response. I’ve noticed that after my network updates its IP address (Internet, Dynamic IP), the port forwarding on the RAXE500 stops working. It only returns to normal after I re-edit and reapply the rules. Do you have any thoughts on why this might be happening?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
How is the RAXE configured for internet connection? Using the Internet port or the Multi Gig port to the ISP modem/ONT?
Be sure uPNP is disabled on the router. = yes already
netgear raxe500 v1.2.14
Thank you for your response. I’ve noticed that after my network updates its IP address (Internet, Dynamic IP), the port forwarding on the RAXE500 stops working. It only returns to normal after I re-edit and reapply the rules. Do you have any thoughts on why this might be happening?What is the Mfr and model# : Askey RTF8207W-E / Internet port
When the dynamic IP changes, that DDNS is working fine, but port forwarding is not working
There are two parts to connecting from the internet to resources on the local network:
- Forwarding specific ports to specific devices (and ports) on the local network, and
- Setting up a mechanism to ensure that external users are attempting to connect to the public IP address of the router. (Although external devices could simply include the public IP address in their configuration, the most common mechanism is to subscribe to a Dynamic DNS service (DDNS) which translates a URL into the current public IP address.
If the public IP address is dynamic, then the router has to inform the DDNS service when the public IP address changes. Because each DDNS service uses their own protocol for updating their DNS database, Netgear has included code in the router for specific providers. (My Orbi, for example, can use DDNS from Netgear, No-IP.com, and Dyn.com.)
What this appears to be is that the ISP has changed the public IP assigned to this RAXE500 and the DDNS database had not been updated when the remote connection was attempted. (Or, perhaps, the remote device had cached the previous IP address and was attempting to connect to the wrong public IP address.)
The next time a remote device cannot connect to the local network, it might be worthwhile to record the public IP address that it is attempting to reach. On Windows, for example, do a nslookup for the URL. (on the remote machine)
The router log file should contain entries every time the DDNS service is update. Something similar to this:
[Dynamic DNS] host name CrimpOnNet registration successful, Wednesday, Dec 11,2024 23:12:58
