[opensuse-factory] Samba issues after snapshot 20160613
Hello! After installing the Samba 4.4.4 update which came with snapshot 20160613 I cannot access my shared folders anymore: I get timeout errors everytime. You can find more details in the bug report I submitted [1]. Is anybody experiencing similar issues? Ciao, Giuseppe. [1] https://bugzilla.opensuse.org/show_bug.cgi?id=986096 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Guiseppe, this has been introduced with the so-called BADLOCK security fixes in Samba some time ago (I believe from Samba 4.4.2). I worked around it adding client use spnego = no to the [global] section in smb.conf. René 2016-06-24 12:04 GMT+02:00 Giuseppe Gorgoglione <gorgogsp@gmail.com>:
Hello!
After installing the Samba 4.4.4 update which came with snapshot 20160613 I cannot access my shared folders anymore: I get timeout errors everytime. You can find more details in the bug report I submitted [1].
Is anybody experiencing similar issues?
Ciao, Giuseppe.
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=986096 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi René, thank you for pointing me to that piece of information. I tried to add that to my smb.conf file, but apparently that's not enough: it just made the smbclient error message to change from "protocol negotiation failed: NT_STATUS_IO_TIMEOUT" to "session setup failed "NT_STATUS_INVALID_PARAMETER". Then searching Samba 4.4.2 release notes [1] for the parameter you cited, I found that they introduced two new configuration defaults: "client ntlmv2 auth = yes" and "client use spnego = yes" So I reverted those, adding both "client ntlmv2 auth = no" and "client use spnego = no" to my smb.conf. This worked fine but I discovered to my utter surprise (ok, I'm not a Samba expert, and the "client" prefix to those parameters should have made me think better...) that they must be added to the client's smb.conf, not to the server's. So now I'm able to access my Linux shares from another Linux box, but still not from Windows, which is my main use case. Then, since those parameters are specific to the SMB1 protocol, I tried to force both the client and the server to use SMB2 or SMB3 as min protocol, but didn't worked. Any idea? Thanks, Giuseppe [1] https://www.samba.org/samba/history/samba-4.4.2.html On Fri, Jun 24, 2016 at 1:03 PM, René Krell <renda.krell@gmail.com> wrote:
Hi Guiseppe,
this has been introduced with the so-called BADLOCK security fixes in Samba some time ago (I believe from Samba 4.4.2).
I worked around it adding client use spnego = no to the [global] section in smb.conf.
René
2016-06-24 12:04 GMT+02:00 Giuseppe Gorgoglione <gorgogsp@gmail.com>:
Hello!
After installing the Samba 4.4.4 update which came with snapshot 20160613 I cannot access my shared folders anymore: I get timeout errors everytime. You can find more details in the bug report I submitted [1].
Is anybody experiencing similar issues?
Ciao, Giuseppe.
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=986096 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Giuseppe Gorgoglione -
René Krell