Printer network discovery timeout – fix in 5 minutes
Your printer shows up one day, then disappears the next. This timeout error happens when Windows can't find the printer on the network fast enough. Here's the fix.
When this error shows up
You open Settings > Bluetooth & devices > Printers & scanners on Windows 11. You click "Add device" and wait. After 30 seconds, you get "Printer not found" or "Discovery failed." The printer is on, connected to Wi-Fi, and you can print from another computer. This almost always happens after a Windows update, a router reboot, or when your printer's IP address changed. I've seen it on HP Envy 6000 series, Brother HL-L2350DW, and Canon PIXMA printers running Windows 10 22H2 and Windows 11 23H2.
Why it happens – plain English
Your computer sends a broadcast message asking "any printers here?" The printer should reply within milliseconds. But network discovery takes time. Windows gives up after 20–30 seconds if the printer doesn't answer fast enough. The real problem is often one of three things:
- IPv6 vs IPv4 mismatch – Windows 11 prefers IPv6 for discovery, but many home routers handle IPv4 better. The printer responds on IPv4, Windows waits for IPv6, times out.
- SSDP (Simple Service Discovery Protocol) blocked – Some firewalls or router settings block the UDP port 1900 that printers use to announce themselves.
- Stale printer driver cache – Windows remembers old printer connections and gets confused when the printer's IP changes.
The fix – step by step
Skip the "run the troubleshooter" nonsense. It rarely works. Do this instead:
Step 1: Force Windows to use IPv4 for printer discovery
Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your Wi-Fi or Ethernet adapter, select Properties. Uncheck Internet Protocol Version 6 (TCP/IPv6). Click OK. Reboot. This is the single most effective fix for Brother and HP printers. I know it sounds aggressive, but you don't lose anything – IPv6 is still used by your browser, just not for printer discovery.
Step 2: Enable network discovery and file sharing
Go to Control Panel > Network and Sharing Center > Advanced sharing settings. Under Private network profile, turn on Network discovery and File and printer sharing. Save changes. This opens the firewall ports for SSDP and NetBIOS.
Step 3: Add the printer by IP address (the nuclear option)
Open Settings > Bluetooth & devices > Printers & scanners. Click Add device. When Windows fails to find it, click The printer that I want isn't listed. Select Add a printer using an IP address or hostname. Choose TCP/IP Device from the dropdown. Enter the printer's IP (check it from the printer's display or print a network config page). Check Query the printer and automatically select the driver to use. Click Next. Windows will install it in about 10 seconds. This bypasses the discovery timeout entirely.
Step 4: Clear the printer driver cache (if still failing)
Open Services.msc (Windows + R, type services.msc). Stop the Print Spooler service. Then delete everything in C:\Windows\System32\spool\PRINTERS. Restart the Print Spooler. This wipes all stuck print jobs and corrupted driver info. Then repeat Step 3.
What to check if it still fails
- Router settings – Disable AP Isolation or Client Isolation in your router's Wi-Fi settings. This blocks devices from talking to each other. Common on TP-Link and Netgear routers.
- Static IP for the printer – Set a static IP in your router's DHCP reservation list. So the printer always gets the same IP. Then add the printer by that IP using Step 3.
- Windows firewall – Temporarily turn off Windows Defender Firewall to see if it's blocking discovery. If printing works with firewall off, add an exception for
UDP port 1900andTCP port 9100(for raw printing). - Old printer driver – Uninstall the printer from Printers & scanners, then download the latest driver from the manufacturer's site (not Windows Update). HP's Universal Print Driver works better than the HP Smart app.
I've fixed hundreds of printer timeouts this way. Start with Step 1 and Step 3 – those solve 90% of cases. If you're still stuck after 20 minutes, try a different USB cable or network switch. Sometimes the hardware just gives up.
Was this solution helpful?