SMB1 Locked file for roaming clients

[Uri Simchoni]

Thanks! This does not seem applicable to my case as the roaming client
gets a different IP address. However I think it validates the analysis
that it's an smb1 issue, best solved by moving to smb2.

On Thu, Jun 18, 2015 at 1:42 PM, Volker Lendecke
<Volker.Lendecke at sernet.de> wrote:
> On Thu, Jun 18, 2015 at 01:01:38PM +0300, Uri Simchoni wrote:
>> Hi,
>>
>> I have an issue with samba 3.3.16-based smb servers and roaming
>> clients. When clients roam to a different IP address (e.g. moving the
>> laptop to a different floor), suddenly their excel/word files cannot
>> be saved because "someone else is editing them".
>>
>> With SMB2 the problem is not reproduced - looks like durable file
>> handles fix this. With latest samba, the problem is reproduced if the
>> connection is limited to SMBv1.
>> The way I figure it:
>> - Office opens the document file for r/w with share read.
>> - Client disappears - does not properly close the file.
>> - Client opens a new session, again trying r/w
>> - smbd has no way of knowing that this is the same application
>> instance that's re-opening the file, especially if it comes from a
>> different IP address. It therefore considers this as a sharing
>> violation.
>>
>> Would it be correct to say that this is an SMB1 limitation, and is
>> there any known workaround for this using smb1?
>
> We have "reset on zero vc = yes" for this. Not sure when
> this went in tough.
>
> Volker
>
> --
> SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
> phone: +49-551-370000-0, fax: +49-551-370000-9
> AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
> http://www.sernet.de, mailto:kontakt at sernet.de