NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Devices on mk62[mr60 and ms60] become invisible to each other
I have two google homes, a chromecast, two phones, and a desktop connected to my network. The desktop is the only one wired. On occasion, the LAN seems to be split into two networks for my devices be...
I've been having similar problems. I've had the router for a few days now. At first I thought the problem was random then I did further testing. I'm quite sure the problem is related to the 5GHz wifi on the SATELLITES.
I have the MK63 (MR60 router and two MS60 satellites) with each node placed in SEPERATE rooms. I have 3 media devices (Google Home speaker, Google Home Mini speaker and Google Chromecast) and a few phones. The Chromecast is connected to the router, the Home to satellite 1 and the Mini to satellite 2. All devices are configured properly and connected to the internet. I have the latest firmware (V1.0.6.102) on the router and satellites.
The good news: No matter which node my phone is connected to, I can cast to a device connected to the router (Chromecast in my case). Also, if my phone is connected to the router, I can cast to all devices in the house. If my phone is connected to a satellite then I can cast to a device on the OTHER satellite (the speaker in the other room in my case), as well as to the device connected to the router. All is fine up to this point.
The problem start when my phone AND media device are connected to the SAME satellite. So when I'm next to a speaker I CAN'T cast to that speaker. Furthermore, the problem only happens when the media device is connected to the 5GHz band. (When the speaker uses the 2.4GHz band, the problem goes away.)
So does anyone out there have a solution?
Hey Netgear, Has anyone looked into the problem? It's been a while since the initial post. Is a new firmware with a fix available soon?
shaun_s wrote:I've been having similar problems. I've had the router for a few days now. At first I thought the problem was random then I did further testing. I'm quite sure the problem is related to the 5GHz wifi on the SATELLITES.
I have the MK63 (MR60 router and two MS60 satellites) with each node placed in SEPERATE rooms. I have 3 media devices (Google Home speaker, Google Home Mini speaker and Google Chromecast) and a few phones. The Chromecast is connected to the router, the Home to satellite 1 and the Mini to satellite 2. All devices are configured properly and connected to the internet. I have the latest firmware (V1.0.6.102) on the router and satellites.
The good news: No matter which node my phone is connected to, I can cast to a device connected to the router (Chromecast in my case). Also, if my phone is connected to the router, I can cast to all devices in the house. If my phone is connected to a satellite then I can cast to a device on the OTHER satellite (the speaker in the other room in my case), as well as to the device connected to the router. All is fine up to this point.
The problem start when my phone AND media device are connected to the SAME satellite. So when I'm next to a speaker I CAN'T cast to that speaker. Furthermore, the problem only happens when the media device is connected to the 5GHz band. (When the speaker uses the 2.4GHz band, the problem goes away.)
So does anyone out there have a solution?
Hey Netgear, Has anyone looked into the problem? It's been a while since the initial post. Is a new firmware with a fix available soon?
EDIT: I did some more testing. The problem also happens on the 2.4GHz band.
So the problem happens when BOTH the media device and phone are connected to the SAME satellite on the SAME wifi band.
(It was difficult to test since the media devices don't allow selecting the band to connect, but I have an older phone which does allows me to choose the band to connect so it made it slightly easier to test.)
shaun_s wrote:EDIT: I did some more testing. The problem also happens on the 2.4GHz band.
So the problem happens when BOTH the media device and phone are connected to the SAME satellite on the SAME wifi band.
(It was difficult to test since the media devices don't allow selecting the band to connect, but I have an older phone which does allows me to choose the band to connect so it made it slightly easier to test.)I'm having the exact same problem with MR60 with two MS60 satalites. On another post, the workaround was to bring my old router back in and turn off the wifi on it. Then flip the router on the MR60 off so that it just became a Wireless AP system. As soon as I got that setup, everything worked across all satalites.
Hope netgear fixed this in their next update.
AlbanyMatt wrote:
shaun_s wrote:EDIT: I did some more testing. The problem also happens on the 2.4GHz band.
So the problem happens when BOTH the media device and phone are connected to the SAME satellite on the SAME wifi band.
(It was difficult to test since the media devices don't allow selecting the band to connect, but I have an older phone which does allows me to choose the band to connect so it made it slightly easier to test.)I'm having the exact same problem with MR60 with two MS60 satalites. On another post, the workaround was to bring my old router back in and turn off the wifi on it. Then flip the router on the MR60 off so that it just became a Wireless AP system. As soon as I got that setup, everything worked across all satalites.
Hope netgear fixed this in their next update.
Hi AlbanyMatt, Thanks for your suggestion.
Unfortunately, using the MR60/MS60 as a wireless AP was the setup I used at the very beginning. I thought it was the old router begin incompatible with MR60, so I reconfigured to use MR60 as the main router but the problem persisted.