Why a network printer keeps going offline in the office, and the four settings that fix it

A print queue on a Windows PC is a pointer. It points at a port, and the port points at the printer, either by address or, for a printer Windows added on its own, by a discovery protocol called WSD that finds the device by broadcasting for it. Both pointers can go stale without anything being wrong with the printer.

The address goes stale when the printer took it from DHCP and the lease expired or the router handed it to somebody else. The queue on every PC still points at the old address, so every PC reports the printer offline, and the printer sits there with a green light wondering where everyone went.

The discovery pointer goes stale when the printer goes to sleep. WSD relies on the printer answering broadcasts; a printer in deep sleep does not answer, Windows marks it offline, and it stays marked offline after the printer wakes, because Windows only rechecks when it feels like it.

The third cause hides under the first two: the printer was installed by whoever needed it that day, so there are thirty queues on thirty PCs, half by address and half by discovery, with four driver versions among them. Whichever cause hits, it hits a different set of PCs each time, which is why the problem never looks like one problem.

Give the printer a DHCP reservation on whatever hands out addresses, usually the firewall, the router, or a Windows Server. The reservation ties the address to the printer's hardware address, so it gets the same one every time it asks, for as long as the reservation exists.

A reservation is better than typing a static address into the printer's panel. A static address the DHCP server does not know about can be handed to somebody else, and then two devices argue over it; a reservation means one place knows every address and why.

If the printer has already been set static, either move it to a reservation or make sure the address sits outside the DHCP pool. Then check every queue points at that address, or better, at a name that resolves to it.

Open the printer's properties on a PC that keeps losing it and look at the Ports tab. If the ticked port is a WSD port, that queue is finding the printer by discovery, and it will keep losing it. Remove that queue and add the printer again by address: a Standard TCP/IP Port, protocol RAW on port 9100, or LPR if the device only speaks that.

One more box on that port: SNMP status. Windows polls the printer over SNMP to decide whether it is online, and if the printer's SNMP is switched off or uses a different community name, Windows decides it is offline even though it prints. Either match the community name or untick SNMP status on the port.

Doing this on thirty PCs is the wrong shape of work, which is what the next setting is for.

Put the queue on a print server, one queue and one driver per model, and let Group Policy or Intune hand it to the PCs. Every PC then points at the same queue, with the same driver at the same version, and a fix is made once.

Since the printing security changes of 2021, a user without admin rights often cannot install a printer driver on their own PC, which is why 'just add it again' produces a password prompt. A print server with packaged drivers, or Microsoft's Universal Print, which does away with both the server and the driver question, is how that prompt goes away without handing out admin rights.

If a print server is more than the office needs, the smaller version is still worth doing: one documented queue per PC, by address, with one driver version, and a note of which it is.

Most office printers have two or three sleep levels, and the deepest one switches off the network interface to save a few watts. A print job sent to a sleeping interface times out before the printer wakes. Lengthen the sleep timer or, in the printer's network settings, keep the interface awake in sleep; the setting is often called something like network standby or wake on LAN.

Wi-Fi printers have every one of these problems plus radio. If there is an Ethernet port within cable reach, use it.

On the switch side, check the port is not set to a power-saving mode that drops the link, and that the printer sits on the same VLAN as the print server, or that the route between them is allowed by the firewall.

Every reboot resets the discovery, wakes the interface, and renews the lease, so it does work. It also teaches the office that a reboot is the fix and stops anyone asking why, and each 'add printer' along the way leaves another queue behind, so the PC has a printer, a printer (Copy 1), and a printer (redirected 2), and nobody knows which one is real.

The tell that the problem is addressing rather than hardware is the pattern: it happens after weekends, after power cuts, or after the printer has sat idle, and it never happens to the PC whose queue was added by address.

The copier dealer owns the machine: firmware, toner, the fuser, the lease. The queue, the port, the driver, the reservation, the VLAN and the sleep setting are network work, and they are why the dealer's technician and the IT provider each say the fault is the other's. If you write to us about a printer, include the model, whether it is on a cable or on Wi-Fi, and what the Ports tab on one affected PC says: that answers most of it before anyone drives out.

Label printers on a warehouse floor fail in their own ways, mostly around the label language and the scanners feeding them; that story is in the case study on eight industrial label printers, and the queue and driver side of it is the printer, scanner, and peripheral work on our Enterprise IT services page.