NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Directions for Port Forwarding don't match what's on my screen.
I'm trying to follow the directions for setting up Port Forwarding on my new Orbi RBK753, but the directions seem to be wrong. I've seen several comments like the instructions at https://kb.netgear....
Here's also a picture matching CrimpOn's instructions and showing where the Port Forwarding controls can be found in the orbilogin.com admin website. The submenu seems to be named "Advanced" now instead of "Advanced Settings".
Mikey94025 Thanks for posting the screen shot. I know that "A foolish consistency is the hobgoblin of little minds" (Emerson) but really? Some programmer just decides one day, "Advanced Settings" is silly. I'll just change it to "Advanced". Ah, much better." Sort of like every router supporting DHCP options 60 and 61 until some guy thinks, "huh? nobody needs THAT anymore. I'll just take it out."
Somehow I'm not able to find my own postings here, so I don't know if my last attempt at a reply worked, so I'll add another.
The advice for finding the Port Forwarding settings "worked" in a weak sense. I was able to type in the info for forwarding HTTP (port 80) to our server (192.168.1.40). But when I use my phone to connect as an outsider (setting it to only use the phone system, not the local wifi), there's a long pause, then it says it can't connect.
I just went to orbilogin.com, the ADVANCED -> Advanced -> Port Forwarding / Port Triggering pGFWE, and it still shows the "HTTP 80 80 192.168.1.40" line as before. But I see no sign that it does anything. I don't see the common "Do It" sort of button that woulld tell the software to make the connection or whatever it's called here. The Port Forwarding stuff seems to have accepted it, and said nothing else. But connections from the outside still fail, so it's still in the "failed" category.
What else can I do to diagnose this failure and/or fix it?
jc1742 wrote:
I don't see the common "Do It" sort of button that woulld tell the software to make the connection or whatever it's called here. The Port Forwarding stuff seems to have accepted it, and said nothing else. But connections from the outside still fail, so it's still in the "failed" category.
This is another example of the Orbi inconsistent interface. Many operations require clicking the "Apply" button at the top of the page to have changes take effect, but the Port Forwarding does not. Once an rule has been created, it is operational.
I had assumed that the only change was replacing a router that forwarded ports to the web server with the RBK753. Port forwarding has two requirements:
- That the Orbi router be totally open to the internet, i.e. not "behind" another router (which would block incoming connections).
- That the target device is accepting connections. Windows Firewall, for example, has separate rules for public networks (the internet) and private networks (the local LAN subnet).
As FURRYe38 suggested, knowing what equipment is supplying internet to the RBR750 router will enable us to see if that device is actually a router.
Another step is to verify by using one of the internet sites that report open ports. My favorite is Gibson Shields Up!
jc1742 wrote:
Somehow I'm not able to find my own postings here, so I don't know if my last attempt at a reply worked, so I'll add another.
The advice for finding the Port Forwarding settings "worked" in a weak sense. I was able to type in the info for forwarding HTTP (port 80) to our server (192.168.1.40). But when I use my phone to connect as an outsider (setting it to only use the phone system, not the local wifi), there's a long pause, then it says it can't connect.
You may have Double NAT but please follow the community FAQ instructions to verify that your port and server are exposed to the Internet properly.