On 08/06/2023 21:19, Marco Gaiarin via samba wrote:> Mandi! sambalsauce1 via samba > In chel di` si favelave... > >> I am running Samba version 4.10.16-24 on RHEL7 kernel 3.10.0-1160. My Windows 10/Server 2019 clients appear to be dropping connection to the shares randomly, within hours to a couple days. There are Windows client event IDs 30808, showing that the connection to the network share is re-established (oddly, there is usually not an event showing that the connection is lost). The clients also show their mapped network drives as disconnected with a red X icon, but they immediately reconnect upon accessing them. I have tried setting smbclient configs with keepconn, sessiontimeout, and extendedsessiontimeout values raised, but it didn't resolve the issue. The server does not appear to have lost network connectivity, but I'll need to try and see if I can verify that 100%. Is there an option in the config file I might need to reconfigure? > > Some users recently complain on Access, i've found: > > https://learn.microsoft.com/it-it/office/troubleshoot/access/your-network-access-was-interrupted-error > https://learn.microsoft.com/it-it/troubleshoot/windows-client/networking/mapped-drive-connection-to-network-share-lost > https://learn.microsoft.com/en-us/azure/governance/policy/samples/guest-configuration-baseline-windows#security-options---microsoft-network-client > > I've tried to set an higher 'AutoDisconnect' timeout, and seems work.It sounds like this is a Windows problem then, but that smb.conf was awful. Rowland
Mandi! Rowland Penny via samba In chel di` si favelave...> It sounds like this is a Windows problem then, but that smb.conf was awful.I've not understood what you mean with 'but that smb.conf was awful', but, anyway, i can confirm that work. I can also suppose that this came from my move from an 'NT-like' domain (eg, SMB1) to an 'AD-like' domain (eg, SMB2+): with the old domain i've no trouble like this, that appear only when i've switched to AD/SMB2. What puzzeled me was the fact that an app like Microsoft Access is not able to do 'keepalive' and i was forced to put share timeout to an indecent amount of time to make it work. I've googled a bit about this (with some difficulty, Microsoft choose 'Access' as the name of their DBMS ;-) but really found nothing. Ok, it is a bit OT, but... if someone have some clue... -- ...e andate chissa` dove per non pagar le tasse col ghigno e l'ignoranza dei primi della classe. (F. Guccini)
Hi Rowland, On 6/8/23 22:49, Rowland Penny via samba wrote:> It sounds like this is a Windows problem then, but that smb.conf was awful.sorry, but I don't think painting someones config as "awful" is in the spirit of: https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely Thanks! -slow -- Ralph Boehme, Samba Team https://samba.org/ SerNet Samba Team Lead https://sernet.de/en/team-samba SAMBA+ Samba packages https://samba.plus/ -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20230613/1844f802/OpenPGP_signature.sig>