samba - Aug 2019 - Stale Microsoft Office temp files

Hi.

We're having a strange issue: we have several office temp files left around
even when files get closed.
Right now there are no open files on Samba, but there are more than twenty lock
files around.

So, given that the file has been accessed correctly by the user and has been
correctly saved (no data loss has been reported), what could prevent Office from
deleting its files?
Any suggestion on where to look at to debug the issue?

Thanks

This wasn't happening with Samba 3.x.

Samba 4.3.11-Ubuntu. 
Config follows:

 [global]
     server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd,
ntp_signd, kcc, dnsupdate
     realm = brivaplast.lan
     ldap server require strong auth = no
     netbios name = SMBSERVER
     workgroup = DOMAIN
     server role = active directory domain controller
     log level = 5
     idmap_ldb:use rfc2307 = yes
     log file = /var/log/samba/log.%m
     ea support = yes
 [users]
          path = /home/users/
          read only = no
 [profiles]
    comment = Users profiles
    path = /home/profiles
    read only = no
     browsable = no

 [CONDIVISI]
 path = /home/CONDIVISI
 read only = No

-- 
Lorenzo Milesi - lorenzo.milesi at yetopen.it

YetOpen S.r.l. - https://www.yetopen.it/
Via Salerno 18 - 23900 Lecco - ITALY -
Tel +39 0341 220 205 - Fax +39 178 6070 222

Think green - Non stampare questa e-mail se non necessario / Don't print
this email unless necessary

-------- D.Lgs. 196/2003 e GDPR 679/2016 --------
Tutte le informazioni contenute in questo messaggio sono riservate ed a uso
esclusivo del destinatario.
Tutte le informazioni ivi contenute, compresi eventuali allegati, sono da
ritenere confidenziali e riservate secondo i termini
del vigente D.Lgs. 196/2003 in materia di privacy e del Regolamento europeo
679/2016 - GDPR - e quindi ne e' proibita l'utilizzazione ulteriore non
autorizzata.
Nel caso in cui questo messaggio Le fosse pervenuto per errore, La invitiamo ad
eliminarlo senza copiarlo, stamparlo, a non inoltrarlo a terzi e ad avvertirci
non appena possibile.
Grazie.

Confidentiality notice: this email message including any attachment is for the
sole use of the intended recipient and may contain confidential and privileged
information;
pursuant to Legislative Decree 196/2003 and the European General Data Protection
Regulation 679/2016 - GDPR - any unauthorized review, use, disclosure or
distribution
is prohibited. If you are not the intended recepient please delete this message
without copying, printing or forwarding it to others, and alert us as soon as
possible.
Thank you.

On 12/08/2019 13:56, Lorenzo Milesi via samba wrote:
> Hi.
>
> We're having a strange issue: we have several office temp files left
around even when files get closed.
> Right now there are no open files on Samba, but there are more than twenty
lock files around.
>
> So, given that the file has been accessed correctly by the user and has
been correctly saved (no data loss has been reported), what could prevent Office
from deleting its files?
> Any suggestion on where to look at to debug the issue?
>
> Thanks
>
> This wasn't happening with Samba 3.x.
>
> Samba 4.3.11-Ubuntu.
> Config follows:
>
>   [global]
>       server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbindd, ntp_signd, kcc, dnsupdate
>       realm = brivaplast.lan
>       ldap server require strong auth = no
>       netbios name = SMBSERVER
>       workgroup = DOMAIN
>       server role = active directory domain controller
>       log level = 5
>       idmap_ldb:use rfc2307 = yes
>       log file = /var/log/samba/log.%m
>       ea support = yes
>   [users]
>            path = /home/users/
>            read only = no
>   [profiles]
>      comment = Users profiles
>      path = /home/profiles
>      read only = no
>       browsable = no
>
>   [CONDIVISI]
>   path = /home/CONDIVISI
>   read only = No
>
OK, I give in, where did the 'netlogon' & 'sysvol' shares go
?

You appear to be trying to use a Samba AD DC as a standard Samba server, 
What OS is this on ?

I would start by upgrading everything, 4.3.11 is very old and is EOL

I would also add a Unix domain member, a Samba AD DC used as a 
fileserver works very differently from a Unix domain member.

Rowland