Ok, I finally figured out what the problem was. In case anyone has the
problem in the future, here is what it was. I had the 'addprinter
command' parameter set to cupsaddsmb (as I read to do somewhere), when I
ran cupsaddsmb by hand, it would fail. Once I took the 'addprinter
command' parameter
Daniel T. Gynn wrote on Samba-Digest:
Message: 16
From: Daniel T. Gynn [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 21 Oct 2002 15:59:18 -0400
Subject: [Samba] SetPrinter call failed
I am having trouble getting the cupsaddsmb script to work to add the
drivers. Everything seems to work
:
Message: 16
From: Daniel T. Gynn [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 21 Oct 2002 15:59:18 -0400
Subject: [Samba] SetPrinter call failed
I am having trouble getting the cupsaddsmb script to work to add the
drivers. Everything seems to work (it copies the drivers
: [Samba] SetPrinter call failed
I am having trouble getting the cupsaddsmb script
to work to add the
drivers. Everything seems to work (it copies the
drivers to the correct
directories), but I keep getting the result
NT_STATUS_UNSUCCESSFUL error
message on the rpcclient
