On Fri, Nov 22, 2024 at 1:27 PM D. R. Evans <doc.ev...@gmail.com> wrote:
>
> D. R. Evans wrote on 11/19/24 09:38:
> > I have recently added a Xerox C325 multifunction printer to my home LAN.
> >
> > When I originally plugged it in and ran some quick print tests from my
> > Debian
> > stable system, everything seemed to be fine. But now, a few days later, I
> > can
> > no longer persuade it to print :-(
> >
> > The printer appears OK in CUPS. As of right now, the status page at the CUPs
> > port, http://127.0.0.1:631, says that the printer is: (Paused, Accepting
> > Jobs,
> > Not Shared), and there are two jobs visible in the printer's queue.
> >
> > If I go to Maintenance and click "Resume", CUPS says "Printer
> > Xerox_R_C325_Color_MFP has been resumed". But neither of the queued pages is
> > printed, and after a few seconds, the page goes back to saying: (Paused,
> > Accepting Jobs, Not Shared).
> >
> > If I cancel the two queued jobs, and then do:
> > Maintenance | Resume
> > the printer state becomes:
> > (Idle, Accepting Jobs, Not Shared)
> >
> > But as soon as I send a job to print (for example: Maintenance | Print Test
> > Page), the job appears on the queue and the status becomes (Paused,
> > Accepting
> > Jobs, Not Shared).
> >
> > So it seems that what appears to be happening is that as soon as a job is
> > sent
> > to the printer, it enters the Paused state, and the job never actually
> > prints.
> >
> > Any advice gratefully received.
>
> Fortunately, I had another (older) Xerox printer that has always worked
> correctly. So I carefully compared the configuration of the two printers, and
> saw that the old one is configured with an explicit IP address and was reached
> via socket://ip-address:9100, whereas the new one had something like (I forget
> the exact string) implicitclass://printer-name. I manually changed the new one
> so that it had the same format as the old one, and, rather to my surprise,
> suddenly it seems that the new printer now works correctly. [I couldn't find
> where to make this change via the usual CUPS web interface, so I used my
> desktop environment control centre, which provided a way to edit the device
> connection information.]
I think you should setup your printer's network protocols for lpr and
ipp{s}. Disable all the other crap, like Bonjour, Windows printing and
9100 printing.
Then, send print jobs to the printer using ipp{s}. IPP is the way of
the future. In fact, Microsoft is removing lpr support in Windows, and
now uses ipp. See
<https://en.wikipedia.org/wiki/Internet_Printing_Protocol>.
You do not need a static IP address. The only machine on your network
that requires a static IP address is your DNS server(s). You do need
to know the printer's name, however.
See <https://ibb.co/X8f0J5k> and <https://ibb.co/b5cfVkT>. It really
is that simple.
> To my simple mind that suggests that some auto-configuration magic that is
> supposed to happen when the new printer was plugged into the network was not
> handled correctly by debian stable.
>
> The fact that the printer seems to be accessible from Macs without any manual
> intervention on the Macs strongly hints that the issue lies with debian. It is
> a brand-new model printer (Xerox C325), and at this point the base code for
> debian stable is something like 18 months old (although I do keep it up to
> date), so possibly it's just a matter that the printer is too new for the OS,
> and the problem won't exist when the next release of debian comes along.
Apple is using Bonjour a/k/a mDNS. If you are running DNS locally, you
don't need Bonjour. DNS is the source of truth on your network, not
Bounjour. In fact, I removed Bounjour and mDNS packages from all my
Linux machines because DNS is the source of truth on my network.
Jeff
