search for: myldap

...disable spoolss = yes ldap ssl = off idmap config * : backend = tdb idmap config * : range = 65536-4294967296 idmap config MYDOMAIN : backend = rfc2307 idmap config MYDOMAIN : range = 1000-65535 idmap config MYDOMAIN : ldap_server = stand-alone idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org idmap config MYDOMAIN : user_cn = no idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 idmap config MYDOMAIN : ldap_user_dn = cn=samba,ou=agents,dc=myldap,dc=org [home] comment = Home Directories path = /home/...

...end = tdb > > idmap config * : range = 65536-4294967296 > > > > idmap config MYDOMAIN : backend = rfc2307 > > idmap config MYDOMAIN : range = 1000-65535 > > idmap config MYDOMAIN : ldap_server = stand-alone > > idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org > > idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org > > idmap config MYDOMAIN : user_cn = no > > idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 > > idmap config MYDOMAIN : ldap_user_dn = > cn=samba,ou=agents,dc=myldap,dc=org &gt...

...gt; > idmap config * : backend = tdb > idmap config * : range = 65536-4294967296 > > idmap config MYDOMAIN : backend = rfc2307 > idmap config MYDOMAIN : range = 1000-65535 > idmap config MYDOMAIN : ldap_server = stand-alone > idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org > idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org > idmap config MYDOMAIN : user_cn = no > idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 > idmap config MYDOMAIN : ldap_user_dn = cn=samba,ou=agents,dc=myldap,dc=org > > [home] > commen...

...our Linux servers are using en openldap base to authenticate. All the samba 3 servers use this openldap base /passdb backend = ldapsam:ldaps://ldap.intra.labo.fr// (in the smb.conf) I tried to migrate the users account of my openldap database to internal samba4 ldap database. For this I used the myldap-pub.py script with this command line : /./myldap-pub.py --ldap_uri=ldap://ldap-server.labo.fr \// //--ldap_binddn="cn=admin,ou=administrateur,dc=labo,dc=fr" \// //--ldap_bindpwd="password" \// //--output_basedn="dc=labo,dc=fr" \// //--input_domain_name="DOMAIN&q...

...ge = 65536-4294967296 > >>> > >>> idmap config MYDOMAIN : backend = rfc2307 > >>> idmap config MYDOMAIN : range = 1000-65535 > >>> idmap config MYDOMAIN : ldap_server = stand-alone > >>> idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org > >>> idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org > >>> idmap config MYDOMAIN : user_cn = no > >>> idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 > >>> idmap config MYDOMAIN : ldap_user_dn = > >&gt...

...> idmap config * : range = 65536-4294967296 >>> >>> idmap config MYDOMAIN : backend = rfc2307 >>> idmap config MYDOMAIN : range = 1000-65535 >>> idmap config MYDOMAIN : ldap_server = stand-alone >>> idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org >>> idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org >>> idmap config MYDOMAIN : user_cn = no >>> idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 >>> idmap config MYDOMAIN : ldap_user_dn = >> cn=samba,ou=agents,dc=m...

...967296 >>>>> >>>>> idmap config MYDOMAIN : backend = rfc2307 >>>>> idmap config MYDOMAIN : range = 1000-65535 >>>>> idmap config MYDOMAIN : ldap_server = stand-alone >>>>> idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org >>>>> idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org >>>>> idmap config MYDOMAIN : user_cn = no >>>>> idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 >>>>> idmap config MYDOMAIN : ldap_user_dn =...

Obviously I am missing something and I don''t know what it is... I am following the instructions at http://rubyforge.org/docman/view.php/381/114/activeldap_rb.html and also here... http://wiki.rubyonrails.org/rails/pages/HowtoAuthenticateViaLdap my model looks exactly like this... class LdapUser < ActiveRecord::Base ldap_mapping :dnattr => ''uid'', :prefix

...samba 2 schema. I used -with-ldapsam when building in the hope that that would be OK. I had a problem when it came to "net groupmap ..." because samba was trying to use the samba 3 schema attribute sambaSID. I got round this by setting passdb backend = smbpasswd ldapsam:ldap://<myldap> so it appears to be creating the new entries in smbpasswd, not the LDAP. Now I have a problem I can't see a solution for. When I try to get a PC to join the domain the log shows samba trying to access the DN: sambaDomainName=MYDOM,dc=ex,dc=ac,dc=uk (first in smbldap_search_domain_i...

...gt;> > >>>>> idmap config MYDOMAIN : backend = rfc2307 > >>>>> idmap config MYDOMAIN : range = 1000-65535 > >>>>> idmap config MYDOMAIN : ldap_server = stand-alone > >>>>> idmap config MYDOMAIN : bind_path_user = ou=users,dc=myldap,dc=org > >>>>> idmap config MYDOMAIN : bind_path_group = ou=groups,dc=myldap,dc=org > >>>>> idmap config MYDOMAIN : user_cn = no > >>>>> idmap config MYDOMAIN : ldap_url = ldaps://ldap.myldap.org:636 > >>>>> idmap config MYDOMA...

...yes # IDMAP MDMAD XM #GLOBAL idmap config *: backend = tdb idmap config *: range = 19000-19999 #DOMAIN_A idmap config DOMAIN_A : backend = ldap idmap config DOMAIN_A : range = 20000-9999999999 idmap config DOMAIN_A : ldap_url = ldap://myldap.domain_a.com idmap config DOMAIN_A : ldap_base_dn = ou=Idmap,dc=domain_a,dc=com idmap config DOMAIN_A : ldap_user_dn = cn=SuperUser,dc=domain_a,dc=com #DOMAIN_B idmap config DOMAIN_B backend = nss idmap config DOMAIN_B: range = 500-19000 guest account...

...ng up a pure ldap environment, that means NO nt domains or any ms dependency. we want also allow some windows machines to access nfs+samba file servers but we dont need samba acting as PDC, only authenticate with a username and password stored in ldap. is sufficient with setting password server = myldap.server:389 or do i need to set also in idmap backend? i repeat just to clarify: centralized ldap authentication nfs shares smb shares identical to nfs ones mainly linux clients (this is done for now and it works) MAYBE: windows clients authenticating with ldap through pgina windows clients acces...

I'm looking for direction on converting from openldap / samba3 backend to samba4. At this point I've got my samba4 domain provisioned and working and I now want to start importing users but for the life of me I can't find any information on the net about the process. Few questions. Do I need to use the converted schema from oLschema2ldif? Do I need to convert the exported ldifs

I'm attempting to migrate a Samba 3.x / NT domain to Active Directory. I have a Windows 2003 SE host and ADMT. I've established trusts between the Samba 3 domain and the Windows 2003 AD domain. I can use "User Account Migration Wizard" up to the "Account Transition Options". Then of I check the option to Migrate SIDs it fails with - "Could not verify auditing

Hi! I have to migrate a samba domain to an Active Directory and therefore I need as first step to have a NT4.0 BDC in my network. As I don't find an useful answer via google I want to ask you if a NT4 BDC will work in a Samba PDC enviroment? regards Martin

I have been doing some work with the new Samba4 version and have some questions. Is this the right list to ask on, or is there a development list that would be better? (I am currently following the Samba4 HOWTO Wiki at: http://wiki.samba.org/index.php/Samba4/HOWTO, and building from the "git" repository. The system seems to be working well, but I have some questions about migrating

...#GLOBAL > idmap config *: backend = tdb > idmap config *: range = 19000-19999 > #DOMAIN_A > idmap config DOMAIN_A : backend = ldap > idmap config DOMAIN_A : range = 20000-9999999999 > idmap config DOMAIN_A : ldap_url = ldap://myldap.domain_a.com > idmap config DOMAIN_A : ldap_base_dn = > ou=Idmap,dc=domain_a,dc=com idmap config DOMAIN_A : ldap_user_dn = > cn=SuperUser,dc=domain_a,dc=com #DOMAIN_B > idmap config DOMAIN_B backend = nss > idmap config DOMAIN_B: range = 500-19000 > &g...

Hi All, Answering to myself, this problem still occurs again and again, every week as I mentioned before. Rejoining the domain each time for samba4 file server is the only workaround. What could be the origin of this kind of problem? Any answer would be helpfull Regards Le 17/07/2017 à 10:12, Julien TEHERY a écrit : > Hello, > > > We recently put in place a trust relationship