If LanSender can send files from Windows but cannot receive them, or nearby devices do not appear, Windows Firewall may be blocking local network access. This can happen even when your internet connection works normally.

This guide explains how to check the Windows network profile, allow LanSender through the firewall, and identify other settings that can affect local discovery. The steps apply mainly to Windows 10 and Windows 11.

Quick Fix

For a trusted home or office network:

  1. Set the connected Windows network to Private.
  2. Allow LanSender through Windows Firewall for the Private profile.
  3. Make sure Blocks all incoming connections is turned off for the Private profile.
  4. Keep Windows Firewall enabled.
  5. Restart LanSender and scan for nearby devices again.

Do not disable Windows Firewall completely, and do not enable LanSender on a public network unless you understand the security risk.

Why Windows Firewall Can Affect LanSender

LanSender needs local network access to discover nearby devices and establish direct connections for chat and file transfers. Windows Firewall can block this access when:

  • LanSender was blocked during its first Windows Firewall prompt.
  • Windows classified your home or office network as Public.
  • A Windows update changed an existing permission.
  • An old firewall rule points to a previous LanSender installation path.
  • A VPN, virtual network adapter, or security suite filters local traffic.
  • The Private profile blocks all incoming connections.

Typical symptoms include:

  • The nearby-device list is empty.
  • A device appears offline even though LanSender is running.
  • Windows can send files but cannot receive them.
  • Chat messages do not arrive.
  • A transfer starts but cannot establish a connection.

Step 1: Set the Windows Network Profile to Private

LanSender is intended for nearby devices on a trusted local network. Check the profile used by your home or office connection:

  1. Open Settings.
  2. Select Network & internet.
  3. Select Wi-Fi or Ethernet.
  4. Open the connected network.
  5. Set Network profile type to Private.

Use Private only for a network you trust. Keep unfamiliar hotel, airport, café, and guest networks set to Public.

Step 2: Allow LanSender Through Windows Firewall

To allow LanSender on a trusted Private network:

  1. Open Windows Security.
  2. Select Firewall & network protection.
  3. Select Allow an app through firewall.
  4. Select Change settings.
  5. Find LanSender in the list.
  6. Select Private and leave Public unchecked.
  7. Select OK, then restart LanSender.

If LanSender is not listed, select Allow another app, browse to the current LanSender.exe file, and allow it on the Private profile only.

Allowing the application is safer than turning off the entire firewall. Do not open random ports unless LanSender support specifically provides a port requirement for your installed release.

Step 3: Check the Private Profile's Incoming-Connection Setting

Windows Firewall has a setting called Blocks all incoming connections, including those in the list of allowed apps. When it is enabled, Windows ignores allowed-app exceptions and blocks incoming connections.

To check it:

  1. Open Windows Security.
  2. Select Firewall & network protection.
  3. Open the active Private network profile.
  4. Confirm that Blocks all incoming connections, including those in the list of allowed apps is turned off.

Keep the firewall enabled. Change only this setting when you are troubleshooting a trusted Private network.

Step 4: Check for Outdated or Duplicate Rules

If LanSender was moved or reinstalled, Windows may still have a rule for an older executable path. In Allow an app through firewall, check that the entry matches the current installation.

If the rule is missing or points to an old path, remove the outdated entry if your Windows permissions allow it, then add the current LanSender.exe again. Reinstalling the app alone does not always remove old firewall rules.

Step 5: Check Other Software That Can Block Local Traffic

Third-party antivirus, endpoint-security tools, VPNs, proxies, and virtual network adapters can apply their own network rules. Check for settings such as:

  • Local network protection
  • Blocked applications
  • Network traffic filtering
  • Isolation mode
  • VPN LAN access blocking

If your security software allows it, pause its network filtering briefly for a controlled test on a trusted network. If LanSender works afterward, add a specific allow rule for LanSender and turn the protection back on.

Do You Need to Enable File and Printer Sharing?

Usually, no. LanSender is not the same as Windows SMB file sharing, so enabling File and Printer Sharing should not be treated as a required LanSender fix.

Windows Network Discovery and File and Printer Sharing are Windows features used for discovering Windows devices and sharing folders or printers. They may be relevant to a separate Windows sharing problem, but they are not proof that every local transfer application requires those rules.

If LanSender still cannot discover devices after its own Private firewall permission is enabled, check Network Discovery, router isolation, VPN settings, and the other troubleshooting steps in this guide. Do not enable broader sharing rules unless your workflow needs them or LanSender support specifically recommends them.

If LanSender Still Cannot Find Devices

Check the following in order:

  1. Both devices are connected to the same trusted Wi-Fi or local network.
  2. The phone is not connected to a guest network.
  3. Router Client Isolation or AP Isolation is not blocking device-to-device traffic.
  4. LanSender is running on both devices.
  5. Windows Firewall allows the current LanSender application on the Private profile.
  6. VPNs and proxies are temporarily disabled.
  7. The receiving device has enough storage.
  8. Windows has not entered sleep mode.

For router-side checks, see Router Client Isolation: Why LanSender Cannot Find Devices.

Frequently Asked Questions

How do I allow LanSender through Windows Firewall?

Open Windows Security → Firewall & network protection → Allow an app through firewall, select Change settings, find LanSender, and enable Private. Leave Public unchecked for normal home or office transfers.

Why can LanSender send files but not receive them on Windows?

Outbound traffic may be allowed while incoming connections are blocked. Check LanSender's Private firewall permission and confirm that Blocks all incoming connections is turned off for the active Private profile.

Do I need to allow LanSender on Public networks?

No. LanSender is best used on a trusted Private network. Keep Public access disabled unless you have a specific, understood reason to allow it.

Why did LanSender stop finding devices after a Windows update?

A Windows update may change network classification, disable an existing rule, or leave a rule pointing to an older LanSender path. Recheck the Private profile, the current executable path, and any third-party security settings.

Can antivirus software block LanSender even when Windows Firewall allows it?

Yes. Security suites may apply separate local-network or application rules. Check their blocked-app and LAN-protection settings and add LanSender as a trusted application when appropriate.

Does turning on Network Discovery fix LanSender?

It may help with Windows device discovery, but it is not a universal requirement for LanSender. First allow the current LanSender application on the Private profile, then check router isolation, VPNs, and security software.

Related Links

Conclusion

Windows Firewall can prevent LanSender from discovering nearby devices or accepting incoming files while normal internet access continues to work. The safest fix is to use a trusted Private network and allow the current LanSender application through the Private firewall profile.

Keep Windows Firewall enabled, avoid unnecessary port or file-sharing changes, and check router isolation, VPNs, and third-party security tools if the problem continues.