Displaying 20 results from an estimated 1000 matches similar to: "Adding a cups printer driver"
2003 Feb 20
3
cupsaddsmb - why the heck can't I get rpcclient-addprinter to work?
I can't seem to get the rpcclient-addprinter to work - grrrrrr
It looks like the drivers files are copied correctly and the NT drivers are added
correctly but the addprinter command says it's unsuccessful!
rpcclient localhost -N -U JOHNSON\\root -c 'enumprinters'
shows the printer!!
What's going on? I've tried removing
/var/cache/samba/ntdrivers.tdb
2003 Apr 16
4
driver download problem - win 98 + cups
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
2002 Oct 28
3
Samba, Cups, printer driver download problems
I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running
Solaris 9. Cups has replaced the stock system V lp spooler on this system
(original packages removed.)
Cups working from UNIX command line is A-OK.
I have been working on setting up Samba to play nice with cups. I have
followed the instructions from both the Cups and Samba websites to set up
downloading of the
2003 Feb 11
4
Adding printer driver with cupsaddsmb
-----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:
2003 Jan 06
3
Printer Driver Download Problem - PPD's Not DL'ing
Hey All, just a quick question about printer upload/download stuff
that's been confusing the hell out of me for a couple days...
This might be a Samba, or a CUPS problem, so i've posted this on both
newsgroups, but if anyone's had a similar problem I'd really appreciate
any help!
I'm running Samba 2.2.7 and CUPS 1.1.17 on a RedHat 7.3 System.. I'm
trying to get the
2003 Jun 17
3
cupsaddsmb NT_STATUS_NO_SUCH_DEVICE
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
2006 Sep 01
2
unmodified guests (VMX?) access PCI devices
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello folks
I played a lot with Xen last days,
isnt it possible to access PCI devices which are hidden
from dom0?
I didnt get it - at least my windows domain didnt get it.
Another question:
Im using hvmloader but many pages also talk about the vmxloader,
was it prior the hvmloader coz it doesnt exist anymore?
cheers
- --
Georg
2003 May 29
3
Samba+CUPS+Driver autodownload
Hi,
I'm trying to get Samba to offer the Adobe driver automatically for the
two printers I have set up with CUPS.
I have all of the necessary files plucked out of the Adobe Postscript
Windows driver package, but I'm hitting the problem when I come to run
"cupsaddsmb -v ..." that the "rpcclient adddrivers" command always fails
with NT_STATUS_UNSUCCESSFUL. The drivers
2003 Jun 29
2
rpcclient returns NT_STATUS_NO_SUCH_DEVICE on adddriver
Hi,
samba 2.2.8a freshly compiled
cups 1.1.19final-1 (debian)
while using cupsaddsmb, all runs well until adddriver, when rpcclient
returns a cryptic NT_STATUS_NO_SUCH_DEVICE. I've followed the
SambaPrintHowto 3.0 from 7.11.6.1 to 7.11.6.6, and it fails on the
latest as well.
Here is some more information.
===8<===
cupsaddsmb -a -v
Running command: smbclient //localhost/print\$ -N
2003 Apr 23
1
rpcclient (adddriver: move_driver to_download_area, fail)
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
2004 Apr 01
1
using cupsaddsmb with W98
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
2002 Feb 20
1
a change in rpcclient from 2.2.2 to 2.2.3a
Samba version 2.2.3a doesn't seem to work with the "cupsaddsmb" program
available in CUPS... cupsaddsmb merely runs a few rpcclient commands.
The verbose output from cupsaddsmb is printed below. This output is
from cups version 1.1.14, but I received the same error from version
1.1.12. On 2 different computers - both clean installs. When run on
Samba version 2.2.2, the command
2003 Aug 14
1
Converting smbpasswd from Samba-2.0 to Samba-2.2 ?
Hi,
I have a smbpasswd file from a Samba-2.0.x, generated with pwdump2 [1] . I'm in
a NT-PDC to Samba-PDC migration. The documentation says that it generates
Samba-2.0 style smbpasswd file [2]. But I would like to use the smbpasswd on
a Samba-2.2.x machine.
I've read that smbpasswd format changed . Is there a tool to convert smbpasswd
from 2.0 to 2.2 ? I cannot find one. Any URL or
2002 Nov 20
1
cupsaddsmb failure
When running the cupsaddsmb command, I get the following: Since I am
running as root, what do I not have access to and why?
Any help would be appreciated.
Glen Crowley
<<...OLE_Obj...>>
2002 Nov 06
1
cupsaddsmb: cli_pipe: return critical error. Error was SUCCESS - 0
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
2002 Sep 09
1
cupsaddsmb - problem; once again
Hello,
I posted 2 weeks ago this problem and it is currently not working.
First thanks a lot for all the hints and helps.
In the attached file I have added (hopefully) all informations.
To summarize:
I want to setup a print server, which allows the user to
download the necessary files for new printers.
Installed are (on top of suse 7.1) samba 2.2.6_pre2 and cups 1.1.15_1.
Installed the printers,
2002 Feb 15
4
rpcclient error
Hello all, I'm trying to use CUPSADDSMB to add some printer shares.
Using the verbose output, everything looks good except the following
line.
session setup ok
Domain=[WHEELZ] OS=[Unix] Server=[Samba 2.2.3a]
cmd = addprinter kubrick_linux kubrick_linux "kubrick_linux" ""
addprinter kubrick_linux kubrick_linux "kubrick_linux" ""
result was NT code
2002 Aug 30
1
cupsaddsmb - problem
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
2003 Jul 28
3
cupsaddsmb claims to work but fails
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
2003 May 29
4
Samba+CUPS+Drivers autodownload
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 */