NETGEAR Orbi 750 Series mesh port forwarding is not working

The checks in more detail

The common reason a forward fails is a modem in front of the router that is also routing. If your provider's gateway has its own firewall and addressing, incoming traffic is stopped there, and you need to set the gateway to bridge mode, or to forward the same port to the Orbi's address as well. Check the Orbi's WAN address on the main status page: if it is private, in the 10, 172.16 to 172.31, 192.168 or 100.64 ranges, the router is behind another router or the provider shares an address, and no forward from the router alone will work.

Test from outside, on mobile data, not from inside the home. If the forward looks right and still fails, check the application and the device firewall: the app must be running and listening on the port, and the device's firewall must allow it. Port triggering is an alternative for applications that open ports on demand, and it can help old games. Remember that an Orbi system's satellites do not forward, only the router does. Update the firmware and restart. If you have dynamic addressing at home, use a dynamic DNS name. Keep forwards to the minimum, and remove ones you no longer need.

If a rule will not save, check that the ports do not overlap with the router's remote management port. Contact Netgear with the serial number if the page misbehaves. The Orbi 750 series is a Wi-Fi 6 system, and the rule is made on the main router, not on a satellite, so make sure that you are signed in to the router unit. If your internet provider supplies a modem that also routes, you may have two routers in a row, and the forwarded port must then be opened on the provider's equipment as well or the modem placed in bridge mode. A rule that works on the home network but not from outside usually points to this second layer.