Listers, I encountered a problem with samba (2.2.7a) when I was setting CUPS (1.1.14) up. I set it up through the web interface, setting the appropriate values in smb.conf: [global] <snip> printing = cups load printers = yes printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes printer admin = @sysadmin use client driver = yes -- I used printconf-tui to set the /etc/printcap, up and it connected and printed the windows test page perfectly. And then it stopped. When I tried the Windows test page again it said the printer didn't exist, so I deleted the entry and tried to re-install the printer, but now it doesn't exist, yet it WILL still print from the CUPS web interface! I went to the console and types 'smbclient -L firewall' and saw all the shares EXCEPT for the printer share. So I decided to run printconf -tui to set it up. How did that go? Not to good. When I attempted to print from there it said "an error was encountered..." So for some reason I can't seem to get the print share to activate. I've rebooted a few times, checked the smb.conf several times, even went into cupsd.conf and didn't find anything different. Now it WAS partially working, by that I mean if I was having permission problems with the directories. I also tried setting 'printcap name = /etc/cups/printers.def, this gave me a share called </printers> which wouldn't connect. Somehow, somewhere I am missing something. Why would Samba NOT set up a share that is defined? Thanks, Kev
> printing = cups...> I used printconf-tui to set the /etc/printcapAs I understand it, CUPS and /etc/printcap don't mix. Typically CUPS is configured with /etc/cups/cupsd.conf (for the daemon, Web interface, etc), /etc/cups/printers.conf for the printer definitions, /etc/cups/classes.conf for the class (pool) definitions, etc. So is lpd running or cupsd? You'll want the cupsd daemon running and then you should be able to interface via a browser to http://<your.host>:631 - similar to the way swat listens on port 901. Then you can define printers, etc through the Web interface and watch what happens in /etc/cups. Hope this helps. -Mike MacIsaac, IBM mikemac at us.ibm.com (845) 433-7061
Message: 5 Date: Thu, 22 May 2003 10:42:55 -0400 From: Michael MacIsaac <mikemac@us.ibm.com> Subject: Re: [Samba] Samba and Cups. To: samba@lists.samba.org Message-ID: <OF3E2214BF.5157E3E8-ON85256D2E.0050312E-85256D2E.0050D5A3@us.ibm.com> Content-Type: text/plain; charset=US-ASCII> printing = cups...> I used printconf-tui to set the /etc/printcapAs I understand it, CUPS and /etc/printcap don't mix. Typically CUPS is configured with /etc/cups/cupsd.conf (for the daemon, Web interface, etc), /etc/cups/printers.conf for the printer definitions, /etc/cups/classes.conf for the class (pool) definitions, etc. --- I tried it this way to get the share to work. As it stands smbclient -L firewall doesnt see it. And I inagine it should with cupsd running. -- So is lpd running or cupsd? You'll want the cupsd daemon running and then you should be able to interface via a browser to http://<your.host>:631 - similar to the way swat listens on port 901. Then you can define printers, etc through the Web interface and watch what happens in /etc/cups. -- Cupsd *is* running lpd is not , the only problem is I cant seem to get an "Unable to connect to CUPS server" in /var/log/cups/error_log. and as far as I cn see, its set up as it should be. Thanks. Kev