similar to: Account lockout - Bad password count

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,

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

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. When authentication fail, samba seems to call init_ldap_from_sam asking to update the bad password count. When I set the lockout threshold to 1, the account is locked after a failed attempt and the badPasswordCount attribute is updated correctly

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:

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

Hello everyone, I am having a problem adding a machine account with pdbedit. My setup is the latest samba (3.0.21b) compiled from source on Solaris 10, SUN's latest JES' Directory Server. I am in a beginning stage of setting up this environment, so I may not have done something right. I was following the Samba PDC LDAP howto by Ignacio Coupeau

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I run a ldap backednd smaba 3.0.21c domain. I have 1 PDC, and 6 BDC's. On all the BDC's I can run 'pdbedit -Lw' but I get an error on the PDC. I turned the debuging up to 5, here's the output: pdbedit -Lw INFO: Current debug levels: all: True/5 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0

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]

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 =

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

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

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; +

I have a directory shared out via Samba for Quickbooks and seem to have some issues with permissions. The directory being shared is a subdirectory in an ext3 partition being mounted with the acl option. It has been setup as follows: chown root:DOMAIN\AD_Group /mnt/Intuit_Data/ chmod 2770 /mnt/Intuit_Data/ And the Samba share config is has: create mask = 0660 directory mask =

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 trying to add W2K8 server to our domain "ns.local". This domain is working O.K. for all XP machines we have (~10), but when adding a W2K8 server, I get user/pass prompt and then after typing my* username and password I get: --------------------------- Computer Name/Domain Changes --------------------------- The following error occurred attempting to join the domain

hi, i see the same error message with samba 3.0.14a and OpenLDAP 2.2.23 (Debian Packages) with Master/Slave setup. i did not set up a referral to the master, so why does samba get a referral when attempting to write to a slave? is this an in-build samba feature? do i have to enable referrals to get this to work properly? any advise is appreciated! thx! micha Zwonarz Ivo wrote: > We use

We use sambaPDC + LDAP On our BDC we have a replicated ldap slave. Everything seems to work fine. Hower, in the smbd log file we have the following messages (only on the BDC's) [2006/05/31 15:25:08, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1495) ldapsam_modify_entry: Failed to modify user dn= uid=pc01233$,ou=Machines,dc=brrc,dc=be with: Referral [2006/05/31 15:25:08, 0]

So I've got a PBX running with one Fritz card with the fcpci module and that works fine, but add another one and... kersplat... Kernel Panic. It boots fine with two cards, but panics as soon as the first fcpci.ko module is 'modprobe'd - I don't even get as far as modprobing the second. Any ideas on what's going on? Should I just back-up to an older version of the fcpci module