cups-1.1.14-15.2
samba-2.2.7-1.7.3
Educate me please ...
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?
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? 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)
Kurt Pfeifle ([EMAIL PROTECTED]) wrote*:
>
>> Date: Thu, 20 Feb 2003 20:11:21 +0000
>> From: "Brian Johnson" <[EMAIL PROTECTED]>
>> To: [EMAIL PROTECTED]
>> Subject: [Samba] cupsaddsmb - why the heck can't I get rpcclient-addprinter to work?
>> Message-ID: <[EMAIL PROTECTED]>
>> 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
>
>
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
