NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Wireless Printer connection sharing across RBK30 router and Satellite.
Hello All, I have a Orbi RBK30 running with one main unit and one Satellite. About 10 devices using the system with some connected main router and other to Satellite. No performance issues for th...
Hello all,
RIP does not make a difference. Finally got some time and ran a low level network scan. Found packets getting lost between router and satellite.
Tired full power down and other scenario. Finally gave up and factory reset with backup.
Restored from backup and then upgraded to today's latest patch. RBR40 2.3.5.30 and RBW30 / V2.3.5.6. Full power down and generated new password for Satellite and Router communication.
Added device one by one.
Ping works, Printers work, Network scan is clean. All Device on DHCP.
Access control on with "Newdevice addition."
Will let things stabalize and then change access control to "Block all new device.".
Fingers crossed.
Thanks for all you help and assistance.
Hello CrimpOn.
Let me disable the RIP and test it out. Will get back to you soon.
Thanks for all your assistance and advice. I appreciate it.
Hello all,
RIP does not make a difference. Finally got some time and ran a low level network scan. Found packets getting lost between router and satellite.
Tired full power down and other scenario. Finally gave up and factory reset with backup.
Restored from backup and then upgraded to today's latest patch. RBR40 2.3.5.30 and RBW30 / V2.3.5.6. Full power down and generated new password for Satellite and Router communication.
Added device one by one.
Ping works, Printers work, Network scan is clean. All Device on DHCP.
Access control on with "Newdevice addition."
Will let things stabalize and then change access control to "Block all new device.".
Fingers crossed.
Thanks for all you help and assistance.
I was having a similar problem. I was not able to access my NAS from two of my computers, but I could from a third. I spent quite a bit of time messing with Samba and SMB (as I had recently installed the Win10 1903 update), but not only could I not access via SMB, I could not ping. Using Wireshark, I was able to watch the pings go out, but no response. I could also not ping from the server back to the computers.
Eventually, and accidently, I moved the working laptop to another part of the house, and it stopped connecting to the NAS. This got me thinking about my Orbi setup. On a whim, I changed the RIP version from Disabled to RIP-2M, as 2M has to do with multicast packets (such as used by Bonjour and other modern dynamic addressing services). After changing the RIP version and a router reboot, everything was working again.
So, either I just needed to restart my router. Or, the 2.3.5.30 firmware created a issue between my RBR50 and RBR30 for handling multicast packets.
Once things settle out, perhaps I'll turn RIP off and see if everything keeps working to determine if all I needed was a reboot.
Thanks for letting us know.
Has a factory reset of the RBR and setup from scratch been performed after updating to v30? One more thing to try to see if printer sharing and such using defaults gets resolved with out having to change RIP settings.
ALso be aware that SMB v1 is disabled now in Windows 10. You can enable it.
RetroViator wrote:I was having a similar problem. I was not able to access my NAS from two of my computers, but I could from a third. I spent quite a bit of time messing with Samba and SMB (as I had recently installed the Win10 1903 update), but not only could I not access via SMB, I could not ping. Using Wireshark, I was able to watch the pings go out, but no response. I could also not ping from the server back to the computers.
Eventually, and accidently, I moved the working laptop to another part of the house, and it stopped connecting to the NAS. This got me thinking about my Orbi setup. On a whim, I changed the RIP version from Disabled to RIP-2M, as 2M has to do with multicast packets (such as used by Bonjour and other modern dynamic addressing services). After changing the RIP version and a router reboot, everything was working again.
So, either I just needed to restart my router. Or, the 2.3.5.30 firmware created a issue between my RBR50 and RBR30 for handling multicast packets.
Once things settle out, perhaps I'll turn RIP off and see if everything keeps working to determine if all I needed was a reboot.
Hello All,
My system has been stable for a while now. Ping response across the board is working.
Factory reset, software update and password generation... worked.
I did try multiple different scenarios for RIP and it does not make any diff. Currently RIP is off and system works. I tried with RIP on and diferent version... works.
I think the last firmware did some fix. :-)
I have a printer and a NAS on the LAN. All on DHCP. Printer is wireless and NAS is wired into the main orbi router.
Regards.
Thanks for letting us know.
Enjoy. :smileywink:
NewGeek wrote:Hello All,
My system has been stable for a while now. Ping response across the board is working.
Factory reset, software update and password generation... worked.
I did try multiple different scenarios for RIP and it does not make any diff. Currently RIP is off and system works. I tried with RIP on and diferent version... works.
I think the last firmware did some fix. :-)
I have a printer and a NAS on the LAN. All on DHCP. Printer is wireless and NAS is wired into the main orbi router.
Regards.
Well, after awhile, I once again lost my ability to access the NAS. As as expected, it seems RIP had nothing to do with my problems accessing the server from a computer connected via a satellite (but I could access via computers connected through the main router).
As before, a router restart restored the connection. I suppose I will have to perform a factory reset. It is a bit frustrating that I have to do that periodically. Perhaps it is tied to firmware updates.
A final update to share that performing a factory reset of the Router did not resolve the problem, but a full factory reset of the satellite did. Actually, I should say a reset, downloading the latest firmware again, and another reset solved the problem. It has been more than a week, and the connection issue has not returned.
