LanSender Can’t Find Devices: Fix AP & Client Isolation

One common LanSender problem looks confusing: your phone and computer are connected to the same Wi-Fi and can access the internet, but LanSender cannot find either device.

In many cases, the network is preventing device-to-device communication. A router feature such as Client Isolation or AP Isolation can allow internet access while blocking local discovery and direct connections between wireless clients.

Quick Fix

If LanSender cannot find devices on the same Wi-Fi:

Confirm that both devices are using the same trusted network.
Make sure neither device is connected to guest Wi-Fi.
Check the router for Client Isolation or AP Isolation.
Temporarily disable VPNs and proxies.
Check Windows, macOS, or Android local network permissions.
Restart LanSender after changing the network settings.

Only disable isolation on a trusted home or office network. Do not bypass isolation on hotel, airport, café, or other public Wi-Fi.

What Is Client Isolation?

Client Isolation is a security feature that limits communication between devices connected to the same wireless network. Router and access-point vendors may use different names for similar controls, including:

Client Isolation
AP Isolation
Wireless Isolation
Intra-BSS Blocking
Device Isolation

For example, TP-Link documents AP Isolation as a feature that prevents wireless clients from communicating with one another. Cisco Meraki describes Wireless Client Isolation as a feature that blocks communication between wireless clients on the same network segment.

Related settings can also affect local discovery, but they are not always the same feature. These may include guest-network isolation, VLAN rules, multicast filtering, proxy settings, and options that restrict intranet access.

Why Can’t My Phone and PC Find Each Other on the Same Wi-Fi?

The same Wi-Fi name does not always mean that devices are allowed to communicate. Common causes include:

Client Isolation or AP Isolation
Guest-network isolation
Devices connected to different VLANs or network segments
VPN or proxy interference
Windows, macOS, or Android network permissions
Firewall rules blocking local traffic
Android background or battery restrictions

Typical symptoms include:

Android remains on “Discovering nearby devices”
The computer does not appear in the nearby devices list
A device always appears offline
Devices have internet access but cannot find each other
A transfer fails after the connection starts
A device appears briefly and then disappears

How to Check Whether Client Isolation Is the Cause

1. Confirm the Network Connection

Check that both devices are connected to the same local network. Pay attention to these situations:

The phone is connected to guest Wi-Fi
The computer is connected to the main Wi-Fi
The devices use separate SSIDs
One device is connected through a wireless repeater or mesh node
The computer uses Ethernet on a different VLAN
Two networks have similar names but different access rules

The connection methods do not have to match. A computer can use Ethernet while a phone uses Wi-Fi, as long as both devices are on the same local network and peer-to-peer communication is allowed.

2. Check the Router or Wireless Controller

Search for options such as:

Client Isolation
AP Isolation
Wireless Isolation
Intra-BSS Blocking
Device Isolation
Guest Network Isolation
Allow Intranet Access

Menu names vary by manufacturer. Do not search only under Firewall settings because client isolation is often located under wireless or SSID settings.

On a trusted home or office network, disable the relevant isolation setting for the SSID used by your devices. Save the change, reconnect the devices if necessary, and restart LanSender.

Router terminology and behavior vary by manufacturer, so check your router's own documentation when you need the exact setting name.

3. Check Whether You Are Using Guest Wi-Fi

Guest networks commonly isolate connected devices to protect guest privacy. If your phone and computer are connected to guest Wi-Fi, move both devices to the main home or office network.

Do not disable security isolation on public Wi-Fi. Isolation on hotel, airport, café, and other public networks is usually intentional.

4. Temporarily Disable VPNs and Proxies

VPNs, proxy tools, network accelerators, virtual adapters, and some security applications can interfere with local discovery.

Temporarily turn off the relevant tool, restart LanSender, and check the nearby devices list again. If discovery works after the VPN is disabled, review the VPN’s local-network or split-tunneling settings before using it with LanSender.

Android: LanSender Cannot Find the Computer

If Android cannot find the computer:

Open the LanSender Devices screen
Confirm that the phone is on a trusted home or office network
Check LanSender’s nearby-device permission
Check permissions for the files you want to send
Temporarily turn off Battery Saver
Allow LanSender to run in the background
Keep LanSender running on the computer
Restart LanSender on both devices

Some Android phones restrict network access when an app moves to the background. Keep LanSender open during large transfers.

For the full transfer workflow, see How to Transfer Files from Android to PC.

Windows: LanSender Cannot Find the Android Phone

If Windows cannot find the Android phone, check:

LanSender is running on Windows
Both devices are on the same local network
Windows Firewall allows LanSender on the current trusted network
VPNs and virtual network adapters are not interfering
The computer has not entered sleep mode
Client Isolation is disabled on the trusted SSID
The phone and computer are not separated by different VLANs

Keep Windows Firewall enabled. Allow LanSender through the appropriate private-network rule rather than disabling the entire firewall.

For detailed Windows steps, see Windows Local Network File Transfer.

macOS: LanSender Cannot Find a Local Device

If a Mac cannot find an Android or Windows device, check:

LanSender has Local Network permission
The Mac is connected to the intended Wi-Fi network
The macOS firewall is not blocking LanSender
No VPN or proxy is active
Wireless client isolation is not enabled on the router
The phone is not connected to guest Wi-Fi

On macOS, open:

System Settings → Privacy & Security → Local Network

Make sure LanSender is allowed to access the local network. For a Mac-to-Android transfer guide, see How to Transfer Files Between Mac and Android.

A Simple Connection Test

If you are unsure whether the router is the cause:

Turn off VPNs on the phone and computer.
Connect both devices to the same trusted Wi-Fi.
Make sure LanSender is running on both devices.
Open the Devices screen on Android.
Wait for nearby-device discovery to finish.
Select the computer shown as online.
Send a short message or a small file.

If a short message works but a large file fails, the problem may be related to background restrictions, storage, sleep mode, or firewall settings rather than client isolation.

If the device never appears, check Client Isolation, guest-network settings, VLAN configuration, VPNs, and firewall rules first.

Client Isolation Is Not the Same as a Disconnected Network

When Client Isolation is enabled, devices may still browse the internet normally. This can make the network appear to be working correctly.

There are two separate communication paths:

Device-to-internet communication
Device-to-device communication within the local network

Client Isolation may block the second path while leaving the first path available. The following does not prove that local device communication is working:

The phone can open websites
The computer can access the internet
Both devices show the same Wi-Fi name
Both devices appear in the router’s admin panel

LanSender needs the devices to discover and communicate with each other, not only to access the internet.

Security Recommendations

Client Isolation is useful on untrusted networks, including:

Hotel Wi-Fi
Airport Wi-Fi
Café Wi-Fi
Guest networks
Public wireless networks
IoT or smart-home networks

If you need to use LanSender, choose a trusted network instead of weakening security on a public network. A safer setup is to create a private SSID for your own devices and leave public-network isolation enabled.

Frequently Asked Questions

Why can’t LanSender find devices on the same Wi-Fi?

The router may have enabled Client Isolation, AP Isolation, or guest-network isolation. Devices may also be on different VLANs, or a VPN, proxy, or firewall may be interfering with local discovery.

Does disabling Client Isolation reduce network security?

It reduces separation between devices on that wireless network. Disable it only on a trusted home or office network, and keep your router password, device software, and firewall settings secure.

Can my phone use Wi-Fi while my computer uses Ethernet?

Yes. The connection methods do not have to match. Both devices must be on the same local network and allowed to communicate with each other.

Can I disable Client Isolation on public Wi-Fi?

No. Public Wi-Fi isolation is usually an intentional security protection. Do not disable or bypass it.

Can mesh Wi-Fi or a Wi-Fi extender cause the same problem?

It can, depending on the configuration. Some mesh systems and extenders place devices on different segments or apply client isolation. Check the mesh or extender settings for client isolation, device isolation, or local-network access.

How do I know if my router has Client Isolation enabled?

Log in to the router admin page and open the wireless, SSID, or guest-network settings. Look for Client Isolation, AP Isolation, Wireless Isolation, or Intra-BSS Blocking. If enabled, devices on that SSID may be unable to discover each other even while internet access works.

My device appears online, but file transfers fail. What should I check?

Check Windows or macOS firewall permissions, Android background restrictions, available storage, VPN or proxy settings, and the router’s Client Isolation setting. Send a short message first to confirm that the connection is stable.

Conclusion

Router isolation does not always mean that the network is disconnected. It may simply prevent devices from communicating directly with one another.

When LanSender cannot find a computer, the Android Devices list is empty, or a device always appears offline, check whether both devices are on the same trusted network, whether guest Wi-Fi or Client Isolation is enabled, and whether VPN, firewall, VLAN, or Android background settings are blocking local discovery.

After correcting the relevant setting on a trusted home or office network, restart LanSender and scan again. The devices should then be able to appear in the nearby devices list and transfer files over the local network.

Router Client Isolation: Why LanSender Cannot Find Devices