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

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

i meant upgrading the OS (squeeze) that samba4 is compiled on, rather than
installing new OS (jessie) with samba4 on and joining as new DC. if i go
with another DC route would it matter if samba4 is compiled or installed
from a package or should i compile it like on the first initial DC?



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

On Tue, 18 Oct 2016 09:38:31 -0700 (PDT)
yabko via samba <samba at lists.samba.org> wrote:
> i meant upgrading the OS (squeeze) that samba4 is compiled on, rather
> than installing new OS (jessie) with samba4 on and joining as new DC.
> if i go with another DC route would it matter if samba4 is compiled
> or installed from a package or should i compile it like on the first
> initial DC?
> 
Sorry, in that case I would go with a new DC and compile Samba
yourself, that way you will get a supported OS and an up to date Samba.

Rowland