NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Devices not connecting in mesh network??? Orbi RBK50
I have the RBR50V2 mesh router and 1 satelite that came in the RBK50 kit. I have read a couple of threads about this topic. I don't have a managed switch and I don't understand back haul. I think ...
That means that the AV receiver was using a Static IP rather than Dynamic IP from DHCP. And since the static IP was for a different subnet than the 192.168.1 subnet of your Orbi, it was not seen on the network. Glad you got it figured out now. Since you set the static IP to 192.168.1.90, I suggest adding that to the DHCP Address Reservations under the Advanced -> Setup -> LAN Setup page of the web interface to the Orbi. That way nothing else will get assigned a conflicting IP by DHCP if your receiver is off the network.
Ltripreno wrote:SOLVED!!!!
Thank you, everyone for your ideas!
I was thinking more about the IP address.
The reciever IP address was 192.168.182.1. It was configurable, so I changed the .1 to a .5
The app has the ability to put in specific IP addresses for which the app would search. I put in the .5 address. No go.
Everything else is 192.168.1.xxx. A 1 where the receiver had 182.
I went to the receiver and put in 192.168.1.90, then put that in the app. Voila!! It worked.
Don;t ask why or how...I have no idea. But it worked.
Thank you all again!! I love forums like these!
Cheers,
theoak wrote:I kind of glossed over it too ... but are you using Circle or Armour or any other type of security appliance?
I have a UTM device that just implemented a "Threat Prevention" module where web sites are ranked according to "reputation" essentially on a scale of 1 being good to 5 being bad. So I set my network to 4 to block supicious and high risk sites - sounds good right?. Netflix stopped working, my satellite reciever stopped working ... the sites these apps/devices are connecting to is crazy.
I would also try turning off any "security" to start off with to make sure Yamaha is not trying to connect to someting that the security appliance may consider "bad".
I just spent a fair amount of time reviewing every darn screen in the Orbi administrative area...security, setup, etc. I could not find anything that seemed like it would block anything. I can't find any mention of Armour. I did see Circle...it is not active.
I did upgrade the firmware. No chnage.
SOLVED!!!!
Thank you, everyone for your ideas!
I was thinking more about the IP address.
The reciever IP address was 192.168.182.1. It was configurable, so I changed the .1 to a .5
The app has the ability to put in specific IP addresses for which the app would search. I put in the .5 address. No go.
Everything else is 192.168.1.xxx. A 1 where the receiver had 182.
I went to the receiver and put in 192.168.1.90, then put that in the app. Voila!! It worked.
Don;t ask why or how...I have no idea. But it worked.
Thank you all again!! I love forums like these!
Cheers,
That means that the AV receiver was using a Static IP rather than Dynamic IP from DHCP. And since the static IP was for a different subnet than the 192.168.1 subnet of your Orbi, it was not seen on the network. Glad you got it figured out now. Since you set the static IP to 192.168.1.90, I suggest adding that to the DHCP Address Reservations under the Advanced -> Setup -> LAN Setup page of the web interface to the Orbi. That way nothing else will get assigned a conflicting IP by DHCP if your receiver is off the network.
Ltripreno wrote:SOLVED!!!!
Thank you, everyone for your ideas!
I was thinking more about the IP address.
The reciever IP address was 192.168.182.1. It was configurable, so I changed the .1 to a .5
The app has the ability to put in specific IP addresses for which the app would search. I put in the .5 address. No go.
Everything else is 192.168.1.xxx. A 1 where the receiver had 182.
I went to the receiver and put in 192.168.1.90, then put that in the app. Voila!! It worked.
Don;t ask why or how...I have no idea. But it worked.
Thank you all again!! I love forums like these!
Cheers,
I presumed the AVR had already been using 192.168.1.something. :smileyembarrassed:
Glad you found this out. Interesting. Glad it's working now.
Please mark your thread as solved so others will know.
Enjoy. :smileywink:
Ltripreno wrote:SOLVED!!!!
Thank you, everyone for your ideas!
I was thinking more about the IP address.
The reciever IP address was 192.168.182.1. It was configurable, so I changed the .1 to a .5
The app has the ability to put in specific IP addresses for which the app would search. I put in the .5 address. No go.
Everything else is 192.168.1.xxx. A 1 where the receiver had 182.
I went to the receiver and put in 192.168.1.90, then put that in the app. Voila!! It worked.
Don;t ask why or how...I have no idea. But it worked.
Thank you all again!! I love forums like these!
Cheers,
