Re: [Samba] 2.2.6 and printer questions
Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 8 Nov 2002, Thomas Bork wrote: Is it correct, that the automatic download of printer drivers is only possible for printers, which are associated with an printcap entry? When I'm uploading a postscript driver for a *virtuell* printer, which is not associated with an printcap entry and then making an automatic installation of the driver on w2k, the status of this printer is always Failure. The definition in smb.conf is: No. Any printer can have drivers associated with it. cheers, jerry - Hewlett-Packard - http://www.hp.com SAMBA Team-- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2SAMS Teach Yourself Samba in 24 Hours 2ed I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9z8CbIR7qMdg1EfYRApPvAJ9XERToLG0lXTzqNTJ9ng/mk8STVwCglGYO TMHHKq64hrwr4iCG4Y4eM1A= =JTgf -END PGP SIGNATURE- Of course, but since the lpq command for a virtual printer don't give a successfull result - you get an error on the client for the status. My solution here was to set a special lpq command for the virtual printer, which always returned a successful result when asked. Eirik Thorsnes -- REAL Programmers never work 9 to 5. If any REAL Programmers are around at 9 AM, it's because they were up all night. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 2.2.6 and printer questions
Hi, sorry for reposting this long mail, but there was no answer. An answer like: Automatic download and install of printer drivers for printers, which are not associated with an printcap entry, is not implemented yet. will be okay - then I know, there is no failure on my side ;o) Hallo Gerald (Jerry) Carter, you wrote: If printers served from Samba it is nessesary to double click the netbios name of the samba server to see printershares. Why? Unknown. Tim had looked into this but I don't remember the details. I'm also thinking to remember (may be this is very bad english ;o) the question on this list and someone, who wants to look into it for 2.2.6. But the behavior is the same as in 2.2.5. That probably would have been me. I think it just fell off the plate as a non-essential feature for 2.2.6. We should make sure this works in 3.0. Thanks you for that :o) Is it possible, to bundle/deliver printer drivers in an tarfile, whith their relationships to predefined shares? Theoretically yes. But Probably not really a good idead since it would involve messing with the tdb files directory. The other problem is that printer information can only be initialized (Device Mode Printer data) by running the driver bound to the printer. Really messy. Then there is the EULA as well. I think, there is a free postscript driver included in cups. If you could get around the EULA, then you could package preinitialized drivers and write the information to smbd's tdbs. We have support for storing driver initialization data already. Where can I get more informations about that? Sounds interesting. Hmmmwish I could read German :-) Sorry, this is a very new project and the english version of the page is not completly done and existing parts are outdated. You don't need printing.tdb. That's a volatile tdb used to cache jobs listed in the queue. The rest of your assessment is correct. Thanks again. But another question: Is it correct, that the automatic download of printer drivers is only possible for printers, which are associated with an printcap entry? When I'm uploading a postscript driver for a *virtuell* printer, which is not associated with an printcap entry and then making an automatic installation of the driver on w2k, the status of this printer is always Failure. The definition in smb.conf is: [pdf] comment = pdf-service on %h browseable = yes printable = yes path = /tmp print command = ( /usr/local/bin/samba-print-pdf %s ~%u %L\\%u %m %I ) public = yes create mode = 0700 The driver is not the reason because I tested it also with a normal driver for the HP Laserjet 4 Plus, for which the automatic installation for non-virtuell printers works fine, if the sharename will be found in /etc/printcap or if in the share a statement like printer = printername in printcap exists. I think, automatic installation of printer drivers would be also usefull for virtuell printers, if there are for instance 200 workstations, which want to print to pdf-service... I looked into the tdb-files but could not find any associations with the printcap entries? Here are the other informations about my printing situation: [global] printing = lprng printcap name = /etc/printcap printer admin = root, eis load printers = no print command = chmod 666 %s;\ name=`echo '%J' | sed s/^.*- //` ;\ /usr/bin/lpr -P%p -J$name %s;\ rm %s lpq command = /usr/bin/lpq -P%p -L lpq cache time = 4 lprm command = /usr/bin/lprm -P%p %j lppause command = /usr/sbin/lpc hold %p %j lpresume command = /usr/sbin/lpc release %p %j queuepause command = /usr/sbin/lpc stop %p queueresume command = /usr/sbin/lpc start %p Share definitions, where automatic download works: [pr1] comment = local printer pr1 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [pr2] comment = local printer pr2 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [repr1] comment = remote printer repr1 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [repr2] comment = remote printer repr2 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [repr3] comment = remote printer repr3 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp Share for printer drivers: [print$] comment = samba printer drivers on %h browseable = yes writeable = no path = /samba_printer_drivers public = yes write list = root, eis /etc/printcap #-- -- # Lprng configuration file generated by
CUPS PostScript drivers for Samba explained -- was: Re: [Samba] 2.2.6 and printer questions
Volker Lendecke wrote on Samba-digest: Message: 10 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [Samba] 2.2.6 and printer questions Reply-To: [EMAIL PROTECTED] Date: Mon, 04 Nov 2002 08:54:01 +0100 Organization: Service Network GmbH, Goettingen, Germany -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If you could get around the EULA, then you could package preinitialized drivers and write the information to smbd's tdbs. We have support for storing driver initialization data already. Have you heard that you can get CUPS printer drivers exactly for that from cups.org? If they are good drivers, this could be very interesting. Hi, all, I'll give you some more info about the PostScript driver Volker mentioned above here as a reference. (Maybe one day before the 3.0 release it will end up as a worked-out paragraph inside the HOWTO collection): You can download the driver files from http://www.cups.org/software.html. It is a separate package from the CUPS base software files, tagged as CUPS 1.1.16 Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k). The filename to download is cups-samba-1.1.16.tar.gz. Upon untar-/unzip-ping it will reveal the files cups-samba.install cups-samba.license cups-samba.readme cups-samba.remove cups-samba.ss These have been packaged with the ESP meta packager software EPM. The *.install and *.remove files are simple shell script, which untars the *.ss (which is nothing else than a tar-archive) and puts its contents into /usr/share/cups/drivers/. Its contents are 3 files: cupsdrvr.dll cupsui.dll cups.hlp [ ATTENTION: due to a bug the current release puts the cups.hlp into /usr/share/drivers/ instead of /usr/share/cups/drivers/. To work around this, copy/move the file after running the ./cups-samba.install script manually to the right place: cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ ] This new CUPS PostScript driver is currently binary-only, but free (as in free beer); no source code is provided (yet). The reason is this: it has been developed with the help of the Microsoft Driver Developer Kit (DDK) and compiled with Microsoft Visual Studio 6. It is not clear to the driver developers if they are allowed to distribute the whole of the source code as Free Software. However, they will likely release the diff in source code under the GPL, so anybody with a license of Visual Studio and a DDK will be able to compile for him/herself. Once you have run the install script (and possibly manually moved the cups.hlp file to /usr/share/cups/drivers/), the driver is ready to be put into Samba's [print$] share (which often maps to /etc/samba/drivers/ and contains a subdir tree with WIN40 and W32X86 branches), by running cupsaddsmb (see also man cupsaddsmb for CUPS 1.1.16). [Don't forget to put root into the smbpasswd file by running smbpasswd should you run this whole procedure for the first time.] Once the driver files are in the [print$] share, they are ready to be downloaded and installed by the Win NT/2k/XP clients. NOTE 1: Win 9x/ME clients won't work with this driver. For these you'd still need to use the ADOBE*.* drivers as previously. NOTE 2: It is not harming if you've still the ADOBE*.* driver files from previous installations in the /usr/share/cups/drivers/ directory. The new cupsaddsmb (from 1.1.16) will automatically use the newest installed driver (which here then is the CUPS drivers). NOTE 3: Should your Win clients have had the old ADOBE*.* files and the Adobe PostScript drivers installed, the download and installation of the new CUPS PostScript driver for Windows NT/2k/XP will fail at first. It is not enough to delete the printer (as the driver files will still be kept by the clients and re-used if you try to re-install the printer). To really get rid of the Adobe driver files on the clients, open the Printers folder (possibly via Start -- Settings -- Control Panel -- Printers), right-click onto the folder background and select Server Properties. A new dialog opens; select the Drivers tab; on the list select the driver you want to delete and click on the Delete button. (This will only work if there is no single printer left which uses that particular driver -- you need to delete all printers using this driver in the Printers folder first...) NOTE 4: Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all printers to this one by proceeding as described elsewhere in the Samba HOWTO Collection to change a driver for an existing printer What are the benefits with the CUPS PostScript driver for Windows NT/2k/XP as compared to the Adobe drivers? * no hassle with the Adobe EULA; no hassle with the question where do I get
Re: [Samba] 2.2.6 and printer questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 1 Nov 2002, Thomas Bork wrote: If printers served from Samba it is nessesary to double click the netbios name of the samba server to see printershares. Why? Unknown. Tim had looked into this but I don't remember the details. I'm also thinking to remember (may be this is very bad english ;o) the question on this list and someone, who wants to look into it for 2.2.6. But the behavior is the same as in 2.2.5. That probably would have been me. I think it just fell off the plate as a non-essential feature for 2.2.6. We should make sure this works in 3.0. Is it possible, to bundle/deliver printer drivers in an tarfile, whith their relationships to predefined shares? Theoretically yes. But Probably not really a good idead since it would involve messing with the tdb files directory. The other problem is that printer information can only be initialized (Device Mode Printer data) by running the driver bound to the printer. Really messy. Then there is the EULA as well. If you could get around the EULA, then you could package preinitialized drivers and write the information to smbd's tdbs. We have support for storing driver initialization data already. I'm the maintainer of a Samba package for the GPL project eisfair (www.eisfair.org), an easy to use internet server. In my package, currently based on Samba 2.2.6, it is possible to print to an virtual printer for creating PDF files and to a virtual printer for the fax package (installed ghostscript package is needed) . On the windows clients a postscript printer driver must be installed for each of this virtual printers. Sounds interesting. Hmmmwish I could read German :-) It will be nice, if the driver installation is so easy as possible for the user. Thats why I'm interested in an automatic driver installation based on the print$ share. But I can see any problems with this: If I want to deliver drivers for nt/w2k/xp and win9x/me in the package, I think I have to include in the package not only the complete directory predefined in [print$] with the drivers. I think I have also to deliver the tdb-files ntdrivers.tdb ntforms.tdb ntprinters.tdb printing.tdb because anywhere here the relationship between printershare and driver (format and so on...) is saved. But how can this be done without breaking existing relationships with existing drivers and printers in the existing configuration on user side? You don't need printing.tdb. That's a volatile tdb used to cache jobs listed in the queue. The rest of your assessment is correct. cheers, jerry - Hewlett-Packard - http://www.hp.com SAMBA Team-- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2SAMS Teach Yourself Samba in 24 Hours 2ed I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9xTYZIR7qMdg1EfYRAtRyAKC6cQDqb1UmZl+YcYMEpM1eS253jgCfXVVi KVgUygxAGvrBfS27kxjF1rg= =OKLh -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 2.2.6 and printer questions
Hallo Gerald (Jerry) Carter, you wrote: If printers served from Samba it is nessesary to double click the netbios name of the samba server to see printershares. Why? Unknown. Tim had looked into this but I don't remember the details. I'm also thinking to remember (may be this is very bad english ;o) the question on this list and someone, who wants to look into it for 2.2.6. But the behavior is the same as in 2.2.5. That probably would have been me. I think it just fell off the plate as a non-essential feature for 2.2.6. We should make sure this works in 3.0. Thanks you for that :o) Is it possible, to bundle/deliver printer drivers in an tarfile, whith their relationships to predefined shares? Theoretically yes. But Probably not really a good idead since it would involve messing with the tdb files directory. The other problem is that printer information can only be initialized (Device Mode Printer data) by running the driver bound to the printer. Really messy. Then there is the EULA as well. I think, there is a free postscript driver included in cups. If you could get around the EULA, then you could package preinitialized drivers and write the information to smbd's tdbs. We have support for storing driver initialization data already. Where can I get more informations about that? Sounds interesting. Hmmmwish I could read German :-) Sorry, this is a very new project and the english version of the page is not completly done and existing parts are outdated. You don't need printing.tdb. That's a volatile tdb used to cache jobs listed in the queue. The rest of your assessment is correct. Thanks again. But another question: Is it correct, that the automatic download of printer drivers is only possible for printers, which are associated with an printcap entry? When I'm uploading a postscript driver for a *virtuell* printer, which is not associated with an printcap entry and then making an automatic installation of the driver on w2k, the status of this printer is always Failure. The definition in smb.conf is: [pdf] comment = pdf-service on %h browseable = yes printable = yes path = /tmp print command = ( /usr/local/bin/samba-print-pdf %s ~%u %L\\%u %m %I ) public = yes create mode = 0700 The driver is not the reason because I tested it also with a normal driver for the HP Laserjet 4 Plus, for which the automatic installation for non-virtuell printers works fine, if the sharename will be found in /etc/printcap or if in the share a statement like printer = printername in printcap exists. I think, automatic installation of printer drivers would be also usefull for virtuell printers, if there are for instance 200 workstations, which want to print to pdf-service... I looked into the tdb-files but could not find any associations with the printcap entries? Here are the other informations about my printing situation: [global] printing = lprng printcap name = /etc/printcap printer admin = root, eis load printers = no print command = chmod 666 %s;\ name=`echo '%J' | sed s/^.*- //` ;\ /usr/bin/lpr -P%p -J$name %s;\ rm %s lpq command = /usr/bin/lpq -P%p -L lpq cache time = 4 lprm command = /usr/bin/lprm -P%p %j lppause command = /usr/sbin/lpc hold %p %j lpresume command = /usr/sbin/lpc release %p %j queuepause command = /usr/sbin/lpc stop %p queueresume command = /usr/sbin/lpc start %p Share definitions, where automatic download works: [pr1] comment = local printer pr1 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [pr2] comment = local printer pr2 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [repr1] comment = remote printer repr1 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [repr2] comment = remote printer repr2 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp [repr3] comment = remote printer repr3 on %h browseable = yes printable = yes public = yes create mode = 0700 path = /tmp Share for printer drivers: [print$] comment = samba printer drivers on %h browseable = yes writeable = no path = /samba_printer_drivers public = yes write list = root, eis /etc/printcap #-- -- # Lprng configuration file generated by /var/install/config.d/lprng.sh # # Version of Lprng for eisfair is 1.0.1 # # Do not edit this file, use # # 'Edit Lprng Configuration' # # in Printer Services Menu ! # # Creation date: Sat Oct 26 20:39:37 #-- -- #-- -- # Configuration for local Printer
Re: [Samba] 2.2.6 and printer questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If you could get around the EULA, then you could package preinitialized drivers and write the information to smbd's tdbs. We have support for storing driver initialization data already. Have you heard that you can get CUPS printer drivers exactly for that from cups.org? If they are good drivers, this could be very interesting. Sounds interesting. Hmmmwish I could read German :-) Part of that site is translated :-) Volker -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Key-ID D32186CF, Fingerprint available: phone +49 551 370 iD8DBQE9xieXOmSXH9Mhhs8RAkMvAJ9sigDXJi9n2njyO2+0EVsFnDNkXACeOqz3 G1Ta4CGXvmhc2ZUp8Nff7fg= =zlGF -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 2.2.6 and printer questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 1 Nov 2002, Thomas Bork wrote: Hi all, I have 2 questions about printer driver installation on w2k-client for a samba served printer: 1. If I want to install a driver on w2k workstation, I choose network printer and then can browse the network. If printers are served from a Nt/w2k-server, in my opinion it is not nessesary to double click the netbios name of the Nt/w2k-server to see the shared printers. In this case under the Workgroup-Name are all shared printers of all servers visible like - workgroupname \\server1\printer1 \\server2\printer1 + server1 + server2 If printers served from Samba it is nessesary to double click the netbios name of the samba server to see printershares. Why? Unknown. Tim had looked into this but I don't remember the details. 2. If I'm uploading printer drivers for w2k and win9x via the APW (Add Printer Wizzard) from a NT/W2K/XP-client to the Samba server, w2k alway show me, that on the samba server only a driver for w2k exists. Why? No idea. Need more details. cheers, jerry - Hewlett-Packard - http://www.hp.com SAMBA Team-- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2SAMS Teach Yourself Samba in 24 Hours 2ed I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9wpJNIR7qMdg1EfYRAt+1AKCKmNb/xxh0Fe1aRmM7GYCnHi2QsgCgpSpO Qb3aWxifRhRiDwaP8ha/OQY= =w2Mb -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] 2.2.6 and printer questions
Hallo Gerald (Jerry) Carter, you wrote: I have 2 questions about printer driver installation on w2k-client for a samba served printer: 1. If I want to install a driver on w2k workstation, I choose network printer and then can browse the network. If printers are served from a Nt/w2k-server, in my opinion it is not nessesary to double click the netbios name of the Nt/w2k-server to see the shared printers. In this case under the Workgroup-Name are all shared printers of all servers visible like - workgroupname \\server1\printer1 \\server2\printer1 + server1 + server2 If printers served from Samba it is nessesary to double click the netbios name of the samba server to see printershares. Why? Unknown. Tim had looked into this but I don't remember the details. I'm also thinking to remember (may be this is very bad english ;o) the question on this list and someone, who wants to look into it for 2.2.6. But the behavior is the same as in 2.2.5. 2. If I'm uploading printer drivers for w2k and win9x via the APW (Add Printer Wizzard) from a NT/W2K/XP-client to the Samba server, w2k alway show me, that on the samba server only a driver for w2k exists. Why? No idea. Need more details. I'll try to give more details, please answer, if it is not enough: Uuups... Sorry, my failure. I was a little bit confused, because when uploading drivers via (in W2K german version called:) Freigabe/Zusätzliche Treiber -- may be in english Share/Additional drivers and choosing Intel Windows NT 4.0 or 2000 then, after upload, on the same tab, checkbox Intel Windows 2000 is checked an not Intel Windows NT 4.0 or 2000, which I checked for uploading. Sorry for the confusion. But another question: Is it possible, to bundle/deliver printer drivers in an tarfile, whith their relationships to predefined shares? The background is this: I'm the maintainer of a Samba package for the GPL project eisfair (www.eisfair.org), an easy to use internet server. In my package, currently based on Samba 2.2.6, it is possible to print to an virtual printer for creating PDF files and to a virtual printer for the fax package (installed ghostscript package is needed) . On the windows clients a postscript printer driver must be installed for each of this virtual printers. It will be nice, if the driver installation is so easy as possible for the user. Thats why I'm interested in an automatic driver installation based on the print$ share. But I can see any problems with this: If I want to deliver drivers for nt/w2k/xp and win9x/me in the package, I think I have to include in the package not only the complete directory predefined in [print$] with the drivers. I think I have also to deliver the tdb-files ntdrivers.tdb ntforms.tdb ntprinters.tdb printing.tdb because anywhere here the relationship between printershare and driver (format and so on...) is saved. But how can this be done without breaking existing relationships with existing drivers and printers in the existing configuration on user side? Any ideas or references would be appreciated. Thanks :o) tom -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
