[Samba] rpcclient and WERR_INVALID_PRINTER_NAME christian.loew at steyr-ssf.com christian.loew at steyr-ssf.com Sat Feb 28 08:23:56 GMT 2004
Hi,
I'm trying to set up a samba-cups-pdf-printserver.
samba itself is running fine, but when i try to add the cups printer-drivers for windows i got the following error:
System: Debian/sarge with 2.4.20 i686 GNU/Linux
samba 3.0.2-2
cupsys 1.1.20final-13
Windows-driver from cups-samba-5.0rc1.tar
ssflx01_v2:~# cupsaddsmb -a -v -U uuuu
Have you installed your new printer SSFP102 just before running this command?
Before you did run this command -- have you checked that Samba "sees" the new printer SSFP102?
Password for uuuu required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'uuu%xxxx' -c 'mkdir W32X86; put /var/spool/cups/tmp/40404c740a656 W32X86/SSFP102.ppd; put /usr/share/cups/drivers/cupsdrv5.dll W32X86/cupsdrv5.dll; put /usr/share/cups/drivers/cupsui5.dll W32X86/cupsui5.dll; put /usr/share/cups/drivers/cups5.hlp W32X86/cups5.hlp' Domain=[STEYR-SSF] OS=[Unix] Server=[Samba 3.0.2-Debian] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
...no problem.
putting file /var/spool/cups/tmp/40404c740a656 as \W32X86/SSFP102.ppd
putting file /usr/share/cups/drivers/cupsdrv5.dll as \W32X86/cupsdrv5.dll
putting file /usr/share/cups/drivers/cupsui5.dll as \W32X86/cupsui5.dll
putting file /usr/share/cups/drivers/cups5.hlp as \W32X86/cups5.hlp
...good.
Running command: rpcclient localhost -N -U'uuuu%xxxx' -c 'adddriver "Windows NT x86"
"SSFP102:cupsdrv5.dll:SSFP102.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"'
Printer Driver SSFP102 successfully installed.
...good.
Running command: rpcclient localhost -N -U'uuuu%xxxx' -c 'setdriver SSFP102 SSFP102'
result was WERR_INVALID_PRINTER_NAME
This means that Samba doesn't "see" yet your printer.SSFP102 However, it has installed a driver named SSFP102.
tdbdump ntdrivers.tdb shows that the drivers are installed
Does "rpcclient -U'uuu%xxxx' -c enumprinters localhost" show your printer "SSFP102"? If not, re-start Samba or do a "kill -HUP `pidof smbd`" and try the "enumprinters" command again. If now you see SSFP102 recognized, you can repeat the "cupsaddsmb" with complete success. Or just run
"rpcclient -N -U'uuuu%xxxx' -c 'setdriver SSFP102 SSFP102' localhost" or "rpcclient -d 5 -N -U'uuuu%xxxx' -c 'setdriver SSFP102 SSFP102' localhost"
from the commandline.
There is a bug in Samba which prevents newly
searching on google doesn't show any solution :-(
Google is *bad*. It should know all my previous answers to that queston... ;-)
any hints?
Hmmm.... ;-)
Chris
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
