cupsaddsmb

Anonymous anonymous at easysw.com
Sun Jan 9 16:10:57 PST 2005


anonymous wrote:
> hi,
>   i have exactly the same problem i would like to know if you found a solution.

Which version of Samba are you using? Which version of CUPS? Which version of Operating System?

> please send a posting i already tested the ppd file and it got a
> PASS.
> Erik wrote:
> > Hello everybody, I'm new to Linux and building up a Linux
> > printserver for our Win 2000 domain.
> > If I install the printers on the Linux machine everything works
> > fine.
> > Now I'm trying to make samba offer the drivers for the windows 2k
> > terminalserver.
> > Uploading via the "Add printer wizzard" on the Windows machine
> > ends up in "The drivers for HP Business Jet 2280, Windows 2000,
> > Intel could not be installed".
> > Using cupsaddsmb brings:
> >
> >
> > linux:~ # cupsaddsmb -a -v
> > Password for root required to access localhost via SAMBA:
> > Running command: smbclient //localhost/print\$ -N -U'root%xxx' -c 'mkdir W32X86;put /var/spool/cups/tmp/40c2f3114fa36 W32X86/Tintenstrahler.ppd;put /usr/share/cups/drivers/cupsdrv5.dll W32X86/cupsdrv5.dll;put /usr/share/cups/drivers/cupsui5.dll W32X86/cupsui5.dll;put /usr/share/cups/drivers/cups5.hlp W32X86/cups5.hlp'
> > Domain=[LINUX] OS=[Unix] Server=[Samba 3.0.2a-SUSE]


Sorry. You are using a very ancient release of Samba. The only thing
to do here is paraphrase something "pipitas" recently wrote here (and adapt it to your case of Samba:

# Please read this document first:
#
#    http://us4.samba.org/samba/history/samba-3.0.10.html
#
# to decide wether you really want to stay on a Samba version that has seen
# 10 bugfix releases since 3.0.2a.
#
# If you dont have the time to read this link (I could fully understand
# that :->  ), please try to count all occurences of "print", "driver", "lp"
# or "spool" enumerated there.
#
# If you're guess is similar to mine, you'd say "more than 110", roughly 90%
# of these since 3.0.2 was releaed. Ask yourself if you want to go on and
# live/work without 100+ bug-fixes provided, features added, enhancements
# developed, security-issues resolved by continuing to use 3.0.2?
#
# If you say, "I'll rather stay with 3.0.2" you are throwing away the last
# 12 months of wonderfull work the Samba developers have provided for you for
# free  ;-)
#
# Honestly, I dont think that there is anybody on this list/newsgroup, nor
# the Samba one, who could be motivated to put time and energy into
# investigating an obscure bug that happens on your old system, when they
# all have newer ones themselves.

> > NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
> > putting file /var/spool/cups/tmp/40c2f3114fa36 as \W32X86/Tintenstrahler.ppd (70.5 kb/s) (average 70.5 kb/s)
> > putting file /usr/share/cups/drivers/cupsdrv5.dll as \W32X86/cupsdrv5.dll (1455.8 kb/s) (average 791.9 kb/s)
> > putting file /usr/share/cups/drivers/cupsui5.dll as \W32X86/cupsui5.dll (1729.0 kb/s) (average 1031.5 kb/s)
> > putting file /usr/share/cups/drivers/cups5.hlp as \W32X86/cups5.hlp (278.0 kb/s) (average 961.1 kb/s)
> >
> > Running command: rpcclient localhost -N -U'root%xxx' -c 'adddriver "Windows NT x86" "Tintenstrahler:cupsdrv5.dll:Tintenstrahler.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"'
> > result was DOS code 0x00000042

BTW, try to use only 8 characters for your printer name -- your "Tintenstrahler" has 14, and that wont work for the Win95/98/ME clients






More information about the cups mailing list