On March 6, 2017 8:17:37 PM GMT+01:00, Grant Edwards <grant.b.edwa...@gmail.com> wrote: >On 2017-03-06, J. Roeleveld <jo...@antarean.org> wrote: >> On March 6, 2017 5:14:39 PM GMT+01:00, Grant Edwards ><grant.b.edwa...@gmail.com> wrote: >>>On 2017-03-06, Kai Krakow <hurikha...@gmail.com> wrote: >>> >>>>> I'm going to try to set up a Wireshark capture in ring-buffer mode >>>and >>>>> somehow detect the failure and stop the capture... >>>> >>>> Did something on the Windows side change? >>> >>>Probaby, but I've learned not to ask questions like that. They never >>>get answered, and it just causes problems when it is revealed that >the >>>client having problems is a Linux machine. >>> >>>> Maybe force Windows down to a lower SMB version or reduce/disable >>>> SMB client side caching? >> >> Windows sharing is designed as a 'link when used' option. Not as a >> permanent mount like Linix treats it. >> >> Even 'mounting' in Windows doesn't mean the share is actually >> accessed. >> >> A windows CIFS server will not be reliable enough for long term >> mounting. With Samba, it does work more reliable. (In my experience) > >It's worked perfectly fine for 10+ years, and apparently continues to >do so for other Linux users in the office.
And trying to troubleshoot it is not simple. Especially as MS Windows event viewer never shows anything remotely useful. (I tried to troubleshoot various issues, never got anything usefull from the windows admins or event viewer) How do the other Linux users access the shares? >> For this reason, I use KDE/Dolphin to access CIFS shares. It is >> closer to how Windows expects the shares to be treated. > >I don't see how things like shell scripts or other applications that >need to access files on the CIFS mounts would use something like that. Did you test if a small script that touches a file on the share every minute resolves the issue? -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
