Samba 3.5.9. We have printers exported to Windows and have the following
options configured:
enable privileges = yes
load printers = yes
printing = cups
printcap name = cups
cups options = raw
[printers]
admin users = @printer-admins
comment = All Printers
browseable = yes
path =
When serving printer drivers to Windows 7 hosts, under what circumstances is
it normal for the Windows clients to be locking driver files? Using
smbstatus, I see clients constantly touching these files, even in cases
where it is highly unlikely that the user is actively installing a printer.
I
On Sat, Dec 25, 2010 at 5:49 AM, Andrew Bartlett abart...@samba.org wrote:
On Fri, 2010-12-24 at 09:17 -0500, Nico Kadel-Garcia wrote:
On Thu, Dec 23, 2010 at 7:00 PM, Matt LaPlante ma...@google.com wrote:
I'm currently compiling Samba 3.3.X with the following:
CFLAGS = -g -Wall -O2
I'm currently compiling Samba 3.3.X with the following:
CFLAGS = -g -Wall -O2
./configure --cache-file=./config.cache \
--with-fhs \
--enable-shared \
--prefix=/usr \
--sysconfdir=/etc \
--libdir=/usr/lib/samba \
I've run into this with every version 3.3. Very hard to isolate. I
suggest adding to https://bugzilla.samba.org/show_bug.cgi?id=7567
On Wed, Sep 22, 2010 at 4:27 PM, Bryan Hodgson hodg...@cse.lehigh.eduwrote:
Same problem (0x03e6) here, W7 (but not XP) 32 and 64-bit
using the Ricoh
I'm using ads security. Everything is working fine, but the logs show that
the samba servers regularly try to authenticate user 'nobody' against the
DC. I know that these are part of standard operation, but it seems
suboptimal to be constantly doing these checks on a large network...
generating
