Printer Offline - Quick Fix Stops Working on Windows 10/11

Quick Answer

If your printer's offline and you're in a hurry: open Command Prompt as admin, type net stop spooler, then ipconfig /flushdns, then net start spooler. Reboot the printer. That's it.

Why This Happens

Your printer's not really offline — it's Windows losing track of it. The print spooler crashes or gets stuck processing a bad job (usually a PDF that's too large or a corrupted driver). Meanwhile, DNS entries for network printers get stale, especially on networks with DHCP that reassigns IPs. I've seen this with HP LaserJet Pro M404dn and Brother HL-L2350DW printers — fine for weeks, then suddenly 'offline' after a power outage or a Windows update. The OS tries to resolve the printer's hostname but gets a cached IP that no longer works, or the spooler's stuck on a job that won't cancel.

Step-by-Step Fix

1. Restart the Print Spooler — Press Win+R, type services.msc, find 'Print Spooler', right-click and select Restart. If it's stuck, open Task Manager, kill the spoolsv.exe process, then start the service again.
2. Flush DNS Cache — Open Command Prompt as admin. Run ipconfig /flushdns. This clears any cached IP addresses. Then run ipconfig /registerdns to force the printer to re-register its name.
3. Check Printer's IP — Print a config page from the printer's menu (usually under Network or Setup). Compare it to what Windows shows. In Control Panel > Devices and Printers, right-click the printer, select Printer Properties, go to Ports tab, check the port — if it's a Standard TCP/IP port, note the IP address. If it's wrong, add a new port with the correct IP.
4. Reset the Printer — Power off the printer, wait 30 seconds, power back on. Do this AFTER steps 1-3.
5. Clear the Print Queue — In Services, stop the spooler. Go to C:\Windows\System32\spool\PRINTERS and delete everything in that folder. Start the spooler again. This gets rid of stuck jobs.

If That Didn't Work

Sometimes the spooler fix doesn't stick because of SNMP settings or power management. Try these:

• Disable SNMP Status Monitoring — In Printer Properties > Ports > Configure Port, uncheck 'SNMP Status Enabled'. Windows polls the printer using SNMP, and if the printer doesn't respond correctly (older firmware, or a switch blocking SNMP), Windows flags it offline. I've seen this with Kyocera printers on networks with VLANs.
• Disable Power Saving on the Printer's Network Card — Access the printer's web interface (type its IP in a browser), go to Network Settings > Power Saving, and disable any 'Deep Sleep' or 'Energy Saving' mode. Some printers drop their network connection after 15 minutes of inactivity to save power, and Windows doesn't wake them properly.
• Update the Printer Driver — Go to the manufacturer's site, download the latest driver (not the one from Windows Update). Uninstall the printer, reboot, install the new driver, add the printer back by IP address.
• Add a WSD Port — If TCP/IP ports keep failing, try WSD (Web Services for Devices). In Devices and Printers, 'Add a printer' > 'The printer I want isn't listed' > 'Add a Bluetooth, wireless or network discoverable printer'. If it appears, use that — it avoids IP changes.

Preventing This from Happening Again

Three things: give the printer a static IP via DHCP reservation (set it in your router's admin panel, not on the printer itself — keeps things consistent). Weekly, restart the print spooler using a scheduled task (trigger it at 3 AM on Sundays). And disable SNMP monitoring for the printer's port after you've set it up. That combo stops 95% of offline errors. Also, avoid using USB-connected printers on shared networks — they cause more problems than they solve.

Had a client last month whose entire print queue died because of a DNS change after their ISP swapped their public IP. The printer's IP was 192.168.1.100 but the DNS record pointed to 192.168.1.50. Flushing DNS fixed it, but it kept happening until I set the DHCP reservation. Now it's been solid for 6 months.