[Samba] Windows clients require reboot once a day in order to access mapped drives

Mason Schmitt mason at ftlcomputing.com
Thu Apr 25 03:29:25 UTC 2019

> At this point I'm starting to get in over my head and could use some
> direction.  This looks like a Windows 10 client bug, but given that I can't
> see the full SMB conversation (due to encryption) I'm not certain whether
> the samba server is replying in the way the client expects.  Can you or
> someone else help me either find a work around or a resolution?  Because
> the Windows 7 clients (SMB2 not SMB3) don't exhibit this behaviour, I'm
> thinking that forcing all clients to downgrade to SMB2 would probably work
> around the issue.  Can you confirm this?  If not, I can just try it and see
> what happens.

I added "server max protocol = SMB2" to my smb.conf file.  After restarting
smbd, I tried to connect using a windows 10 client and was denied (error
message on the client and server says that a parameter is incorrect).  I
rebooted the PC and tried again.  No go...  So apparently it's not possible
to force W10 to downgrade to SMB2?

I'm really hoping someone is able to give me something to go on here,
because now I'm really stuck....


More information about the samba mailing list