NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS50 - Cannot Ping Synology From Almost All PC's on Same Network
I have had this issue for a while but it has just annoyed me enough to ask. I have 1 RBS50 and 3 Satellite RBK50. The Synology is plugged into the router and I setup a static IP for it and also made...
JoeCole wrote:Here is the part why I believe this issue is with Orbi, when I have my laptop plugged directly into the router the Synology is in I can reach the device fine, its only on wifi or when wired connection to satellites (satellites are wifi backhaul) that can no longer reach the device.
Can you confirm for us the IP address of the Synology and the IP address of the laptop where you are pinging from. They should be on the same subnet, e.g., both 192.168.1.##.
If you can't ping from one IP to another over wifi or wired to satellite, then are you also unable to ping other 192.168.1.## devices on the same Orbi network? Or is it only the Synology device that is unpingable?
If only the Synology is unpingable then is there a firewall of some sort running on it? If not just the Synology then there may be class of Orbi network devices you cannot reach (e.g., from the satellite you can't ping any devices connected to a different satellite). Understanding the nature of this network partitioning may help use trace the issue. This doesn't seem like a DNS issue if you cannot ping by IP address.
So I just set the DHCP scope to 192.168.1.21-254 which seemed to trigger a full on reboot of everything. Once everything came back up the IP address is now working again. Sadly I think it had more to do with all the devices rebooting then the change but I guess I will not know until later on. Could take some time to find out.
As for the last post, nothing special just the basic out of the box setup for the network. 192.168.1.1-255 with the DHCP range just being altered to start at 21-254 and yes all devices reside on the same subnet and all setup with default gateway 192.168.1.1 and subnet mask 255.255.255.0. Everything else pings fine from anywhere else on the network. I do have a Pihole setup for DNS but this was setup previous to this starting plus I have disabled it as well as point my devices DNS to another server when testing just to see, plus IP is just not pingable either so really shouldnt be DNS related.
No firewall, just using the Synology firewall rules to block some stuff by geolocation but I also specifically whitelisted my internal network just in case but had no change. Also using the external domain name to hit it works fine so sending traffic outside my network then back in works, just the internal routing gets weird.
Thanks for the suggestions. Just an FYI I have been a sys admin for the last 15 years now. I have never seen something like this though which is why its so frustrating haha.