NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port forwarding problem RBR50
Help, I have installed a new Orbi RBK50 with a Dratek Vigor 130 modem. This replaced my BT Hub 6. I have a CCTV DVR with a No-ip DNS which has been working fine on my old BT Hub. I coped the open por...
Kentboyjohn wrote:
Ok thank you for your help.
Looked up the DNS domain and that IP address shows different to the one I was using and thought the DVR was. I tried using that for port forwarding but when trying to apply it states 'This IP should be in the same subnet as the LAN IP'
Looked up the WAN IP of the Orbi as your advice but cant see anything under the Router status settings as you advise and any IP address I can see there does not match the one found against my DNS look up.
This is sounding promising!
There are two sets of IPs in play here--public WAN addresses and private LAN addresses.
The public WAN IP address of the Orbi router should be shown under the "Internet Satus" display. See attached screen shot from the user's manual. Your No-IP dynamic DNS must resolve to this WAN IP, or port forwarding will not work. You should also see the same WAN IP if you go to http://www.whatsmyip.org from a device connected to Orbi.
Your DVR will have a private LAN IP when connected to Orbi, something like 192.168.1.25. When you setup your forwarding rule, you must reference the private LAN IP of the DVR as the Internal IP address in the forwarding GUI.
It would help if you posted your IP addresses and some screen shots of what you are entering. You can replace part of the WAN IP address for provacy, e.g. 71.23.XX.125.
It could be a couple things. If your Dratek is doing any routing, you would need to forward ports on both the Dratek and the Orbi. Also check to make sure your DNS entry is updated and accurate.
Log into Orbi and look up its WAN address. If it's not a public IP address, then you have a problem with dual NAT. If it is a public address, try port scanning using the numerical IP address of Orbi's WAN interface instead of the domain name.
Ping your domain name (from a device outside your LAN) and make sure the DNS entry resolves to the WAN IP of Orbi.
I am sure thats a very good answer but you have lost me as that seems very technical. The Draytek has no port forwarding option and I am told its straight through so will have no effect on the Orbi. If I swap it back to the BT Hub it works fine so why is the Orbi so difficult to set up?have I wasted £300!
Kentboyjohn wrote:
I am sure thats a very good answer but you have lost me as that seems very technical. The Draytek has no port forwarding option and I am told its straight through so will have no effect on the Orbi. If I swap it back to the BT Hub it works fine so why is the Orbi so difficult to set up?have I wasted £300!
Did someone else setup your CCTV DVR or did you do it yourself?
Your best solution is to leave your BT hub in place and run Orbi in Access Point mode.
I aset the DRV up myself 5 years ago and has worked perfectly since. I dont really want to leave by BT Hub in place as I spent £90 on the Vigor 130. Why would the BT Hub make a difference as I would only be using the Modem part. If I set port forwarding on the Orbi why doesnt those ports show as open. Doesnt seem good to me if it only half works!
Kentboyjohn wrote:
I aset the DRV up myself 5 years ago and has worked perfectly since. I dont really want to leave by BT Hub in place as I spent £90 on the Vigor 130. Why would the BT Hub make a difference as I would only be using the Modem part. If I set port forwarding on the Orbi why doesnt those ports show as open. Doesnt seem good to me if it only half works!
Assuming you have the Dratek and Orbi configured properly with Orbi in router mode, and assuming everything else is working except for public access of your DVR, there are two possibilities to check:
1) It's possible your Dratek/Orbi combo has pulled a new public IP and your dynamic DNS entry has not updated yet. This would mean public queries are not mapped to the WAN IP of Orbi. It may take several hours for DNS entries to update.
2) Double check to make sure your port forwarding is setup correctly, especially if you copied the rules from your old router. Make sure the forwarding rules reflect the current LAN IP of the DVR when configured with Orbi, and make sure you can access the DVR over the LAN using that LAN IP. It's likely that your DVR has a different IP address with Orbi than it did when it was behind the BT. It's also possible the DVR was configured with a manually entered IP, which might not be on the same subnet as Orbi. Even if the static IP is on the same subnet, it could conflict with a dynamic IP handed out by Orbi to another device.
Etiher of these conditions would cause the online port check to fail.