similar to: AIX 7.1 Samba4.10.6 missing library

Sorry... A couple more questions... I've installed krb5-libs and krb-workstation... this is all I need? I ask because the krb5 config file was not created on the system... One was "installed" to /opt/freeware/etc/krb5.conf, which could be copied over... Do I need to install samba-winbind-krb5-locator? Thank you for everything! Regards, Bob Wyatt -----Original Message----- From:

Thanks to you and Louis for your guidance. I really apologize for my lack of knowledge of AD and Samba; and I appreciate your patience and willingness to help. And I apologize for not trimming the reply - don't know how much to retain... The referenced document seems to be leveraging domain services that we're not using. We are only using AD user authentication to access shares on AIX. No

Thanks again for the continued help... Current thinking is using rid for the backend does not place any new administrative functions on the staff - agree? Begs questions of what is being written in smbpasswd, and do we have administrative work on AIX? Such as adding users and a group or two in the range specified for idmap? A mapping "table"? If rid is hands-off administration,

The below Globals section is reporting some testparm failures that don't make sense to me. Perhaps someone could shine a light for me? This is a new installation - from 3.6.23 to 4.10.6-1. Necessitated by a Windows Server 2016 DC being installed. The testparm command, when run, reports the following error(s): # testparm Load smb config files from /etc/samba/smb.conf Loaded

Hi sambalist, I'm using sernet samba for several years. I found that there's error in the log.samba file like this: [2019/07/10 14:55:25.892988, 0] ../../lib/util/fault.c:79(fault_report) =============================================================== [2019/07/10 14:55:25.893187, 0] ../../lib/util/fault.c:80(fault_report) INTERNAL ERROR: Signal 11 in pid 9906

Reindl/Harald, What is your first name? Sorry for asking, but always wondered about it. I just wanted to note here that... 1) I have seen this also if samba is upgraded and not restarted. Or 2) if a packages is not upgrade because an extra package is also needed at install. And that should be tested/checked/tried out first and if that all fails, then its needed to contact sernet support.

Rowland, If you were up for another hint at rid versus ad... I'd like to understand a bit more. With rid, I map the administrator to root only... no mapping of users in AIX. How does Samba figure out that bobw at mydomain.com should use the samba user ID bobwsmb? If I use ad, I would use rfc2307 attributes to address that (I think). It seems more "specific" to use ad, but

Rowland, The wiki suggested doing "smbd -b | grep HAVE_LIBACL" and expecting to get back "HAVE_LIBACL". This is not the case on our IBM system with 4.10.6. The current version from IBM is 4.10.13 - considering upgrading in the hopes "HAVE_LIBACL" is present if I really need it. On the other hand, "smbd -b" does report that smbd was built with vfs_aixacl

Hello, according to this: https://gitlab.com/samba-team/samba/merge_requests/26 samba should support DNS record scavenging is this only true for the internal DNS or also BIND? Should this work? I enabled it (dns zone scavenging = yes) to try it out and got this (didn't enable it from the DNS Manager tool as I got the error first): Jul 24 16:39:20 dc1 samba[29071]: [2019/07/24

Please disregard unless this conclusion is wrong. We would be running in AD mode, not NT4 mode with Server 2016. Regards, Bob Wyatt From: Bob Wyatt <bwyatt_sub at comcast.net> Sent: Tuesday, April 21, 2020 4:32 PM To: 'sambalist' <samba at lists.samba.org> Subject: Samba 4.10.13-1 as a domain member, AIX 7100-05-05 In perusing Red Hat manuals for a

In perusing Red Hat manuals for a different issue with Red Hat, this was in their RHEL 7 documentation: You can run Samba as: * An Active Directory (AD) or NT4 domain member * A standalone server * An NT4 Primary Domain Controller (PDC) or Backup Domain Controller (BDC) NOTE Red Hat supports these modes only in existing installations with Windows versions which support NT4 domains.

Has anyone successfully installed and configured Samba as a domain member from the various RPM's offered from the IBM Toolbox website? Can you offer any advice for getting it up and running? Any advice would be greatly appreciated. Here was my last post latish Friday night US Eastern Time. ====================== Posted some time ago on 4.6 - updated it to 4.10.13-1 as released by IBM.

Sorry for all these replies, i missed this. > Is the upgrade path from samba 4.6 + libldb 1.1 to samba 4.6 + libldb 1.3 No, that wil break your samba!!! Samba 4.6 max 1.1.29 for ldb. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Vincent S. Cojot via samba > Verzonden: woensdag 18 april 2018 14:06 >

Hi Rowland, Yes, that's right (Thank you). Here is what happened: On the DC's, libldb was this version on el7.4: - libldb-1.1.29-2.el7_4.wing.x86_64 (from Wing's repo). el7.5 brought in a more recent version: - libldb-1.2.2-1.el7.x86_64 - libldb-1.2.2-1.el7.i686 What would be the best course of action here? A) Downgrade el7.5 to libldb-1.1.29-2.el7_4.wing.x86_64? B) rebuild

On 05/02/2020 00:25, Bob Wyatt via samba wrote: > The below Globals section is reporting some testparm failures that don't > make sense to me. > > Perhaps someone could shine a light for me? > > > > This is a new installation - from 3.6.23 to 4.10.6-1. > > Necessitated by a Windows Server 2016 DC being installed. > > > The following is the Global

I am building in source4. Where are these symbols defined? Is any library that is not getting linked? samba/source4 # make WAF_MAKE=1 ../buildtools/bin/waf build Waf: Entering directory `/usr/src/bamba/samba/source4/bin' [1816/1961] Linking default/source4/lib/ldb/libldb-samba4.so [1908/1961] Linking default/source4/lib/ldb/ldbadd default/source4/lib/ldb/libldb-samba4.so: undefined

> That's probably because you don't have a system-wide install of ldb on > your system. Here's what I have on mine: > > # rpm -qa libldb\* > libldb-1.4.6-2.el7.x86_64 > libldb-devel-1.4.6-2.el7.x86_64 > > # rpm -qf /usr/include/ldb.h > libldb-devel-1.4.6-2.el7.x86_64 > I have libldb-1.3.4-1.el7.x86_64 which is the stock CentOS 7.6 version. From where

In some spare time, been trying to get Samba 4.10.6-1 working on AIX. Several earlier posts handled by Louis and Rowland. Which were much appreciated and beneficial. Using this stripped (leaving comments out of it) GLOBALS section of smb.conf: [global] workgroup = boost realm = BOOST.COM server string = Samba Server Version %v interfaces = lo eth0

Ha! That should be libtdb: /usr/lib/x86_64-linux-gnu/libtdb.so.1 /usr/lib/x86_64-linux-gnu/libtdb.so.1.3.5 /usr/lib/x86_64-linux-gnu/samba/libtdb-wrap.so.0 /usr/lib/x86_64-linux-gnu/samba/libtdb_compat.so.0 /usr/local/samba/lib/private/libtdb-wrap-samba4.so /usr/local/samba/lib/private/libtdb.so.1 /usr/local/samba/lib/private/libtdb.so.1.3.7 Sorry for the typo, I compose most of my replies on

AIX Toolbox builds openssh with vac.C 5.0.2.0, and configures with very few options: export blibpath="/opt/freeware/lib:/usr/lib:/lib" %configure --prefix=%{prefix} \ --sysconfdir=/etc/ssh \ --libexecdir=%{_libexecdir}/openssh \ --with-ipv4-default \ --with-rsh=/usr/bin/rsh If you extract the openshh.spec file from the SRPM, you can see exactly what we do (you already have it in