NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Svtex830's avatar
Apr 05, 2023

Since I updated the MR60 firmware in January 2023

Since I updated the MR60 firmware in January 2023, I have had three different times where devices started dropping from the router. Not being very knowledgeable about these matters but able to follow directions, I spent roughly a full work day the first two times bringing everything back online. Yesterday was the third occurrence. In the 17 months I’d owned this mesh system prior to this latest firmware upgrade, I had not had any problems with it. I spent some of last night and most of today following the advice of every thread on the subject. I learned far more about routers than I ever wanted to. All the resetting and rebooting failed. Finally I followed this thread to install the old V1.0.6.116 firmware. Thankfully it worked. I don’t know much about routers and I shouldn’t have to. I installed the mesh system initially following NETGEAR’s relatively easy instructions and it worked well for 17 months. Then a new firmware comes along and it all went to hell. It shouldn’t have taken me this many hours to fix and I should have to go back to old firmware. NETGEAR has a problem with this firmware (just look at the number of threads on the internet about it) and they need to fix it. Based on this experience I’d be hesitant to buy another one of their routers.

6 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    What Firmware version is currently loaded?
    What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
    Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended. 

     

    How was the system updated? Manually or using the Nighthawk app? 

    Did you first update the MS then the MR lastly? 

     

    How many RBS are deployed? 
    What is the size of your home? Sq Ft?
    What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between MR and MS🛰️ to begin with depending upon building materials when wirelessly connected.
    https://kb.netgear.com/000061709/Where-should-I-place-the-Mesh-WiFi-satellite-of-my-Nighthawk-Mesh-WiFi-6-and-Tri-band-Mesh-WiFi-6-products 📡


    What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
    Any Wifi Neighbors near by? If so, how many?

     

    Has a power off for 1 minute then back ON with the ISP modem and router been performed since last update?
    Be sure to restart your network in this sequence:
    Turn off and unplug modem.
    Turn off router and computers.
    Plug in and turn on modem. Wait 2 minutes for it to connect.
    Turn on the router and wait 2 minutes for it to connect.
    Turn on computers and rest of network.

     

    Has a factory reset and setup from scratch been performed since last FW update? A complete pull of the power adapters for a period of time after the factory reset then walk thru the setup wizard and setup from scratch with a wired PC and web browser. Recommend setting the default DHCP IP address pool range to the following after applying and a factory reset: 192.168.#.100 to 192.168.#.200.
    https://kb.netgear.com/24089/How-do-I-specify-the-pool-of-IP-addresses-assigned-by-my-Nighthawk-router

     

    I've not seen any issues with current version of FW loaded. Factory reset and setup from scratch with mine. 

    https://community.netgear.com/t5/Nighthawk-Wi-Fi-6-AX-Mesh/New-MR60-MS60-Firmware-Version-1-1-7-134-Released/td-p/2284614/jump-to/first-unread-message

     

    • Svtex830's avatar
      Svtex830
      Tutor

      Thank you for the response. I read many of your posts on other reads while researching the issue and followed all the steps you, and others, recommended. None worked until I reinstalled the old firmware and then - poof - like magic, everything was good again - no fiddling with settings, no having to have a computing degree. Just simple. This highlights my issue - a firmware update should be simple. It should not require someone to spend hours researching and trying different things. If it's that hard, then something is wrong. Appreciate all the advice you've given me and others! Here's hoping the next firmware update doesn't require a visit to this forum.