samba - Apr 2001 - 2.2.0 printing

After installing 2.2.0 I've discovered clients other than WinNT or Win2K
can't print; their jobs go to the spool area I've defined but never get
printed. In an attempt to fix this I discovered my Win2K client couldn't
run the add printer wizard, which led me to a readme that told me to add
a printers directory and a print$ share to smb.conf. This led to adding
two entries to my smb.conf, "admin users" and "printer
admin". I'm
feeling like I'm now pulled down the drain to my chin; nothing is
installing the way the many and contradictory files claim and
ultimately, my Windows 9x users not only can't print, but they don't get
to download files from the samba server.  Me and my users just want to
print like we did with 2.0.7. I don't want to have to do any gpg this or
that(Imprints), I don't care about my users downloading printer drivers
from a samba share or any of the seemingly "new" features of printing
in
2.2.0.

I hate to sound like this, but what in the world is the thinking here by
the samba team? Have several key members gone off on their own and
decided to torpedo this aspect of what used to be the best of the best?
Or have I simply read one too many of the published readme's that's
out-of-date, that directs me to do something that can't be done in
whole, only part? If there is anybody out there that is actually using
this release and not having their users hunt them down I'd love to hear
from them and fix whatever it is that's broken on this end.

Bob Rohde
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rrohde.vcf
Type: text/x-vcard
Size: 302 bytes
Desc: Card for Bob Rohde
Url :
http://lists.samba.org/archive/samba/attachments/20010424/12e2a8ee/rrohde.vcf

I've got the same problem so I you guys could also mail me the solution...
GREAT!!

-----Original Message-----
From: Bob Rohde [mailto:rrohde@wfubmc.edu]
Sent: Tuesday, April 24, 2001 5:29 PM
To: samba@lists.samba.org
Subject: 2.2.0 printing


After installing 2.2.0 I've discovered clients other than WinNT or Win2K
can't print; their jobs go to the spool area I've defined but never get
printed. In an attempt to fix this I discovered my Win2K client couldn't
run the add printer wizard, which led me to a readme that told me to add
a printers directory and a print$ share to smb.conf. This led to adding
two entries to my smb.conf, "admin users" and "printer
admin". I'm
feeling like I'm now pulled down the drain to my chin; nothing is
installing the way the many and contradictory files claim and
ultimately, my Windows 9x users not only can't print, but they don't get
to download files from the samba server.  Me and my users just want to
print like we did with 2.0.7. I don't want to have to do any gpg this or
that(Imprints), I don't care about my users downloading printer drivers
from a samba share or any of the seemingly "new" features of printing
in
2.2.0.

I hate to sound like this, but what in the world is the thinking here by
the samba team? Have several key members gone off on their own and
decided to torpedo this aspect of what used to be the best of the best?
Or have I simply read one too many of the published readme's that's
out-of-date, that directs me to do something that can't be done in
whole, only part? If there is anybody out there that is actually using
this release and not having their users hunt them down I'd love to hear
from them and fix whatever it is that's broken on this end.

Bob Rohde
-------------- next part --------------
HTML attachment scrubbed and removed