similar to: Samba 3.0.21 and after creates ldapsam:trusted display problems in User Manager?

Hi , I'm trying to migrate an old server with ubuntu 9.10 ,samba3 +ldap to a new server ubunut 14.04. I could follow the steps of https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_domain_to_a_Samba_AD_domain_%28classic_upgrade%29 but when running samba-domain tool classicupgrade --dbdir = / util / tdb --use-xattrs = yes --realm = gruporesasco.local --dns-backend = BIND9_DLZ

I got more information ,after enable log_level to 10: ``` push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 3 push_conn_ctx(0) : conn_ctx_stack_ndx = 2 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 3 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups Adding cache entry with key=[ACCT_POL/password history] and timeout=[Thu Jan 1 03:00:00 AM 1970 MSK]

Hi everyone, I'm unable to make the account lockout to work properly. & this is driving me mad. I am running samba Version 3.0.23c-1.fc5 as a PDC with openldap 2.3.19 on a fc5 (all packages from yum). I was running a 3.0.21 with the same issue. I'm using as well the Idealx script to manage the LDAP. The fact: I have a very strange behavior. The domain policy have been setup with the

I?m setting up our new server that will handle file storage. The new system is redhat running samba 3.0.23c. We currently have this same service running on DEC server running version 3.0.20 without any issues. Here is the smb.conf for both? [global] passdb backend = ldapsam:ldap://xxxxxxxxx ldap suffix = dc=temple,dc=edu name resolve order = wins bcast hosts ldap machine suffix =

Sure. ``` [global] workgroup = EXAMPLE server string = dns proxy = no interfaces = eth0 bind interfaces only = yes log file = /var/log/samba/log.%m max log size = 1000 # new options log level = 5 netbios name = FILES #panic action = /usr/share/samba/panic-action %d server role = STANDALONE SERVER local master = no security = user encrypt passwords =

Hi, I test samba 3.0.23a and I used a existant LDAP tree. But, samba 3.0.23a won't start : In smbd.log : ...... [2006/07/28 09:58:14, 10] registry/reg_cachehook.c:reghook_cache_add(61) reghook_cache_add: Adding key [/HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/Ports] [2006/07/28 09:58:14, 8] lib/adt_tree.c:pathtree_add(201) pathtree_add: Enter [2006/07/28 09:58:14, 10]

Hi We have an all SAMBA Domain (all samba-3.0.23d) running with two OpenLDAP servers (2.3.27). We experience quite a few NT_STATUS_IO_TIMEOUTs when using smbclient. Windows clients just experience delays (up to several minutes). I've done some debugging: On the client i issue: smbclient -Umhansen //lfs1/mhansen lfs1 is a domain member server. On lfs1 (log level 10) i get the following in

Hello, I've got a problem using ldap support on my Ubuntu jaunty. Here are the versions : samba/jaunty uptodate 2:3.3.2-1ubuntu3.2 smbldap-tools/jaunty uptodate 0.9.4-1 First of all, smbldap-groupadd don't use the sambaNextRid to create a group, it compute it. Is this a normal way ? I've patch smbldap-groupadd to do this : - #$group_rid = 2*$_groupGidNumber+1001; +

Greetings. Since this is my first post to this list, hello everyone. Here's an issue concerning the ldapsam backend. I'm having a problem with the "ldap user suffix" param not being honored as expected. Specifically, when a user logs on, the "ldap user suffix" is ignored and the ldapsam backend attempts to lookup the user doing a full subtree search in the context

Hello, I seem to be having an issue where one of my BDC servers constantly needs to rebind to the "master" ldap server (ldap1.ae-solutions.com). Whenever this happens I see several entries in the log like this: "smbldap_search_ext: waiting 928 milliseconds for LDAP replication." It appears to cause delay when browsing samba shares whenever this happens. The master

Hello All, I am currently having an issue with my samba PDC. I have recently updated to 3.6.5 Samba, and have made what i believe to be the correct changes in my config to account for the changes to the idmap system. My setup is as follows, SAMBA PDC on RHEL 6.2, which authenticates passwords through Kerberos, and Deals with user profiles via LDAP. I had about 25 Windows clients which were able

Hi all: I am trying to migrate my NT4 domain to a samba server which uses an LDAP server on the backend for authentication This machine that I want to be the new PDC is running RHEL5 with samba 3.0.23c and an openldap 2.3.27 running on the same machine. I used the by-example page http://us3.samba.org/samba/docs/man/Samba-Guide/ntmigration.html as my guide I set this up in a test environment

Samba 3.0.21(and 'a'), AIX 5.2. Was looking as what appears to be a fantastic optimization, but can't find info in source code or swat and turning the option on makes smbd do exit(-1) (on AIX anyway). ldapsam:trusted = yes Does this really exist? Does it need a maintainer? Are there any docs/source? Cheers, Bill

Ok, this one is driving me nuts. I am using smbk5pwd to sync samba, ldap, and heimdal kerberos passwords. I have the overlay working if called from the ldappasswd command. However, if I set "ldap passwd sync = only", I get no joy from Samba. It does a series of searches, but doesn't send any kind of password update request to the server. If I use ldap passwd sync = yes, then

Hello all! Is there a reason that the "root" uid is sought after in "ldap suffix" and not in "ldap user suffix","ldap suffix" when smbd is started? This seems incorrect to me. I have three domains in the same tree and it's arranged like so (varying the last dc on each suffix): ldap group suffix = cn=Groups,dc=devex ldap idmap suffix

Hi Daryl, > I recently migrated our samba PDC to an LDAP backend on a test machine. > Testing my account policies, I found out that the password lockout did not > work. bad password lockout works fine in Samba AD mode. Is there a technical reason for you to keep on using PDC NT4 mode? In AD mode, you'll also get a LDAP, and it will be much easier to setup and manage! By the way,

Hello All, I am having a very strange problem with samba 3.0.23c. I upgraded everything from 3.0.9 and I am able to smbclient to the samba 3.0.23c PDC with the administrator user just fine. When I go to add a machine to the domain, it adds the unix machine account to the ou=computers like it is supposed to but none of the samba entries are added. I get an error on the windows side of

I found out the answer to why the bad password count was failing by following the stack trace If anyone has the same problem, this was caused by my access rights being too restrictive. source/passdb/Init_sam_from_ldap.c:1064 => There is a "goto fn_exit;" in case ldapsam_get_entry_timestamp() fails before the cache is read via login_cache_read. This function will fail if it cannot

Hi Denis, Thanks for your suggestion When I looked into Samba4 AD, I figured it would take too much effort to port our infrastructure to it, seemingly without benefits We already have a quite extensive network architecture with OpenLDAP acting as a LDAP server. Samba4 AD seems to require its own LDAP implementation (and some more quirks IIRC). There's also the additional DNS configuration

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: