[Samba] Win2K sp4 can't print

[Bob Crandell]

Ok, thanks, I will.

These were brand spanking new, fresh out of the box, never touched by human hands
(sort of), computers.

Thanks

Van Sickler, Jim (vansickj-eodc at kaman.com) wrote:
>
>You can blame SP4 if you want too;  I won't mind.
>
>Weren't those PCs printing ok prior to the
>upgrade to SP4?
>
>Honestly,  I've only had one of about
>1/2 dozen PCs that I've put SP4 on show any
>oddities aftewards.  And the one PC was flaky
>prior to the SP install.
>
>The SP4 folks here that are using Solidworks 2003
>have noticed their systems are much more stable,
>and what used to be BSODs are now CTDs (Crash
>To Desktops) instead.  Solidworks crashing
>now only kills itself, instead of the whole
>system...
>
>Jim
>
>> -----Original Message-----
>> From: Bob Crandell [mailto:bob at assuredcomp.com]
>> Sent: Thursday, July 24, 2003 10:06 AM
>> To: Samba List
>> Subject: RE: [Samba] Win2K sp4 can't print
>>
>>
>> Van,
>>
>> I think part of it was my fault.  I went back and looked at
>> some of the other NT4,
>> XP and Win2K that were working fine and found out that they
>> were all setup as local
>> printers, that is, captured LPT ports.  I don't think I can
>> blame sp4.  I wish I
>> couldn't blame me.
>>
>> Thanks
>>
>>
>> Van Sickler, Jim (vansickj-eodc at kaman.com) wrote:
>> >
>> >Bob,
>> >
>> >  I've upgraded several systems here to SP4,
>> >and haven't run into any of these errors (yet!).
>> >
>> >However...
>> >
>> >  Spoolss was updated in SP4;  I'd try deleting
>> >the printers & their ports on the SP4 PCs, then
>> >adding them again.  If you toggled or added the
>> >"disable spoolss = yes" setting, or upgraded
>> >to 2.2.8a after the ports on the win2k PCs
>> >were created, it may cause the "Access Denied" error.
>> >
>> >  Are you setting the printers up as Network or
>> >Local on the PCs?  It makes a difference.  Local gave
>> >me fewer problems.  Use  \\server\printshare as the
>> >port name.
>> >
>> >  The lpc commands don't look quite right -
>> >mine are from lprng, but the syntax is pretty
>> >much the same:
>> >
>> >        lpq command = /usr/local/bin/lpstat %p
>> >        lprm command = /usr/local/bin/lprm -P%p %j
>> >        lppause command = /usr/local/sbin/lpc hold %p %j
>> >        lpresume command = /usr/local/sbin/lpc release %p %j
>> >        queuepause command = /usr/local/sbin/lpc stop %p
>> >        queueresume command = /usr/local/sbin/lpc start %p
>> >
>> >  To be honest, I've pretty much given up on printing in
>> >Samba 2.x, and gone over to Standard TCP/IP Ports, printing
>> >to the lprng daemon on the Samba server.  I posted a whole
>> >bunch of times trying to get a way to enumerate the correct
>> >print job info on the clients, instead of the smbprn.xxx.xxx
>> >that is usually available.  I never got a solution...
>> >
>> >  Printing through lprng has given me two big benefits:
>> >my Lanier 2138 no longer goes off into la-la land
>> >(don't get me started on Ricoh's COMPLETELY CRAPPY job
>> >of de-bugging their firmware), and the correct info is displayed
>> >for the printer queues.
>> >
>> >Hope this helps,
>> >Jim
>> >
>>
>> --
>> Bob Crandell
>> Assured Computing
>> When you need to be sure.
>> bob at assuredcomp.com
>> www.assuredcomp.com
>> Voice - 541-689-9159
>> FAX - 541-463-1627
>> Eugene, Oregon
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  http://lists.samba.org/mailman/listinfo/samba
>>
>

--
Bob Crandell
Assured Computing
When you need to be sure.
bob at assuredcomp.com
www.assuredcomp.com
Voice - 541-689-9159
FAX - 541-463-1627
Eugene, Oregon