NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi & the new Roomba i7+ connectivity
(I apologize for the repost. There was some sort of techinical error with my original post.) We recently purchased a Roomba i7+. We could not get it to connect to Roomba's servers to update it's s...
Yes if you had a modem/router combo before and it wasn't bridged, the Orbi will re-configure for 10. address pool. Since you have the newer SB series modem only, I presume you haven't every reset the Orbi thus keeping the 10 address pool. This is fine. It could be possible that maybe if you have not done a reset on the Orbi since, then maybe you can do this as a last resort.
Yes you set up the DMZ for the 3700 correctly. I was hoping this would help avoid any issues between the Orbi and Roomba however someting seems to be keeping the Roomba from fully connecting. It's possible there is some port issue or someting on Orbi thats stopping it.
Yes you'll see other wired devices on the 3700 as it's connected client app is searching was connected to it's LAN port thus seeing other devices stemming from the Orbi thru the 3700. This is expected.
If you decide to do the factory reset on the Orbi, go ahead and turn OFF the 3700 and Roomba for now. Set up the Orbi router from scratch, walk thru the setup wizard. This time you'll get a 192.168.1.1 on the router, You might first test the Roomba to see if it connects thru the router first. Then try setting WPA to disable temporarily. If the Roomba still does not connect fully with WPA disabled and it's services don't appear, then Roomba and NG need to review this and hopefully collaborate and find a fix. Be sure to re-enable WPA2 and AES after testing the Roomba.
Try this, set up Guest network on the Orib and see if the Roomba will connect here...
Try the 3700 LAN to LAN connected to the Orbi. Ensure that the 3700 is configured for AP mode fully, I don't remember if the 3700 had a web page AP option or not. You can manually set AP mode by setting a new IP address for the routers IP address from 192.168.1.1 to .1.37. Turn OFF items such as uPnP, Firewall, Guest Network Wifi and any Traffic or QoS features. Configure the SSID on the 3700 for something different and make sure the channels between the Orbi and 3700 are far from each other, they can't be on the same channe. When these are all disabled, disable DHCP server at the very last. Save settings. Then connect the 3700 LAN port to a open LAN port on the Orbi. You should be able to access the 3700 web page at 192.168.1.37 from the Orbi side of it's LAN port with a wired PC.
Thank you for your help. I believe many things I have tried have come from reading your posts in my search. :) I DID try setting up a guest network on the Orbi and connectng to that. (It did not work.) Add that to the list of things I have tried. lol
I will try the other stuff with my 3700 and get back to you.
Ok, keep us posted. I'm hoping the 3700 method will work. You may still need to put it's IP address into the Orbi DMZ as well.
You can try separating the wifi SSIDs on the Orbi however I don't recommend it as this defeats the Orbi MESH design and purpose. So this is why I suggested the use of the 3700 as an entry point for the Roomba...
JenEricRal wrote:
Thank you for your help. I believe many things I have tried have come from reading your posts in my search. :) I DID try setting up a guest network on the Orbi and connectng to that. (It did not work.) Add that to the list of things I have tried. lol
I will try the other stuff with my 3700 and get back to you.
FURRYe38 wrote:
Ok, keep us posted. I'm hoping the 3700 method will work. You may still need to put it's IP address into the Orbi DMZ as well.
You can try separating the wifi SSIDs on the Orbi however I don't recommend it as this defeats the Orbi MESH design and purpose. So this is why I suggested the use of the 3700 as an entry point for the Roomba...
You could possibly reach out to those who have been successful in seperating the freqs. The question would be did it affect overall performance of the Orbi?,..... as opposed to labeling it a defeatist effort.
This doesnt' concern performance rather operation of the Orbi and connetion with devices. Some devices have issues with MESH systems and Smart Connect. There both router Mfr and Device participants involved. Not just NG. Device Mfrs have to ensure there devices and wifi drivers meet wifi standards. They may or may not depending on how they are set up and designed. Regardless, Users shouldn't have to separate the MESH system to make devices work. I've never had to along with others. if others have had to then thats fine as well. I believe NG may be close that solution or may work towards users not being able to separate as NG wants the Orbi working as intended.
Retired_Member wrote:
FURRYe38 wrote:
Ok, keep us posted. I'm hoping the 3700 method will work. You may still need to put it's IP address into the Orbi DMZ as well.
You can try separating the wifi SSIDs on the Orbi however I don't recommend it as this defeats the Orbi MESH design and purpose. So this is why I suggested the use of the 3700 as an entry point for the Roomba...
You could possibly reach out to those who have been successful in seperating the freqs. The question would be did it affect overall performance of the Orbi?,..... as opposed to labeling it a defeatist effort.
FURRYe38 wrote:
Ok, keep us posted. I'm hoping the 3700 method will work. You may still need to put it's IP address into the Orbi DMZ as well.
You can try separating the wifi SSIDs on the Orbi however I don't recommend it as this defeats the Orbi MESH design and purpose. So this is why I suggested the use of the 3700 as an entry point for the Roomba...
Exactly. Separating the SSID's is not something I want to do just to get this to work correctly. The new i-Series Roombas are the only ones that work on both 2.4 and 5 GHz networks. Is it still possible that is what is causing the issue?
In my original post, I mentioned that I tried forcing both my phone and the Roomba to the 2.4 GHz band. (It was another tutorial I had read. I had changed signal strengths or something like that, and then verified that both were connected to 2.4 GHz instead of the 5 GHz they usually are connected to.)