Devices & Setup

Printer not found on network

Recover a missing network printer without reinstalling everything first — it is usually offline, on the wrong Wi-Fi, at a changed IP, or behind a stale queue.

Problem summary

A missing printer is usually offline, on the wrong Wi-Fi, at a changed IP address, or blocked by a stale driver queue. If Windows already sees the printer but refuses jobs, use printer says offline but connected before reinstalling drivers.

Operator snapshotEvidence first

First proof

Print or view the printer network status page.

Screen to open

Printer control panel/app > Network status/report

Expected signal

The printer shows the expected SSID/Ethernet, IP address, and online state.

Stop boundary

Stop before changing router firewall or business-managed printer settings.

Layer path

1Printer discovery depends on printer network status, router lease, same trusted LAN, computer printer port, firewall profile, driver/app state, and queue health.

2Vendor cloud status is not the same as local print reachability.

3A direct IP test and printer network report are stronger evidence than browsing or automatic discovery.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Get the printer's real IP

Check: Use the printer screen or network report to record IP, SSID, and MAC.

Expected result: You know whether the printer joined the trusted LAN.

If not: If not, reconnect the printer before touching the computer.

Confirm router visibility

Check: Find the printer in the router client list and reserve its address.

Expected result: The printer has a stable local identity.

If not: If missing, check printer Wi-Fi, Ethernet, and guest network state.

Test from one computer by IP

Check: Add or update the printer using the reserved IP and send one test page.

Expected result: The page prints without relying on discovery browsing.

If not: If not, check network profile, firewall, and printer status.

Clean stale queue state

Check: Clear stuck jobs for only this printer and restart the printer once.

Expected result: The queue accepts a fresh simple job.

If not: If not, fix the driver or printer object on that computer.

Update the home note

Check: Record printer IP, MAC, admin page/app, and which computer was fixed.

Expected result: Future router changes can be repaired quickly.

If not: If multiple computers disagree, fix one at a time.

Decision tree

If: Printer has no valid local IP.

Then: The printer is not on the trusted LAN.

Action: Reconnect Wi-Fi/Ethernet and check router lease.

If: Printer has IP and direct IP printing works.

Then: Discovery or saved printer object is the weak layer.

Action: Reserve the IP and update/re-add the printer using that address.

If: Printer has IP but computer cannot reach it.

Then: Network profile, guest/VPN, firewall, or subnet mismatch is suspect.

Action: Check same network and Private profile before driver reinstalls.

If: One computer fails and others print.

Then: Computer queue, driver, or stale port is active.

Action: Update only that computer's printer object.

If: Printer is work-managed or on a business print server.

Then: Local changes may violate policy.

Action: Stop and contact the owner or support.

Safe stop: Stop before changing router firewall or business-managed printer settings.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Printer does not appear in add-printer flow.	Printer network report and router client list.	Discovery/network identity	Use direct IP and reserve address.
Printer app shows online but PC cannot print.	Cloud app status versus local IP reachability.	Local path	Test local IP printer path.
Only one PC cannot find it.	Other computer or phone prints successfully.	Computer queue/port/driver	Fix that PC's printer object.
Issue began after router change.	Old printer IP/port differs from current DHCP lease.	Stale port	Reserve current IP and update printer port.

Reference

Commands and settings paths

Printer network report

Printer control panel/app > Network status/report

Where: On the printer or vendor printer app.

Expected: The printer has the expected SSID/Ethernet and a valid local IP.

Failure means: No IP or wrong SSID means local discovery cannot work.

Safe next step: Reconnect printer to the trusted LAN.

Windows printer path

Settings > Bluetooth & devices > Printers & scanners > Add device / Printer properties > Ports

Where: On the Windows PC.

Expected: The printer port points to the current reserved IP or valid WSD path.

Failure means: Old ports keep sending jobs to the wrong address.

Safe next step: Update or re-add one printer object.

Network profile

Settings > Network & internet > active connection > Network profile type

Where: On the computer trying to print.

Expected: The trusted home LAN is Private, not guest or public.

Failure means: Public/guest profiles can block local discovery and sharing.

Safe next step: Switch only your trusted home LAN to Private if appropriate.

Hardware boundary

Hardware and platform boundary

Change only when

Replace a printer only after network report, router lease, direct-IP print, queue, and driver evidence show the printer cannot be made reliable.

Evidence that matters

Ethernet option, documented driver support, clear network status reports, and sane local printing matter.

Evidence that does not matter

Cloud-print branding does not fix stale local ports or guest-network isolation.

Avoid

Avoid duplicate printer installs, broad firewall disablement, and guest Wi-Fi placement for shared printers.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

Device setup troubleshooter

Last reviewed

2026-05-07 · Reviewed by HomeTechOps. Reviewed for printer discovery using network reports, router lease evidence, direct-IP paths, Windows printer ports, queue state, and Private-network boundaries.

Sources/assumptions

Assumes home network printers and consumer routers.
Printer admin steps vary by brand and model.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Microsoft Support: Fix printer connection and printing problems in WindowsUsed for printer status, queue, connection, and Windows printer troubleshooting order.Microsoft Support: Essential network settings in WindowsUsed for the Public vs Private network-profile decision before enabling sharing on a trusted home LAN.Microsoft Support: Fix network connection issues in WindowsUsed for Windows network baseline checks before changing router-wide settings.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

Why does my printer disappear after a router restart?

It may receive a new IP address. A router DHCP reservation usually makes discovery more stable. See printer network basics for why mDNS caching causes the offline-but-on symptom.

Should I reinstall the printer driver first?

Check Wi-Fi and IP address first. Reinstalling drivers will not help if the printer is on the wrong network.

Windows 11 24H2 / 25H2 removed my printer's vendor driver — how do I print now?

Windows 11 24H2 started removing legacy third-party print drivers in favor of the Microsoft IPP (Internet Printing Protocol) class driver. 25H2 expanded the removal. Most modern network printers (HP, Brother, Epson, Canon) work via Mopria/IPP without a vendor driver — but vendor-specific features (duplex defaults, color profiles, scan-to-folder) may be missing. Fix: add the printer as 'IPP Network Printer' (Settings > Bluetooth & devices > Printers & scanners > Add a printer). If a vendor feature is critical, install the vendor's Universal Print Driver (UPD) which still works in 24H2/25H2. Don't reinstall the legacy per-model driver — it'll be removed again on the next monthly update.

macOS Tahoe AirPrint compatibility — anything to watch for?

macOS Tahoe (26) tightened AirPrint discovery to require IPP Everywhere or AirPrint 2.0+. Older HP/Brother printers (pre-2018) that worked on Sequoia via legacy IPP may stop appearing in the Print dialog. The fix is usually a printer firmware update from the vendor's app — most still ship firmware updates for 7-10 year old models. If no firmware update is available, add the printer manually as 'IPP' rather than 'AirPrint' in System Settings > Printers & Scanners.