NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Help to ensure a port is open
RBR850
Firmware Version V4.6.9.11_2.3.5
Thanks for all you folks do. I've benefitted many times.
I need help setting up my router to allow traffic to pass through port 9090. I have an app running on my MacBook that would receive packets from my iPad browser through my WiFi. The app log on my MacBook is not receiving packets and the iPad browser (Safari or Chrome) times out with a message that the server is not responding. I enter (http://) 192.168.1.13:9090. I am assuming that port 9090 is not open on the router.
I know the app is working because I can see its function when I use Safari on the MacBook and hit either localhost:9090 or 127.0.0.1:9090. Safari immediately show me what the app provides. So I think the issue lies between the MAcBook and the iPad -- my RBR850 WiFi router.
Both my MacBook and my iPad are connected to the router - I can see that in the router screen for connected devices. I have no anti-virus, no VPN running, and only 1 SSID.
I ventured into the router Port Forwarding/Port Triggering section and am unsure of what to put where in order to setup port 9090 to be open.
Would someone please give me the step-by-step on how to configure this?
Much appreciated.
4 Replies
Within the local network (LAN) all ports are open. Port Forwarding is a feature to allow access to a local device from the internet by "opening a port" through the router.
On my Windows computers, the Firewall denies all incoming connection requests unless the user has specifically told the Firewall to permit them. My guess is that the MacBook has a similar Firewall and is blocking the connection.
For certain, the router is not blocking anything.
Thank you for this education! I learned a lot and have applied it to the challenge here.
With your information I focused on the MacBook Firewall, which I had turned off earlier and had no effect on the problem.
So then I thought ... reboot the Mac and try again. Maybe the Firewall isn't an instant update and requires its settings to be re-read at boot up to become in effect.
So again I learned a lot ... with the Firewall turned off and the MacBook rebooted -- the app now works.
Thank you. Even with the app's bin file allowed through the firewall it has to be off and the machine rebooted in order for the app to work. So there must be an additional file(s) that need to be allowed through to enable the app to work with the Firewall on.
Much appreciated!
Firewalls are a bit tricky. They often have separate rules for "in" and "out" and for "private" vs. "public" networks.
In general, I prefer to keep Firewalls active and specify which applications can be reached.
