My mistake, i was talking all the time about smbspool, which is not included in
mandrake.
Too bad, since it is the only way to print from cups to smb printers...
From the cups manual:
<quote>
Printing to Windows Servers
CUPS can print to Windows servers in one of two ways. The first way uses the LPD
protocol
on the CUPS system and the "TCP/IP Printing Services" on the Windows
system. You can find out more about this configuration in the LPD section earlier in
this
chapter.
The second way is through the Microsoft Server Message Block ("SMB") protocol. Support
for
this protocol is provided with the free SAMBA software package. You can
download SAMBA from:
http://www.samba.org
To configure CUPS for SAMBA, run the following command:
ln -s `which smbspool` /usr/lib/cups/backend/smb ENTER
The smbspool(1) program is provided with SAMBA starting with SAMBA 2.0.6. Once you
have
made the link you can configure your printers with one of the following
device URIs:
smb://workgroup/server/sharename
</quote>
I already pointed this list to this problem once, to no avail. Redhat is doing a
better
job at this.
This is even more strange, since cups is going to be the default printing system for
Mandraks, IIRC.
Rgrds,
Moshe Vainer
[EMAIL PROTECTED]
Reinhard Katzmann wrote:
> Hi Moshe!
>
> > > Well actualy mandrake DOES include smbprint in its samba package, and I have
> > > it installed.
> > >
> > > [root@dark /root]# rpm -qf /usr/bin/smbprint
> > > samba-client-2.0.6-4mdk
> > >
> > > SHadowX
> >
> > But not in latest cooker - (samba-client-2.0.7-7mdk)
> > The only way it worked for me was to install
> > samba-client-2.0.7-4utmp from Redhat.
>
> No, you're wrong here definitifely. I just checked myself
> (and smb printing works for me at office):
>
> [root@linux cups]# rpm -qf `which smbprint`
> samba-client-2.0.7-7mdk
> [root@linux cups]#
>
> Maybe something is wrong with your samba-client-package,
> so you might want to reinstall it.
>
> > Anyway, it is easily tested by the command you just provided,
> > so to the original poster, you can use
> > #rpm -qf /usr/bin/smbprint
> > to see if you have smbprint in your samba-client package.
> >
>
> It works for me :) Hopefully ShadowX can test if smbprint itself
> works, before seeking the problem within cups.
>
> Best regards,
>
> Reinhard Katzmann
> --
> E-Mail: [EMAIL PROTECTED]
