[Samba] oplocks and Excel

2006-01-26 Thread Matt Morgan
I have a small business client with a new samba file server. It's
CentOS 4.2 and Samba samba-3.0.10-1.4E.2.

When they save open Excel files from Windows, they are prompted to
overwrite the existing file. I mean, when they click the little disk
icon or use Ctrl-S or File--Save. Excel would normally just write over
the file, not check with an are you sure? prompt. But that's what
they get.

So I looked into this a little, and although I can't find anyone with
this specific issue, I do see that newer versions of Excel create a
bit of file-locking trouble for samba. Now, I don't know enough to
know whether my problem has anything to do with file-locking, but it
seems likely enough. So I have two questions:

1) I find very conflicting opinions on this list, and across the net,
about whether to leave oplocks and level2 oplocks on. I have never had
to touch them in the past, but most of the places where I've used
samba have old versions of Excel and/or OOo. If this place does not
use much MS-Access, can I turn off oplocks? Might I expect doing so to
help with this prompt-to-overwrite problem?

2) More generally, has anyone else seen this problem before and been
able to do anything about it?

Thanks,
Matt
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Samba w/o local users on Samba server?

2005-06-06 Thread Matt Morgan
On 6/6/05, Robert Schuettler [EMAIL PROTECTED] wrote:
 Hi everyone,
 
 is it possible to have a Samba server without creating local accounts
 for users on that server?
 
 Share level security doesn't count though. ;-) The idea is not to need
 to create and update users on the Samba server itself (i.e. no local
 users, no entries in /etc/passwd, etc).
 
 The documentation says something about  Domain and ADS level security
 being basically just forms of user level security, so - for the moment-
 it looks to me as if there's no way around creating those local users.
 Is that correct?

Not quite, but you can save a few steps if you have some easy 
dynamic way to create  maintain the local users.

We do linux auth against ADS with a combination of winbind, kerberos,
pam_mkhomedir (to auto make the home dir), and pam_mount (to
mount/unmount the shares automatically without the user needing root
access, and no prior modifications to fstab). With that we have what
you want, but it was pretty hard to set up. (I didn't do it--it was
our genius network admin doing a ton of reading and a lot of trial and
error. But we're not the only ones who've done it.)
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Samba w/o local users on Samba server?

2005-06-06 Thread Matt Morgan
On 6/6/05, Matt Morgan [EMAIL PROTECTED] wrote:
 On 6/6/05, Robert Schuettler [EMAIL PROTECTED] wrote:
  Hi everyone,
 
  is it possible to have a Samba server without creating local accounts
  for users on that server?
 
  Share level security doesn't count though. ;-) The idea is not to need
  to create and update users on the Samba server itself (i.e. no local
  users, no entries in /etc/passwd, etc).
 
  The documentation says something about  Domain and ADS level security
  being basically just forms of user level security, so - for the moment-
  it looks to me as if there's no way around creating those local users.
  Is that correct?
 
 Not quite, but you can save a few steps if you have some easy 
 dynamic way to create  maintain the local users.
 
 We do linux auth against ADS with a combination of winbind, kerberos,
 pam_mkhomedir (to auto make the home dir), and pam_mount (to
 mount/unmount the shares automatically without the user needing root
 access, and no prior modifications to fstab). With that we have what
 you want, but it was pretty hard to set up. (I didn't do it--it was
 our genius network admin doing a ton of reading and a lot of trial and
 error. But we're not the only ones who've done it.)

Oh, I just read John Terpstra's response and realize that the OP was
asking about servers. I, of course, described how we do it for clients
(linux desktops on an ADS network). So, don't take my advice in this
case! (but pam_mkhomedir and pam_mount are really, really cool).
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] very slow writes from samba client to samba server

2005-04-11 Thread Matt Morgan
I'm running Fedora Core 3 on two machines; a server and a client. On
the server, I have the package samba-3.0.10-1.fc3 installed; I assume
this means I have samba version 3.0.10. On the client, I have
samba-client-3.0.10-1.fc3, i.e., the same version.

On the same network, I have a Windows XP home machine that connects to
the same shares as the FC3 client machine.

Reading and writing files on the WinXP machine to and from the server
works perfectly. Reading files stored on the server from the FC3
client machine also works fine. But when I try to write files from FC3
client to FC3 server, it takes a very long time. Extremely long, like
 1mbit/s, and this is a 100mbit/s network. Actually, it takes so long
that for a file of any real size (1Mb+) the copy/save errors out
before the writing is done.

I have googled this issue, and written to fedora-list, but nothing is
helping so far. All the advice suggests that this is a master-browser
collision problem. So I edited my smb.conf files accordingly (setting
the os_level, etc. lower in the client), but that didn't help. Here
are my smb.conf files anyway, just in case I've done something wrong.

On the server (I've removed all commented lines for brevity):
-
[global]
   workgroup = CONCRETE
   netbios name = ONE
   server string = Samba Server
   hosts allow = 192.168.1. 127.
   printcap name = /etc/printcap
   load printers = yes
cups options = raw
 log file = /var/log/samba/%m.log
   max log size = 50
   security = user
  encrypt passwords = yes
  smb passwd file = /etc/samba/smbpasswd
   create mask = 0644
   directory mask = 0755
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   local master = yes
   os level = 33
   domain master = yes 
   preferred master = yes
   wins support = yes
   dns proxy = no 
   idmap uid = 16777216-33554431
   idmap gid = 16777216-33554431
   template shell = /bin/false
   winbind use default domain = no
[homes]
   comment = Home Directories
   browseable = no
   writable = yes
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   guest ok = no
   writable = no
   printable = yes
[Music]
   comment = Music
   path = /home/music
   public = yes
   read only = no
   valid users = amy matt
   writable = yes
   create mask = 666
   directory mask = 777
   guest ok = no
--
And on the client:
---
[global]
   workgroup = CONCRETE
   netbios name = MATT
   server string = Samba Server
   printcap name = /etc/printcap
   load printers = yes
cups options = raw
 log file = /var/log/samba/%m.log
   max log size = 50
   security = user
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   local master = no
   os level = 3
   domain master = no 
   preferred master = no
 name resolve order = wins lmhosts bcast
   wins server = 192.168.1.1
   dns proxy = no 
   idmap uid = 16777216-33554431
   idmap gid = 16777216-33554431
   template shell = /bin/false
   winbind use default domain = no
-
Any advice? 

Thanks a lot,
Matt
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba