[cups.general] Printing to a Windows Server fails

[Gerard Seibert]

On Mon, 12 Mar 2012 13:51:03 -0700
Michael Sweet articulated:

> On Mar 12, 2012, at 12:20 PM, William Moore wrote:
> 
> > Hello
> > 
> > I'm trying to send print jobs from CUPS to a print server on
> > Windows Server 2003 via http. This used to work with version 1.4.3
> > of CUPS, although I had to set the Error Policy for the printers to
> > abort-job, otherwise the jobs never finished.
> > 
> > Now I have had to upgrade to version 1.5.2 of CUPS and the
> > abort-job policy no longer works. All the printer jobs hang on
> > "Waiting for job to complete". I tried setting a Timeout value of
> > 30 in cupsd.conf, but that didn't make any difference.
> > 
> > Is there something else I can to set to make this work again, or do
> > I have to install an old version of CUPS? Installing an old version
> > of CUPS is my least preferred option.

> Enable debug logging (cupsctl --debug-logging), try printing, and
> then look at the messages coming from the backend.  My guess is that
> Windows' (very) limited IPP/1.0 support is to blame...

I wouldn't be so quick to blame Windows. For starters, the OP stated
that it did work under CUPS 1.4.3. Personally, I have had problems with
version 1.5.x of CUPS also. Printing that use to work just fine
suddenly stopped and no one can figure out why.

-- 
Gerard ✌
gerard at seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________