Re: cups - samba - frustration! - LIKE SOLVED
Hi Clive,
the last 2 hours I set up a new (about the 10th) pure! sarge (doing all
testing in vmware),
installed all the necessary stuff, joined to domain, installed a printer test
under cups and tested it.
then I went on a w2k client, connect to the printers share, uploaded the
windows driver to the samba machine. (This was not possible with an xp-pro
client, don't know why)
tThen from another machine I could connect to the printer and print.
so I think I will have to use this way instead of cupsaddsmb, which is a great
tool and very confortable! I used it the last 2 years on my old samba:
you don't need to install every printer locally on windows before and need
only! a ppd, from linuxprinting or from vendor.
As we will use pykota for accounting, because I cannot way longer for a
running version of the cups driver, I don't need the cupsdriver for
accounting anymore, also if it has the advantage that the users can define
billing per print job.
thank you very! much for your effort and help!!!
angela
Am Dienstag, 10. Januar 2006 18.23 schrieb Clive Menzies:
> Angela Gavazzi wrote:
> > Am Dienstag, 10. Januar 2006 12.10 schrieb Clive Menzies:
> >>http://www.faqs.org/docs/Linux-mini/Debian-and-Windows-Shared-Printing.ht
> >>ml
> >
> > I will have a look at it.
> >
> >>>When I try to prepare the printerdrivers for the windows clients with
> >>>cupsaddsmb "nothing" happens: no error message, "Printer added
> >>>successfully" but not drivers copied to print$ share, no updates from
> >>>ntprinters.tdb, nothing.
> >>
> >>At the risk of asking a dumb question, have you set up the windows
> >>driver sharing within smb.conf?
> >
> > sure [print$] [printers] and necessary permissions. On the post from 2 1.
> > 06 16.17 I attached all the configs if you like to see them
>
> I haven't got a copy of your original post but there is printer share
> section and an additional share for the drivers. I don't use the
> downloadable drivers and have this commented out:
>
> [printers]
> comment = All Printers
> browseable = yes
> printable = yes
> public = yes
> create mode = 0700
> guest ok = yes
> guest only = yes
> use client driver = yes
> path = /tmp
>
>
> # Windows clients look for this share name as a source of downloadable
> # printer drivers
> # [print$]
> # comment = Printer Drivers
> # path = /var/lib/samba/printers
> # browseable = yes
> # read only = yes
> # guest ok = no
>
> >>Also can you print from windows printer setting it up with a driver
> >>sourced from somewhere other than the server?
> >
> > do you meen from windows client to the printer connected to cups with a
> > locally installed driver? Or do you meen if I loaded the windows driver
> > to the server via windows printer wizard?
>
> I just reread what I wrote and it doesn't make much sense to me either
>
> :) What I meant to say was:
>
> Also can you print from a windows 'PC' setting it up with a driver
> sourced from somewhere other than the server?
>
> What I do is install cups on the server with the requisite driver for
> the printer using the cups web interface (using lynx, I don't have a gui
> installed). Test it will print a test page from the web interface.
>
> Set to use the client (in your case windows) driver within the smb.conf
> (see above).
>
> Then set up each individual printer from windows and make sure it will
> print via the server. Typically, I source an appropriate driver for the
> operating system and particular printer. On Windows it's a little
> confusing because you have to select local rather than network printer
> and then configure a new port for the windows/samba share.
> Alternatively, if you explore and then right click on the printer you
> can install from there.
>
> Apologies, if this is 'teaching your grandmother to suck eggs'
>
> I was asking whether you've tried this before attempting to automate any
> driver installation.
>
> Regards
>
> Clive
Reply to: