similar to: How do I remove printer drivers from print$

Hey folks. I am trying to set up a cups/samba printer server, and I am having trouble using cupsaddsmb. I isolated the problem to a rpcclient and here is the information I gathered from the various commands. If I delete all the files in "/var/lib/samba/drivers" cupsaddsmb installs the folders and files, but doesn't move the files in to the WIN40/0 folder with the adddriver

-----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:

Hi, I have a linux box on RH7.3 with samba 2.2.5-1 and cups-1.1.14-15. I create a cups printer on to this machine with success, It called lptest? and apparently, when I send a page test it works fine. But now I want to share It via Samba then I putted the different setting in smb.conf . I extracted the different files from the ADOBE POSTSCRIPT DRIVER and I put them in /usr/share/cups/drivers .

Hello I've got some problems downloading Adobe PostScript printer drivers on a Windows 98 client : On the server side (Red Hat 9 / Samba 3.0.2 / Cups 1.1.17) : I installed succesfully my printers with Cups and they work fine on Linux I ran cupsaddsmb tool to copy the Adobe files in the [print$] directory which gives this result : in /etc/samba/W32X86/2 : cupsdrvr.dll cups.hlp

hi list, We got the following problem: We try to use samba 2.2.5 as a printserver for windoze clients (samba 2.2.5 on RH linux 8 w/ CUPS 1.1.15). CUPS works w/o any problems, but when we try to generate the drivers for the windoze clients (by using cupsaddsmb), we get the following error: >> cli_pipe: return critical error. Error was SUCCESS - 0 result was NT_STATUS_UNSUCCESSFUL

I'm having trouble with driver downloads to Win98 clients from a Cups server/ red hat 8.0 (2.4.18-26.8.0) cups-1.1.18 samba 2.2.8 netatalk-1.6.1 I have windows clients successfully installing and printing to printers over samba and macs over netatalk. I'm using the stock Adobe drivers. Windows 2000 and Windows XP clients successfully grab drivers off of the print$ share without a

I'm running Ubuntu 10.04 LTS and loaded (via apt-get) Samba version 2:3.4.7 as part of the effort to bring up Sambafax. A dpkg-query gives the following: # dpkg-query -l | fgrep samba ii libcrypt-smbhash-perl 0.12-3 generate LM/NT hash of a password for samba ii samba 2:3.4.7~dfsg-1ubuntu3.1 SMB/CIFS file, print, and login server for U ii

Hi, I played around with samba 2.2.5 and cups and tried to get it working. Well everything is fine, but the driver upload to the client WILL NOT WORK. I used the current stable downloads, latest patch for printing, prebuilds from Lars Mueller .... I put together everything. If one has a working samba//cups please tar it and place it on our ftp-server. I don't know what's wrong here

We're using Cups and Samba with Adobe Postscript Drivers to print from XP SP2 machines via our Solaris and Linux Domain Controllers. Everything has been working OK, but when I setup an a new printer (identical ppd file to another one), it doesn't download the drivers on XP when I add the printer. This is happening on two domain controllers in different offices. It gives the error when

Hi I've got some problems with the download of Adobe PostScript printer drivers on a Windows 98 client : On the server side (Red Hat 9 / Samba 3.0.1 / Cups 1.1.17) : I installed succesfully my printers with Cups and they work fine on Linux I ran cupsaddsmb tool to copy the Adobe files in the [print$] directory which gives this result : ...../W32X86/2 : cupsdrvr.dll cups.hlp

I have som trouble with rpcclient.. I have all my adobe-drivers in /usr/share/cups/drivers/ and a directory in /etc/samba/drivers for the targetdrivers after i run cupsaddsmb. But when i run cupsaddsmb, directorys named Win40 and W32X86 in /etc/samba/drivers is created. And the files from /usr/share/cups/drivers in the directorys. But when cupsaddsmb is running "adddriver..." it

I am having problems with the driver installation for WIN40 (9x machines) in Samba 2.2.5 / Samba 2.2.6pre2 on a Solaris 8 machine. I build binary packages for both debian and solaris environments. For debian 2.2.5, I use the 2.2.5 source with the printing patch provided by Jerry Carter. I use the packaging/Debian/debian systems to build and package the source. For Solaris I use the

My W9x clients cannot download printer driver from samba 3.0.2rc1 with cups 1.1.17, while w2k clients do. The W9x clients open the Add Printer Wizard, connect to print$ share, request the ADOBEPS4.DRV file, but they stop at the beginning of the download. Permissions on print$\WINNT\0 directory are the same as print$\W32X86\2. cupsaddsmb was successful. I sniffed the packets while client was

Windows 98 client cannot print via samba to PrintPro printer "exported" via Cups/PrintPro on PrintPro/Samba server. "Exporting" with Cups on server node allows print drivers to be downloaded to Windows clients from the server. Any help or suggestions are greatly appreciated. Win98 node gim98.rsmas.miami.edu [129.171.97.21] connects to Samba 3.0.0-15 server "prima"

I am having quite some difficulty adding printer drivers to the print$ share of my Linux box. Here are the details: Debian Gnu/Linux with kernel 2.4.18 on a Sun Ultra 2. Samba version 2.2.3a. CUPS version 1.1.19. I am following along in the printer_driver2.txt file. Here are the relevant lines of my smb.conf: [global] username map = /etc/samba/user.map workgroup = CDE server string = %h

I am logged on as a domain admin and printer admin. I have created and assigned the correct rights to /srv/printers and have created W32X86 and WIN40 subdirectories. I was able to go into server properties and upload all the necessary drivers. When I right click on the printer and say "No." to "Printer driver not installed, do you want to install the driver now?" the drivers

Before anyone responds I would like to let everyone know my problem is fixed :) The problem was lpr would only spool so big of a file, so I had to add a -s option to it. Thanks once again for this great piece of software... > First of all I would like to thank all the developers and testers for > such a great piece of software. It has simplified my life and made > things much better

Hi there, I have a problem with the rpc driver stuff: I have copied the driver files to //atlas/print$/W32X86 and WIN40 (via filesystem copy), added and set the driver without errors. But getdriver reports no driver associatet with the printer?! So reports below. I am sure, this was working on this system. I tried to reinit the ntprinters.tdb, printing.tdb, nt_forms.tdb and ntdrivers.tdb by

Hi Matt, the problem you referred to is discussed in detail as bug #82 in Samba's bug tracking tool. It consists of 2 bugs. One prevents the registration of drivers and is due to a NULL-pointer passed from that part of code in rpc_server/srv_spoolss_nt.c which calls sys_adminlog function. It begins with the comment /* BEGIN_ADMIN_LOG */ and ends with the comment /* END_ADMIN_LOG */

I'm setting up cups printing with Samba 4.0.5. I downloaded both the windows drivers and the postscript drivers and put them into /usr/share/cups/drivers/. I configured cups through the web interface. Created a printer and printed a test page. I edited smb.conf and put in the necessary entries for cups printing: [global] ... load printers = yes