Re: [SLE] Re: [Samba] Re: [SLE] Samba, CUPS, or ?

From: M. Halegua (phantom21_at_mindspring.com)
Date: 09/24/04

  • Next message: Carlos E. R.: "Re: [SLE] Postfix question" 
    To: suse-linux-e@suse.com
Date: Thu, 23 Sep 2004 20:01:03 -0400

    David,

    the stuff you gave me worked!!

    I edited the smb.conf file by adding lines you had I didn't, and made sure the
    permissions were the same, and printers.conf was good, and

    VOILA!!! :-)

    I and my client are very happy.

    Thank you.

    Mark

    On Wednesday 22 September 2004 14:34, David Rankin wrote:
    > Here is my working setup with 9.0 and samba 3.0.7. I have a LJ_4 attached
    > to the server and 2 XP clients
    >
    > Relevant parts of smb.conf
    >
    > # Global parameters
    > [global]
    > min print space = 2000
    > printing = cups
    > printcap name = cups
    > print command = /usr/bin/lp -d%p -oraw %s; rm %s
    > lpq command = /usr/bin/lpstat -o%p
    > lprm command = /usr/bin/cancel %p-%j
    > queuepause command = /usr/bin/disable %p
    > queueresume command = /usr/bin/enable %p
    >
    > [printers]
    > comment = The Printers
    > path = /var/spool/samba
    > guest ok = Yes
    > public = Yes
    > writeable = no
    > printable = Yes
    > browseable = no
    >
    > skyline:/var/spool # cat /etc/cups/printers.conf
    >
    > # Printer configuration file for CUPS v1.1.19
    > # Written by cupsd on Mon 17 May 2004 06:57:09 PM CDT
    > <DefaultPrinter HP_LJ4>
    > Info HP Laserjet 4
    > Location
    > DeviceURI parallel:/dev/lp0
    > State Idle
    > Accepting Yes
    > JobSheets none none
    > QuotaPeriod 0
    > PageLimit 0
    > KLimit 0
    > </Printer>
    >
    > Now for the spool directory permissions:
    >
    > skyline:/var/spool # ls -al
    > drwx--x--- 3 lp lp 3096 Sep 22 00:17 cups
    > drwxrwxrwt 2 root root 48 Sep 22 00:17 samba
    >
    > That's it - and it works fine from XP clients
    >
    >
    > --
    > David C. Rankin, J.D., P.E.
    > RANKIN * BERTIN, PLLC
    > 510 Ochiltree Street
    > Nacogdoches, Texas 75961
    > (936) 715-9333
    > (936) 715-9339 fax
    > www.rankin-bertin.com
    > --
    > ----- Original Message -----
    > From: "M. Halegua" <phantom21@mindspring.com>
    > To: <suse-linux-e@suse.com>; <samba@lists.samba.org>
    > Sent: Wednesday, September 22, 2004 12:00 PM
    > Subject: [Samba] Re: [SLE] Samba, CUPS, or ?
    >
    >
    > I don't believe the problem is with CUPS itself as the printer does print
    > locally from the command line and from scripts.
    >
    > If the CUPS daemon was going dead, printing wouldn't work at all.
    >
    > Since the issue is also that windows systems (which now include XP Pro and
    > XP
    > Home laptops I tested on the network) AREN'T SEEING THE PRINTER IN ANY
    > NETWORK BROWSING COMPONENT -- NETWORK NEIGHBORHOOD, ADD A PRINTER, ETC. --
    > it
    > leads me to believe the problem is with Samba in some way.
    >
    > Since the same system displays other shares (directories and the pdf
    > printer)
    > the question is why it won't show the laserjet printer.
    >
    > Today I tried sonething else. I deleted the printer and reinstalled it
    > using
    > YaST (which calls CUPS). The printer again worked locally, but didn't
    > display during windows discovery.
    >
    > I've looked at the logs, they don't indicate any problem. What I'll do is
    > copy the logs and include them in my next plea for help.
    >
    > Can anyone point to something I'm not getting here?
    >
    > Mark
    >
    > On Monday 20 September 2004 02:57, Richard wrote:
    > > On Monday 20 September 2004 01:18 am, M. Halegua wrote:
    > > > I've been going over a problem and haven't been able to resolve it.
    > > >
    > > > I think I've narrowed the problem down to Samba, but I could use some
    > > > advice on this.
    > > >
    > > > A few weeks ago I installed a print and fax server for a client. I used
    > > > an old PII system with 64 MB RAM, SUSE Pro 9.1, configured to use Samba
    > > > and HylaFAX. There are 8 client workstations running Window 98 SE (most
    > > > of the systems are PII and PIII, so Win98 is the best solution for
    > > > now).
    > > >
    > > > After getting the kinks out it worked perfectly for about 1.5 weeks.
    > > > Then, one of the people used a different system and sent a print job
    > > > from a DOS app through a captured printer port. The printer driver was
    > > > for a Brother HL-1440 laser, but the job was going to a HP LaserJet 5Si
    > > > (the printer connected to the print/fax server).
    > > >
    > > > It spewed garbage until one of the users finally went to the printer
    > > > and cancelled the job. Since then most of the users can't print from
    > > > either Windows or DOS apps to the 5Si. And sometimes some of them can,
    > > > but they lose the capability later. Sometimes they get an error message
    > > > "invalid access code" or a system error.
    > > >
    > > > The reason I think it's Samba is, none of the systems see the printer
    > > > in network neighborhood. They DO see the system, a couple of folders
    > > > I've made available for admin and testing purposes, and the pdf printer
    > > > Samba has, but no longer see the 5Si, which they should see as
    > > > hp_laserjet5si.
    > > >
    > > > I've checked to see, through ldd, the proper linking of Samba to the
    > > > required printing and CUPS libs. They're there. The printer works
    > > > properly from the server itself from the command line and from within
    > > > scripts (the client wanted the faxes to print automatically upon
    > > > receipt, and they continue to print out properly).
    > > >
    > > > I looked in /var/spool/samba and I saw a number of files, with the
    > > > usernames of the people who submitted the jobs, and the group users.
    > > > But all the files were 0 bytes. When I tried to print one from the
    > > > command line, it gave a stdin nothing found message (approximate
    > > > message, I forget the word for word).
    > > >
    > > > If it was one system, I'd guess a windows problem. But the browse and 0
    > > > byte for printer jobs is .... unusual. I've never seen Samba do this
    > > > before.
    > > >
    > > > I've reset the server (not necessary, I know, but just in case) and
    > > > manually restarted the Samba (smbd, nmbd) daemons, the windows systems
    > > > still don't see the printer.
    > > >
    > > > To add to the issue, a file server set up a couple of years ago with
    > > > SUSE 7.3 Pro is at Samba 2.2. Thinking this may be a conflict between
    > > > Samba versions on the same network, I shutdown the file server,
    > > > shutdown and restarted the print/fax server, and restarted the windows
    > > > workstations. This didn't help.
    > > >
    > > > As a last try, thinking the print/fax server itself may have some
    > > > problem, and to eliminate it as a variable, I set up a different system
    > > > and set it up as the first print/fax server and the same thing
    > > > happened.
    > > >
    > > > I'm totally stumped on this.
    > >
    > > I just had a rather perplexing problem with one machine printing which
    > > may give you something to think about.
    > >
    > > The machine would not print. I ran and reran the cups installation and
    > > each time the daemon would die. During the setup it would detect the
    > > correct printer but would not print at all. I kept getting an error
    > > message telling me some spool file was to long.
    > >
    > > I ran across a thread on SLE with the subject Suicidal cups daemon.
    > >
    > > in it Johannes Meixner gives a 'brutal method' to do a complete
    > > reinstallation of cups..
    > >
    > > I did it and it succeeded in getting cups to working again.
    > >
    > > The steps are simple:
    > >
    > > -stop cupsd
    > > -uninstall the cups packages (I used yast)
    > > -remove the contents of /etc/cups/* (but not /etc/cups/)
    > > -remove the /var/spool/cups/ and /var/log/cups/ directories
    > > -make sure that permissions, group and owner of /etc/cups/ is drwxrwxr-x
    >
    > lp
    >
    > > lp
    > > -re-install the cups packages
    > > -start cupsd
    > >
    > > That solved my two days of frustration. Dont know what was wrong but it
    > > sure fixed the problem for me. Maybe it can help you by giving you a
    > > fresh start.
    > > Richard
    > > --
    > > Old age ain't for Sissies!
    >
    > --
    > To unsubscribe from this list go to the following URL and read the
    > instructions: http://lists.samba.org/mailman/listinfo/samba 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Carlos E. R.: "Re: [SLE] Postfix question"

    Relevant Pages

    • Re: File permissions when ftp
      ... But yes both users were using sftp in all ... > the same permissions as the original file on the source computer. ... > Regular ftp clients don't usually do this. ... file and still have Apache act normal not giving the 403 error. ...
      (Fedora)
    • server 2008 / vistax64 client shared folder permissions issue
      ... I am having issues with shared file permissions using server 2008 and vista ... Here is my setup. ... I only have 3 clients connected to the server. ...
      (microsoft.public.windows.server.networking)
    • Re: NETLOGON Errors on clients
      ... next guess would be permissions. ... The preceeding article explains where and ... All the clients show up fine. ... in the event log I am seeing these NETLOGON errors. ...
      (microsoft.public.windows.server.active_directory)
    • Re: Organizational Forms Libray Setup on Server - Not Available on Clients
      ... The symptoms would indicate that the permissions are not set right, regardless of what the verifier said. ... Sue Mosher, Outlook MVP ... > Outlook 2000/2/3 Clients ...
      (microsoft.public.outlook.program_forms)
    • Re: [opensuse] CUPS server problem
      ... with a number of systems all running the CUPS daemon as clients on one system running the CUPS daemon as both a client and server. ... On all the systems except the server I can bring up the CUPS configuration info, in Firefox, at localhost:631 but on the server I get a 404 Not Found error. ...
      (SuSE)