Why The Printer Is Offline And The Cable Is Fine

The printer is powered, connected and displaying a cheerful ready message. The computer insists it is offline. Both statements are accurate from where each device is standing.

The computer is looking for an address that moved

Most home and small office printers receive their network address automatically from the router, on a lease that expires and is renewed periodically.

If the printer is off when a lease expires, it can come back with a different address, while the print queue on the computer still holds the old one.

Nothing announces the change. The queue sends its request to an address where nothing answers, waits, and reports the printer as unavailable.

Discovery does not cross network boundaries

Printers advertise themselves using protocols that broadcast across the local network, and those broadcasts stop at the edge of the network segment.

A laptop on a guest network, a separate frequency band with isolation enabled, or a mesh node configured as a distinct segment will simply never hear the announcement.

The printer is a few metres away and, as far as the protocol is concerned, on a different network entirely. Distance has nothing to do with it.

Offline is a guess, not a report

The status shown is derived from whether a periodic query received a reply within a short window, not from any message the printer sent.

A busy printer, a slow wireless link or a device that has dropped into low-power mode will miss that window while being entirely functional.

Once the state is set, many systems are slow to clear it, so a printer that recovered a minute ago continues to be described as offline until something forces a recheck.

Sleep makes a working printer unreachable

Printers spend most of their lives idle and are pushed hard on energy consumption, so they sleep deeply and wake on network activity.

Waking takes seconds, which is longer than the status query is prepared to wait, so the first attempt after a quiet period frequently fails and the second succeeds.

This produces the familiar pattern where printing twice works, and it is why the folk remedy of sending the job again is genuinely effective.

The queue remembers failures that have passed

Print subsystems keep state about past errors, and a job that failed for a transient reason can leave the queue paused with nothing indicating why.

Duplicate queues accumulate over time, created by installers and by the operating system's own discovery, and only one of them may point at the right address.

Deleting the printer and adding it back works so reliably because it discards all of that accumulated state, which is a confession about how the state is managed.