similar to: samba bad password count reset between logins (not loaded from login_cache.tdb)

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,

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

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

Hi All, I have a strange problem with passwords, stored in LDAP. When i try to logon as a user with the correct password, access is denied and the log says check_ntlm_password: Authentication for user [administrator] -> [administrator] FAILED with error NT_STATUS_NO_SUCH_USER When i try to logon a user with incorrect password, access is (of course) denied, but the log now says

Sorry all, I think I attached the wrong files. Apologies for the noise. Correct files attached. again .. these are from the logfile on the server and were in the log file named 192.168.168.13.log 192.168.168.13 is the IP address of the test client orgonon that I have set up for this. I have cut two sections from the log and they start at the same point and seem to be the same until line 162;

Q#1. What SAMBA related object classes and attributes I must add to a POSIX user in LDAP (SunOne DS 5.2) before it can be used by SAMBA for authentication? Q#2. Why does the SAMBA log for the user show the error ?FAILED with error NT_STATUS_WRONG_PASSWORD? even before the user is prompted for username and password on the SAMBA client? Also in this log, I saw another error ?NT MD4 password

Hi, Can anybody confirm the following problem: Sequence: bash-2.05# grep ankerpos /usr/samba.moonrock/private/smbpasswd ankerpos:921:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-0 bash-2.05# /usr/samba.moonrock/bin/smbpasswd -c /usr/samba.moonrock/lib/smb.conf ankerpos New SMB password: Retype new SMB password: bash-2.05# grep ankerpos

I've had samba in production for a few weeks, as follows: samba 3.0.20b openldap 2.2.13-4, idealx tools 0.9.1 red hat AS 4 clients: all XP sp2 Samba's the PDC, nothing fancy about the setup other than trying to use LDAP for authentication. So far everything's been mostly fine, then yesterday for some reason a number of my users couldn't authenticate after logging out or

Hi, i'm trying to configure a samba-3.0.9-2.3 with suse 9.2 and openldap2-2.1.12-74 in another server but i have a strange problem. My samba schema is old and i have use the ldapsam_compat parameter on samba 3. My problem: I mount a share of samba 3 server on my linux: # mount -t smbfs -o username=joanr //192.9.200.147/dpd /mnt Password: 30004: tree connect failed: ERRDOS - ERRnoaccess

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

Dear Help, Initially, I thought that I had solved this problem, but it turns out that I haven't. I currently have Samba set up as a PDC with an eDirectory/LDAP backend. There are also a few Samba BDCs in play as well. If a user enters the correct password, there are no issues and everything authenticates fine. If I turn off the PDC and force a user to authenticate against a BDC with the

I have two SAMBA PDC's with an OpenLDAP backend. My goal is to establish an interdomain trust between the two domains so that users from each backend can login to Windows systems by specifying accounts from either domain. I've followed the steps to establish the trusts and I can see accounts and groups using wbinfo and getent. I can access resources/shares from each domain but I'm

Hello list - I am not sure my messages are getting out to the list, so I will attempt in this message to summarize the problems I am having that have been the subject of a few other posts. I recently upgraded from a command-line Slackware installation to Debian Jessie. As part of that exercise, Samba was upgraded from 3.5.x to 4.1.17. My upgrade method was probably not idea: I recursively

This is a repost of my first mail: Hello, I'm trying to configure a Samba server to simply use LDAP backend for authenticate users. Just that, I don't care of PDC/BDC, etc. The samba schema is present in the LDAP, and in the users profile. The samba server have the same SID as the domain. I can log to my samba server using LDAP account, so I think that NSS/PAM

I have some old boxes called Auditron that use an ancient version of Windows CE. These clients worked fine on Fedora 19 with Samba 3. I have now upgraded to Fedora 22 and Samba 4, and now these old boxes no longer connect. This is the config file I am using that was working fine: # Global parameters [global] netbios name = MEDIA server string = %v Samba on %h

Hello List. We have a number of working ADS servers. One of out clients is not in the Kerberized domain so there users log in via NIS. Having looked at the options for enabling NIS authentication I have decided to use the smbpasswd. Now I can't get that to work. After using smbpasswd to create two users, one created locally, in the /etc/passwd, and one that exists already in NIS. Not only

I'm running Centos 4.3 and Samba 3.0.24. I have an OpenLDAP backend. I have successfully got a Windows Domain to work, Windows XP -> Samba -> OpenLDAP. I can add machines to the domain and I can login and change passwords. The trouble is that I'm using NTLM and have been told that I must upgrade to NTLMv2, but I'm having great difficulty doing so. I have existing NTLM users. I

Hi All, I'm posting this just in case someone can tell what's going on with samba that would prevent this from working. Cisco has the ability to see a smb share from their webvpn product with CIFS. We can browse windows shares but not samba shares. The following log outputs are from my ASA firewall. I know these are cisco logs but I'm hoping a lightbulb will come on for someone. The

Hello, My apologies for my bad english, this is not my birth langage and I'm still learning it. I'm trying to configure a Samba server to simply use LDAP backend for authenticate users. Just that, I don't care of PDC/BDC, etc.The samba schema is present in the LDAP, and in the users profile. The samba server have the same SID as the domain. I can log to my samba server using LDAP