Nicki Messerschmidt, Linksystem Muenchen GmbH
2003-Feb-11 19:01 UTC
[Samba] Adding printer driver with cupsaddsmb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have a problem adding printer drivers for automatic downloading via samba for windows 2000 clients. Under cups I added my printer and copied the Adobe postscript driver files like mentioned in printer_driver2.html. And when I finally commit: cupsaddsmb -v -U root normal (normal is the name of the printer) And here is the output: sphinx:/usr/share/cups # cupsaddsmb -v -U root normal Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%<password>' - -c 'mkdir W32X86;put /var/spool/cups/tmp/3e4946cfeee23 W32X86/normal.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.XXX.XXX nmask=255.255.255.XXX Domain=[LINK-M] OS=[Unix] Server=[Samba 2.2.7a-0.1 for Debian] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86 putting file /var/spool/cups/tmp/3e4946cfeee23 as \W32X86/normal.PPD (24631.6 kb/s) (average 24632.8 kb/s) putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (42421.5 kb/s) (average 39457.0 kb/s) putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (32399.4 kb/s) (average 37381.4 kb/s) putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (19304.8 kb/s) (average 36377.3 kb/s) Running command: smbclient //localhost/print\$ -N -U'root%<password>' - -c 'mkdir WIN40;put /var/spool/cups/tmp/3e4946cfeee23 WIN40/normal.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.XXX.XXX nmask=255.255.255.XXX Domain=[LINK-M] OS=[Unix] Server=[Samba 2.2.7a-0.1 for Debian] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40 putting file /var/spool/cups/tmp/3e4946cfeee23 as \WIN40/normal.PPD (24631.6 kb/s) (average 24632.8 kb/s) putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (40148.5 kb/s) (average 38209.3 kb/s) putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (43123.8 kb/s) (average 41376.5 kb/s) putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (37939.3 kb/s) (average 40972.2 kb/s) putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (13175.5 kb/s) (average 40437.7 kb/s) putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (38451.9 kb/s) (average 40329.4 kb/s) putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (27998.6 kb/s) (average 39896.8 kb/s) Running command: rpcclient localhost -N -U'root%<password>' -c 'adddriver "Windows NT x86" "normal:ADOBEPS5.DLL:normal.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL" ' cmd = adddriver "Windows NT x86" "normal:ADOBEPS5.DLL:normal.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL" Printer Driver normal successfully installed. Running command: rpcclient localhost -N -U'root%<password>' -c 'addprinter normal normal "normal" ""' cmd = addprinter normal normal "normal" "" result was NT_STATUS_UNSUCCESSFUL Running command: rpcclient localhost -N -U'root%<passowrd>' -c 'adddriver "Windows 4.0" "normal:ADOBEPS4.DRV:normal.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS. MFM,DEFPRTR2.PPD,ICONLIB.DLL"' cmd = adddriver "Windows 4.0" "normal:ADOBEPS4.DRV:normal.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS. MFM,DEFPRTR2.PPD,ICONLIB.DLL" Printer Driver normal successfully installed. As you can see, the process won't finish successfully. I send my smb.conf as attachement and can provide logfiles, if they are of any help to you. I don't understand, why this procedure is not successful and I hope, that anyone of you can shed light onto this miracle... Cheers Nicki Messerschmidt - -- Linksystem Muenchen GmbH info@link-m.de Schloerstrasse 10 http://www.link-m.de 80634 Muenchen Tel. 089 / 890 518-0 We make the Net work. Fax 089 / 890 518-77 -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com> Comment: Get my key at: https://www.link-m.de/pgp/n.messerschmidt.asc iQA/AwUBPkk6ces1nPm17iBDEQKS4ACg2pVeCCmuZjTnzLN24s9acwTD+QAAnj+b 5zRvthCj9zT6h0Br/2CIhLod =mzmk -----END PGP SIGNATURE-----
Nicki Messerschmidt, Linksystem Muenchen GmbH
2003-Feb-11 19:02 UTC
[Samba] Adding printer driver with cupsaddsmb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have a problem adding printer drivers for automatic downloading via samba for windows 2000 clients. Under cups I added my printer and copied the Adobe postscript driver files like mentioned in printer_driver2.html. And when I finally commit: cupsaddsmb -v -U root normal (normal is the name of the printer) And here is the output: sphinx:/usr/share/cups # cupsaddsmb -v -U root normal Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%<password>' - -c 'mkdir W32X86;put /var/spool/cups/tmp/3e4946cfeee23 W32X86/normal.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.XXX.XXX nmask=255.255.255.XXX Domain=[LINK-M] OS=[Unix] Server=[Samba 2.2.7a-0.1 for Debian] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86 putting file /var/spool/cups/tmp/3e4946cfeee23 as \W32X86/normal.PPD (24631.6 kb/s) (average 24632.8 kb/s) putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (42421.5 kb/s) (average 39457.0 kb/s) putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (32399.4 kb/s) (average 37381.4 kb/s) putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (19304.8 kb/s) (average 36377.3 kb/s) Running command: smbclient //localhost/print\$ -N -U'root%<password>' - -c 'mkdir WIN40;put /var/spool/cups/tmp/3e4946cfeee23 WIN40/normal.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.XXX.XXX nmask=255.255.255.XXX Domain=[LINK-M] OS=[Unix] Server=[Samba 2.2.7a-0.1 for Debian] NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40 putting file /var/spool/cups/tmp/3e4946cfeee23 as \WIN40/normal.PPD (24631.6 kb/s) (average 24632.8 kb/s) putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (40148.5 kb/s) (average 38209.3 kb/s) putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (43123.8 kb/s) (average 41376.5 kb/s) putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (37939.3 kb/s) (average 40972.2 kb/s) putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (13175.5 kb/s) (average 40437.7 kb/s) putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (38451.9 kb/s) (average 40329.4 kb/s) putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (27998.6 kb/s) (average 39896.8 kb/s) Running command: rpcclient localhost -N -U'root%<password>' -c 'adddriver "Windows NT x86" "normal:ADOBEPS5.DLL:normal.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL" ' cmd = adddriver "Windows NT x86" "normal:ADOBEPS5.DLL:normal.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL" Printer Driver normal successfully installed. Running command: rpcclient localhost -N -U'root%<password>' -c 'addprinter normal normal "normal" ""' cmd = addprinter normal normal "normal" "" result was NT_STATUS_UNSUCCESSFUL Running command: rpcclient localhost -N -U'root%<passowrd>' -c 'adddriver "Windows 4.0" "normal:ADOBEPS4.DRV:normal.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS. MFM,DEFPRTR2.PPD,ICONLIB.DLL"' cmd = adddriver "Windows 4.0" "normal:ADOBEPS4.DRV:normal.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS. MFM,DEFPRTR2.PPD,ICONLIB.DLL" Printer Driver normal successfully installed. As you can see, the process won't finish successfully. I send my smb.conf as attachement and can provide logfiles, if they are of any help to you. I don't understand, why this procedure is not successful and I hope, that anyone of you can shed light onto this miracle... Cheers Nicki Messerschmidt - -- Linksystem Muenchen GmbH info@link-m.de Schloerstrasse 10 http://www.link-m.de 80634 Muenchen Tel. 089 / 890 518-0 We make the Net work. Fax 089 / 890 518-77 -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com> Comment: Get my key at: https://www.link-m.de/pgp/n.messerschmidt.asc iQA/AwUBPkk6ses1nPm17iBDEQL1pwCgjUs8Th6uUK1tdgdTHS9cLkSbLY0Anj/9 Q1dIWhfuyo+1HOg43M2Wdh8Y =0v1o -----END PGP SIGNATURE-----
Nicki Messerschmidt, Linksystem Muenchen GmbH
2003-Feb-13 16:22 UTC
[Samba] Adding Printer driver with cupsaddsmb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi lists, I still have a problem adding a driver to samba 2.2.7a-0.1 with cupsaddsmb. Everything works fine except the addprinter call, which terminates with NT_STATUS_UNSUCCESSFULL. This is because of a WERR_ACCESS_DENIED message, which I don't understand. Perhaps someone can shed light onto this. What files do you need, to get an understanding of what is going on? In my post to the samba user mailinglist 2003-02-11 I attached some output of cupsaddsmb. With hope, Nicki Messerschmidt - -- Linksystem Muenchen GmbH info@link-m.de Schloerstrasse 10 http://www.link-m.de 80634 Muenchen Tel. 089 / 890 518-0 We make the Net work. Fax 089 / 890 518-77 -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com> Comment: Get my key at: https://www.link-m.de/pgp/n.messerschmidt.asc iQA/AwUBPku4Ges1nPm17iBDEQJy0wCeKNp3tVvy1tyHxsNi97N5ddD8URIAnRcu VNpdzn+xpP7Ebv0MODoftsL/ =SpTd -----END PGP SIGNATURE-----
Nicki Messerschmidt, Linksystem Muenchen GmbH wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi lists, > I still have a problem adding a driver to samba 2.2.7a-0.1 with > cupsaddsmb. Everything works fine except the addprinter call, which > terminates with NT_STATUS_UNSUCCESSFULL. This is because of a > ...Sounds like you are using an old version of CUPS; current releases use the setdriver command instead. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Printing Software for UNIX http://www.easysw.com
Nicki Messerschmidt wrote on Samba-Digest:> Date: Thu, 13 Feb 2003 17:22:01 +0100 > From: "Nicki Messerschmidt, Linksystem Muenchen GmbH" <samba@alienn.net> > To: <samba@lists.samba.org>, <samba-technical@lists.samba.org> > Subject: [Samba] Adding Printer driver with cupsaddsmb > Precedence: list > Message: 13 > > > Hi lists,Hi, Nicki,> I still have a problem adding a driver to samba 2.2.7a-0.1 with > cupsaddsmb.You tell the version of Samba -- yet you don't tell the version of the other important component: CUPS. Which is it?> Everything works fine except the addprinter call, which > terminates with NT_STATUS_UNSUCCESSFULL.The "adddprinter" call used to be there in older versions of cupsaddsmb. Recent version use the "setdriver" command instead. My advice is to upgrade CUPS and then try again.> This is because of a > WERR_ACCESS_DENIED message, which I don't understand.Here are two more tips about useful troubleshooting techniques: 1-- Try to use this command in an xterm window on the Samba host (as root): "watch --interval=1 smbstatus" "watch" will update the output of the "smbstatus" command every 1 second(s). "smbstatus" will show, which connections are active, to which service, from which machine, and under which username (uid/gid). While this runs, make sure there are not too many other connections active (best do it in the evening when the users have gone home...). (This is just to make sure that what you want to see is not drowned in too much other info...) Now run cupsaddsmb and watch for the connection(s) being made during the process. Are they made as the user you're expecting? (Once you have "cupsaddsmb" completed successfully, you may apply the same technique to troubleshoot any failing printer driver download to the clients, or a failing setting of the default devmode....) 2-- Investigate the smbd log file for errors. If you have a low debug level, you will not see a lot. Set the debuglevel to a higher value, if you need more. (I'd recommend "3" for a beginning) Don't necessarily do it in the smb.conf file. Try to change it on the fly: "smbstatus smbd debuglevel" will reveal the currently used value. "smbstatus smbd debug 3" will set it to "3" on the fly. "tail -f /path/to/smbd-log-file" will show the updates to the log file in realtime, while you try to work with cupsaddsmb, driver download from the client (or anything else...)> Perhaps someone > can shed light onto this. What files do you need, to get an > understanding of what is going on? > In my post to the samba user mailinglist 2003-02-11 I attached some > output of cupsaddsmb. > > > With hope, > Nicki MesserschmidtWith confidence, Kurt ;-)