similar to: cupsaddsmb

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 try to set up a samba print server with cups, but when i use the cupsaddprinter command, all copy start & stop with no problem, and when the rppcclient command is launch to add the printer driver, it fails and show me this error: # cupsaddsmb -v -U root -a [...many lines...] result was WERR_INVALID_PRINTER_NAME I try to find somthing on the net and other ML & i find this to

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:

Hi, I'm trying to set up a samba-cups-pdf-printserver. samba itself is running fine, but when i try to add the cups printer-drivers for windows i got the following error: System: Debian/sarge with 2.4.20 i686 GNU/Linux samba 3.0.2-2 cupsys 1.1.20final-13 Windows-driver from cups-samba-5.0rc1.tar ssflx01_v2:~# cupsaddsmb -a -v -U uuuu Password for uuuu required to access

Greetings ... I'm using the "cupsaddsmb" to upload the CUPS printer drivers onto my Samba server, but seem to be having problems with new printer queues. I find if that I reload Samba, the upload works fine, otherwise I get "result was WERR_INVALID_PRINTER_NAME", which I think maybe Samba needs to ask CUPS if the queue is new or something. Could any boby help

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 have the following setup. Samba/LDAP PDC, Samba BDC, Samba member server, Win2K member server, 300 Win XP Client PCs. I can access the shares on the PDC from all Win XP clients. I can access the shares on the Win2K member server from all XP clients, I can't however access any of the shares on the Samba BDC or Samba member server from the XP clients. LDAP is working fine and

SUSE 9.1 samba-3.0.9-2.6 samba-client-3.0.9-2.6 I am getting some errors that I can't seem to track down in any of the archives. I came across this problem when trying to delete a driver none of the printers are listed in the smb.conf - it is all being generated from the cups and the printcap that cups makes on load First enumprinters works: rpcclient $> enumprinters

Hello. I've been trying to set CentOS 3.1 as a print server for PC running NT4 using Samba + CUPS. I've successfully done this with Fedora Core 1 but have encountered the following error after running cupsaddsmb in CentOS 3.1: WERR_INVALID_PRINTER_NAME. This error also occurs with FC1, but is solved by restarting the smb service i.e. service smb restart. Run cupsaddsmb again after

Hi all, I encountered a bug, that prevents me from moving mail and as a side effect it messes up all thunderbird/mozilla mail clients (they won't do any message copy/move until I restart them). Here is the info and the header of the mail that produces the error (a spam mail): Dovecot version: 1.0.0 Mail header: Return-Path: <xxdwwu at boboakes.com> Delivered-To: bgs-hu-bgs at

Hi List, I've just updated from Samba 3.0.33 to 3.5.6 on my Centos 5.5 PDC and am having problems accessing home directories. To allow a backout option I set up a new server, put 3.0.33 on it, joined it to the domain and rsynced the home directories over with the flags necessary to maintain the permissions and user/group ownership. This worked and after completion I upgraded the new

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

Hi all, I have a Samba PDC running on OpenSuSe 10 with LDAP as the backend and am running Mandriva 2006 as a member server with a few shares for users. The PDC seems OK and I've added the member using the instructions in the Samba example documents and I'm at the following point: OpenLDAP is running on the PDC itself. I can login to Linux as any LDAP user account suggesting that NSS

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

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