Discussion:
[Samba] [semi-ot] Printing w/ NT, automated driver download and modifying printer settings
Andreas K. Huettel
2003-12-01 18:38:04 UTC
Permalink
Greetings,

I've configured Samba for automated printer driver download by all Windows
clients. However, I run into the following problem with NT4/2000/XP
computers:

Every user can connect to any printer and install the driver. (OK.)

Only the printer admins can change hardware settings (f.ex. "Can it do
duplex?"). (semi-OK.)

BUT: Printer hardware settings are stored in the user profile. So, the
printer admins can set up their printer config properly, everyone else is
glued to the default settings (which are partly wrong). (NOT OK. BAD. :])

Do you know of any tips and tricks how to resolve this problem and similar
ones? Is there anything like a howto, or some documentation?

kind regards,
Andreas

- ---------------------------------------------------------------------
Dipl.-Phys. Andreas K. Huettel tel. +49 89 2180 3349 (univ.)
Sektion Physik der LMU fax +49 89 2180 2069 (univ.)
LS Prof. J.P. Kotthaus ***@lmu.de
Geschwister-Scholl-Platz 1 ***@akhuettel.de
80539 Muenchen ***@physik.uni-muenchen.de
Germany http://www.akhuettel.de/research/
- ---------------------------------------------------------------------
Please use GNUPG or PGP for signed and encrypted email. My public key
can be found at http://www.akhuettel.de/pgp_key.html
- ---------------------------------------------------------------------
Reason #135 why you can't find your system administrator: He joined a
cult practizing Windoze XP.
Chris Smith
2003-12-01 18:38:04 UTC
Permalink
On Tue, 2002-07-09 at 13:43, Andreas K. Huettel wrote:
> Every user can connect to any printer and install the driver. (OK.)

Same here.

> Only the printer admins can change hardware settings (f.ex. "Can it do
> duplex?"). (semi-OK.)

Same here.

> BUT: Printer hardware settings are stored in the user profile. So, the
> printer admins can set up their printer config properly, everyone else is
> glued to the default settings (which are partly wrong). (NOT OK. BAD. :])

Don't see that situation at all. When the driver is configured by the
printer admin it is instantly changed for all users on the domain.

Chris

--
'Nix MS - Just Say .NyET
Erlend Mjaavatten
2003-12-01 18:38:13 UTC
Permalink
> > BUT: Printer hardware settings are stored in the user profile. So, the
> > printer admins can set up their printer config properly, everyone else is
> > glued to the default settings (which are partly wrong). (NOT OK. BAD. :])
>
> Don't see that situation at all. When the driver is configured by the
> printer admin it is instantly changed for all users on the domain.


Through quite a lot of trial and error I found that both the version of
samba and the driver are factors in the success of printer driver settings
getting all the way to the client.

I realize that the following paragraph is a bit specific to my setup but
it's obviously the setup I know best.

Using samba 2.2.5 (with jerry's patch)

* Xerox Docucenter 230 (both PCL and PS)
Works perfectly, all settings are visible to all users.

* HP Laserjet 4050/4100 (PCL and PS)
The devicemode is not working correctly. I the settings (eg. duplex) is
correct in the properties sheet of the 'Printers' window both on the
local machine and on the server, but when you go to the print dialog
from an application all settings are gone.


Using samba 2.2.2

* All the above drivers are working perfectly.


Upgrading to samba 2.2.3 or any newer version breaks the functionality of the HP driver.


--
Erlend Mjaavatten - ***@stud.ntnu.no
There's no such thing as cutting corners in engineering.
Jesse Becker
2003-12-01 18:38:05 UTC
Permalink
Elsewhere on the list, Andreas K. Huettel wrote:
> I've configured Samba for automated printer driver download by all Windows
> clients. However, I run into the following problem with NT4/2000/XP
> computers:
>
> Every user can connect to any printer and install the driver. (OK.)

Ah...if only I could get that far along, I'd be a happy man. Could you
perhaps shed some light on how you got things to work?

I have a Samba server (2.2.5) that also runs CUPS. The printer is an HP
4550N printer connected via TCP (the printer has a JetDirect card
attached). I can print directly from the server ('lp file.ps' for
example). I can also print from remote clients--if I manually install
drivers for the printer first. Finally, I am able to 'upload' drivers to
the samba server.

The remote clients are currently just Windows 2000 boxes, and there will
be NT4.0 boxes later on

What I cannot do is twofold:

1) Automatically download drivers to clients. When I try to add the
printer, I get a pop-up box reading:

"The server on which the printer resides does not have the correct
printer driver installed. If you want to install the driver on
your local computer, click OK."

On clicking OK, you get the usual 'add printer wizard' dialogue box, and
if I choose, I can add the correct drivers.


2) There appear to be permission problems somewhere as well. After
uploading the drivers, I am unable choose one for the printer to actually
use. The drivers loaded on the server correctly appear in the 'Advanced'
tab of the printer properties window, but when I click 'OK' or 'Apply', a
dialogue box appears reading:
"Printer settings could not be saved. Access is denied."

I find this curious for a few reasons: I am logged in a Administrator on
the W2K box, The Admin. user is mapped to root on the Samba server, the
permissions are such that anyone can read the driver files on the Samba
server, and anyone can read the /var/cache/samba files as needed. Lastly
(and strangest), I *can* modify the options in the Security tab, and have
set full access to "Everyone" (print, manage jobs, and manage printers).

Snippits from smb.conf:
[global]
load printers = yes
printcap name = lpstat
printing = cups
printer admin = @wheel, @printers
addprinter command = cupsaddsmb

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = no
writable = no
printable = yes
create mode = 740
printing = cups

[print$]
comment = printer drivers
path = /etc/samba/drivers
browsable = yes
guest ok = no
read only = yes
write list = root, @wheel, @printers


Any suggestions or ideas that people may have would be more than welcome.
I've checked the mailing list for things along these lines, but none of
them seem to quite apply. :-/

Thanks,

--Jesse
sthom
2003-12-01 18:38:05 UTC
Permalink
Many of us could prattle on about how we got our printer drivers to download
to the clients automatically, but to head off a possible shortage of "bits",
I would direct you to the documentation where the issue is dealt with in
precise fashion.

Look for /samba-2.2.x/docs/htmldocs/printer_driver2.html on your box. I
suppose you could find that on the samba site as well, or better yet google
the filename.

Your issue is a permissions issue *imho*.

Go therefore and sin no more.

Cheers,
Steve
----- Original Message -----
From: "Jesse Becker" <***@fryed.net>
To: <***@samba.org>
Sent: Tuesday, July 09, 2002 6:52 PM
Subject: Automatic driver downloads (was: [Samba] [semi-ot] Printing w/ NT,
automated driver download and modifying printer settings)


>
> Elsewhere on the list, Andreas K. Huettel wrote:
> > I've configured Samba for automated printer driver download by all
Windows
> > clients. However, I run into the following problem with NT4/2000/XP
> > computers:
> >
> > Every user can connect to any printer and install the driver. (OK.)
>
> Ah...if only I could get that far along, I'd be a happy man. Could you
> perhaps shed some light on how you got things to work?
>
> I have a Samba server (2.2.5) that also runs CUPS. The printer is an HP
> 4550N printer connected via TCP (the printer has a JetDirect card
> attached). I can print directly from the server ('lp file.ps' for
> example). I can also print from remote clients--if I manually install
> drivers for the printer first. Finally, I am able to 'upload' drivers to
> the samba server.
>
> The remote clients are currently just Windows 2000 boxes, and there will
> be NT4.0 boxes later on
>
> What I cannot do is twofold:
>
> 1) Automatically download drivers to clients. When I try to add the
> printer, I get a pop-up box reading:
>
> "The server on which the printer resides does not have the correct
> printer driver installed. If you want to install the driver on
> your local computer, click OK."
>
> On clicking OK, you get the usual 'add printer wizard' dialogue box, and
> if I choose, I can add the correct drivers.
>
>
> 2) There appear to be permission problems somewhere as well. After
> uploading the drivers, I am unable choose one for the printer to actually
> use. The drivers loaded on the server correctly appear in the 'Advanced'
> tab of the printer properties window, but when I click 'OK' or 'Apply', a
> dialogue box appears reading:
> "Printer settings could not be saved. Access is denied."
>
> I find this curious for a few reasons: I am logged in a Administrator on
> the W2K box, The Admin. user is mapped to root on the Samba server, the
> permissions are such that anyone can read the driver files on the Samba
> server, and anyone can read the /var/cache/samba files as needed. Lastly
> (and strangest), I *can* modify the options in the Security tab, and have
> set full access to "Everyone" (print, manage jobs, and manage printers).
>
> Snippits from smb.conf:
> [global]
> load printers = yes
> printcap name = lpstat
> printing = cups
> printer admin = @wheel, @printers
> addprinter command = cupsaddsmb
>
> [printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = no
> guest ok = no
> writable = no
> printable = yes
> create mode = 740
> printing = cups
>
> [print$]
> comment = printer drivers
> path = /etc/samba/drivers
> browsable = yes
> guest ok = no
> read only = yes
> write list = root, @wheel, @printers
>
>
> Any suggestions or ideas that people may have would be more than welcome.
> I've checked the mailing list for things along these lines, but none of
> them seem to quite apply. :-/
>
> Thanks,
>
> --Jesse
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>
Gerald Carter
2003-12-01 18:38:08 UTC
Permalink
On Tue, 9 Jul 2002, Jesse Becker wrote:

> What I cannot do is twofold:
>
> 1) Automatically download drivers to clients. When I try to add the
> printer, I get a pop-up box reading:
>
> "The server on which the printer resides does not have the correct
> printer driver installed. If you want to install the driver on
> your local computer, click OK."
>
> On clicking OK, you get the usual 'add printer wizard' dialogue box, and
> if I choose, I can add the correct drivers.

Sounds like you did not read the HOWTO. It says to click "no" if you are
installing the drivers on the server.







cheers, jerry

---------------------------------------------------------------------
Hewlett-Packard http://www.hp.com
SAMBA Team http://www.samba.org
-- http://www.plainjoe.org
"Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2
--"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Jesse Becker
2003-12-01 18:38:08 UTC
Permalink
On Wed, 10 Jul 2002, Gerald Carter wrote:
> On Tue, 9 Jul 2002, Jesse Becker wrote:
>
> > What I cannot do is twofold:
> >
> > 1) Automatically download drivers to clients. When I try to add the
> > printer, I get a pop-up box reading:
> >
> > "The server on which the printer resides does not have the correct
> > printer driver installed. If you want to install the driver on
> > your local computer, click OK."
> >
> > On clicking OK, you get the usual 'add printer wizard' dialogue box, and
> > if I choose, I can add the correct drivers.
>
> Sounds like you did not read the HOWTO. It says to click "no" if you are
> installing the drivers on the server.

Actually, I did read the HOWTO, and that part specifically several times.
I've done it both ways, and the result is the same. The problem is *NOT*
adding the drivers to the server--that works correctly, and the samba
server sees and reports them correctly. Instead, I think the problem has
to do with downloading the drivers from the server to the client, and also
some strange permissions problem. I'm going to scrap the whole thing and
start from scratch later today

--Jesse
Jesse Becker
2003-12-01 18:38:12 UTC
Permalink
On Wed, 10 Jul 2002, Gerald Carter wrote:

> Sounds like you did not read the HOWTO. It says to click "no" if you are
> installing the drivers on the server.

Now that I have the box in front of me, perhaps I can explain what
happens. As a general rule, I always read HOWTOs, mailing lists and other
documentation before posting.


> On Tue, 9 Jul 2002, Jesse Becker wrote:
>
> > What I cannot do is twofold:
> >
> > 1) Automatically download drivers to clients. When I try to add the
> > printer, I get a pop-up box reading:
> >
> > "The server on which the printer resides does not have the correct
> > printer driver installed. If you want to install the driver on
> > your local computer, click OK."
> >
> > On clicking OK, you get the usual 'add printer wizard' dialogue box, and
> > if I choose, I can add the correct drivers.

I have already uploaded the drivers to the Samba server, and they have
been copied into \\$print\W32X86\* as appropriate. This was done by
choosing the "no" option from the dialogue box I mentioned above. As I
said, this appears to work correctly.

Now, when I try to install this printer for use on a computer--either the
same windows box used to upload the drivers, or a different one--the
problems start.

On the Windows box, using Either the "Add Printer" icon in the
Printers folder, or simply dragging the printer icon from the Samba
printers share, I get a message
"The server on which the printer resides does not have the correct
printer driver installed. If you want to install the driver on
your local computer, click OK."
Clicking "Cancel" stops the process completely, and clicking "OK" prompts
me for the driver location.

If I choose the "Properties" option for the printer icon located on the
Samba server share, I get this message:
"Device settings cannot be displayed. The driver for the
specified printer is not installed. Only spooler properties will
be displayed. Do you want to install the driver now?"
Clicking "No" displays just the spooler properties. Clicking "Yes" brings
up the "Add printer driver wizard", and prompts for a driver location.

In the spooler properties window, under the "Advanced" tab, I *ALREADY*
have the printer drivers listed. Remember, this is *after* uploading the
drivers to the server (or so I thought). When I try to select the driver
from the list, and hit "apply" I then get a small pop-up box reading:
"Printer settings could not be saved. Access is denied."
There is only an "OK" button.

Furthermore, if I choose the "Server Properties" context menu option from
the Printers share on the Samba server, the "Drivers" tab shows all the
drivers that I have installed.

So, I'm going to try again, but hopefully that clarifies the problem a
bit. :-/

--Jesse

P.S. I don't mean to come off sounding displeased--just frustrated. I'm
actually very happy with Samba. :)
Jesse Becker
2003-12-01 18:38:13 UTC
Permalink
In a display of terrible form, I'll reply to my own message with the
results of my second foray into the world of printer driver downloads.

The problem turned out to be both a Samba, CUPS, and PPD issue.

System refresher: Samba 2.2.5, HP4550N printer, and Win2K clients.

Step 1) Start with a (mostly) clean slate. I stopped Samba and
CUPS, moved /var/cache/samba to /var/cache/samba.old (just in in case),
and nuked /etc/samba/drivers/*. I kept my existing shares, [printers] and
[print$] settings.

Step 2) Reread, and followed, the printer_driver2.txt file. After
messing with permissions a bit, I got the drivers to correctly upload and
download to the Win2K clients. However, nothing would actually print with
those drivers.

Step 3) I tried using the HP postscript drivers (from lj598.exe on their
website), as well as ones from lj602.exe that support PCL5 and 6, as well
as postscript. After much trial and more error, I scrapped them all, and
used Adobe's generic Postscript printer driver. This was uploaded to the
samba server, and downloaded to the clients.

Step 4) Test the printers...and it works! <cheer> But only in black and
white <boo> (the 4550 is a color laserjet printer--very nice).

Step 5) Here, the problem turned out to be CUPS--I think. The .ppd file
that was being used by both CUPS, and that was being fed to the clients
simply didn't grok color (or I couldn't get it to, one of the two...). I
grabbed a new .ppd that was developed in part by HP from http://hp.sf.net,
and manually placed that on the server in place of the old .ppd files. I
also replaced the one CUPS was using as well (just to be safe). Restarted
everything, and nuked/redownloaded the drivers for the windows clients.

Step 6) Print. It works. I have several wonderful printouts of images
from http://www.irtc.org adorning my walls now. :-)

Thanks to people who emailed me.

--Jesse



On Wed, 10 Jul 2002, Jesse Becker wrote:

> On Wed, 10 Jul 2002, Gerald Carter wrote:
>
> > Sounds like you did not read the HOWTO. It says to click "no" if you are
> > installing the drivers on the server.
>
> Now that I have the box in front of me, perhaps I can explain what
> happens. As a general rule, I always read HOWTOs, mailing lists and other
> documentation before posting.
>
>
> > On Tue, 9 Jul 2002, Jesse Becker wrote:
> >
> > > What I cannot do is twofold:
> > >
> > > 1) Automatically download drivers to clients. When I try to add the
> > > printer, I get a pop-up box reading:
> > >
> > > "The server on which the printer resides does not have the correct
> > > printer driver installed. If you want to install the driver on
> > > your local computer, click OK."
> > >
> > > On clicking OK, you get the usual 'add printer wizard' dialogue box, and
> > > if I choose, I can add the correct drivers.
>
> I have already uploaded the drivers to the Samba server, and they have
> been copied into \\$print\W32X86\* as appropriate. This was done by
> choosing the "no" option from the dialogue box I mentioned above. As I
> said, this appears to work correctly.
>
> Now, when I try to install this printer for use on a computer--either the
> same windows box used to upload the drivers, or a different one--the
> problems start.
>
> On the Windows box, using Either the "Add Printer" icon in the
> Printers folder, or simply dragging the printer icon from the Samba
> printers share, I get a message
> "The server on which the printer resides does not have the correct
> printer driver installed. If you want to install the driver on
> your local computer, click OK."
> Clicking "Cancel" stops the process completely, and clicking "OK" prompts
> me for the driver location.
>
> If I choose the "Properties" option for the printer icon located on the
> Samba server share, I get this message:
> "Device settings cannot be displayed. The driver for the
> specified printer is not installed. Only spooler properties will
> be displayed. Do you want to install the driver now?"
> Clicking "No" displays just the spooler properties. Clicking "Yes" brings
> up the "Add printer driver wizard", and prompts for a driver location.
>
> In the spooler properties window, under the "Advanced" tab, I *ALREADY*
> have the printer drivers listed. Remember, this is *after* uploading the
> drivers to the server (or so I thought). When I try to select the driver
> from the list, and hit "apply" I then get a small pop-up box reading:
> "Printer settings could not be saved. Access is denied."
> There is only an "OK" button.
>
> Furthermore, if I choose the "Server Properties" context menu option from
> the Printers share on the Samba server, the "Drivers" tab shows all the
> drivers that I have installed.
>
> So, I'm going to try again, but hopefully that clarifies the problem a
> bit. :-/
>
> --Jesse
>
> P.S. I don't mean to come off sounding displeased--just frustrated. I'm
> actually very happy with Samba. :)
>
>
>
Sven Schwengel
2003-12-01 18:38:13 UTC
Permalink
Hello,

I think you?re steps are right. But you install the driver from the
wrong machine. I had the same problem. You must install the first driver
from a NT4.0 box.
After that you have a NT40 folder in your print$ share and you can add
also the drivers for w2k or xp.

Regards sven
-------------- next part --------------
HTML attachment scrubbed and removed
Chris Smith
2003-12-01 18:38:13 UTC
Permalink
On Thu, 2002-07-11 at 04:41, Erlend Mjaavatten wrote:
> Through quite a lot of trial and error I found that both the version of
> samba and the driver are factors in the success of printer driver settings
> getting all the way to the client.

Agreed, and even expanded to include whether or not the drivers work at
all! One client has a bunch of large Ricoh machines, needed PCL drivers
(DOS application that only sends PCL) and it wasn't until I loaded the
"point and print" type drivers that they could print at all via Samba.

Chris

--
'Nix MS - Just Say .NyET
Jesse Becker
2003-12-01 18:38:14 UTC
Permalink
On Thu, 11 Jul 2002, Sven Schwengel wrote:

> Hello,
> =20
> I think you=B4re steps are right. But you install the driver from the
> wrong machine. I had the same problem. You must install the first driver
> from a NT4.0 box.
> After that you have a NT40 folder in your print$ share and you can add
> also the drivers for w2k or xp.

Actually, I don't think that it matters. I managed to install drivers=20
both from a Win2K box, and also "by hand" via cupsaddsmb. This includes=20
both printer specific drivers from HP, and generic Adobe PS drivers as=20
well.

--Jesse
Sven Schwengel
2003-12-01 18:38:14 UTC
Permalink
In my case it works, but I don?t use cups. I tried to install the xp
driver for my kyocera fs600 several times from the xp box and it had not
work.
After I did the same procedure from a nt box, it still works. I had the
same problems with the pol editor and nt policies will only work after
add them from a nt box.

sven

-----Urspr?ngliche Nachricht-----
Von: samba-***@lists.samba.org [mailto:samba-***@lists.samba.org] Im
Auftrag von Jesse Becker
Gesendet: Donnerstag, 11. Juli 2002 17:08
An: ***@lists.samba.org
Betreff: Re: Automatic driver downloads (was: [Samba] [semi-ot] Printing
w/ NT, automated driver download and modifying printer settings)


On Thu, 11 Jul 2002, Sven Schwengel wrote:

> Hello,
>
> I think you?re steps are right. But you install the driver from the
> wrong machine. I had the same problem. You must install the first
> driver from a NT4.0 box. After that you have a NT40 folder in your
> print$ share and you can add also the drivers for w2k or xp.

Actually, I don't think that it matters. I managed to install drivers
both from a Win2K box, and also "by hand" via cupsaddsmb. This includes

both printer specific drivers from HP, and generic Adobe PS drivers as
well.

--Jesse


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