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

Forum Discussion

GhettoSmurf373's avatar
Jul 17, 2020

Chromecast and Mesh Routing issues

If anyone is like me and recently upgraded to the Netgear Nighhawk Whole Home Mesh WiFi 6 (AX1800), you have probably discovered issues with Chromecast. I searched and searched the web and could not find any information other than "AP Isolation issues" and "reset chromecast" over and over. 

We found that if the Chromecast is connected to the 'main' router, you can be connected to any satellite and cast to your device. However, if your Chromecast is powered down, and or network resets for any reason, you will be placed to the nearest device. In my case, that was the satellite. We believe the Chromecast locks to the MAC address and cannot associate back to the main router. So once a power cycle happens, even if your phone and Chromecast are connected to same satellite, you will not be able to cast.

 

The solution (for me and my AX1800, I hope it works for you)
1. Go to your routers home page (typically 192.168.1.1)

2. Select Advanced Settings

3.Select Setup tab

4. Select LAN Setup

5. Scroll down to the "RIP Direction" section

6. Ensure "Both" is selected for "RIP Direction"

7. Select RIP_1 for "RIP Version"

 

After selecting this, it didn't matter which satellite my Chromecast or my phone was connected to, I was able to cast. Hope this helps someone!

36 Replies

  • Additional question: so the solution below worked for me temporarily.  I believe it worked temporarily because it involved me restarting my router, but when I looked further I realized the issue I was having was larger than just not being able to connect to the chromecast or cast to the google display.  Since getting the mesh network I am unable to connect to my Google Display from my android phone at all. If I logoff/on to the wifi I will be able to connect to my google devices temporarily, but it eventually times out and I lose connection and I can't reconnect unless I repeat the process.  
    Does anyone have any insight 
    Thanks
    JECaine

    GhettoSmurf373 wrote:

    If anyone is like me and recently upgraded to the Netgear Nighhawk Whole Home Mesh WiFi 6 (AX1800), you have probably discovered issues with Chromecast. I searched and searched the web and could not find any information other than "AP Isolation issues" and "reset chromecast" over and over. 

    We found that if the Chromecast is connected to the 'main' router, you can be connected to any satellite and cast to your device. However, if your Chromecast is powered down, and or network resets for any reason, you will be placed to the nearest device. In my case, that was the satellite. We believe the Chromecast locks to the MAC address and cannot associate back to the main router. So once a power cycle happens, even if your phone and Chromecast are connected to same satellite, you will not be able to cast.

     

    The solution (for me and my AX1800, I hope it works for you)
    1. Go to your routers home page (typically 192.168.1.1)

    2. Select Advanced Settings

    3.Select Setup tab

    4. Select LAN Setup

    5. Scroll down to the "RIP Direction" section

    6. Ensure "Both" is selected for "RIP Direction"

    7. Select RIP_1 for "RIP Version"

     

    After selecting this, it didn't matter which satellite my Chromecast or my phone was connected to, I was able to cast. Hope this helps someone!


     

  • I have the Nighthawk MR62 Bundle (1 MR60 router, 1 MS60 satellite) running firmware V1.0.6.102_2.0.45. I, like everyone else was having issues with my Google casting devices. What ended up working for me was to uncheck "Disable IGMP Proxying". Ever since I did that everything has been running smoothly. I hope this will help someone out there.
    • JECaine's avatar
      JECaine
      Tutor
      Thank you Rivinence,
      I unchecked that setting and I will check it in the morning. I will let you know how it goes.
      JC
      • JECaine's avatar
        JECaine
        Tutor
        Thanks again Rivinence, unfortunately this solution didn't fix the problem I'm having. I'm just going to buy myself some MoCA adapters and go wired. Hopefully that fixes the problem
  • Thank you so much! Didn't only solve my issue with Chromcast, but also my connectivities issues with my Sonos devices. You made my entire family happy :) :) :)

    Thank you, thank you, from Montreal, Canada.

     

     

  • I cannot begin to thank you for this!!! We kept wondering what went wrong and finally we have found out. You are more helpful than the technical service team for my internet service haha
  • I can't start to thank you for this!!! We saved wondering what went wrong and sooner or later we've got located outhere. You are greater useful than the technical carrier team for my internet service haha

  • Also had to factory reset my Chromecast to finalize the resolution.  So if it's still failing after your change on the router, factory reset the Chromecast itslef.  

     

    Thanks for the post and answer!

  • I have the MK63 (MR60 router and two MS60 satellites).

     

    I've tried all the suggested solutions but none worked.  (It may seem to work for a while but after the devices connect back to their respective satellite, the problem returns.)

     

    I've waited over 8 months for a firmware fix but none of the updates fixed the problem.  It's been a waste of time.

     

    Get a refund if you can.  Unfortunately, I'm stuck with mine.  Very disappointed.

    • FURRYe38's avatar
      FURRYe38
      Guru - Experienced User

      Instead of waiting for a fix, did you open a support ticket to let NG know about the problem your seeing? 

      Highly recommended to contact NG support and let them know about this. Reference this forum thread as well. 

      DarrenM 


      shaun_s wrote:

      I have the MK63 (MR60 router and two MS60 satellites).

       

      I've tried all the suggested solutions but none worked.  (It may seem to work for a while but after the devices connect back to their respective satellite, the problem returns.)

       

      I've waited over 8 months for a firmware fix but none of the updates fixed the problem.  It's been a waste of time.

       

      Get a refund if you can.  Unfortunately, I'm stuck with mine.  Very disappointed.


       

  • I tried all of the suggestions in this forum and none worked for me (using MR62 1 base and 1 satellite). What I had to do to set up the chrome device was unplug my satellite and just use the base station wifi. My house it small enough were I get 1 bar from the base in the furthest part of the house. That being said after plugging the satellite back in I do not know if the device is still connected to the base or now the satellite after inital setup. However this inconvenient work around has worked for me and every google device I've had to set up I've had to do this way. 2 nest minis and 1 nest home(the small screen one).

  • Incredible this is working and also that Netgear don´t fix and focus on this. I have the same problems and the suggestions in this post doesn´t seem to fix it. I will do a complete reinstallation of it when I can and see if that works.

     

    No other updates or fixes for this anyone can share? Thanks

    • FURRYe38's avatar
      FURRYe38
      Guru - Experienced User

      What NG router product model# do you have? 


      toftegaarden wrote:

      Incredible this is working and also that Netgear don´t fix and focus on this. I have the same problems and the suggestions in this post doesn´t seem to fix it. I will do a complete reinstallation of it when I can and see if that works.

       

      No other updates or fixes for this anyone can share? Thanks


       

  • A new update of the firmware has been released on Nov 11.  I have been testing it for the past day.  So far so good -- the Chromecast problems seem to be fixed.  You can find the downloads here:

     

    https://kb.netgear.com/000064370/MR60-MS60-Firmware-Version-1-1-6-122

     

    The release notes indicated the new firmware fixes issues with AirPlay, but actually the Chromecast issues were also fixed.  This probably meant the problem was fundamental and related to general communication between devices.  They finally acknowledged and sorted out the problem but it still took well over a year of people complaining.

     

    BTW FURRYe38 ...

    DarrenM never ended up replying to my personal message concerning the issue.  But I guess the problem somehow got escalated and attention was given.  Perhaps you had something to do with it.  Thanks.