USB Printer Not Showing Up on Wi-Fi? AirPrint & Mopria Fixes

You shared the printer, but it is nowhere in the AirPrint or Mopria list. This is the single most common issue with local network printing, and it is almost never a printer problem. In nearly every case it comes down to one of a handful of network or firewall settings.

Work through this list in order. Each step has the exact fix.

---

First, Confirm the Printer Is Actually Shared

On the Windows PC, run:

./printman.exe share

You should see a line like this:

  [NETWORK PRINTERS]  Sharing 1 printer as "Printman - HP LaserJet Professional P1102"
    URL:               ipp://192.168.1.50:631/ipp/print

If that line is missing, the printer was not shared. Run ./printman.exe share --select and tick the printer, or pass its name directly.

---

1. Check the Windows Firewall Prompt

The first time you share, Windows shows a UAC and firewall prompt. If it was dismissed, inbound printing traffic is blocked.

1. Open Windows Security, then Firewall & network protection.
2. Open Allow an app through firewall and make sure printman is allowed on Private networks.
3. If it is not listed, re-run printman share and approve the prompt.

Printman also runs a read-only check at startup and prints the exact netsh commands to allow inbound printing if it looks blocked. Running those commands and restarting printman share fixes most firewall cases.

---

2. Make Sure Both Devices Are on the Same Network

The printer and the device you print from must be on the same subnet. A few things break this:

• The phone is on a guest Wi-Fi. Guest networks usually isolate clients from each other, so the phone can never reach the PC.
• The PC is on Ethernet into one router and the phone is on a mesh node or extender that puts it on a different subnet.
• A VPN on the phone routes all traffic away from the local network.

Switch the device to the main Wi-Fi and disconnect any VPN, then try again.

---

3. Check for Client (AP) Isolation

Client isolation stops wireless devices from talking to each other. It is common on guest networks, hotels and some ISP routers.

• In the router settings, look for AP isolation, client isolation or wireless isolation and turn it off.
• Reboot the router after changing the setting.

---

4. Port 631 Is Already in Use

The IPP standard uses port 631. If another print service or an old install is holding it, Printman cannot bind and devices will not find the printer.

Share on a different port:

./printman.exe share --ipp-port 8631

Then add the printer by URL using the new port, for example ipp://192.168.1.50:8631/ipp/print.

---

5. Multicast (mDNS) Is Blocked

Discovery relies on multicast DNS. Some routers, VLANs and corporate networks block it. When that happens the printer still works, it just is not auto-discovered.

Two options:

• Manual URL. Keep sharing and add the printer by the ipp:// URL from the console. On macOS use the IP tab, on Windows use Add printer by URL, and on Android or ChromeOS paste the URL in the manual add screen.
• Turn discovery off to avoid waiting on multicast that never arrives:

./printman.exe share --no-mdns

---

6. The Printer Only Appears After a Restart

If you changed firewall or router settings, restart Printman and re-open the print dialog so the client refreshes its printer list.

# Stop with Ctrl+C, then restart
./printman.exe share

On phones, toggling Wi-Fi off and on forces a fresh discovery scan.

---

7. Confirm With a Quick Test

From another computer on the same network, open the printer URL in a browser. You should get a response from the print server rather than a timeout. A timeout means the network path is blocked, not that the printer is broken.

If a browser can reach the URL but the device still does not list the printer, add it manually by URL. That confirms rendering and the Windows spooler work, and isolates the remaining issue to discovery alone.

---

Still Stuck?

A good next step is to compare against a known working setup. The AirPrint and Mopria sharing guide covers the full process device by device, and the Chromebook, Android and macOS guides show the exact add-printer steps for each platform.

---

Frequently Asked Questions

Why does my shared printer not appear in the print dialog?

The most common causes are Windows Firewall blocking Printman on a Private network, a guest or isolated Wi-Fi that blocks multicast, or another service already using port 631. Work through the checks in order and the printer almost always appears.

How do I know if Printman is actually running?

Run printman share and look for the [NETWORK PRINTERS] line with an ipp:// URL. If that line is missing, the printer was not shared. You can confirm the process is still alive by watching the console for incoming job logs.

What does client isolation mean and why does it matter?

Client isolation, also called AP isolation, is a router setting that stops wireless devices from talking to each other. Guest networks often enable it. When it is on, phones and laptops cannot reach the shared printer at all, so use the main Wi-Fi.

Can I add the printer manually if discovery does not work?

Yes. Start printman share --no-mdns and add the printer by the ipp:// URL it prints, for example ipp://192.168.1.50:631/ipp/print. Manual IPP is a reliable fallback when multicast is blocked.