[cups.general] Jobs going to Stopped - Cups Restart the Only Resort

[gene heskett]

On Thursday, November 04, 2010 05:07:23 pm Anurag Chourasia did opine:

> Hi Mike,
> 
> Both the printer and the machines have the same subnet mask i.e.
> 255.255.255.0

If you have the devices on different 10.xx.subnets, AIUI, you are forcing 
the first 3 triplets to match.  I may be wrong, but that raises flags to me 
as historically, the 255.255.255.0 has always indicated that miss-matches 
in the first 3 triplets are a full miss, and to be ignored.

From the addresses quoted below that would be 255.0.0.0, which would open 
up a security hole.

Or is my ancient wet ram in error?  Heck, I don't even know which man page 
would be authoritative.

> Please note that both the working and non-working machine are on same
> network.
> 
I assume you are referring to the same switch when you say network.

> However, I have seen this problem with two physical printers now.
> Printer model is Zebra ZM400 and both are using D-Link Network Server.
> 
> Is there anything else I could try to get to the bottom of this issue?
> 
> Regards,
> Anurag
> 
> On Fri, Nov 5, 2010 at 1:55 AM, Michael Sweet <msweet at apple.com> wrote:
> > On Nov 4, 2010, at 11:34 AM, Anurag Chourasia wrote:
> > 
> > HI Mike,
> > 
> > We have tried using Socket Protocol again for printing but the problem
> > persists. Out of 100 Label print requests, only a few actually come
> > out of the printer while the others are shown as completed
> > successfully but nothing comes out of the printer.
> > 
> > I have also captured the logs using tcpdump for this scenario.
> > 
> > The log in http://paste.org/pastebin/view/22779 is when the print
> > command was sent to the printer but nothing came out of the printer
> > (Even though the JOB Was set to successful Status).
> > 
> > The log in http://paste.org/pastebin/view/22780 is when the print
> > command was sent to the printer and a label came out of the printer
> > well printed.
> > 
> > The IP of the printer is 10.15.98.14
> > 
> > The IP of the machine from where the command was sent is 10.0.157.86
> > 
> > 
> > Do the printer and machine have the same netmask defined?
> > 
> > How about the default router?
> > 
> > ...
> > 
> > I am not sure how to interpret this. From another Linux machine in the
> > network, I am able to print successfully to this same physical printer
> > using socket protocol.
> > 
> > 
> > Is the other machine on the same network segment as the non-working
> > one?
> > 
> > My suspicion is that you either have a configuration problem or have a
> > bad network card, port, or cable causing the one machine not to work
> > with this printer.
> > 
> >  _____________________________________________________________________
> >  ___
> > 
> > Michael Sweet, Senior Printing System Engineer, PWG Chair
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > cups mailing list
> > cups at easysw.com
> > http://lists.easysw.com/mailman/listinfo/cups


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Halley's Comet: It came, we saw, we drank.