similar to: Problems with idmap_adex module

Hi, I'm trying to integrate an existing linux environment with a Windows AD environment. All my users are already in AD with valid rfc2307 attributes defined so I need a way to authenticate my users using username, uid, gid, shell and homedirectory from AD. I've been using Kerberos+LDAPs before but that requires a dummy AD user hardcoded with username and password in /etc/ldap.conf

Hi Guys, I'm setting up a new file server in our domain environment and I'm having problems with the adex configuration/module. I have couple of working file servers using rfc2307/idmap_ad and they are working perfectly. What attracted me to the idmap_adex module is the domain trust/forrest authentication support. I have 2 domains not in the same forest with a 1-way trust setup. The

Hi, Actually I am using the Backend Idmap_AD. I thought Idmap_adex is still under heavy development. Tobias Mit freundlichen Gr??en Tobias Mucke LFK-Lenkflugk?rpersysteme GmbH Serverpool, FCI4 Landshuter Stra?e 26, 85716 Unterschlei?heim, GERMANY Phone: +49 89 3179 8438 Fax: +49 89 3179 8927 Mobile: +49 170 635 3830 E-Mail: tobias.mucke at mbda-systems.de http://www.mbda.net Chairman of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the second release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the second release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

Hi! $SUBJECT says it all. Why am I asking? A few times in the recent past I've stumbled across this module when trying to make changes in the winbind infrastructure that would involve changes to idmap_adex. The problem here is that I have no chance to test those changes, because I do not have the test setup including a Likewise Cell infrastructure around. Is anybody around using this module

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the second preview release of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the second preview release of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

We have Windows 2008R2 domain controllers running 2003 functional level with SFU (i think thats what its called, im not the windows admin :p ) . With Winbind 3.0.33 (on Redhat 5.5) I can get the UIDs/GIDs from AD without issue using: idmap config DOMAIN:backend = ad idmap config DOMAIN:default = yes idmap config DOMAIN:schema_mode = rfc2307 idmap config DOMAIN:range = 10000 - 30000

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the first release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release Announcements ===================== This is the first release candidate of Samba 3.3.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Major enhancements in Samba 3.3.0 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "After all, computers crash, people die, relationships fall apart. The best we can do is breath and reboot." Sarah Jessica Parker ================================================================ Release Announcements ===================== This is the first

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "After all, computers crash, people die, relationships fall apart. The best we can do is breath and reboot." Sarah Jessica Parker ================================================================ Release Announcements ===================== This is the first

After spending some time trying to figure out how to merge the allocating backend from idmap_ldap and the rest of idmap_adex, I have found that it may not be worth the effort to avoid having to configure idmap_ldap. Has anyone had success with idmap_ldap as the uid/gid allocator and idmap_adex in Samba4? I haven't done much with ldap, so any instructions on how to add schema info needed

Greetings, I have had Samba/Winbind/Kerberos single-sign-on authentication working for a few years now, for a single domain, and it works great. It pulls the RFC2307 populated attributes just like you'd expect, and people get the IDs mapped according to their attributes in AD. This works for version 3.2.7 and 3.4.3. I had to give the domain's Domain Users group a gid in the range of

I am having a strange problem that I thought someone might be help resolve. I am using Samba 3.4.7 at the moment, but I've had the same issue with Samba 3.4.6 and Samba 3.5.2. NOTE: Domain, hostnames, usernames and SIDs have been changed to protect the guilty. I am seeing an unable to successfully execute a variety of lookups from wbinfo and I think this is the underlying cause of some

I'm currently compiling Samba 3.3.X with the following: CFLAGS = -g -Wall -O2 ./configure --cache-file=./config.cache \ --with-fhs \ --enable-shared \ --prefix=/usr \ --sysconfdir=/etc \ --libdir=/usr/lib/samba \ --with-privatedir=/etc/samba \ --with-piddir=/var/run/samba \

Ok. But to the time in a short term period is there is way to make building successfull ? May be some temporal solution ? One more, I need to build-in to binaries: libreplace,libwinbind-client,libwbclien, that is replace,winbind-client,wbclient "targets" while building all regarding configure options specified below: --prefix=/usr \ --enable-fhs \

On 4/15/2016 2:30 PM, Rowland penny wrote: > On 15/04/16 18:54, lingpanda101 at gmail.com wrote: >> Hello, >> >> I'm unable to update my Samba from 4.1.17 to 4.4.2. I'm looking >> to build from tar instead. From what I gather the following should be >> the steps taken. >> >> ./configure --without-ad-dc -- sbindir= /usr/sbin >>

Hi I want to build samba-4.10.0 for SUSE openLeap 15.1. Config and make works fine but make install sucks: ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --libdir=/usr/lib64 --libexecdir=/usr/lib64 --with-cachedir=/var/lib/samba --with-lockdir=/var/lib/samba/lock --with-logfilebase=/var/log/samba --with-modulesdir=/usr/lib64/samba --disable-rpath --disable-rpath-install