Router it works with - Netgear RBK50
Printer - Richo SP C250DN
I can visit the Richo page with http://local-address of the printer and can see the status page.
However when I try to connect printer with windows it doesn't connect.
When I switch the wifi over to Orbi (model above) windows is able to recognize and register the printer.
Can you connect it to Nest Wifi by ethernet cable? This diagram shows how:
I'd also try to update the printer firmware:
And make sure it's not stuck with an IP from your previous network, check the Google Home app for what IP it gets. It should be 192.168.86.X.
If it still does not work, I'd ask Ricoh support. Devices on same SSID, but on different bands (2.4ghz, 5ghz, and 6ghz if Nest Wifi Pro) are not blocked from communicating with each other, they are on the same LAN.
I will try connecting via ethernet for troubleshooting but it needs to work on wifi.
Firmware is latest - already did baseline troubleshooting.
Advanced IP scanner shows the printer connected - address is listed. I also prited test page with the ip to confirm its the same. I can also access printer's internal http server serves (status) via http for that same 198.168.86 address in the browser its connected to network.
Also simply switching out the Nest with Orbi works just fine so printer is not an issue.
That eliminates printer as an issue. Only thing I can think of is that nest is blocking other port/printer communication for some reason !.
One more question: Is the modem/ ISP equipment in front of the primary/ main Nest Wifi unit in bridge mode, not broadcasting any Wi-Fi? You are connected with the computer to Nest Wifi, either wirelessly or by ethernet?
Some other mesh unit manufacturers put their units in bridge mode if they detect double NAT, Nest Wifi does not.
Configuration is as follows -
Desktop -> Hub -> main hub with wan -> Hub -> printer
I was able to add and print using a laptop in the same room (connected to the same hub) as printer and it works fine.
However when I bring the laptop where my desktop is it doesn't work.
So the issue is somewhere in hops between hubs?!
@olavrb, appreciate your helpful response.
@harit, give these steps a whirl:
Factory reset your printer to ensure that it’s not connected to any Wi-Fi network. Then, create a hotspot with a mobile phone. However, 2 mobile phones are required:
Use the first device to create a hotspot (mobile phone).
How to set up a mobile hotspot:
Go to Settings.
Tap the Network & internet option.
Select Hotspot & tethering.
Tap on Wi-Fi hotspot.
Set up the hotspot name and password the same as the primary network.
Choose the AP Band > 2.4 GHz band > Apply.
Go to Settings.
Tap on Cellular. Tap the slider to turn Cellular Data on.
Under Cellular, tap the slider to turn Personal Hotspot on.
Tap the slider next to Allow Others to Join.
Set up the hotspot name password the same as the primary network.
To change the hotspot password, under Personal Hotspot Wi-Fi Password.
To change the hotspot name, go to Settings > General > About > Name.
Use the second device to connect to the mobile hotspot.
Disconnect all of the Google Wifi or Nest Wifi points from the power outlet.
Connect the device to the 2.4 GHz band of the hotspot with the same SSID and password of the current network (case sensitive).
Once connected to the hotspot, plug in your primary Google Wifi point or the Nest Wifi router.
Turn off the hotspot and check if the device automatically connects to the Google Wifi network.
Let us know how it goes.
Hi Abi thanks for the response. I am not sure what these steps will accomplish. As mentioned the printer is already connecting to the network over 2.4ghz to nest. Can you please explain what do you think is the problem and why these steps above would solve it?
Doing these steps will help us make sure that any previous settings in your printer are removed once you do the factory reset. Try the hotspot method I mentioned and let us know if it helps with the issue. We'll wait for your update.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.