What you will achieve

Find and connect to a network printer when Windows reports it missing — checking discovery, spooler, and firewall without reinstalling drivers blindly.

1) Confirm the printer is reachable

On the printer or router admin page, note the printer IP address (e.g. 192.168.1.50).
Open Command Prompt and run: ping 192.168.1.50 (replace with actual IP).
If ping fails, fix network connectivity first — Wi‑Fi isolation, VLANs, or the printer sleeping can block access.

2) Restart the Print Spooler service

Admin PowerShell:

Stop-Service Spooler -Force
Remove-Item C:\Windows\System32\spool\PRINTERS\* -Force -ErrorAction SilentlyContinue
Start-Service Spooler

3) Add the printer manually

Open Settings → Bluetooth & devices → Printers & scanners → Add device.
If not listed, click Add manually → Add a printer using an IP address.
Enter the IP, leave port as Auto detect, install the correct driver (or Generic / MS Publisher Imagesetter for testing).

4) Enable network discovery and firewall rules

Control Panel → Network and Sharing Center → Change advanced sharing settings → turn on Network discovery and File and printer sharing for Private networks.
In wf.msc, confirm File and Printer Sharing (Echo Request – ICMPv4-In) is enabled on Private profile if you rely on ping.

5) Clear stuck print queue on server PC

On the PC sharing the printer, restart Spooler and check Print Management (printmanagement.msc) for offline status.

6) WSD vs TCP/IP port

Prefer Standard TCP/IP port with raw IP if WSD discovery fails across subnets.
Disable SNMP status if false offline reports appear during driver install wizard.

7) Print Spooler RPC errors

Event Viewer → Application log, source PrintService — Event 808 indicates spooler crash; check driver.
Enable SMB 1.0 only if legacy printer requires it — Windows Features → SMB 1.0/CIFS (security risk, isolate on VLAN).

8) mDNS and Bonjour on mixed networks

Some printers advertise via Bonjour — install Apple Bonjour Print Services or use IP direct if discovery fails across subnets.
Multicast must be allowed on Wi‑Fi — guest networks often block printer discovery.

Verification checklist

Print test page from Settings → Printers. Check printer web UI shows job received — isolates Windows spooler vs network path failures.

Reboot once after changes that affect services, drivers, or firmware.
Confirm the original problem is resolved under normal daily use, not only immediately after the fix.
Note date, Windows version (Settings → System → About), and what changed in your personal runbook for next time.