similar to: samba+ldap

what flag from smbd -b confirms ldapsam is built in? I see: # smbd -b | grep -i ldap HAVE_LDAP_H HAVE_LDAP HAVE_LDAP_ADD_RESULT_ENTRY HAVE_LDAP_INIT HAVE_LDAP_INITIALIZE HAVE_LDAP_SASL_WRAPPING HAVE_LDAP_SET_REBIND_PROC HAVE_LIBLDAP LDAP_SET_REBIND_PROC_ARGS idmap_ldap_init pdb_ldap pdb_smbpasswd pdb_tdbsam pdb_wbc_sam I was expecting to see something with

Hello, i have installed Sun Java Enterprise Directory 5.2 configured it for messaging and posix accounts i can logon to solaris no problem i complied samba with --with-ldapsam i configured the smb.conf testparam check and report Ok when i start samba no errors in messages when i try to add smbpasswd -a root here is the error No builtin nor plugin backend for ldapsam found Loading

Solaris 11 include samba 3.6.25. I compiled samba 4.5.1 using GCC 4.8 and gmake. Had set following env variables to make sure krb5.conf was found # CPLUS_INCLUDE_PATH=/usr/include:/usr/include/kerberosv5/ # C_INCLUDE_PATH=/usr/include:/usr/include/kerberosv5/ After setting "client ldap sasl wrapping = plain" I was able to join to a Windows 2008 domain with samba 4.

Hi, I try to set up samba (latest) to use LDAP. I get # smbpasswd -w secret -w not available unless configured --with-ldapsam I xompiled with LDAP support. Any hints? -- Jochen Witte <devnull@alpha-lab.net>

On Thu, 2017-06-08 at 10:09 +0200, awl1 via samba wrote: > Hello again, Samba experts, > > sorry for being such a pain in your necks, but I really need to get a > recent Samba version to compile, and it looks like I definitely need > your help with this. > > In the meantime, I have found that the huge number of "conflicting > types" errors for rpc_*_init(...)

Hello, I've compiled Samba 3.0.4 with Heimdal 0.6.2 and all of the other trimmings to join and ADS tree, which I have successfully done. Winbind correctly pulls all of the username and group information from the ADS tree and all is good. However... I seem to be running into a wall with the wonderful Solaris 8 character username / groupname limit. Usernames with spaces or names longer than

Need some help if anyone can provide it on this issue. I have a very basic setup and am trying to have samba utilize openldap. I have made sure the password is correct but for whatever reason, I am unable to connect. Here is a log of what is going on. Any help would be greatly apprecated. TIA Maximum core file size limits now 16777216(soft) -1(hard) get_current_groups: user is in 7 groups: 0,

Samba 4.12.1, single server with AD+DC on Ubuntu 18.04. Filesystem: /dev/sdb1 on /home type ext4 (rw,relatime,stripe=32750,data=ordered) It all work as expected, but I occasionally get the error in subject which denies access to shares. Restarting Samba will restore functionality. What can be the cause of this problem? Thanks. [2020/05/27 18:24:35.795379, 8]

Hi! I'm experiencing problems with access to one of shares on server with Samba working as PDC for windows clients, after I upgraded Samba from 3.0.22 to 3.0.23 (this problem also present in 3.0.23a). There are config section for this share: ---------------------------------------------------------------- [domain] comment = Domain users exchange share path =

Tried configure of samba-3.2.0 on Sparc Solaris 9 with the following line: ./configure --with-ldap --with-ads --with-pam --with-winbind --with-krb5=/usr/local > $log 2>&1 There is a problem where the following error is produced: configure: error: Active Directory support requires ldap_initialize I can use the same line on samba-3.0.10 and it compiles and works. $

I'm curious to know where the tdbsam password database file is kept on my Fedora 7 system. Using the unmodified smb.conf file that shipped with Fedora 7, I've enabled users using smbpasswd, and successfully accessed shares. I just can't figure out where the password database is located: [root@box ~]# service smb start [root@box ~]# setsebool samba_enable_home_dirs on [root@box ~]#

Hi all. I've been searching various archives and lists to see if I can track down what I'm doing wrong ? but I suspect something is getting in my way (bug perhaps)? I thought I'd ask on the list to see if others have any experience here. Situation is as follows: 1. Solaris 11.1 box, successfully bound to active directory domain using traditional net join ads syntax. 2. Can

Hello Andrew, and many thanks for your fast reply! :-) Am 08.06.2017 um 11:05 schrieb Andrew Bartlett: > I think the key to avoiding the issue is that you have listed rpc > modules which are not modules. The only rpc server module is > rpc_mdssvc_module. Ah, OK, I see - so I seem to have been wrong when assuming that I could take the output of Samba 3.5.16 "smbd -b" command

Hi, we want to use ldapsam:trusted=yes to improve performace as nss_ldap is killing our ldap server doing enumeration. once i enable it smbd dies silently... this is the last part of a ./smbd -d 10 -i NT user token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups smbldap_search: base => [ou=groups,ou=filestore,dc=sunderland,dc=ac,dc=uk], filt er =>

Good morning! I compiled samba 4.10.8 from source in a slackware 14.2 machine and imported a samba classic domain from an ldap backend. Everything works flawlessly except for a couple of user who are getting their accounts locked out periodically. I'm trying to debug this problem so I modified the smb.conf file of the DC so that it looks like this # Global parameters [global] ??????? dns

Hello, I'm trying to set up samba using ADS for authentication. I can successfully join the samba machine to the domain. Windows hosts can "see" the samba machine. After successfully joining, doing: # wbinfo -u shows me ADS-defined users. Same goes for groups. However, when I try and assign one of those users ownership of a file, I get: # chown user1 /tmp/test chown: test1:

So I am compling the newest release of samba 3.0.14a on Solaris 2.8. I can get it to compile but I don't get all the built in modules that I should and smbd when fired up bombs out with something like, ------- derek@supernova:/opt/UMsmb/sbin# ./smbd -c /etc/samba/smb.conf -i smbd version 3.0.14a started. Copyright Andrew Tridgell and the Samba Team 1992-2004 No builtin nor plugin backend for

I've got some problems with file access control on a linux-server with samba 3.0.14a compiled from a src-rpm. This is the method I've been using for the past 5-6 releases. It's a redhat 8.0 machine and the kernel version is 2.4.30. The problems seem to have appeared since upgrading from 3.0.13. Symptom 1: When using force group on a share, users from the two groups edb and

Running Sun OS 5.10 sparc. OK, I am trying to establish an Active Directory connection from my Sun Solaris box and am trying to utilize Samba to accomplish this task. I've installed OpenLDAP & Samba, but when I run a few checks, it appears that Samba is not seeing KRB or ADS, but is seeing LDAP & WINBIND. (This is Samba 3.3.3) # cd /usr/local/samba/sbin # smbd -b|grep LDAP

Hi, I'm seeing regular tdb corruption; typical log messages are: tdb(/var/db/samba/sessionid.tdb): tdb_rec_read bad magic 0x42424242 at offset=672032 tdb(/var/db/samba/connections.tdb): tdb_rec_read bad magic 0x0 at offset=1111638594 tdb(/var/db/samba/locking.tdb): tdb_rec_read bad magic 0x42424242 at offset=1034396 which then prevents fileserving from working properly (N.B. the bad magic