NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bjhoag
Apr 15, 2020Star
Nighthawk Mesh Wifi 6 Router MR60 losing connection to 2.4 devices
I have a Nighthawk Mesh MR60 with the Satelite. About once a day, it loses connection to all the 2.4 devices on my network. It remains connected to the 5.0 devices. I have to reboot the router and...
Nug
Aug 06, 2020Tutor
Wow. The form to reply to this thread asks for a model number. So I type in ‘MR60’ and it doesn’t appear and doesn’t allow adding it. How long has this router line been out?
Anyway, for the most part I’ve been pretty happy with the performance and stability of the MR60 + satellite. It’s been far better than the Telstra (Australian isp) supplied unit I was running before.
Even so, I’ve been experiencing the previously mentioned issues where some devices ‘lose the internet’. I don’t know how.. it’s so big!! Sorry, dad joke.. had to bring some humour :)
Perhaps a little more detail than I’ve read in the past 6 pages, for me, the device wifi adaptor actually stays connected to the wifi network. But the device loses its DHCP supplied address.
When manually trying to renew the DHCP lease, it rejects pretty quick and defaults to the 169... address, which denotes self-assigned and infers inability to get a lease.
Yes rebooting the router, usually solves the issue. But also stops everything else on the network.
Also, setting a manual IP for that device (go high in the range to avoid conflicts) without rebooting anything has worked for me every time (and is slightly more convenient).
Having said that, it’s a major PITA that this brand new netgear product running the latest firmware as of August 6th 2020, has issues with a simple DHCP service.
Searching for ‘DHCP’ across this forum, I can see this issue seems to occur with many other netgear devices.
netgear, I’m not sure what more info the users on this forum (your customers) can provide. I’d be surprised if this issue has not occurred in your QA labs. But if by some chance it has not, maybe you should do some real-world testing where there are lots of devices, walls, microwave ovens, xboxes and competing wifi networks. Maybe that will shed some light?
If not, maybe you need to pay your customers to diagnose this apparently widespread issue, rather than asking us to pay you.
This could be your moment. We’re all struggling thru covid, some countries and cities harder than others. I’m currently in city-wide lockdown in Melbourne, Australia. We turn to you to help us work and play from home, now more than ever.
(No, I’m not trying to pull your heart strings.. just your business acumen)
Anyway, for the most part I’ve been pretty happy with the performance and stability of the MR60 + satellite. It’s been far better than the Telstra (Australian isp) supplied unit I was running before.
Even so, I’ve been experiencing the previously mentioned issues where some devices ‘lose the internet’. I don’t know how.. it’s so big!! Sorry, dad joke.. had to bring some humour :)
Perhaps a little more detail than I’ve read in the past 6 pages, for me, the device wifi adaptor actually stays connected to the wifi network. But the device loses its DHCP supplied address.
When manually trying to renew the DHCP lease, it rejects pretty quick and defaults to the 169... address, which denotes self-assigned and infers inability to get a lease.
Yes rebooting the router, usually solves the issue. But also stops everything else on the network.
Also, setting a manual IP for that device (go high in the range to avoid conflicts) without rebooting anything has worked for me every time (and is slightly more convenient).
Having said that, it’s a major PITA that this brand new netgear product running the latest firmware as of August 6th 2020, has issues with a simple DHCP service.
Searching for ‘DHCP’ across this forum, I can see this issue seems to occur with many other netgear devices.
netgear, I’m not sure what more info the users on this forum (your customers) can provide. I’d be surprised if this issue has not occurred in your QA labs. But if by some chance it has not, maybe you should do some real-world testing where there are lots of devices, walls, microwave ovens, xboxes and competing wifi networks. Maybe that will shed some light?
If not, maybe you need to pay your customers to diagnose this apparently widespread issue, rather than asking us to pay you.
This could be your moment. We’re all struggling thru covid, some countries and cities harder than others. I’m currently in city-wide lockdown in Melbourne, Australia. We turn to you to help us work and play from home, now more than ever.
(No, I’m not trying to pull your heart strings.. just your business acumen)