NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
sresam89
Dec 01, 2020Guide
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...
n8man
Nov 14, 2021Star
I installed the new firmware a few days ago and I been working well for me, maybe even perfectly. I haven’t tested internal network speeds yet.
UpIrons
Nov 14, 2021Tutor
Yep this is good. They finally fixed it from what I can tell..
I'm averaging a 3ms ping between 2 devices that are on disparate netgear units as well as a 12 MB/s transfer rate which is about as good as expected.
I also ran a few wireshark sessions just to look for anything weird going on and nothing is out of the ordinary, whereas before I was seeing a lot of retransmissions and outright lack of handshaking between devices.
My only wish at this point would be that they would detail what exactly they did to fix it. Doesn't even say anything in the release notes.
- Sanjith92Nov 30, 2021StarI confirm that the Chromecast issue and failure to ping satellite connected devices is now resolved with firmware v1.1.6.122 .
Hope this fix is carried forward to future updates as well .
Release notes say it fixed the airplay issue with iphone/ipad connection to apple tv , so may be same bug was causing issue for Chromecast too .- ktiedtJan 02, 2022Aspirant
Running the MR80 nighthawk mesh + 2 satellites and seeing the same problem still on firmware v1.1.6.6_3.1.93...
Kinda glad to see its not just me, but also... WTF on this being a problem for as long as this thread has been open.- FURRYe38Jan 03, 2022Guru - Experienced User
You can try more updated FW and see:
Id make a new post or contact NG support if you seem to have continued problem with this.
ktiedt wrote:
Running the MR80 nighthawk mesh + 2 satellites and seeing the same problem still on firmware v1.1.6.6_3.1.93...
Kinda glad to see its not just me, but also... WTF on this being a problem for as long as this thread has been open.