[Samba] Time out tuning ?

[david.j as]

From: "Mitch (WebCob)" <mitch at webcob.com>
To: samba at lists.samba.org
Date: Mon, 28 Feb 2005 09:19:31 -0800
Subject: RE: [Samba] Time out tuning ?
> Hello,
>
> I have a samba server running at a customer site and they have the
> follwing problem:
> Employees of that company have for extended periods sometimes
> word documents opened for editing, but it happens regularly that
> for an half hour or more no activity takes place because they are
> working on something else (it's a flower seed growing company , with pc's
> in the glasshouses and they have to monitor the seedbeds and fill in
> now and then something in in word documents). When that happens
> the word application returns a message that , "There was a sharing
> violation"
,.....
> Is this caused by a time out on the server? or the client? Is it possible
> to configure the samba server to forcefully keep the connection between
> the
> client and the server alive?

>[Mitch says:] Are there any VPN's, smart switches or routers involved?

>I've not seen any app timeout problems with my servers, but I know that some
>routers or VPN arrangements have short timeouts / lack keep alive and can
>cause this sort of behaviour.




We have this same exact problem in an networked environment where
clients are connected to a Samba server that is hosting to multiple
subnets.    I've been trying to debug this for over a year without
success.  It seems that if one user has a word document open for an
extended amount of time Windows will corrupt the file.  Also, if file
explorer is open on a share for an extended amount of time it will
show  a disconnected dialog box.  The network switches we have here in
the network are configured to forward broadcast packets from our main
server to all other subnets and samba is configured to advertise in
these subnets specifically, however, this doesn't seem help.

Is there anything wrong with this smb.conf file that might be causing this?


[global]

        workgroup = NDGENG
        server string = B2 Samba 
        log file = /var/log/samba/log.%m
        max log size = 50

        log level = 3

        security = user

        encrypt passwords = yes
        smb passwd file = /etc/samba/smbpasswd
        unix password sync = Yes
        passwd program = /usr/bin/passwd %u
        min password length = 8
        passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*passwd:*all*authentication*tokens*updated*successfully*
        username map = /etc/samba/smbusers

        remote announce = 192.168.3.255 192.168.7.255 192.168.11.255
192.168.15.255

;       os level = 255

        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
SO_KEEPALIVE IPTOS_LOWDELAY

        preferred master = yes
        domain master = yes
;       local master = yes

        wins support = yes

;       wins server = 192.168.0.4

        time server = no
        dns proxy = yes

        preserve case = yes
        short preserve case = yes

        default case = lower



;       try to fix "lease broken - owner pid = ????" syslogs (JB 10/27/04)
;       http://www.spinics.net/lists/samba/msg27983.html

        kernel oplocks = false

;       try to fix file corruption (TW 09/01/04)

        oplock break wait time = 50
        lock spin count = 50
        lock spin time = 30

        debug level = 2



[homes]
        comment = Home Directories
        browseable = yes
        read only = no
        create mode = 0700