NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

JustinDS89's avatar
JustinDS89
Aspirant
Jan 11, 2018

Orbi RBR50 - Port Forwarding Not Working

I have an Emby media server set up which works great locally, but does not work remotely. I have the neccessary ports forwarded in Orbi, but it doesn't work at all.

 

I have checked with various port checkers and they all show that the port is closed. It's almost like the port forward rule is not actually taking affect. I have rebooted the router also just to make sure.

 

Any ideas? Or is something wrong with the router?

 

Thanks,

Justin

Troubleshooting

4 Replies

  • DarrenM's avatar
    DarrenM
    Sr. NETGEAR Moderator
    Jan 15, 2018

    Have you checked with your ISP that those ports are not blocked by them? or if you have a combo modem router that you have them opened on the ISP router.

     

     

    DarrenM

    • JustinDS89's avatar
      JustinDS89
      Aspirant
      Jan 16, 2018

      Thanks for the replies!

       

      I forgot to post back, but I actually figured this out. My modem had everything restricted by default so I forwarded the port from my modem to the router and then forwarded the port from the router to my PC and everything is working.

       

      Justin

      • QQQQ's avatar
        QQQQ
        Aspirant
        Jul 09, 2018

        Found the custom button (not a drop down) and that seems to be working ok. Problem resolved. It's not an elegant method for doing this and the "http" drop down is deceptive, but it's working now.

         

        Thank you everyone for your help on this.

  • CSK401's avatar
    CSK401
    Aspirant
    Jan 16, 2018

    You don't say which ports or protocol you are tring to open;  I have opened both ports 80 & 8080 for HTTP for some webcams; this has worked perfectly on two different routers.  I did run into some proceedural issues; such as I had to open 8080 first for the first internal IP; edit the name to something other than HTTP; then go back and open port 80 for the other internal IP.  Then you MUST reboot the server for the changes to take effect.  hope that is of some assistance.