NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
aandmhill
Feb 03, 2021Tutor
MR60 Satellite won't connect
After doing an update, 1 of 2 satellites wont connect. Tried customer support, but no help there. System is less than 30 days old and was functioning great until the update. App shows zero firmware...
- Sep 28, 2021
You need to update the MS before updating the MR. Keep this in mind for future updates.
What you need to do is factory reset the MS. Wire connect a PC to the 1st satellite. Already have the most current FW version files downloaded on to this PC.
Wire connect 1 PC to the back of the MS. Factory reset the MS, wait about 5 minutes. The PC will get a IP address from the satellite. The RBS will be 192.168.1.250. Use this IP address in a web browser to log in to the satellites web page. Log in as admin and password. Use the satellites web page FW update feature to select the FW update file that was unpacked from the .zip file. Then factory reset and then re-sync the satellites to the MR.
dserang
Apr 04, 2021Guide
Good news... Today I opened the Nighthawk iOS app. It is now version 2.9.0.13 and all the prior issues that I reported after having updated my MR60 and MS60 units to firmware version V1.0.6.110 have been fixed. The main symptom (now solved) was that one of the two MS60 satellites would improperly appear in the Network Map as not connected and its status indication was not "green light good." In my system of one MR60 and two MS60 satellites, both satellites both have an Ethernet (hardware) connection to the MR60 for higher performance backhaul. For more details on the symptom see my past posts on this subject.
So... Netgear must have recently updated the iOS Nighthawk app to fix the issue.
I also used a browser to login to the MR60 router (www.routerlogin.net with an Ethernet cable connecting computer to the MR60) and it also not correctly shows the two satellites as connected with good status, which is a fix over the prior situation.
In summary, Netgear fixed the issue and I have no need to roll back the MR60 and MS60 firmware from V1.0.6.110 to the prior version.
Thanks, Netgear, for correcting this issue that appeared after having updated MR60 and MS60 firmware to V1.0.6.110 (in response to a Nighthawk iOS prompt to do so).
All is good.