Nighthawk mesh system (MK63)

---

michaelkenward wrote:

---

nighthawk-anono wrote:

Same situation here.

---

Same as what?

 

---

---

I actually thought I was replying to another poster's similar concerns; not sure how this ended up as its own post - maybe because I selected a separate product or something. 😕 

So to clarify, whenever my internet service (Quantum fiber) has an outage or we lose power entirely, the wifi provided by the Netgear mesh system takes an inordinate amount of time and effort to restore successfully and always ends up with me having to do a hard/factory reset. I try unplugging everything, allowing time to pass, then plugging in only the modem (and confirming service/access to the internet by a hard-wire connection to a PC), then restoring the power to the router and it just does not work. I repeat this process, waiting longer and longer each time before re-trying and finally just end up doing a factory reset on the router each time this occurs. I understand the occasional need to "help" an unplanned outage restoration by power cycling and restoring modem-router in that order, but each time this occurs it should not be necessary - this is too complicated for the average user. 

---

We have internet via Quantum fiber and every.single.time the internet or power drops out from underneath our Nighthawk mesh system (MK63), we have to do a hard reset as well.

---

Why? What happens when the power comes back on?

 

The router will broadcast the wifi networks but not successfully. Non-IoT devices such as phones and PCs say "connected, no internet". IoT devices are simply offline.

---

What tells you that the router causes this problem rather than the modem/ONT/gateway that connects you to the Internet?

 

What is the thing that sits between the Internet and the router?

---

I remove the Netgear router from the equation and I can connect to the internet directly from the modem (ethernet cable). Browsing this forum, its not hard to find other posters with various modems and underlying ISPs all reporting the same issue with Netgear routers...what about this tells me that the modem/ISP is the problem?