NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot ping the device in same network (MR60)
Switched to this device 3 days ago and having a hardtime managing my network since then. Worst customer-care support ever even with premium support Spend Three hours on calls all-together today wit...
Someone please mark this topic as unsolved as no workaround exists.
Workaround to put in another router and use MR60 as an AP, is like buying a new car but being forced to drive the old one because new one does not have wheels.
For those of you saying "I would love to have some sort of firmware update that would allow traffic to/from the wired ports on the MR60/MS60 to be bridged/switched onto the wifi network, so that my wifii devices could talk with my wired NAS when the MR60 is in router mode."
Let me tell you: this is basic LAN routing capability and not something nice to have. Is an undeniable defect which Netgear did not catch.
I have the same problem. Two wifi connected printers can not be used/pinged if the computer is connected to the same satellite as the printers. If I move the computer to another satellite it works fine. As a workaround I connected the printers via wired connection and l can use the printers now even if I'm connected to the same satellite. Did anyone found a solution to communicate wirelessly with devices connected to the same satellite? This might require a firmware update. Netgear please look into it.
Is there a class action lawsuit for this yet? Absolutely ridiculous problem to still be having with it being on the market this long.
Hello everyone,
For those still experiencing issues, please send me a private message with your email address and serial number.
Regards,Christian
Follow-up: most likely explanation seems to have been "user error" on my part!
After a helpful several-hour-long telephone investigation with Jason from Level 2 tech support, we resolved my issue with the MR60 router + 2*satellite nighthawk mesh-networking system by updating the firewall settings on my Synology NAS.
It turns out that my old TP-Link network was 192.168.0.*, while my new Netgear MR60 network is 192.168.1.*. In my initial reconfiguration after buying the Netgear router in Dec 2020, the Synology DSM had correctly picked up a 192.168.1.* LAN address via DHCP from the MR60 router, but its firewall settings were still configured to grant permissive access only to 192.168. 0.*. Oops. The crucial hint came when I put the wired connection of a new Intel NUC side-by-side with the Synology NAS, and I was able to ping the NUC but not the NAS.
I am still puzzled that I had also observed, back in Dec 2000, that I was unable to ping a wired Brother printer that was side-by-side with the NAS, but as I write today, I am able to ping, from my wifi network, both the Synology NAS and the Brother printer, both of which are connected to the LAN port on the MR60 router via an unmanaged Netgear switch (since the MR60 has only one LAN port).
So this issue appears to be fully resolved, thanks to the patient assistance of Jason from L2 support.
I'm curious whether any of the other, similar reports in this thread persist after careful investigation.
We resolved this last week, thanks to Jason in L2 support. I posted a longer message in another thread. Issue was synology NAS firewall had rules set to allow 192.168.0.* whereas new MR60 router switched over to 192.168.1.*, so even though NAS was getting 192.168.1.* LAN address via DHCP from MR60, its firewall was rejecting local pings. As far as I can tell, it was "user error" on my part.
