You tap the Cast button, and your phone says there is nothing to cast to. Your Chromecast or Google TV Streamer is powered on. The TV is on the same Wi-Fi. The device even works from your laptop, or it worked yesterday.
The “no cast devices found” error almost never means your Chromecast is broken. It means your phone can’t see the device across your home network. Your router or access point is usually the reason. The fastest fixes are turning off AP isolation, disabling Protected Management Frames, and testing IGMP snooping one setting at a time.
Most guides stop at “restart everything.” Here is the order that finds the real cause.
Why Your Phone Can’t See a Device on the Same Wi-Fi
Casting depends on your phone discovering the device through local network traffic. It is not like loading a website. Your phone has to reach the device directly, inside your home network.
Google’s own help page on connecting a Chromecast or Google TV Streamer says it plainly. It states: “Your Wi-Fi network configuration may prevent devices from communicating with Google streaming devices.” Any router setting that keeps devices from talking to each other can produce no cast devices found. Your internet can work perfectly while this happens.
That is why the same phone can browse the web fine and still see nothing to cast to.
Fix 1: Confirm Your Phone and Device Share the Same Network
Start with the boring check. It catches more cases than people expect.
How to check:
- Open your phone’s Wi-Fi settings and note the exact network name
- Check the network name your Chromecast or Google TV Streamer uses in the Google Home app
- Make sure both are on the same network, not a guest network, and not a separate 2.4GHz and 5GHz name that look alike
- Turn off any VPN on your phone, then try casting again
- If the names match and the VPN is off, move on to Fix 2
Google also notes that Chromecast (1st gen) only works with 2.4GHz networks. If you have that older model, it can’t join a 5GHz-only network.
Fix 2: Turn Off AP Isolation and Guest Network Isolation
This is the most common cause of the no cast devices found error. AP isolation, also called client isolation, blocks wireless devices from talking to each other. Routers use it on guest networks to keep visitors away from your other devices.
Google’s page names this setting directly. It describes it as “Client Isolation” or “Guest Mode,” and says setup fails on guest, hotel, or public networks when they use it. It also says isolation on a Wi-Fi extender can block setup, so check any extender you own.
How to fix:
- Log into your router’s admin page, often at 192.168.1.1 or the address printed on the router
- Open the wireless settings and look for AP Isolation, Client Isolation, or Wireless Isolation
- Turn it off for the network your phone and Chromecast use
- Repeat the check on any extender or second access point
- Save the changes, restart the Chromecast, and try casting again
Menu names differ by brand. Some routers hide the setting inside the guest network page.
Fix 3: Disable Protected Management Frames (802.11w)
This one rarely appears in beginner guides. It comes from a router community, and it fixed one user’s problem.
In an OpenWrt forum thread about cast devices disappearing, a user found that a cast device on Ethernet stayed visible while Wi-Fi devices dropped out. Their fix: “The reason was 802.11w Management Frame Protection.” Disabling it brought back the Chromecast and a printer.
Treat this as one reported case, not a guaranteed cure. It costs almost nothing to test, though.
How to fix:
- In your router’s wireless security settings, look for Protected Management Frames, PMF, Management Frame Protection, or 802.11w
- If it is set to Required, change it to Optional or Disabled
- Save, wait for the Wi-Fi to restart, and reconnect your phone
- Try casting again
Only change this on the network your cast devices use. If nothing changes, set it back to what it was.
Fix 4: Test IGMP Snooping, One Change at a Time
IGMP snooping is a router feature that manages multicast traffic. Casting discovery relies on that kind of local traffic, so a bad setting can leave you with no cast devices found.
The same OpenWrt thread shows how messy this setting is. One user said many Wi-Fi access points have “broken implementations of the feature, which can actually cause this particular issue.” Another user reported that turning snooping on fixed their problem. Later, one of them called that fix a “false positive” because the problem returned after about 12 hours. A second user saw the fix hold for six days before it failed.
So there is no safe default here. Flip it once, test for a day, and keep notes.
How to check:
- Find IGMP Snooping in your router’s LAN or multicast settings
- Note whether it is on or off right now
- Change it to the opposite value and save
- Restart the Chromecast, then test casting over the next day or two
- If it doesn’t help, set it back to the original value rather than leaving a random change in place
Fix 5: Check Multiple Access Points, Mesh, and Controllers
If your home or office runs more than one access point, your phone may sit on a different AP than your Chromecast. Discovery traffic then has to cross between them.
A Cisco community thread describes exactly that. Google Home devices appeared only when the phone connected to the same AP. The poster fixed it by turning off mDNS on the WLAN and mDNS global snooping on the controller, then confirming multicast was enabled. A Cisco employee in the thread explained that mDNS is “just to bridge multicast traffic to users in separate VLANs.”
Most homes don’t run a Cisco controller. The lesson still applies to mesh systems and routers with extra access points. Settings that filter or limit traffic between points can hide your cast device. If you have a similar setup, our guide to Sonos speakers disappearing from the app covers the same band-steering, guest-network, and double-router traps.
How to check:
- Move close to the Chromecast and see whether it appears
- If it does, your phone and device were likely on different access points
- Look for a Multicast or mDNS setting on your router, mesh app, or controller
- Make sure multicast forwarding is on, and disable any filter that blocks traffic between access points
- Restart the cast device after you save changes, since Cisco’s community suggested rebooting the devices after any change
Fix 6: Rule Out the Simple Network Problems
Some causes of no cast devices found have nothing to do with advanced router settings. Google’s page lists a few that are easy to miss.
How to check:
- Confirm the network doesn’t use a captive portal. Google says its streaming devices “don’t support networks requiring connection through a captive portal,” which covers many hotel and school networks
- If your network name is hidden, enter it manually during setup, because Google notes it won’t appear in the list
- Reboot the router, and check whether it needs a firmware update
- Unplug the Chromecast for 60 seconds, then plug it back in and wait for it to finish starting
Frequently Asked Questions
Why does my phone say no cast devices found when the Chromecast is on the same Wi-Fi? Your phone can’t reach the device directly. AP isolation, guest network settings, or multicast problems on your router are the usual causes. Check isolation first, then try Protected Management Frames and IGMP snooping.
Does AP isolation break Chromecast? Yes, it can. Google says client isolation on a guest network or extender can prevent setup and discovery. Turn it off for the network your cast device uses.
Should I turn IGMP snooping on or off? There is no universal answer. Community reports show it fixing the problem for some people and causing it for others. Change it once, test for a day or two, and revert if nothing improves.
Why does the Chromecast show up only right after I restart the router? That pattern points to a multicast or discovery setting that stops working after a while. Test IGMP snooping and Protected Management Frames, since both are linked to disappearing cast devices in community reports.
Is my Chromecast broken if it won’t appear? Probably not. If the device works over a different network, such as a phone hotspot, the problem is almost certainly your home router settings.
The Bottom Line
The no cast devices found error usually points to your network, not your Chromecast. Start by confirming your phone and device share the same network. Then turn off AP isolation, test Protected Management Frames, and try IGMP snooping one change at a time. If you run several access points, check multicast and mDNS settings too. Be honest about the limits: the router-level fixes come from community reports, and results vary by router. A methodical test order still beats random resets. This is the same pattern as Siri’s “Unable to connect to ChatGPT” error, where a network setting breaks a feature that looks like a device problem.