[Samba] Samba, CUPS and Windows Printer Queue

[ALLEN, David (Shipley)]

Hi,

I cannot help you, but we have experienced a similar problem with 3.0.2a
running on Solaris and cups. 

Old print jobs remain in the queue, connection to the printers is lost, and
worse, samba crashes for the user, causing Outlook to lock up. As a quick
fix we have deleted the printing lock files in /usr/local/samba/var/locks.

Samba.org have said it may be bug 1147, and recommend upgrading to 3.0.5. If
you find anything else I would be interested.

David

-----Original Message-----
From: Collins, Kevin [mailto:KCollins at nesbittengineering.com]
Sent: 26 July 2004 12:51
To: samba at lists.samba.org
Subject: [Samba] Samba, CUPS and Windows Printer Queue


I've had a Samba 3.0.2 Print Server running for nearly 7 months now without
too much of a hitch on RedHat Enterprise "ES" 3.0.  Late last week, RedHat
issued an Errata that moved Samba from the 3.0.2 base to the 3.0.4 base.  So
when I did the "up2date" this weekend as part of my normal maintenance, this
server was updated and everything appeared to be fine.

Things are working, print jobs are getting sent so for the most part I am
happy.  But, I am experiencing one problem.  The Windows printer queue (I
have a mixed set of clients - mostly Windows 2000 and some Windows XP) show
active jobs even *after* the job has completed.

I've checked the CUPS Web-Management console and there are no active jobs.
Yet on my Windows machine, I have 4 printers that show to have a total of 47
print jobs in the queue.

Here is a snippet of the Print Server's smb.conf:
=================================================
[global]
# Server Name and description
   workgroup = nesbitt.local
   netbios name = valykyrie
   server string = Samba 3 Print and Backup Server

# Samba log information
   log file = /var/log/samba/%m.log
   max log size = 7168

# Security information
   security = user
   encrypt passwords = yes

# To help performance
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Settings for PDC setup
   local master = no
   os level = 0
   domain master = no
   preferred master = no
   domain logons = no

# Activate these Network Services
   wins server = 10.200.8.253

# LDAP Declarations -- Needed to allow the LDAP backend to work
   ldap suffix = dc=nesbitt,dc=local
   ldap admin dn = cn=Manager,dc=nesbitt,dc=local
   passdb backend = ldapsam:ldap://stargazer.nesbitt.local
   ldap delete dn = no
   ldap user suffix = ou=People
   ldap group suffix = ou=Groups
   ldap machine suffix = ou=Computers
   ldap filter = (&(uid=%u)(objectClass=sambaSamAccount))
   ldap passwd sync = yes

# Global settings for printers
   printing = cups
   printcap name = cups
   load printers = yes
   use client driver = yes

# Oplocks settings - disable all oplocks for compatibility reasons
   oplocks = no
   level2 oplocks = no
   kernel oplocks = no

[printers]
   comment = All Printers
   path = /var/spool/samba
   public = yes
   guest ok = yes
   writeable = no
   printable = yes
=================================================

Has anyone experienced this?  What other information is needed to help
diagnose this issue?

Any help would be welcomed...
--
Kevin L. Collins, MCSE
Systems Manager
Nesbitt Engineering, Inc. 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba