AUDIO GUIDE / FIX A PROBLEM

MicDrop cannot find or connect to your PC: a LAN checklist

Troubleshoot MicDrop discovery and pairing on home Wi-Fi: host adapter, guest isolation, Private-network firewall access, and iPhone permission.

START HERE

Check that the Windows host is running on the physical home-network adapter, the phone can reach that network, and MicDrop is allowed through the Private-network firewall. Discovery, pairing approval, and audio streaming are separate steps.

Find the step that fails

Connection symptoms and where to start
SymptomFirst check
No host in the discovery listRunning host, correct adapter, local-network access, guest isolation
Pairing request does not completeCurrent private invitation, tapping Connect on the phone, and clicking Approve on Windows
Previously paired phone cannot reconnectHost address/device availability and saved pairing status
Connect succeeds but audio is silentThe audio path, not just discovery

Automatic discovery helps find a computer. It does not approve a phone or establish that audio is flowing. Likewise, a copied invitation does not bypass network isolation.

1. Check the Windows host and adapter

Open MicDrop and confirm the host is started. Under Connection, use the physical home-LAN adapter and its private address. VPN, virtual-machine, and disconnected adapters can appear in the list; choose the one that actually connects to the phone's network.

If the PC changed networks or its address changed while the host was running, stop the host, refresh the network selection, and start it again. Generate a current invitation if the saved address needs updating. Keep the PC signed in and awake. Starting the host does not itself start an audio session; the phone must connect.

2. Check local reachability

Use the ordinary trusted home network for the first test. A wired PC and a Wi-Fi phone can work together when the router permits communication between them. A guest SSID may intentionally prevent devices from talking, even when both have internet access.

Using different Wi-Fi bands is not automatically a problem; the network's routing and isolation matter. For diagnosis, put the phone on the main home SSID near the access point. If a VPN is active, check whether it blocks LAN access. Change that setting only when appropriate for the network and its policy.

3. Verify app permissions without disabling protection

Allow the installed MicDrop application on your trusted Private Windows network. A firewall rule for an old command-line executable may not cover the current desktop app. Keep Windows Firewall enabled and use the app's Windows Firewall… button or Windows settings to inspect the rule. On the experimental Linux host, check Linux Firewall… for ufw or firewalld rules on your LAN interface; on the experimental macOS host, check macOS 15+ Local Network access and macOS Firewall….

On iPhone, check MicDrop's Local Network permission under Settings → Privacy & Security. A denied permission can block a local connection while other internet applications work normally.

4. Retry pairing deliberately

Use a fresh invitation from the running host, scan or paste it on the phone, and tap Connect so the phone sends its pairing request. Then compare the request ID on both screens and click Approve for the intended phone on Windows. Scanning alone never sends a network request, and a phone name is not proof of identity. Do not post QR codes or pairing links in a public bug report.

For an existing pairing, first check whether it is still approved. Avoid uninstalling the phone app as an early troubleshooting step: deletion removes its saved data and may create unnecessary pairing work. Also check that another phone is not already using the host's one active stream.

Local setup is different from remote access

LAN discovery will not find your home PC from cellular data. MicDrop's optional remote mode needs a separately configured rendezvous/TURN service and opt-in on Windows. Follow the project's remote documentation for that setup. Port-forwarding the local listener or disabling the firewall is not a substitute.

When reporting a failure, include the failing stage, app versions, network type, and whether a current invitation behaved differently from discovery. Share sanitized diagnostics rather than screenshots containing access details.

Sources & version notes

Checked against the documentation below on November 13, 2026. App labels and platform support can change; use matching MicDrop builds and check the current release notes. These are setup guides, not new hardware benchmark results.