🪟 The Two PCs That Were Never on the Same Network, Technically
Nearby Sharing relies on Wi-Fi Direct for its actual file transfer, which means both PCs need to be reachable over Wi-Fi hardware that can negotiate a direct peer connection even while both stay connected to the regular network – and a lot of dual-band home routers broadcast one SSID that silently steers different devices onto the 2.4GHz or 5GHz band based on signal strength and device capability, often without either user ever choosing a band explicitly. Two laptops sitting a few feet apart, both showing full Wi-Fi bars and both connected to what looks like the exact same network name, can still fail to see each other in Nearby Sharing’s device list for no visible reason, because the router quietly assigned them to two different radio bands that Wi-Fi Direct discovery doesn’t bridge between.
🔎 The Problem
Laptop A: connected to "HomeNetwork" - actually associated on 5GHz Laptop B: connected to "HomeNetwork" - actually associated on 2.4GHz (same SSID broadcast on both bands by the router, band assignment handled automatically and invisibly per device) Settings > System > Nearby sharing: turned On on both laptops, Bluetooth On on both, both discoverable to "Everyone nearby" Result: neither laptop's Share sheet ever lists the other device, even sitting a few feet apart - because Wi-Fi Direct's peer discovery happens over the Wi-Fi radio actually in use, and two devices parked on different bands of the same-named network don't share the same radio-level discovery path Nearby Sharing depends on.
✅ Fix: Put Both Devices on the Same Band, or Bypass the Router Entirely
- Check each device’s actual connection band (Settings > Network & internet > Wi-Fi > click the connected network > Properties on Windows 11 shows the band under link properties, or check the router’s own connected-devices list) rather than assuming matching SSID names means matching bands – if a router broadcasts one SSID across both 2.4GHz and 5GHz, confirm both devices by checking this directly.
- If the router allows it, split the dual-band SSID into two separate network names (one for 2.4GHz, one for 5GHz) and manually connect both devices to the same one before trying Nearby Sharing again – this removes the router’s automatic, invisible band-steering decision from the equation entirely.
- As a more reliable fallback that sidesteps band-steering altogether, turn Wi-Fi off on both devices and rely on Bluetooth alone for the Nearby Sharing transfer – it’s slower for large files, but Bluetooth pairing discovery doesn’t depend on which Wi-Fi band either device happens to be using at that moment.
🚨 Why This Is Dangerous
- Both laptops report themselves as fully connected to the internet, to the same named network, with strong signal the entire time this is happening, so every obvious troubleshooting signal (signal strength, connectivity, correct network name) looks completely fine while the actual blocking factor – the specific radio band each one landed on – is invisible anywhere in the normal Wi-Fi status UI.
- Because band assignment is decided automatically by the router based on signal strength and can change as a device moves around a house or reconnects after sleep, Nearby Sharing can work perfectly one day between two devices and inexplicably stop the next, with neither user having changed a single setting on either machine.
Same Wi-Fi name doesn’t mean same Wi-Fi radio – and Nearby Sharing’s peer discovery was only ever listening on one of them.
