Re: [Samba] samba 2.4.6 to 2.4.7 update on Fedora update 26 to 27, can't connect to shares
- Date: Sat, 03 Mar 2018 11:40:34 +0100
- From: Harry Jede via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] samba 2.4.6 to 2.4.7 update on Fedora update 26 to 27, can't connect to shares
Am Samstag, 3. März 2018, 21:04:09 CET schrieb Norman Gaywood:
> On 3 March 2018 at 20:40, Harry Jede <walk2sun@xxxxxxxx> wrote:
> > Your IM is the source for users and groups and fill both AD and
> > openldap with the identical information. Is this true?
> Yes. Passwords are also managed this way.
> > I think I know this because I can retrieve usernames and SID
> > > info from wbinfo.
> > This is not necessaryly true. I assume your AD and your Samba/Ldap
> > has different domain names and different SIDs.
> wbinfo only gives me information from my AD domain (I think). I'm not
> sure how to query our local samba but I guess the users and where
> they come from was expressed in the deprecated line in my old config:
> auth methods = guest sam_ignoredomain winbind:ntdomain
> > The solution for you could be an other approach.
> > First one question:
> > The subject of this mail indicates that you have problems after
> > updating from Fedora 26 to 27, versus samba 4.6 to 4.7.
> > So, your Fedora 26 setup has worked properly? If this is true, why
> > are you searching for new solutions. You should fix your upgrade
> > procedure.
> Yes the samba broke when I updated Fedora 26 to 27 when samba went
> from 4.6 to 4.7
> My fault for not testing enough. But samba is an add on feature of the
> system and I overlooked it. Roll back is not possible.
> Installing an older samba I guess could be possible but it means
> stepping outside package management.
OK, so you should functional downgrade 4.7 to 4.6. But how?
The first place is https://www.samba.org/samba/history/ here you can dig
through the release notes and watch for changes in params (smb.conf)
and code. You must know the point releases in use.
Simple and fast approach, which in the past was often succesfull, compare
the param default settings of the build version.
testparm -s -v /dev/null |sort >smb.conf.default.4.6.1
on new server
testparm -s -v /dev/null |sort >smb.conf.default.4.7.2
and diff it.
> > Greeting
> > Harry Jede
To unsubscribe from this list go to the following URL and read the