RS700 Nighthawk BE19000 - Port forwarding not working, even after new Firmware Version V1.0.7.86_2.0

[tamayok]

My new RS700 Nighthawk BE19000 - Port forwarding not working, even after updating to the new Firmware Version V1.0.7.86_2.0

I have rebooted computers, router/modem many times and now also disabled the integrated Netgear 'firewall' service.  The computers have fixed IPs which are granted/respected by the Netgear so that's not the problem.

There are a few THREADS regarding this already (for example https://community.netgear.com/t5/Nighthawk-with-WiFi-7-BE/Port-Forwarding-on-RS700/m-p/2338272#M229)  and they are 'solved' by applying a firmware that Tech Support apparently sends directly to the customer.

Will need to return this 2nd Netgear device.

[ShadowMario3]

Have no issues with port forwarding custom ports on my RS700 on the latest firmware (1.0.7.86). Have you tried seeing if another router is able to port forward the same port, and if it can, have you tried reaching out to Netgear to see if they can help you resolve the issue?

[tamayok]

Yes, my old router is able to port(s) forward the same port(s).

[tamayok]

I reached out to Netgear support.  But still nothing as far as solution.  This is my 2nd RS700.  Some step might be missing in the configuration but nothing stands out.  I've tried many things already.  Strangely several others have posted threads regarding Port Forwarding and the RS700.

[tamayok]

Beyond: Advanced Setup > Port Forwarding and input of the custom service, port # and internal IP. Where else have you configured the RS700 in order to get Port Forwards working?

[FURRYe38]

What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended. 

[ShadowMario3]

---

@tamayok wrote:

Beyond: Advanced Setup > Port Forwarding and input of the custom service, port # and internal IP. Where else have you configured the RS700 in order to get Port Forwards working?

---

I haven't configured port forwarding anywhere else. Advanced Setup > Port Forwarding was the only location I needed to worry about.

[tamayok]

Thanks for the reply,

I get internet service from an ethernet cable.  So the router (in this case the Netgear) also acts as a modem, so to speak.  The RS700/Netgear is offering great speed both wireless and wired (to my computers). 

But any/all port-forwarding instructions are ignored, even though the computers still get the correct and previously assigned (Fixed) IP.

[tamayok]

Thanks for the reply.  I thought so but wanted to make sure the Netgear didn't require multi-steps for setting port-forwarding (other than those in the dedicated form: internal IP, ext-int Port #, etc)

[ShadowMario3]

---

@tamayok wrote:

I get internet service from an ethernet cable.  So the router (in this case the Netgear) also acts as a modem, so to speak.  The RS700/Netgear is offering great speed both wireless and wired (to my computers). 

But any/all port-forwarding instructions are ignored, even though the computers still get the correct and previously assigned (Fixed) IP.

---

The RS700 is strictly a router, not a modem. By "internet service from an ethernet cable", is the other end of the ethernet cable connected to a modem (cable), ONT (fiber), or another router? If it's connected to another router that isn't set to bridge mode, you might need to make other configurations on that router.

[FURRYe38]

What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?

[tamayok]

The RS700 is connected to the ISP's provided ethernet cable which is distributed building-wide. There is no intermediate modem.  When I connect such ethernet cable to other routers, such as a Securifi Almond, I am able to set and do port-forwarding.  The Netgear ignores the port-forwarding instructions but does provide internet connection otherwise and either grants IP addresses (DHCP) or it respects existing Fixed-IPs.

[FURRYe38]

I recommend you reach out to NG support and ask them for continue help and information. 
Might check to see if there maybe any beta FW versions available that may fix what your seeing. 

@BH-C @DarrenM