Hey! We’ll fix why your Linksys is not discovering devices (printers, smart TV, AirPlay/Chromecast, smart home gear) and get local discovery working again. Quick questions so we pinpoint the exact block:
• Which Linksys model: Velop mesh (WHW/MX series), or a classic Linksys router (EA/MR series)? Using the Linksys app / Linksys Smart Wi-Fi?
• What can’t be discovered: printer not found, TV not showing, Chromecast not appearing, AirPlay not showing, Sonos missing, smart plugs/cameras not showing in apps?
• Are your devices on the same network name, or do you have separate SSIDs like Main vs Guest / 2.4 GHz vs 5 GHz / an IoT network?
• Any recent change: firmware update, new mesh node, new switch, VPN, or “security / firewall” settings toggled?
We’ll focus on the top causes: client isolation, guest network separation, blocked multicast (mDNS/SSDP), and IP/DHCP issues.

Got it — when the internet is fine but Linksys can’t discover devices, it’s usually not “Wi-Fi down”, it’s discovery traffic being blocked.

Most smart-home and media devices rely on discovery protocols like:
• mDNS / Bonjour (AirPlay, AirPrint, HomeKit, many smart devices)
• SSDP / UPnP (Chromecast-style discovery, DLNA, some cameras/IoT apps)

These are multicast “shout-out” packets on the local LAN. If Velop enables Guest Access, AP / client isolation, or devices get split across different LAN segments, your phone can’t “see” them even though both have internet.

We’ll do a quick, clean set of checks: same SSID/LAN, disable isolation, confirm UPnP, and refresh DHCP leases so everything is on one subnet.

Yes — that’s one of the most common reasons discovery breaks. Let’s fix it fast.
Step 1 — Confirm all devices are on the same “Main” network (not Guest)
1) On your phone, forget the “-guest” SSID if you’ve ever used it, then connect to the main Wi-Fi.
2) In the Linksys app, check the TV/Chromecast/printer: make sure they’re not connected to a guest SSID or a separate IoT SSID.
3) If you split SSIDs (2.4 and 5), it’s OK for discovery as long as it’s the same LAN, but band-steering + isolation can still break it. For testing, temporarily put phone + one target device (TV or Chromecast) on the same SSID to remove variables.

Step 2 — Turn OFF anything that isolates clients
Look for settings like:
• “Client/AP Isolation”
• “Block LAN access” / “Wireless Isolation”
• “Separate guests from local network” (this is normal on Guest, but your main SSID should allow LAN access)

Once that’s off, discovery (AirPlay/Chromecast/printer discovery) usually comes back within 1–2 minutes, or after a quick Wi-Fi reconnect.

Great — that tells us discovery traffic is partially flowing, but something is still “stale” (often DHCP leases or nodes not synced). Let’s do a refresh the right way so Velop rebuilds the LAN tables.
Step 3 — Power cycle in a clean order (fixes flaky device discovery)
1) Unplug the parent node (main Velop connected to modem). Wait 30 seconds.
2) Unplug child nodes too (if you have them).
3) Power on the parent node first and wait until it’s fully online (solid status light).
4) Power on child nodes one by one (wait 2–3 minutes each).
5) Restart the device you’re trying to discover (TV / Chromecast / printer) so it requests a fresh IP.

Step 4 — Verify “same subnet” and no IP conflicts
• In the Linksys app, tap each device and note the IP address (example: 192.168.1.xxx). Your phone, printer, and TV should be on the same subnet (same first 3 blocks).
• If you see mixed ranges (like 192.168.1.x and 192.168.10.x) on what should be one Wi-Fi, that’s a sign of double-NAT, bridged nodes/switch issues, or a second router handing out DHCP.

This step fixes a lot of “Linksys not discovering devices” cases without touching advanced settings.

Perfect subnet — now we target the two remaining “layers”: (A) router discovery features like UPnP/SSDP and (B) device-side blocks like Windows firewall/VPN.

Step 5 — Confirm UPnP is enabled (Chromecast & many apps rely on it)
In Linksys settings (app or web UI), look for UPnP and make sure it’s Enabled. If it was toggled recently, switch it ON, save, then reboot just the parent node once.

Step 6 — Check for VPN / “Private Relay” / firewall blocking local discovery
On the phone/laptop that can’t discover devices:
• Temporarily disable any VPN app (many VPNs block local multicast discovery).
• On iPhone, if you use privacy/VPN profiles, test once with them off (just to rule it out).

Step 7 — Fix Windows “Network discovery is off” + printer discovery
• Make sure your Wi-Fi network is set as Private (not Public). Public networks often block discovery.
• In Windows Firewall, “Network Discovery” and “File and Printer Sharing” should be allowed on Private networks.
• If the printer still won’t show, a reliable workaround is to add it by IP (since you already see 192.168.1.140). That bypasses flaky discovery while we finish stabilizing UPnP/mDNS on the router.

These are the quick wins for “Linksys not discovering devices” where only certain clients fail (Windows apps, specific casting apps, etc.).

Yes — printer discovery is often mDNS/Bonjour (especially on Apple) or vendor broadcast discovery (some printers/apps). If something on the network blocks multicast, devices feel “invisible.” Here are the Linksys/mesh-related culprits that match your symptoms:

Step 8 — Watch for multicast blockers (mesh + switches + “smart” features)
• If you use a managed switch between Velop nodes, settings like IGMP snooping or multicast filtering can accidentally drop SSDP/mDNS traffic.
• If you have any extra router/extender in the middle (double NAT), discovery often breaks across segments even when internet works.

Guest Access note (important)
Linksys Guest Access is designed to prevent guests from seeing your local devices. So if a TV/printer is connected to guest Wi-Fi (even by accident), other devices on the main network typically won’t discover it. That’s normal behavior — and it looks exactly like “Linksys not discovering devices.”

Since UPnP + VPN fix brought Chromecast back, we’re very close. For printers, adding by IP is a strong “stable” method, and we can also ensure mDNS isn’t being blocked by security apps/firewalls on the client devices.

Great questions — let’s balance device discovery with security without breaking AirPlay/Chromecast/printers again.

Step 9 — If you have wired backhaul + managed switch
For quick testing: temporarily disable IGMP snooping (or any “multicast filtering”) on the switch, then test printer discovery again. If discovery improves, we’ll adjust switch settings properly so multicast is handled correctly rather than blocked.

UPnP safety (practical approach)
• UPnP helps devices request port mappings automatically. The risk depends on whether untrusted devices can join your network.
• Best practice: keep strong Wi-Fi password, use Guest Wi-Fi for visitors, and keep firmware updated. If you don’t need automatic port forwarding, you can disable UPnP later and manually forward ports for specific apps — but many homes keep UPnP enabled for consoles/streaming without issues.

Future-proof discovery on Linksys
• Avoid enabling “client isolation” on your main SSID (use Guest for isolation).
• Keep devices that must see each other (phone + TV + Chromecast + printer) on the same main LAN.
• If you must separate IoT, be aware that mDNS/SSDP won’t cross networks unless you add specific bridging tools (advanced setup).

With these, “Linksys not discovering devices” stops happening after every tweak/update.

Awesome — that matches the pattern: discovery depends on multicast, and a switch/router setting can silently block it. Before the summary, here are two “backup” options if discovery ever fails again:
• Add devices by IP (printers, some TVs, some cameras). It bypasses discovery and stays stable even if multicast is flaky.
• If a single device becomes invisible after updates, do a network reset on that device (forget Wi-Fi / reconnect) to refresh its DHCP lease and local announcements.

If you ever see “device not found” again and you’re not sure whether it’s mDNS/Bonjour, SSDP/UPnP, or isolation, we can troubleshoot it live with your exact Velop model and switch settings.

Summary: if Linksys is not discovering devices, first confirm everything is on the main network (not Guest) and disable client/AP isolation. Then reboot Velop nodes in order and verify all devices are on the same subnet. Enable UPnP for SSDP-based discovery (Chromecast/DLNA-style apps), and make sure VPN/firewalls aren’t blocking local LAN traffic. If you use a managed switch for wired backhaul, multicast settings like IGMP snooping can break mDNS/Bonjour and printer discovery — adjust or disable it if needed. Still stuck? Open the chat and an expert will walk through your Linksys settings step by step.