Chromecast For Pc
Nandan Barahona
I am wondering if there is going to be a fix for the NETGEAR - Nighthawk AX1800 Dual-Band Mesh Wi-Fi 6 System (2-Pack) with chromecast compatibilty. From all the forums that I see there is no actualy solution that is working as some people work and others dont.. So I am wondering to see if there are plans in place to have an update to be compatible with Chromecast, seeing how that is a widley used device in the streaming world, or even that it is a known issue to Netgear. If there are no plans or upcoming updates that will address then please let me know so I can just go and return this product.
If you recently purchased the device I would recommend contacting our support team as newly purchased devices are provided with 90 days of complimentary support. You may open a ticket by registering your device using the link below.
A quick solution would be to manually connect the Chromecast to the 2.4 ghz band but according to Netgear support the Nighthawk automatically connects the devices to the 2.4 and 5 ghz bands.
This is something Netgear need to address.
I have the MR60 Mesh network & a house full of Chromecast devices. I purchased the MR60 system in anticipation of our upcoming fiber installation with the hope of good network performance throughout the home. We have been continually frustrated that our chromecasts over wifi simply do not work on this system. The ONLY time they work is when casting from a PC, or after factory resets and the setup wizard on the chromecast every time we attempt to cast to them. They continually disconnect from the network when using a mobile device... android or IOS over wifi. I am attempting some of the settings I see recommended in this forum (kudos to you all!). However, it would be great if the Netgear forum moderators would take the abundant evidence in these forums and get it to Netgear Dev to correct the issue in an upcoming patch. It should not require all of us calling in spending troubleshooting time with customer service trying to resolve this when it is clearly a known and widespread issue. My generally new chromecasts should work with my brand new MR60 mesh wifi. Ensuring that systems work with common devices is a minimum viable product requirement it would seem.
@ChristianR, is there any awknowledgement from Netgear on this? There's numerous threads reporting the issue. How else can we report the problem and get a response? I've been following these threads for months now and not a single response or fix from Netgear. Ridiculous to say the least when we've all spend hundreds on these mesh setups.
I returned the MR60 Mesh back to the store and purchased Google Nest. It works perfectly with my two Chromecasts and the satellite even works as a speaker for radio, podcasts or music, and a Google assistant. When they accepted the Netgear product back at the store I felt a huge sense of relief that it was gone and I had my money back! Netgear, you guys screwed up! Why the heck is your product not compatible with Chromecast? And if it's not compatible with Chromecast, what other devices is it not compatible with?
Apparantly IGMP proxy will block all muticast packets and convert them to unicast packets , that may be the reason it only works if your device is connected to main router and dont work when its connected to satellite .
ok, so i noticed on the box there is a special costco call number for support - so i called it this morning and got thru like right away. She had me log into the router and go to settings/advanced/advanced setup/wireless settings - and then uncheck the "Enable AX" box. Then i went thru and was able to connect all (3) of my chromecast devices - SUCCESS FINALLY !!! So i did three setting changes on the router - the first 2 didnt seem to work, but the third did - ummmmmmm.
Changing the settings don't work. (It may seem to work, but after a while the devices connect back to the sattelite and the problem returns.) The problem was around since the router was first released. Netgear has only recently addressed and fixed the issue.
ok - i did the firmware update - was a bit difficult as the instructions said use the app on my S20 android, but i could not get that to work - so i had to hook ethernet into it from my laptop and do it manually - and the slowness of it made it a challenge.
So, my next problem, now my alexa does not talk to my Hue bridge - ahhhhhhhh, and grrrrrrrrr - the Hue bridge works fine with the Hue app on my S20, but not thru Alexa, I assume due to the mesh ... gonna search about for a solution to this, next, problem - grrrrrrrr ....
We've had a few issues with Chromecasts on our SSID; What firmware version are you running? I've updated to 25.6 and now things to appear to be working fine. However, I'm assuming it could be related to the known bug "investigation causes 2.4GHz radios to become unresponsive" as per the firmware release notes.
Hi Philip, can you elaborate a bit on the issues you have seen using .local domain ? Does it cause a problem with the AP or clients or both ? Not heard or can find anything, so would be interested in your findings - Thanks
If you use ".local" for unicast services (AKA "normal" IP address), and you have a DNS server defined then you screw this mechanism up, Now the queries will get sent to your defined DNS server, which will know nothing about the multicast DNS service, and fail.
I found a solution for this you need to change the DHCP leasing from in the SSID Settings from NAT DHCP to NAT Bridge Mode DHCP it works, we spend the whole day resolving this but got to the bottom of it.
I have chromecast capable wired AV equipment on a VLAN that is also used by wired workstations and securely attached wireless devices. I do not use bridge mode. An unsought benefit is that once the wireless device has connected to the AV device and the correct stream is playing, the phone can be turned off and the stream continues to play.
From a security point of view, it is preferable to keep AV hardware on a different VLAN to corporate networks. One can either get clever with CIDR super/sub netting or make creative use of DMZ-style configurations.
However, I am led to believe that the Meraki way suggests that Bridge mode be used for typically static devices, whilst Layer 3 roaming be used for mobile devices. There is a certain logic in this. My rule of thumb is to wire anything that doesn't move, so largely unlikely to use the former option. Habitually I reserve a portion of the available IP addresses for any given (V)LAN for those devices that require a fixed IP address, but can't remember when I last had to make use of this. All my AV kit is wired and gets an IP address from a DHCP server.
The problem with most smart devices is that many of them are truly dumb as far as communicating is concerned. Mostly because they have been designed by snowflakes for snowflakes. WiFi chipsets usually selected on the grounds of price alone, no awareness of security, or worse they flagrantly lie about the need for security and the risks involved.
I have just had a similar issues with a large client of mine and having switched from UBNT to Meraki their Chromecasts stopped working, after spending some time today trying to resolve this and also going through this great thread, I just wanted to add my thoughts on the resolution.
We discovered two issues that both stop the Chromecast working, Layer 3 roaming and band-steering, if either of these are on, the CC will not work, so yes, it appears the solution is to create a seperate SSID and make sure these are not enabled and "hay presto" it all works.
Hello Everyone! I have a particular case: Im having troubles to cast from a windows 10 desktop to chromecast, but Im able to do it from a cell phone.. Ive doing a lot of testing bun nothing works, here are the specs of the network:
Hello Philip! thank you for your comment, now you mention it I recall the previous message you post about it, and I asked the customer, yes they are using a "GRUPO-LOMAS.LOCAL" domain.. you think that could be the cause? if so, what is your opinion that I can cast from a cellphone? I think it should have the same problem, but is not..
Im not so familiar with domains, and I guess the solution could be stop using the .local domain, how easy is to do that? just change the name and that is all? how could the customer network be affected with that change?
I have been happily casting Pandora to my Chromecast devices for years using my phone and tablet. However, I have not been able to connect for the last few days to any of my Chromecast devices (Chromecast Audio, Chromecast Ultra). Pandora will see the target device, attempt to connect, but then say, "Your session has ended" after a few seconds of silence.
03c5feb9e7