similar to: Raw Printing, was cupsaddsmb and .inf files

Hi, I've also got problems downloading drivers from samba to a windows client. I'm running Debian Samba 3.0.7-1, and Cupssys 1.1.20final My Windows Client is a Win2KPro. I succesfully installed my printers with Cups and they work fine under Linux, and from remote cups clients. I've been trying to follow the samba docs on serving postscript drivers for cups from the print share in

Hi All, I was recently directed to look at some upstream CUPS changes which impact Samba's printer server functionality: cupsaddsmb has been dropped via https://github.com/apple/cups/commit/f1def5b85f51120f5dc1eb21e1f38860ef41be9c Given that it's only just gone in, I wouldn't expect it to reach distros for some time, but I think it's worth discussing how/whether we should react.

Hi All, I have Samba 3.0.22-1ubuntu4 running on Ubuntu 6.01 (eft) and am trying to add printers using cupsaddsmb. On running it I get the following: root@pykota:/home/printeradmin# cupsaddsmb -U root -a -v Password for root required to access /var/run/cups/cups.sock via SAMBA: Running command: smbclient ///var/run/cups/cups.sock/print$ -N -A /var/spool/cups/tmp/454b654e20cfa -c 'mkdir

HI! I've a problem with cupsaddsmb!! :-( At the console I type: cupsaddsmb -U root -v <printername> and after some operations complete correctly appear this error: [...] Running command: rpcclient localhost -N -U'root%' -c 'adddriver "Windows NT x86" "eps6100l:cupsdrv5.dll:eps6100l.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"' cmd = adddriver

I'm trying to add a printer to Samba 2.2.4, using the cupsaddsmb tool provided with CUPS. cupsaddsmb basically invokes samba's rpcclient program.. The driver part installs fine using cupsaddsmb, but addprinter always fails for some reason. This is what cupsaddsmb returns, does anybody have any idea as to what is wrong?? If I invoke rpcclient manually with a debug level of 10, it goes

This is probably a CUPS bug but maybe not, I'll mention it here just in case. When using cupsaddsmb to install 64bit drivers the drivers must be in the (maybe distro/configure dependent): /usr/share/cups/drivers/x64 to be sure that's "x64" with a lower case "x". The cupsaddsmb app ignores the drivers if the subdirectory is named with an uppercase "X" (X64).

Hello, I tried to find a way to having the setup of cups printing working for windows client. I end up now with "cupsaddsmb -v -a -U root" finishing by "Printer Driver mesange successfully installed. Running command: rpcclient localhost -N -U'root%xxxxxxxx' -c 'setdriver mesange mesange' cmd = setdriver mesange mesange result was NT_STATUS_UNSUCCESSFUL" My

I can't even get cupsaddsmb to work right. I followed the configuration instructions from the documentation, and my smb.conf matches what the cupsaddsmb man page says. I am getting extremely frustrated with this and not being able to allow clients to download drivers from Samba. With cupsaddsmb, this is the error I am receiving when it gets to this point, over and over: Running command:

Hi, I'm having a strange problem with cupsaddsmb ... it fails whenever I try to use it while using the rpcclient command ... the "addriver" command just fails (like below). Does anyone know what is wrong with the command cupsaddsmb is passing to rpcclient? Adding drivers through the windows point and print works fine ... this is samba 2.2.8a, Windows PDC. As far as I can tell,

> [Samba] cupsaddsmb adobe error message > Sundaram Ramasamy sun at percipia.com > Fri Mar 12 04:18:05 GMT 2004 > > > Hi, > > I am trying to add automatic driver install, its giving me ADOBEPS5.DLL > file not found error message. > You should read the man page of "cupsaddsmb". It would tell you that the preparation to be completed *before* running the

Guys, I need a clue here. The command I am using is: cupsaddsmb -H kaliklak -U Administrator -h kaliklak -v Lex_Z53 and despite the fact that the password used is correct the result is: [root@kaliklak root]# cupsaddsmb -H kaliklak -U root -h kaliklak -v Lex_Z53 Password for root required to access kaliklak via SAMBA: Running command: smbclient //kaliklak/print\$ -N -U'root%XXXXXXXXXX'

As an update to fix the badlock vulnerability I applied some updates to our (RHEL5-based) samba printer server last night, taking it from version 0:3.5.10-0.109.el5_8 to 0:3.6.23-12.el5_11 (rpm package versions). After this change attempts to add printer drivers with cupsaddsmb produced errors of the form: Running command: rpcclient localhost -N -A /tmp/cupsc7GVnF -c 'adddriver

hi! i've a problem with my samba server and the cupsaddsmb tool for windows nt4.0 clients. I'm using cups 1.1.22 and samba 3.0.20b! the problem is, if i do a cupsaddsmb printer it will generate a directory with the drivers for windows. these drivers works perfectly with Win2000 Xp but they don't work with Win NT4.0! i used the cups-samba-1.1.19.tar.gz package to install the cups

I'm getting ready to migrate my office of 50+ Windows XP machines to Windows 7, in a mix of 64-bit and 32-bit clients. I've setup a new samba server on a separate domain to prepare and test for this transition. I've gotten everything to work so far except for printing, and I'm at a loss on how to proceed. It appears to me as if adding the printer drivers in the usual way,

Hey everyone. Having a little problem getting cupsaddsmb to work correctly. I have been reading throw the Samb 3 book today as i am trying to have the ability for drivers for our printers to be automatically downloaded when a client adds the printer. I am using: FreeBSD 4.10 samba 2.2.11 cups 1.1 cups-samba I put the following info in smb.conf: [printers] comment = All printers

Base: Red Hat RHAS3, PDC security = user Samba 3.0.14a Cups 1.1.17 Windows XP Pro Epson C42UX (cheap inkjet) USB to the server I was looking for an alternative to the immensely complicated Add Printer Wizard procedure (APW) detailed in chapter 19.6 of the Samba HOWTO guide. The following is a method that works for me, I don't necessarily expect it to work for others, and I'd value any

Hi. Im trying to get cups-printing to work on samba 3.0 - RH9. We are having NT WTS Metaframe servers as the "client" But when running command cupsaddsmb -U root -a -v i get the following error: Warning: No PPD file for printer "printername" - skipping! I have copied over theese files to \usr\share\cups\drivers before running the command [Windows NT, 2000,

when i run this: # cupsaddsmb -H localhost -U root -a -v i get absolutely no ouput my drivers in /usr/share/cups/drivers are as follows: cups6.inf cups6.ini cupsps6.dll cupsui6.dll ps5ui.dll pscript5.dll pscript.hlp pscript.ntf what could be wrong???

Hi People, Trying to be as informative as possible: I'm trying to add printers drivers to cups-owned, samba shared printer. Called "PDF-Creator" But when I issue the command "cupsaddsmb -U root -v PDF-Creator" I get a "NT_STATUS_LOGON_FAILURE" Weird thing is: I was able to do this a few months ago. But I noticed the drivers where missing when I wanted to add

Hi all, I'm trying to add printers with cupsaddsmb on Samba 3.0.20 (Mandrake Linux) with an LDAP backend. I've followed the howto on the samba page and have the error: result was WERR_INVALID_PRINTER_NAME generated when I run it. So far I've Googled for the solution but nothing listed has helped. The full set of errors are as follows: Cupsaddsmb returns: