NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Had to hard reset MR60 twice in two weeks
I have an MR60 mesh system with two satellites. Twice within the last two weeks we have woke up in the morning to find we have no internet service. Both times it was some issue with the MR60 that r...
First, I'm not an inexperienced residential user. I have worked as a network admin for nearly 30 years. My post here was to simply see if anyone else has seen similar issues before I scrap this thing and go buy something else.
Yes, I started with a reboot. Multiple times. Fiber modem, MR60 router, satellites in that order. Blue light came on but devices were still unable to connect and the mobile app was unable to find my router. I was also unable to connect to it via IP from my laptop which is a wired connection.
Firmware version is V1.1.7.134_2.0.65. I said latest because when checking for an update, it says I have the latest.
There is no identifying info on the fiber modem and no, it has no LAN ports on it. It is a modem and not a router.
Thank you for the link. It's a little late to troubleshoot any further since I did the hard reset. Also, it's kind of difficult to troubleshoot a device that I am unable to connect to.
JohnnyG3 wrote:
Yes, I started with a reboot. Multiple times. Fiber modem, MR60 router, satellites in that order. Blue light came on but devices were still unable to connect and the mobile app was unable to find my router. I was also unable to connect to it via IP from my laptop which is a wired connection.
Apologies if you thought I was belittling you. I asked about that because many people who arrive have not worked as network admins for 10 minutes, let alone nearly 30 years. So we have to start from basics. Then we don't confuse people who have never plugged in a router before.
I said latest because when checking for an update, it says I have the latest.
I know of three ways to check for the latest firmware: using an app, via the GUI or by visiting the support pages for a device and checking the firmware library and comparing it with the installed version. Neither method that says "you are up to date" is reliable.
Again, it is a matter of informing people who may not realise that claims of "the latest" may not be accurate. We see that all the time.
It's a little late to troubleshoot any further since I did the hard reset. Also, it's kind of difficult to troubleshoot a device that I am unable to connect to.
That's a useful clue. But if it happens again maybe you could check.
You don't need me to tell you this, but a failure to connect to a router in the usual way can be because, during setup, the Netgear router sees that an upstream router has allocated itself an IP address that it wants, usually 192.168.1.1. So it picks something else. This is often 10.0.0.1.
When that happens it won't work when a browser tries to access the router with the 192.168.1.1 or routerlogin.net.
You have ruled out the "double NAT" scenario but, based on many similar incidents here, I'd start by diagnosing why that happens.
It is a pity that phrases like "fiber modem" are effectively meaningless. The "fiber" word tells us nothing. Every Internet service has optical fibre in it somewhere. The question is how near it gets to you. Front door. Cabinet up the road.
If the fibre gets to the front door, then convention is that it doesn't come through a "modem" but through an optical network termination (ONT). I assume that this distinction is there to differentiate between something that handles an electronic to electronic conversion to one that converts an optical to electronic conversion.