Google Chromecast have issues with Wi-Fi networks
Router vendors have recognised the issue
It appears to emerge through the bulk delivery of MDNS packets
Some Google Chromecast users have reported that they are facing random crashes on their Wi-Fi networks. Router vendors have recognised the crashing issue and have started pushing patches from their end to retain a stable experience. The problem is claimed to exist in Google’s ‘Cast’ feature and is reportedly affecting Google Home devices in addition to Chromecast.
As explained by the TP-Link engineers in an FAQ listing, the issue exists due to multicast DNS (MDNS) packets that are broadcast through Google Chromecast and Home in a large amount, at a very high speed in a short amount of time. MDNS packets are normally sent in a 20-second interval. “This occurs when the device is awakened from the “sleep mode” and could exceed more than 100,000 packets in a short amount of time. The longer your device is in ‘sleep’, the larger this packet burst will be. This issue may eventually cause some of the router’s primary features to shut down – including wireless connectivity,” the FAQ reads. Alongside TP-Link, Linksys and Netgear have also released beta firmware updates to resolve the network issue occurred through Google’s Cast feature.
The latest network issue appears to have a large impact. Some users on Reddit highlight that the issue randomly disables network on all the devices connected to a wireless network which powers their Chromecast. Moreover, an identical effect has been reported with Chromecast Audio. “For me, since I installed the Chromecast on my TV, my router has been kicking everyone off the network. Two phones were unable to even connect to the Wi-Fi and then every now and again you’d find you were connected to Chromecast rather than Wi-Fi,” one of the users explained the issue on Reddit.
Users on Google Product Forums initially concluded that the problem emerges particularly with a network powered by the Archer C7. However, this is not the case, if we believe the constructive information provided by the TP-Link team. A Google Products expert on the official Product Forums stated that the company was looking into the issue. The expert, with username Paula, has also asked affected Google Home Max users to elaborate the issue in a feedback report through the Google Home app alongside necessary screenshots and logs. “We’re looking into this and to help us, please submit feedback report from the Google app after the router is rebooted and devices are back online. Be sure to include the keyword ‘GHT3 – Unable to set up Max to network’ and check the box to ‘Include screenshot and logs’. Also, please confirm the firmware version your router is on,” the expert said.
We’ve reached out to Google to get its clarity on the issue and will update this space upon the receipt of a formal response. Meanwhile, you are recommended to reboot the router that is disabling the network on devices to release the memory and temporarily resolve the issue. You can also try disabling the Cast feature on your devices to help mitigate the issue.
Last month, some Pixel 2 and Pixel users have reported connectivity issues with mesh routers. Google acknowledged that flaw and confirmed a fix. The problem was mainly refraining the hardware to establish connectivity with a mesh router by bringing frequent disconnects and spontaneous reboot of access points.