[Samba] cupsaddsmb - why the heck can't I get rpcclient-addprinter to work?

[Kurt Pfeifle]

> [Samba] cupsaddsmb - why the heck can't I get rpcclient-addprinter to work?
> Brian Johnson bjohnson at jecinc.on.ca
> Fri Feb 21 04:16:15 GMT 2003
> 
> cups-1.1.14-15.2

Please upgrade to CUPS-1.1.18+ to make cupsaddsmb work with Samba-2.2.7a+
Please stick to the settings suggested in "man cupsaddsmb", if your own
ideas don't work.

> samba-2.2.7-1.7.3
> 
> Educate me please ...

I can't...  ;-)

> man rpcclient shows:
> setdriver <printername> <drivername> - Execute a SetPrinter() command
>          to  update  the  printer driver associated with an installed printer.
>          The printer driver must already be correctly installed on  the  print
>          server.
> 
>          See  also  the  enumprinters and enumdrivers commands for obtaining a
>          list of of installed printers and drivers.
> 
> This sounds like the printer must already be installed - how is that done if not via
> addprinter?

The setdriver command is meant to associate a different driver to a printer.
The members of the driver/printer pair to be chosen must be mapping to the
lists of drivers and printers enumerated by the "enumdrivers" and "enumprinters"
commands.

> Currently, if I use enumprinters and enumdrivers (without a level setting), I get a
> listing of installed drivers and installed printers.  If I run setdriver for each of
> the printer/driver pairs, will it work? 

If you didn't get an error message, it should work.
"rpcclient ....-c "enumprinters 2" should list the new driver after the fact.
To get the clients to work with a new driver (if it had one already), you will
have to delete the printer first there (my experience). After that, *you* *will*
*have* *to* *delete* *the* *old* *driver* *too* *!* [To do this fast, right-click
on the *background* of the "printers" folder, select "server properties" and
hangle yourself to the tab/menu/dialog (not sure if it is the same in Win NT) to
remove the driver files in question. Only then will the registry entries be
cleansed. If you don't do that, there is the danger, that Windows will re-install
the *old* drivers" with your second attempt.]

> I just did it but don't have a windows
> client to test it against until tomorrow (I'm connected remotely via a ssh terminal)

Please tell us how it works out.

> Kurt Pfeifle (kpfeifle at danka.de) wrote*:
>>
>>> Date: Thu, 20 Feb 2003 20:11:21 +0000
>>> From: "Brian Johnson" <bjohnson at jecinc.on.ca>
>>> To: samba at lists.samba.org
>>> Subject: [Samba] cupsaddsmb - why the heck can't I get rpcclient-addprinter to work?
>>> Message-ID: <20030220.57L.51223600 at 192.168.0.1>
>>> Content-Type: text/plain;charset="iso-8859-1"
>>> MIME-Version: 1.0
>>> Content-Transfer-Encoding: 8bit
>>> Precedence: list
>>> Message: 39
>>>
>>> I can't seem to get the rpcclient-addprinter to work - grrrrrr
>>
>>Which versions of software are you using? Samba, CUPS?  Which OS?
>>
>>> It looks like the drivers files are copied correctly and the NT drivers are added
>>> correctly but the addprinter command says it's unsuccessful!
>>
>>"cupsaddsmb - why the heck can't I get rpcclient-addprinter to work?"
>>
>>Maybe because your CUPS/cupsaddsmb version is too old ?
>>
>>The "addprinter" rpcclient command formerly used by cupsaddsmb has
>>long been replaced by the "setdriver" command...
>>
>>
>>Cheers,
>>Kurt
>>
 >