similar to: adddriver rpc command generates segmentation fault

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:

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

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:

Has anyone had any success installing windows printer drivers onto a leopard-hosted print$ share? If I use the Add Printer Wizard method, if copies the driver files to \ \SERVER\print$\W32X86 then fails with an "Operation cannot be completed." If I use the rpcclient method I get a WERR_INVALID_PARAM error. Using the Adobe Generic PostScript driver as an example.

Hello, My commandline looks like this: rpcclient localhost -d4 -c 'adddriver "Windows NT x86" "HPLJ4050:PSCRIPT5.DLL:HPLJ4050.PPD:PS5UI.DLL:PSCRIPT.HLP:NULL:RAW:PSCRIPT.NTF,PSCRPTFE.NTF"' The output is: Serverzone is -3600 Initialising global parameters params.c:pm_process() - Processing configuration file "//etc/samba/smb.conf" Processing section

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

[root at samba ~]# cupsaddsmb -U administrator -v hp4 Password for administrator required to access localhost via SAMBA: ********************* Running command: smbclient //localhost/print$ -N -A /tmp/075335545d5bf -c 'mkdir W32X86;put /tmp/07533554ccef1 W32X86/hp4.ppd;put /usr/share/cups/drivers/ps5ui.dll W32X86/ps5ui.dll;put /usr/share/cups/drivers/pscript.hlp W32X86/pscript.hlp;put

Hello, I have set up a cups print server and would like to offer Point'n'Print functionnality for the windows computer clients. So, i've followed informations from the man page of cupsaddsmb as resumed below: -configure smb.conf -add x86 and x64 PS drivers (from x86 and x64 windows 2008 installs). -add x86 and x64 CUPS drivers (from cups SVN) I then launch cupsaddsmb using the

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

Hello all, I'm running Samba 3.5.5 on Debian 5, and following the documentation as closely as I can to install drivers using rpcclient. I first install the driver on a Windows 7 x65 workstation, then use rpcclient/smbclient to fetch the files. I then use smbclient to put those on the print$ share of the Samba server. So far, so good. Then I use rpcclient to add those files, and that

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 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 , i am trying to add a driver to windows using the smbclient and rpc commands [got those from cupsaddsmb -v commands] and i am getting : smbclient //localhost/print$ -U $PASS -N -c ' mkdir W32X86;put GENERIC.ppd W32X86/GENERIC.ppd;put /usr/share/cups/drivers/ps5ui.dll W32X86/ps5ui.dll;put /usr/share/cups/drivers/pscript.hlp W32X86/pscript.hlp;put /usr/share/cups/drivers/pscript.ntf

Hi list I have two very similar printers set up on CUPS and Samba is configured to share the drivers. I had been playing around with setting up a RAW printer queue with native Windows drivers but eventually gave up on that. I deleted all printers and redid them from scratch and now only one of them works. Setup: Ubuntu Karmic 2.6.31-15-server #50-Ubuntu SMP Tue Nov 10 15:50:36 UTC 2009

I'm not having any luck using the rpcclient adddriver functions to install windows point-and-print drivers into print$. The add printer wizard fails after copying the files to \\SERVERX\print $\W32X86 so I am trying to install using rpcclient to see if it tells me anything more. I'm using the cups v6 drivers to test with. I get the same thing trying my HP Laserjet 2100 drivers.

Hi all, Samba 3.0.7 and using CUPS printing. I am logged in as root to an XP Pro system, I have used the APW to install the XP drivers to all of my printers. I went to Shared and clicked "Additional Drivers" and checkmarked both 9x and NT/2K boxes. Using drivers straight from the HP website, the 9x driver installs fine, but it seems like I can't get any NT/2K drivers to

Hi All, My problem is that when I "connect" a printer by right-clicking it on \\smbhost\printers (on a Windows client), it seems to install the printer fine (without error), but I can't print (it seems to print, no error message or so, but it never makes it to the printer). I was able to install the printer drivers both via the Windows GUI (wizard) and via rpcclient (please see

Cups 1.2.7 Debian Etch with Samba 3.0.24 Clients: WinXP SP3 (with Firewall completely off for testing) When I define a printer specifically in smb.conf, they show up as shared printers in WinXP. But when I follow the normal way (see below) to load all from cups they don't. I followed mainly the latest SAMBA-HOWTO (chapter 21-22) The only error I see in log.smbd when accessing the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello, i see a strange behavior on my samba 3.0.11 on solaris 8 when i install printer-drivers fir win-clients. 1. i ask the win-server for the drivers and get a huge list of depend files: # /usr/local/samba/bin/rpcclient -c 'getdriver "SLA D91 Xerox 4500" 3' - -U xxx xxx [Windows NT x86] Printer Driver Info 3:

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