[Samba] 3.6.0 winbind issues
esiotrot at gmail.com
Thu Aug 18 04:32:32 MDT 2011
On 18 August 2011 11:11, Linda Walsh <samba at tlinx.org> wrote:
> Michael Wood wrote:
>> P.S. Sorry for the mostly off-topic post.
> If it's mostly not about samba, it's probably 'ok' t0 NOT cc the list..?
True, but I didn't want other people thinking I might have hidden
messages in my post if they could only find them ;)
> Turning off that param, BTW, did help -- some things that hadn't been
> working started, and then gave all sorts of new indications of
> With that param on, and due to going to winbind as primary resolver
> before local hostfiles, the server and Win7 WS couldn't do name lookups,
> but could still do UID/SID lookups...so that's been going on since June.
The above confuses me. Winbind is not used for hostname lookups as
far as I'm aware. I don't use winbind, though, so I'm not sure what
"local hostfiles" have to do with it. When you say the server and
Win7 WS couldn't do name lookups, are you referring to user/group
names or host names?
> I tried to revert to 3.5.10, but as 3.6 had already mangled the DB, it was
> still mangled w/3.5x...
I still think it's rather unexpected that the DB should have been
mangled and I suspect that if it can be reproduced, the Samba
developers would be very interested.
> It's been one long ongoing problem since I upgraded my server's OS
> -- so many pieces of new SW had compat problems w/previous versions
OK, so it sounds like there could be just about anything wrong with
the OS and/or Samba as a result of all this :)
> (samba was only one, but has proven to be one of the more difficult ones to
> get back 'just right'... -- probably partly to do with my having a manually
> allocated, static TDB for the most part. ... so it turning off that param
> allowed my server to be able to comminicate w/itself, and the Win7
> WS now has a a happy schannel again, though some reminants of the
> up-cased dom/hosts still linger in some DB's -- had to make sure my
> /etc/lmhosts file was read BEFORE netbios (nmbd)...as also forces
> name-changes ... *sigh*...
You've lost me. I haven't gone back to read all your previous posts
(just the one on the 3rd) so I don't remember all the history.
Is there any chance you can try installing Samba on another machine/VM
and get it working there?
I suspect it will be less time consuming to start over that to figure
out what's wrong with your current installation. Of course I don't
know if that's feasible given your existing
Michael Wood <esiotrot at gmail.com>
More information about the samba