similar to: Cupsaddsmb only running "setdriver"

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,

Hi Kurt, You are absolutely right (as always). After restarting smb, rpcclient setdriver works fine. May be - in the next future release - cupsaddsmb will work. Thank you very much. Bernhard -----Urspr?ngliche Nachricht----- Von: Kurt Pfeifle [mailto:kpfeifle@danka.de] Gesendet: Samstag, 8. M?rz 2003 12:06 An: samba@lists.samba.org Betreff: [Samba] rpcclient setdriver fails:

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

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

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).

Dear list, I've upgraded my server from Etch to Lenny and now the printer (HP LaserJet 6P) does not work any more through Samba. Printing a testpage via http://server:631 works perfectly so I skip giving details about the CUPS setup. Also lpstat reports the printer working # lpstat -a HP_LaserJet_6P accepting requests I tried to rerun cupsaddsmb. The driver files are copied to the

hi, my boxes: RH 8.0 with samba2.2.6-2 and cups 1.1.15-10 samba runs ok and cups runs ok.I putted Adobe Postscript Printer in /usr/share/cups/drivers. And when I want to export my Cups Printer with cupsaddsmb, this what it happens: [root@bouffon sbin]# cupsaddsmb -H bouffon -U DOMAINNAME\\root -h bouffon -v infolpPassword for DOMAINNAME\root required to access bouffon via SAMBA: Running

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

Hello, I'm trying to use rpcclient 'setdriver' as an unprivileged user; a special lpadmin user with very limited rights has been created, and ownership of the location of driver files (/home/PrintDrivers) given to him. when executing the smbclient and rpc commands like cupsaddsmb does, nearly everything works fine, except the last command: when i issue an rpcclient localhost -U

Hello, I want to setup a new print server using cups and samba for our new institue. Everything is working well (printing from unix and windows), but the driver download for the windows clients won't work and I have no idea what's wrong. Currently i have installed cups-1.15 and samba 2.2.5 on top of suse 8.0 using the rpm-files from Lars Mueller(?)(ftp.suse.com/pub/people/lmuelle) and

Hello, I am using cups-1.1.19final-1.deb and samba-2.2.3a. When I was working with cups-1.1.15 before, cupsaddsmb worked fine, but now with cups-1.1.19 it gives me: Running command: smbclient //localhost/print\$ -N -U'root%secret?' -c 'mkdir WIN40;put /var/spool/cups/tmp/3eef829eea1b8 WIN40/ps948esb.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put

Case strange... I've past probably 30 hours by now on this, crawling the web, and doing attempts. I managed to make cupsaddsmb run without producing an error, but it fails. Ask me for anything, full trace, versions and so on, but please, if someone has an idea, share it. ============================================ Linux Debian Woody unstable Cups 1.1.19final-1 Samba 2.2.3a-14

Hi all, I have a similar problem as Patrik yesterday. So I can copy some lines, but not all. We have an SuSE 8.1 machine who acts as an printserver. I'm sharing printers via Samba and using CUPS. Samba is 2.2.7a and CUPS 1.1.8. The Microsoft clients (Win9x, Win NT, Win 2k) is downloading the driver from the server. I had no problem to install and upload up to 2 printers but now I am not

Hi all, I'm getting WERR_ACCESS_DENIED error for some of the printers when running setdriver printer_name printer_driver as part of the cupsaddsmb step. Weirdly, it works for some printers, and never works for others, while all the printers have the same settings. Samba 3.5.20 with CUPS 1.5.4. Does this part of log give any clue of why could this happen? function print_access_check() --

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:

Hello, when i send the SIGHUP signal to Samba, then Samba won't load the printers from CUPS. I need to shutdown Samba and start it again. Now when i'am running cupsaddsmb i got the following errors(this error occours in 3.5.x but not in 3.2.x): server-p:/# cupsaddsmb -H server-p -v edv01 edv02 edv03 Kennwort f?r root erforderlich, um ?ber SAMBA auf server-p zugreifen zu k?nnen:

Hi all, I have a problem with adding point and print to a print server. The server details are as follows: 700MHz Celeron + 384MB RAM Mandriva LE2005 (Mandrake 10.2) Samba 3.0.13-2mdk CUPS 1.1.23 cups drivers 10.2-0.11 gimpprint-cups 2-1.1.23-11 foomatic 3.0.2-1 The server is bound to an NT4 based domain (to be replaced with Linux/Samba in the summer) and winbind works fine with wbinfo -u and

I have built a new CUPS print server on Ubuntu 8.04 server for our office (used apt-get to download the CUPS v 1.3.7 and Samba v3.0.28a packages) as a replacement for our existing Suse CUPS print server and I want to use the cupsaddsmb tool to set up printer drivers for download by PCs rather than using the Add Printer Wizard method which we have used on our older CUPS print server. After some

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