Network printer diagnostics from the command line
This ties together the whole section — a sequence combining ping and PowerShell that shows whether a printer problem is on the network, the driver, or in the print queue itself. None of it requires administrator rights.
The diagnostic sequence
ping [printer's IP address] — check it's reachable
No reply means a network problem — check the printer's WiFi and IP address (see the separate article in this section). A reply means the problem is further along, on the Windows side.
Get-Printer — check status in Windows (PowerShell)
Open PowerShell (press Windows, type "PowerShell") and run Get-Printer. You'll get a list of every installed printer along with its status — you can immediately see whether a given printer is marked offline, has an error, or is working normally. Doesn't require administrator rights.
Get-PrintJob -PrinterName "name" — check the print queue
Using the exact printer name from the previous command, you'll see the list of queued jobs and each one's status — this tells you whether a document even reached the queue, and at what stage it got stuck.
The printer's web panel — check its internal state
Type the printer's IP address into a browser. The web panel shows information invisible from Windows: actual ink levels, hardware error messages, and a history of recent print jobs, straight from the device's own perspective.
How to read the whole sequence
- Ping doesn't reply — a network problem; check the printer's WiFi connection.
- Ping works, Get-Printer shows an error or offline — a Windows configuration problem; try removing and re-adding the printer.
- Get-Printer shows a normal status, but Get-PrintJob shows a stuck job — see the article on clearing the print queue.
- Everything looks fine in Windows, but the printer's web panel shows a hardware error — that's a physical device problem, not a configuration one.
Couldn't fix it yourself?
Report the issue — it goes straight into our ticketing system, and our AI assistant assesses priority right away.