Chromecast For Mac 10.7
Sanora Ngueyn
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?
lids the chromecast stick on the same network as your iPad etc? The firewall will have not any affect if they are. The issue is more than likely your chromecast stick needs to talk to the internet with a https scanning exception for the website it needs to talk to.
EDIT. I see that you want it to be accessible by devices on your LAN. If you are trying to control the Chromecast from your iPad to watch content online, you will need to add DNS to the allowed services in the firewall rule.
You can reach it since it replies to ping commands. That means it's on the same network. As a result, the issue is almost certainly DNS related since it is not in the allowed services, unless you have an allow rule below that allows DNS outbound from your LAN/WiFi to the WAN.
I'm glad it worked out. Now you know about allowing DNS. One other thing you should consider is that a firewall rule is not need for devices on your LAN to access other devices on your LAN, since the data doesn't go through the firewall except for special circumstances, such as using inter-VLANs.
The long reason is because a switch operates on layer 2 of the OSI model, which deals with the MAC addresses of the devices connected to it instead of their IP addresses (the router, layer 3), and the switch "knows" where to send data from one device to the other based on which device has the correct MAC address.
I was given a 1st generation chromecast from a friend and we were able to set it up a while ago with no issues when the friend was here, but now we changed our wifi password and wifi information, it got disconnected once again.
I tried to connect it using the Google Home app, but was not able to. I tried to factory reset the chromecast by pressing the button until the light was flicking red and the tv was off for a moment. Then it popped up the welcome screen, and I tried using my Google Home app to connect to the chromecast that is attached using HDMI on the tv, but it still won't find the chromecast via bluetooth or any type of connection. Is it because it was originally set up on a friend's Google Home app account in the first place? Or can I still use it? Please advise.
Nothing appears in the Google Home app when I tried to click on 'Set up new device' then 'Chromecast' then it would continue to say "looking for device" but then return to the same screen and not find the chromecast that we have input in the tv.
We use Trello in our office to keep track of our projects. Recently we started using a Chromecast on a nearby TV for a nice overview. Trello however doesn't seem to support Chromecast other than casting the tab. We're working on rather large UHD screens and keep changing the resolution of our browser. What happens is that the Trello board that we cast rather often changes it's resolution. It's also not independent from my pc.
i agree, native support for chromecast would be a great addition to the mobile app. especially delivery of a proper fullscreen resolution would enhance usability enormous compared to screensharing workarounds on the phone.
None of the devices (Windows/Android/iOS) that are connected to my AX11000 router are able to cast to any of the chromecast devices. I have Chromecast Ultra and Google Nest Home displays. Every time I restart the router the chromecast devices show up on all devices. But after sometime they disappear and so cannot cast to any of them. Restarting the router seems to solve the problem all the time. But it is a pain to restart the router that frequently. From other threads it looks like there are other people facing the same problem. Can you please look into this issue?
I do not know the technical details of OFDMA, but my understanding is it is one of the biggest features of 802.11-AX. So it is a bummer that I have to disable the feature to cast videos to my Chromecast devices.
@Tony - I've turned on the OFDMA again and so far I was able to cast to the chromecast devices. Any idea why turning it off and on has worked? I hope this is a permanent fix. Thank you very much for replying to my questions, appreciate it.
I have the same problem with my AX11000. Chromecast devices would disappear and if I rebooted the router they come back for a period of time before they disappear again. I tried disabling OFDMA and that worked for only a short time before I can't see my chromecast devices again. This time, I turned OFDMA back on without rebooting the router and the chromecast devices showed up again. Will see what happens now and how long they will stay visible.
Yeah, it is frustrating. I've opened a ticket with TP-Link. there is no resolution yet. I've given them a copy of my settings and they said they'll try their device with those settings. I'll post here when I hear back from them.
If you haven't please open a ticket with the support team. Hopefully if they see more tickets this thing will be prioritized. When I opened my ticket I got a response that they will look into it. I gave them a backup of my settings as well so they can use my settings. I haven't heard back from them yet. All they gave me is a beta of the next version of the firmware. That definitely has reduced the number of times I had to restart. Here's the link to it (hopefully it still works)
7fc3f7cf58