Bug 3685 - WERR_UNKNOWN_PRINTER_DRIVER when using cupsaddsmb
WERR_UNKNOWN_PRINTER_DRIVER when using cupsaddsmb
Status: RESOLVED INVALID
Product: Samba 3.0
Classification: Unclassified
Component: Client Tools
3.0.22
x86 Linux
: P3 regression
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-15 11:12 UTC by Casual J. Programmer
Modified: 2006-04-18 17:33 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Casual J. Programmer 2006-04-15 11:12:21 UTC
Running Samba 3.0.22 on Ubuntu 6.06 with CUPS 1.2svn on Intel Platform

1. Copy postscript drivers from WindowsXP (C:/windows/system32/spool/drivers/w32x86/3) to Ubuntu (/usr/share/cups/drivers)files are ps5ui.dll  pscript5.dll  pscript.hlp  PSCRIPT.NTF

2. Issue $sudo cupsaddsmb -a -v -H WORKSTATION1U6 -U root%mypassword

3. The process starts OK but stops with the following lines:

Running command: rpcclient WORKSTATION1U6 -N -U 'root%arendtconsult' -c 'adddriver "Windows NT x86" "BJC-8200:pscript5.dll:BJC-8200.ppd:ps5ui.dll:pscript.hlp:NULL:RAW:pscript5.dll,BJC-8200.ppd,ps5ui.dll,pscript.hlp,pscript.ntf"'
result was WERR_UNKNOWN_PRINTER_DRIVER
Password for root required to access WORKSTATION1U6 via SAMBA:

4. Repeat ad infinitum if you enter the password again, otherwise terminates.

5. Noticing that one of the files is named in capitals (PSCRIPT.NTF) and renaming it to lowercase (pscript.ntf).

6. Repeat from step 2.

7. Now runs for three printers terminating with "$ Succesfully set Postscript-ColorPrinter to driver Postscript-ColorPrinter."

While fixing this issue, it is probably a good idea to make sure that cupsaddsmb accepts files regardless of ownership etc. 

Maybe related to the late error 294 also
Comment 1 Kurt Pfeifle 2006-04-18 15:52:32 UTC
Thanks for the bug report, but...

...please read "man cupsaddsmb". It *specifically says: "...copy the files exactly as named below:" And then *all* names are spelled *lowercase*.

Casual, 

I do not think this is a bug, given what's in the man page. Fact is, Unix has case sensitive file names, while Windows treats them as case insensitive in most cases. You'll have to live with this, I think.

I propose to close this report as INVALID.

Cheers,
Kurt Pfeifle
Comment 2 Gerald (Jerry) Carter 2006-04-18 17:33:35 UTC
I'll go with Kurt on this one.