Hi Esa,
Your issue likely stems from how multicast traffic is handled in enterprise Wi-Fi environments. Chromecast relies on mDNS (UDP 5353) and SSDP (UDP 1900) for device discovery and communication, and these protocols can be blocked by default in controller-based setups. Make sure client isolation is disabled, multicast forwarding is allowed, and IGMP snooping is either disabled or properly configured with a querier. Enabling multicast-to-unicast conversion (if supported by your AP) can also improve performance.
Since you’re using bridged@AP mode, double-check that the multicast traffic is correctly forwarded between wireless clients. You can use Wireshark on both devices to confirm the multicast discovery packets are being exchanged. Also, consider testing with a basic open SSID and minimal security to isolate configuration issues from encryption-related bugs.
For the Spotify issue, it’s likely related to the same multicast discovery challenges. Spotify Connect requires reliable multicast between devices on the same network. If it works on home-grade APs but not on your enterprise gear, it strongly suggests a config gap. Make sure multicast bridging is working end-to-end and that UDP ports used by APK Spotify Premium (usually 5353 and others) are not filtered. Also, try updating your controller/AP firmware, as newer releases often include multicast fixes.
Regards
