search for: have_ldap_add_result_entri

Does this mean that my samba is ready to connect to LDAP server? root at webdev # ./smbd -b |grep LDAP HAVE_LDAP_H HAVE_LDAP HAVE_LDAP_ADD_RESULT_ENTRY HAVE_LDAP_INIT HAVE_LDAP_INITIALIZE HAVE_LDAP_SET_REBIND_PROC HAVE_LIBLDAP LDAP_SET_REBIND_PROC_ARGS root at webdev # Thanks! Paras.

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

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

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 ~]#

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

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,

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

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(...)

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'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

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 =

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]

I'm pasting below the output of the debug script you sent me some time ago. Other than this Samba has been compiled with standard options, just ./configure, following the wiki guide with the offered bootstrap file for ubuntu18.04. root at fileserver:~# smbd -b Paths: SBINDIR: /usr/local/samba/sbin BINDIR: /usr/local/samba/bin CONFIGFILE: /usr/local/samba/etc/smb.conf

Hi list, Disclaimer: not a subscriber, not a samba expert, just trying to get samba running on a Solaris 10 system. We build samba 3.6.4 from source for various platforms. We link against our own builds of cyrus-sasl 2.1.23, openldap 2.4.23, and openssl 1.0.0h. On Solaris we also compile against krb5-1.10.1. Builds are done with GNU tools whenever possible (gcc/ld/make). The build host, as well

So, after rebuilding and finding that somehow fixed my intial issue of failing to connect to the ldap server, I am now having an issue with the guest account. Any ideas, I've done some searches but haven't been having any luck. This is on RHEL. Help is greatly appreciated. Thanks in advance. Maximum core file size limits now 16777216(soft) -1(hard) get_current_groups: user is in 7 groups: