How to Fix Network Scanners and WiFi-Enabled Printers Not Appearing in Scan-to-PC Lists: mDNS, Bonjour, and Discovery Protocol Fixes

You open your scanning software, click Add Scanner, and nothing appears — even though the printer is clearly on the same WiFi network and can print just fine. Or the device was listed yesterday and vanished after your PC woke from sleep. This is one of the most common WiFi frustrations, and it almost always comes down to one of four root causes: a broken mDNS/Bonjour discovery protocol, AP isolation on your router, a subnet mismatch between your PC and printer, or a known Windows WiFi driver bug. This guide walks through each fix in order from fastest to most involved.

How Network Discovery Actually Works

Modern WiFi-enabled printers and scanners advertise themselves using mDNS (Multicast DNS) — Apple calls their implementation Bonjour. The device sends multicast announcements to IP address 224.0.0.251 on UDP port 5353, and any computer on the same subnet listening on that port can discover it automatically. Windows also uses WS-Discovery (Web Services for Devices) on UDP port 3702 for the same purpose.

The critical constraint: multicast packets do not cross subnet boundaries. If your printer and PC are on different subnets — or if your router is blocking multicast traffic — discovery fails silently every time.

Fix 1: Confirm Both Devices Are on the Same Subnet

This is the single most common cause of scanner discovery failures. On your PC, open a command prompt and run ipconfig. Note your IPv4 address and subnet mask (typically 255.255.255.0). On the printer, print a network configuration page (the method varies by brand — check the front panel or your manual). Compare the first three octets of both IP addresses — for a 255.255.255.0 mask they must match. For example, 192.168.1.x on one device and 192.168.2.x on the other means they’re on different subnets and will never discover each other via mDNS.

If the subnets differ, the fix is usually to log into your router and ensure both devices are on the same LAN segment. If you have a mesh system, make sure all nodes are in the same VLAN. Check that the printer is not connected to a guest network (see Fix 2).

Fix 2: Disable AP Isolation (Client Isolation)

Many routers enable AP isolation (also called client isolation or wireless isolation) on guest networks — and some enable it on the main network too. AP isolation prevents WiFi clients from talking directly to each other, which blocks all mDNS and WS-Discovery traffic. Even if the printer and PC are on the same IP subnet, they cannot communicate when this setting is active.

To check and disable AP isolation, log into your router admin page (typically 192.168.1.1 or 192.168.0.1). The setting is usually under Wireless › Advanced or Wireless › Security. On TP-Link routers it’s under Application Management › AP Isolation. On ASUS routers it’s under Wireless › Professional › Enable AP Isolation. Turn it off for the SSID your printer and PC share.

If your printer is connected to a guest network, move it to your main network instead — guest networks almost always have isolation and inter-device blocking enabled by design, which is exactly what breaks discovery.

Fix 3: Update or Roll Back Your WiFi Adapter Driver (Windows)

A well-documented Windows bug affects Intel WiFi adapters including the AX201, AX210, AX211, and older AC8260. After the PC resumes from sleep or hibernate, these drivers stop processing incoming mDNS multicast packets, causing all previously visible network devices to vanish from discovery lists. The printer is still reachable by IP address, but automatic discovery stops working until you disable and re-enable the WiFi adapter.

Temporary workaround

Open Device Manager, expand Network Adapters, right-click your WiFi adapter, and select Disable device. Wait three seconds, then right-click again and select Enable device. Discovery should resume within 30 seconds.

Permanent fix

In Device Manager, right-click your WiFi adapter and select Properties › Power Management. Uncheck Allow the computer to turn off this device to save power. Also go to Advanced and set Wake on Magic Packet and Wake on Pattern Match to Disabled. Finally, visit Intel’s support site and install the latest driver version for your adapter — Intel has issued several patches for this specific issue.

Fix 4: Check Windows Firewall and Multicast Settings

Windows Firewall can block mDNS and WS-Discovery traffic, particularly after a Windows update resets firewall rules. Open Windows Security › Firewall & network protection › Allow an app through firewall. Make sure Bonjour Service and your scanning software (e.g. HP Smart, Epson Scan, Canon IJ) are allowed on Private networks.

You can also test mDNS from the command line. Open PowerShell and run:

dns-sd -B _scanner._tcp .

On macOS, use: dns-sd -B _scanner._tcp . or dns-sd -B _ipps._tcp .. If no services appear after 30 seconds, mDNS traffic is being blocked at the network or driver level. If services appear on macOS but not Windows, the driver or firewall fix applies.

Fix 5: Enable mDNS Reflector or Bonjour Forwarding on Your Router

If your network has multiple subnets — for instance, a wired LAN on one subnet and WiFi on another — you need an mDNS reflector or Bonjour proxy to bridge discovery traffic between segments. Many modern routers support this natively.

• ASUS routers: Enable mDNS under LAN › IPTV or Advanced Settings › LAN
• Netgear routers: Look for Bonjour or mDNS forwarding under Advanced › Advanced Setup
• Ubiquiti UniFi: Enable mDNS in your network settings under Networks › [VLAN] › Advanced › mDNS
• pfSense / OPNsense: Install the Avahi package to act as an mDNS repeater across VLANs

Fix 6: Add the Printer by IP Address as a Fallback

If discovery still fails after the above fixes, you can bypass it entirely by adding the printer using its static IP address. First, assign the printer a DHCP reservation in your router so its IP never changes (use the printer’s MAC address from the network config page). Then on Windows, go to Settings › Bluetooth & devices › Printers & scanners › Add device › Add manually › Add a printer using a TCP/IP address or hostname and enter the IP address. For scanning, use IPP (port 631) or the printer manufacturer’s software with the IP address entered manually.

Quick Checklist

• Verify printer and PC share the same subnet (first three IP octets match on a /24 network)
• Move the printer off the guest network and onto your main SSID
• Disable AP/Client isolation in your router’s wireless settings
• Disable and re-enable your WiFi adapter after sleep to restore mDNS (Intel adapter bug)
• Update your Intel WiFi driver and disable power management for the adapter
• Confirm Windows Firewall allows Bonjour and your scanning app on private networks
• Enable mDNS reflector/Bonjour forwarding on your router if using multiple subnets
• As a last resort, add the printer by static IP address using TCP/IP printer setup

Once discovery is working, run a WiFi speed test near your printer to make sure signal strength is adequate — printers need at least −70 dBm to maintain a stable connection. If signal is weak, see our guide on how to extend WiFi range or check our picks for the best mesh WiFi systems to bring solid coverage to every corner of your home.