Re: upgrading to latest samba

[steve%prd.co.uk@localhost (Steve Blinkhorn)]

I upgraded to Version 4.6.8 of the samba suite from the Q1 binary
collection for amd64 (7.0), and have finally got back to the condition
I was in vis a vis my Windows 10 box before it got stroppy and refused
to connect either way.   I found the following:

The libraries were installed into /usr/pkg/lib/samba/private, where
they were inaccessible to the binaries.   I made hard links for them
in /usr/pkg/lib.

The smb password file was either trashed or became inaccessible.
Whichever, I had to "smbpasswd -a unsername" for each account.

I have yet to get a satisfactory result from setting the protocol in
smb.conf, so to star the daemon I do "smbd -D --option=protocol=SMB3".

For smbclient I use "smbclient -m SMB3 -U myuser //mywindowsbox/Users"

My use of Samba is not at all complex - basically just file access
between one Windows box and a handful of NetBSD machines - so I
haven't by any stretch of the imagination tested things thoroughly.
But I though it might be useful to record this in case anyone else is
struggling.

--
Steve Blinkhorn <steve%prd.co.uk@localhost>

I wrote:
> 
> So I did that, and now:
> 
> %smbclient -U myuser //mymachine/myshare
> Shared object "libreadline.so.7" not found
> 
> So I made a symlink to what is in /usr/pkg/lib. namely
> libreadline.so.6.0.3 and then
> 
> %smbclient -m SMB3 -U myuser //mymachine/myname
> 
> works. But without the -m SMB3 (or SMB2) it doesn't.
> 
> In the other direction I have tried "min protocol = SMB3" in the
> [globals] section of the smb.conf file, also max protocol = SMB3
> and just plain protocol = SMB3, but to no avail, all with kill -HUP
> on the smbd processes after the changes. But with
> 
> %smbd -D --option=protocol=SMB3
> 
> at least Windows gets on to the stae of asking for credentials.   But
> so far I haven't worked out why it doesn't accept my credentials.
> 
> In the pkg_add process, all the samba man pages disappeared, so I am
> having to piece things together from Linux web sites.
> 
> --
> Steve Blinkhorn <steve%prd.co.uk@localhost>
> You wrote:
> > 
> > On Tue, May 22, 2018 at 11:22:37AM +0000, Steve Blinkhorn wrote:
> > > My Windows 10 box has decided to stop talking to my NetBSD boxes over
> > > samba, so I am trying to upgrade to the most recent version.  But:
> > >  
> > > %pkg_add -U -U samba-4.6.8nb5
> > > pkg_add: Package `samba-4.6.8nb5' conflicts with `tdb-[0-9]*', and
> > > `tdb-1.3.3' is installed.
> > > pkg_add: 1 package addition failed
> > > 
> > > Is this a regexp/glob thing?   I tried updating tdb first, but that
> > > failed too.
> > > 
> > > -- 
> > > Steve Blinkhorn <steve%prd.co.uk@localhost>
> > > 
> > 
> > not justifying the behaviour, just explaining what is happening (maybe a
> > better behaviour can be done):
> > samba(3.*) depends on tdb
> > samba4 has builtin tdb and explicit CONFLICTS on tdb.
> > 
> > so if samba and tdb are removed, samba4 can be installed without
> > complaints from pkg_ tools.
> > 
> 
>