Can't Cast to Your TV? How AP Isolation Breaks Chromecast and AirPlay

Your TV is on and streaming works fine on it. Your phone has full wifi bars and fast internet. But when you tap the cast button, the app says no devices found. AirPlay users see the same thing, an empty list where the TV should be.

This exact complaint fills Google's own support forums and every home networking subreddit. The frustrating part is that nothing looks broken. Both devices are online. They just can't see each other.

The cause is almost always one of four things: AP isolation, a guest network, a mesh or extender quirk, or a VPN on your phone. All four are fixable in under ten minutes. Here's how each one breaks casting, and how to switch it off.

Why two online devices can't see each other

Finding your TV never touches the internet. When you tap the cast button, your phone shouts across the local network, asking if any Chromecast or AirPlay device is listening. The technical name for this shouting is mDNS, a type of multicast broadcast. The TV hears it, answers, and the two devices connect directly.

That only works if your router passes traffic between devices. Internet traffic goes up from your phone, through the router, and out to the world. Discovery traffic goes sideways, from your phone to the TV. A router can happily allow the first while blocking the second.

That's why everything looks normal. Speed tests pass, YouTube loads, and the TV streams on its own. The sideways path is the only thing that's dead, and nothing on your phone will tell you that.

AP isolation, the usual culprit

AP isolation is a router setting that blocks device-to-device traffic on the same wifi. Brands label it Client Isolation, Wireless Isolation, or occasionally Guest Mode. With it on, every device gets internet but can't reach anything else in the house. Your phone and your Chromecast end up both online and completely invisible to each other.

The feature exists for coffee shops and hotels, where strangers share one network and shouldn't see each other's laptops. In a home it mostly causes grief. It sometimes arrives enabled on ISP-supplied boxes, and sometimes someone ticks it because it sounds like a security upgrade. Casting breaks a week later and nobody connects the two events.

To check it, log into your router's admin panel, usually at 192.168.1.1, and open the wireless settings. On TP-Link routers, look under Advanced > Wireless > Advanced Settings for a box labeled AP Isolation. Asus keeps it under Wireless > Professional, named Set AP Isolated. On Netgear it's often a checkbox called Enable Wireless Isolation on the wireless setup page.

Mesh systems usually put this in their phone app instead of a web page. Dig through the wifi or network settings for anything named client isolation or block local traffic. The wording varies, but the idea is always the same. Any switch that promises to keep devices apart is the one you want off.

Turn it off, save, and give the router a minute. Then force close the casting app and reopen it. The TV should appear within seconds. If the setting was already off, don't stop here, because three traps remain.

Guest networks block casting on purpose

A guest network isolates its devices by design, and that isolation is the whole point of guest network security. A phone on the guest wifi can never cast to a TV on the main wifi. No hidden toggle changes that. The router is doing exactly what it was built to do.

This one catches people constantly. You joined the guest wifi once, months ago, and your phone quietly remembered it. Or someone set the TV up on the guest network by accident. Both devices show working internet, and nothing on screen hints that they're on different networks.

Open your phone's wifi settings and read the exact network name. Then check the network name inside the TV's own settings menu. If either one says guest anywhere, move it to the main network. Casting usually comes straight back.

Mesh systems deserve a special mention here. On eero, open the app and confirm the TV isn't sitting on the guest profile, then check for any isolation-style settings. Eero doesn't use the AP isolation label, but its guest network behaves the same way.

Extenders and mesh quirks

Wifi extenders are the second trap. Many extenders carry their own AP isolation setting, completely separate from the router's. You can fix the router perfectly and still fail, because your streaming stick connects through the extender. Log into the extender itself and turn its isolation off before you try pairing again.

Bands cause a sneakier version of the same problem. Plenty of older Chromecasts, smart plugs, and budget TVs only speak 2.4GHz, while your phone rides on 5GHz. On most routers both bands share one network, so discovery still works.

On some extenders and older mesh setups, though, the bands act like separate networks. Your phone and TV end up in different rooms of the same house, so to speak. If you suspect this, our guide to wifi bands explained covers how the bands split and how to get devices onto the same one.

Newer mesh systems add one more wrinkle, usually called an IoT network. It quietly parks smart devices on their own fenced-off network, away from your phones. That's genuinely good for security. It also kills casting to anything on it, so keep TVs and speakers off the IoT network.

Your phone's VPN blocks discovery too

VPN apps are the sneakiest entry on this list. When a VPN is active, it grabs all of your phone's traffic, including the local broadcasts that find Chromecasts. The TV never hears your phone asking. No router setting can fix this one, because the block lives on the phone.

Turn the VPN off and try casting again. This is a documented fix for both Chromecast setup and AirPlay discovery, and it works surprisingly often. People forget a VPN is even running, especially the free ones that connect automatically at startup.

Some VPN apps offer a setting called allow LAN access or local network sharing. Turn that on and you can usually cast without dropping the VPN. If your app has no such option, you'll have to toggle the VPN off each time you cast. Annoying, but that's the tradeoff.

The same fix rescues printers, Sonos, and HomeKit

Everything above applies to far more than casting. A printer that shows offline while sitting right next to you is often the same story. So is a Sonos speaker that vanishes from its app, or a HomeKit accessory stuck on No Response. They all rely on the same local discovery traffic that isolation kills.

The same short checklist fixes all of them. Work through it in order whenever a device refuses to show up.

1. Confirm both devices are on the same network name, and that it isn't the guest network.
2. Turn off any VPN on your phone, at least while you set things up.
3. Log into the router and switch off AP isolation, client isolation, or anything named block local traffic.
4. If an extender sits between the two devices, check it for its own isolation setting.
5. Reboot the router, then the TV or speaker, then the phone.

Steps one and three solve most cases. If all five fail, check whether your mesh app hides an IoT or device isolation feature in its security section. Those features are new enough that plenty of manuals barely mention them.

One honest warning before you go flipping switches. Turning isolation off means every device on that wifi can see the others again. In a normal home, that's exactly what you want. Casting, printing, and smart speakers all depend on it.

If you regularly host strangers, don't weaken the main network for them. Keep visitors on the guest wifi and accept that they can't cast. A trusted guest who really needs the TV can join the main network for the evening. Change the password after they leave, and you've lost nothing.