I have a Linux box that connects to a shared folder on a Windows 7 desktop. When the Windows computer goes to sleep and then resumes, the share is no longer accessible. If I reboot the Linux computer, the Windows share becomes accessible again.
The share is mounted by a systemd automount unit. Once the Windows box has gone to sleep and resumed, if I try to cd to the mount point of the share, I get a "Host is down" message.
If I run smbclient -L xxx.xxx.x.xx -U user -d 256 the share is visible in the list but at the end are the errors:
SPNEGO login failed: The transport connection has been reset.
session setup failed: NT_STATUS_CONNECTION_RESET
Why does the share become accessible again when I reboot Linux?
_update I'm adding info to my own question. I've tried all the power options I can find in Windows 7 and in my (updated) NIC driver. No help.
I've updated samba. I've also tried several different approaches to mounting, including with and without automount and adding "noperm" and "_netdev" to the mount command in fstab. I've tried enabling winbind and adding "wins" to the nsswitch.conf file.
Still the share mounts on a reboot, but gets lost after a short time, even if the Windows host doesn't go to sleep. If I unmount and try to remount the share, I get a "no such file or directory" error.
But I can connect to the share with smbclient with no problem.
To me all this suggests that the problem is at least partially with Linux, but I'd still like to hear any suggestions as to possible Windows settings that might be contributing. TIA
