CUPS Network Printing

I wanted Ubuntu to send jobs to an HP DeskJet over the network using IPP and to confirm that the printer produced a physical page.

When lpstat returned command not found, the shell identified cups-client as the missing package. I worked through the CUPS setup and checked the scheduler, which reported that it was running.

I added the HP DeskJet with lpadmin using its network IPP destination and the everywhere model. The recorded queue status showed that the printer was idle and enabled.

I confirmed a successful physical test print. That final check went beyond seeing a queue in the configuration or receiving a healthy scheduler status.

I configured Ubuntu to print to an HP DeskJet over network IPP and confirmed a successful physical print; shared-client printing was not demonstrated.

The October 3–4 session preserves the printer-add command and scheduler and queue status. I confirmed that the print worked, but the original test-job command was not retained.

The package sequence and sample print job in the source are reconstructions. This is network printing from Ubuntu, not evidence of a shared CUPS print server serving other computers.

I practiced separating missing client utilities, service state, and printer queue configuration while troubleshooting.

I learned to use the physical print as the end-to-end result rather than equating an enabled queue with successful output.