From owner-freebsd-questions@FreeBSD.ORG Wed Jan 28 07:12:06 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8220F1065672 for ; Wed, 28 Jan 2009 07:12:06 +0000 (UTC) (envelope-from northg@shaw.ca) Received: from idcmail-mo2no.shaw.ca (idcmail-mo2no.shaw.ca [64.59.134.9]) by mx1.freebsd.org (Postfix) with ESMTP id 5869F8FC18 for ; Wed, 28 Jan 2009 07:12:06 +0000 (UTC) (envelope-from northg@shaw.ca) Received: from pd7ml1no-ssvc.prod.shaw.ca ([10.0.153.161]) by pd6mo1no-svcs.prod.shaw.ca with ESMTP; 27 Jan 2009 23:44:07 -0700 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=0 a=yPt6q2rsAAAA:8 a=ZEcDIKJQI0IztKDZmFQA:9 a=xBMft_jEWcvdFtT4zcQA:7 a=9MK5CNq_4ST5BvHTA0Xt0wiacVQA:4 a=nnAykRNK7500gLCkwmIA:9 a=akWsfVn36sKEcTrsxyUA:7 a=zE0iXpT6dYDF9lS140OzIlLCZr4A:4 a=-5zMTHQtpVcA:10 a=pEYuAFZ7GsoA:10 Received: from s0106000f3d63c5a5.vc.shawcable.net (HELO [10.54.6.21]) ([24.84.182.173]) by pd7ml1no-dmz.prod.shaw.ca with ESMTP; 27 Jan 2009 23:44:07 -0700 Message-ID: <497FFEB7.3000205@shaw.ca> Date: Tue, 27 Jan 2009 22:44:07 -0800 From: Graham North User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: cups raw printing - client print queue sticking X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 07:12:06 -0000 I have cups set up on a FreeBSD server to receive raw queues from windows clients on my home network. It is being used indepently of Samba. Access is invoked directly with http - http://xx.yy.zz.ww:631/printers/lex312raw . The printer is an elderly Lexmark 312L. The printer prints fine from 3 different WinXP clients - except the windows print queue does not clear properly. Basically, I set up the printer via the cups gui interface and all works well but the windows print manager queue sticks. The queue permanently shows status of "processing" . Interestingly, I can print multiple print jobs and only one job remains permanently stuck. Which could/may mean that each new job clears the "processing" status of the last job..?? Each subsequent job prints fine, test pages, images, files all seem to work but the Windows print manager doesn't clear. Seems like a final handshake going wrong..? Could this be a client side setting? Thanks for any advice out there. Graham/ -- Graham North Vancouver BC Canada www.soleado.ca Kindness is infectous, try it.