Devices & Setup
Printer says offline but connected
Check printer status, IP address, queue state, and network path first — a printer can be on Wi-Fi yet appear offline from an old address or stuck queue.
Problem summary
A printer can be connected to Wi-Fi but still appear offline because the computer points at an old address or stuck queue.
Print or view the printer network report.
Printer control panel/app > Network report/status
The printer has a current local IP and shows the trusted SSID/Ethernet.
Stop before changing business printer, firewall, or router-wide settings.
Layer path
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.
Record the printer IP
Check: Use the printer screen or report to write down current IP, SSID, and MAC.
Expected result: You know where the printer actually is.
If not: If the printer has no IP, reconnect it to Wi-Fi/Ethernet first.
Reserve the address
Check: Find the printer in the router and create or confirm a DHCP reservation.
Expected result: The printer keeps a stable address.
If not: If not visible in the router, fix network join first.
Fix the Windows port
Check: Compare the Windows printer port with the reserved IP and update/re-add if needed.
Expected result: The computer targets the right printer.
If not: If the port already matches, inspect queue state.
Clear one queue
Check: Clear stuck jobs and make sure the printer is not paused or set offline.
Expected result: A fresh test page can enter the queue.
If not: If it sticks again, capture the exact error.
Test and document
Check: Print one simple page and record printer IP, driver/object name, and fixed computer.
Expected result: Printing works without duplicate printer clutter.
If not: If several computers still fail, repeat one at a time.
Decision tree
If: Printer report shows a different IP than the computer port.
Then: The PC is targeting the old address.
Action: Reserve the current printer IP and update the port.
If: Printer report and port match, but queue says offline.
Then: Queue state or Windows printer object is stale.
Action: Clear stuck jobs and toggle offline/paused state.
If: Other computers print normally.
Then: This computer's queue, port, or driver is suspect.
Action: Repair this PC only.
If: No computers can print and printer has no valid IP.
Then: Printer network join failed.
Action: Reconnect printer to trusted LAN before drivers.
If: Printer is managed by work or school.
Then: Policy may control ports and queues.
Action: Stop and contact support.
Safe stop: Stop before changing business printer, firewall, or router-wide settings.
Evidence table
| Symptom | Evidence to collect | Likely layer | Next action |
|---|---|---|---|
| Printer screen says connected, Windows says offline. | Printer IP report versus Windows port. | Stale printer port | Update port to reserved IP. |
| Jobs stuck in queue. | Windows queue shows paused/offline/old job. | Queue state | Clear one queue and restart printer/computer. |
| Only one computer fails. | Second computer or phone prints. | Computer-specific driver/port | Repair that printer object. |
| Stopped after router change. | Old subnet in printer port. | Router migration | Reserve new IP and update saved ports. |
Commands and settings paths
Printer network report
Printer control panel/app > Network report/status
Where: On the printer or vendor app.
Expected: The printer reports the expected SSID/Ethernet and current local IP.
Failure means: Wrong network or no IP makes local printing fail.
Safe next step: Reconnect printer and reserve its IP.
Printer port
Settings > Bluetooth & devices > Printers & scanners > Printer properties > Ports
Where: On Windows for the affected printer.
Expected: The selected port points to the printer's current reserved IP or correct printer object.
Failure means: Old ports keep jobs offline.
Safe next step: Update or recreate one printer object.
Print queue
Settings > Bluetooth & devices > Printers & scanners > Open print queue
Where: On the affected Windows PC.
Expected: The queue is not paused, offline, or blocked by an old job.
Failure means: Queue state can block printing after network recovery.
Safe next step: Clear only that queue and send one test page.
Hardware and platform boundary
Change only when
- Replace the printer only after IP, port, queue, driver, and second-device evidence show the printer cannot print reliably.
Evidence that matters
- Ethernet, clear status reports, supported drivers, and stable local network behavior matter.
Evidence that does not matter
- Cloud app online status or new printer marketing does not fix stale local ports.
Avoid
- Avoid installing duplicate printers repeatedly or disabling the firewall broadly.
Related tool/checklist
Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.
Device setup troubleshooterRelated problems
Last reviewed
2026-05-06 · Reviewed by HomeTechOps. Reviewed for offline-printer diagnosis using printer network reports, Windows ports, queue state, router reservations, and single-computer isolation.
Sources/assumptions
- Assumes a home Wi-Fi or Ethernet printer on a trusted LAN.
- Business print servers and managed devices may enforce different settings.
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.