samba - Oct 2016 - samba 4.5.0 strange windows 10 issue | incorrect password

See inline comments:

On Tue, 18 Oct 2016 07:49:39 -0700 (PDT)
yabko via samba <samba at lists.samba.org> wrote:
> smb.conf
> 
> [global]
>         workgroup = WMPNY
>         realm = WMPNY.LAN
>         netbios name = PDC
>         server role = active directory domain controller
>         dns forwarder = 8.8.8.8
> #167.206.112.138
>         log file = /var/log/samba/samba.log
>         max log size = 10000
>         log level = 3
>         idmap_ldb:use rfc2307 = yes
>         ldap server require strong auth = no
>         lanman auth = yes
>         ntlm auth = yes
>         raw NTLMv2 auth = yes
OK, I can understand adding 'ldap server require strong auth', but why
add 'lanman auth', 'ntlm auth' and 'raw NTLMv2 auth' if
all your
clients are using windows 10 ?
> 
>         allow dns updates = nonsecure
> 
> [netlogon]
>         path = /usr/local/samba/var/locks/sysvol/wmpny.lan/scripts
>         read only = No
> 
> [sysvol]
>         path = /usr/local/samba/var/locks/sysvol
>         read only = No
> 
> [profiles]
>         path = /usr/local/samba/var/profiles
>         read only = No
> 
> [home]
>         path = /home/home
>         read only = No
>         vfs objects = acl_xattr recycle
>         recycle:keeptree = yes
>         recycle:versions = yes
>         recycle:maxsize = 1073741824
> 
> 
> uname -r
> 
> 2.6.32-5-amd64
This is a very old kernel, if you were to upgrade to wheezy, you would
get 3.2

Rowland

Rowland

Some of our older Network scanners scanning to samba shares (addc has few
shares available) were using the old smb protocol so i've read that these
settings had to be enabled for it to work. Since then i believe we've
updated firmware on them to handle newer SMB protocols so i'll try to take
these out and test again

I guess i'll have to update it first and see. I just don't want the
upgrade
process to break the samba. Would it be "safer" to create another DC
and
join rather than doing in place upgrade ?



--
View this message in context:
http://samba.2283325.n4.nabble.com/samba-4-5-0-strange-windows-10-issue-incorrect-password-tp4709799p4709844.html
Sent from the Samba - General mailing list archive at Nabble.com.

On Tue, 18 Oct 2016 09:03:18 -0700 (PDT)
yabko via samba <samba at lists.samba.org> wrote:
> Rowland
> 
> Some of our older Network scanners scanning to samba shares (addc has
> few shares available) were using the old smb protocol so i've read
> that these settings had to be enabled for it to work. Since then i
> believe we've updated firmware on them to handle newer SMB protocols
> so i'll try to take these out and test again
> 
> I guess i'll have to update it first and see. I just don't want the
> upgrade process to break the samba. Would it be "safer" to create
> another DC and join rather than doing in place upgrade ?
> 
It is perfectly safe to upgrade Samba in place, but it would be even
better to add another DC ;-)

Rowland