samba - Mar 2003 - Possible Bug?? (was: Win95 & Win98 - NOT WORKING - NT ,2000, XP are ok)

Thanks for the suggestion Andrew, I was hopeful,
but removing the writeable made no difference.
Still prints from NT, 2000, XP  but not from Win95, 98.

Any other ideas?

-peter.





Andrew Bartlett <abartlet@samba.org> on 19/03/2003 07:05:29 PM
On Wed, 2003-03-19 at 18:02, peter.a.bryant@mainroads.qld.gov.au
wrote:
>
>
> Please lend me some expertise...
Sure!  See below:
> RE: [Samba] Win95 & Win98 - NOT WORKING - NT,2000, XP are ok (re
>
>  Printing is working fine for our Windows NT, 2000 and XP clients.
>  However, with windows 95 & 98, the print job gets put into the Samba
>  spool directory (path = /var/spool/lp/tmp/samba)  but doesn't make it
> to the printer.
>  The print files stay there in the directory - don't get removed.
I think Samba is treating this like a file-share for non-NT
(non-spoolss) printing.
>  [global]
>    printing = sysv
>
>   lprm command = /usr/bin/cancel %p-%j
>   lppause command = lp -i %p-%j -H hold
>   lpresume command = lp -i %p-%j -H resume
>   load printers = no
>
>  [hp8100DN1]
>   printer = hp8100dn_1
>  comment = HP LaserJet hp8100 DN
>  path = /var/spool/lp/tmp/samba
>  guest account = nobody
>  guest ok = yes
>  browseable = yes
>  printable = yes
>  writable = yes
Well, I'll start by saying that this last statement will probably just
confuse things - it might turn it back into a disk share.

Andrew Bartlett






************************************************************
Opinions contained in this e-mail do not necessarily reflect
the opinions of the Queensland Department of Main Roads,
Queensland Transport or National Transport Secretariat, or
endorsed organisations utilising the same infrastructure.
If you have received this electronic mail message in error,
please immediately notify the sender and delete the message
from your computer.
************************************************************

Thanks for the suggestion Raj.
I might try using an old backup copy of the conf file.
Don't know why this would work, but worth a shot anyway hey?
:-)
-peter.





"Raj Saxena" <rajan@ipisland.com> on 19/03/2003 07:20:09 PM

Hi,

I am not running it that way but one thing you can do is probably print
directly to your printer server? Do you have a jetdirect card in your
printer? It is a work around but this way you can have the 95/98 print jobs
get by till this is resolved.

I have noticed on two occasions where i have some really weird things
happening all to find out i had a corrupted smb.conf file. Go figure that
one but i used a back copy just to see if that would cure my problem and it
worked.

Hope this helps a bit.

Raj

-----Original Message-----
From: samba-bounces+rajan=ipisland.com@lists.samba.org

Please lend me some expertise...

Ok, I know suggesting a bug is a bit impolite, but I cannot find a solution
for
this and
none of the helpful people who have responded have been able to help
either...
If I come off sounding a bit short it's just because I've tried many
things
to
get these
older clients printing.  :-)  Don't mean to annoy anyone.  Appreciate any
help!

Have several pressing reasons to upgrade to newest Samba (including latest
security fix)
but cannot do this if it means the Win9x clients can't print.

The important point here is that everyone is printing fine on old Samba
server.
Have replicated permissions and conf file is pretty much the same for the
new
Samba server.
It isn't a permissions thing because the Win9x clients are successfully
sending
the print job
to the spool directory.  Then the print job is getting stuck there.
The job being stuck in the spool directory doesn't stop others from printing
though. (Other NT, 2000, XP clients that is)

Obviously most people are able to print from Win9x .
Just wondering if maybe this is a Solaris + HP printers thing??
Thought maybe it was a printer driver issue, But it is printing okay from
the
old Samba
so surely this is not the problem?

Any ideas?  Can anyone replicate my problem?  Is anyone else using Solaris +
HP
+ Samba 2.2.7a  ?

thanks & sorry

-peter.

RE: [Samba] Win95 & Win98 - NOT WORKING - NT,2000, XP are ok (re

 Printing is working fine for our Windows NT, 2000 and XP clients.
 However, with windows 95 & 98, the print job gets put into the Samba
 spool directory (path = /var/spool/lp/tmp/samba)  but doesn't make it
to the printer.
 The print files stay there in the directory - don't get removed.

 Samba version is 2.2.7a,  on Solaris 8
 Printers are HP printers - e.g. HP 8100dn

 All clients including 95/98 were happily printing on a very much older
version of Samba (2.0.6)
 network setup is a peer to peer network.

 printing directly from Unix to the printer is working ok


 (p.s. Just for a wild stab in the dark I tried setting the
"disable spoolss =   yes"
 but this stopped all printing from making it to the computer - even
from the  clients that  were originally working.)


 relevant bits of conf. file included below...
 note that I don't have print command explicitly stated, but testparm
 indicates that it is configured properly...

 [global]
   printing = sysv

  lprm command = /usr/bin/cancel %p-%j
  lppause command = lp -i %p-%j -H hold
  lpresume command = lp -i %p-%j -H resume
  load printers = no

 [hp8100DN1]
  printer = hp8100dn_1
 comment = HP LaserJet hp8100 DN
 path = /var/spool/lp/tmp/samba
 guest account = nobody
 guest ok = yes
 browseable = yes
 printable = yes
 writable = yes




************************************************************
Opinions contained in this e-mail do not necessarily reflect
the opinions of the Queensland Department of Main Roads,
Queensland Transport or National Transport Secretariat, or
endorsed organisations utilising the same infrastructure.
If you have received this electronic mail message in error,
please immediately notify the sender and delete the message
from your computer.
************************************************************

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.462 / Virus Database: 261 - Release Date: 3/13/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.462 / Virus Database: 261 - Release Date: 3/13/2003