Answer the question
In order to leave comments, you need to log in
Why doesn't MS Server 2016 open a Samba SMB2/3 share?
Hello. There is a Windows Server 2016 server, there is a Samba ball on the network (CentOS7, Samba 4.8.3). On Samba, all balls - by password, samba itself - not in the domain, just by login / password.
/etc/samba/smb.conf:
[global]
workgroup = WORKGROUP
server string =
netbios name = kvm1
security = user
map to guest = bad user
passdb backend = tdbsam
guest account = samba_guest
dns proxy = no
log file = /var/log /samba/log.%m
log level = 0
max log size = 50
encrypt passwords = yes
client ntlmv2 auth = yes
lanman auth = no
wins support = no
socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=65536 SO_RCVBUF=65536
case sensitive = no
preferred master = no
use sendfile = yes
client min protocol = SMB2
client max protocol = SMB3
server min protocol = SMB3
[Common]
comment = Common share
path = /samba/share
browsable =yes
writable = yes
guest ok = no
read only = no
Windows 7, 10 quietly enter the balls by login / password, everything is ok. Win Server 2016 cannot enter there. If you make access without a password - everything is OK, it enters. With a password, nothing. Tried enabling insecure guest logins in policies - doesn't help. Where to dig?
Answer the question
In order to leave comments, you need to log in
Everyone, I understand what's going on. On Win, "Network Security: LAN Manager Authentication Level" is set to "Send NTLM response only". And I actually disabled it in the samba config (client ntlmv2 auth = yes). Removed client ntlmv2 auth = yes and set ntlm auth = yes instead. Everything is working. The question is closed.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question