![](https://seccdn.libravatar.org/avatar/482b6c0369f4709de8faa6843cd6b347.jpg?s=120&d=mm&r=g)
On lundi, 27 juin 2016 17.59:21 h CEST Giuseppe Gorgoglione wrote:
Right, I my case the server is my Tumbleweed box itself, now running Samba 4.4.4, the client is a Windows 10 box. During the session, they exchange SMB2 packets with protocol dialect 2.02 or higher.
I don't know why "client ntlmv2 auth = no" and "client use spnego = no" were helping to some degree. Maybe the hostname resolution request is part of the ntlmv2 authentication or some other step which is skipped with those options.
Anyway, the main point here is that if you have a local samba server with a static hostname, which is a quite common setup if you want to share files in a home network, you have to set /etc/hosts accordingly. It was not clear to me.
Cheers, Giuseppe
On Mon, Jun 27, 2016 at 5:07 PM, René Krell <renda.krell@gmail.com> wrote:
2016-06-27 16:25 GMT+02:00 Giuseppe Gorgoglione <gorgogsp@gmail.com>:
Ok, I found a fix and I'm writing about it here just in case anybody is experiencing the same. ...
I stopped it just adding one line in /etc/hosts: 127.0.0.1 nausicaa
Now the access to the network shares are immediate and reliable, and "client ntlmv2 auth = no" and "client use spnego = no" are no longer needed to me.
Ok, in this case your server "speaks" a newer protocol, not NT1, right?
Certainly because you should always have a working dns system. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org