similar to: "Bad lockout attempt" recorded twice

All, I built and installed 3.0.7. I am trying to finalize my setup by limiting the user to 3 failed logon attempts. I used: ./pdbedit -P "bad lockout attempt" -C 3 This works fine for all users EXCEPT for the user with a matching Windows user name. In other words, if my windows user name is 'bender' and my samba user name is 'bender' the number of Bad logon attempts

I've got a Fedora Core 2 box running Samba smbd version 3.0.7-2.FC2. I've set it up as a Domain master for a new domain. I setup a Win2K Server box and had it join the domain. I made an "administrator" user, I mapped the groups via: net groupmap modify ntgroup="Domain Admins" unixgroup=admins net groupmap modify ntgroup="Domain Users" unixgroup=users I

Hi, I have a Debian stable (woody aka 3.0) machine. I am moving my existing samba 2.x installation (that has users stored in smbpasswd) to samba 3.0.4 with LDAP as the backend. I am able to move the users to LDAP just fine. However, the password policy of bad lockout attempt does not seem to work. I installed the samba deb file from the samab.org site. I also have OpenLDAP slapd

Help!! I have been using tbdsam as a backend and I have been unable to get the pdbedit -P "bad lockout attempt" -C 3 to be enforced. When I set the attribute it seems that I can try to login as many times as I want. Any help out there? Terrance

Hopefully someone can put my mind at ease... I have about 10 W2K boxes with account lockout threshold of 5 failed logins and Additional Restrictions for Anonymous Connections set to 'No access w/o explicit anon. permissions' (Administrative Tools -> Security Settings -> Local Policies -> Security Options) I've set up a Samba server this week and in the past few days

Hello, I have the following test setup: 1) Samba3 + slave OpenLDAP - the same PC, win2k in same LAN 2) OpenLDAP master OpenLDAP slave and master are divided by a rather slow internet VPN link. Whenever I want to add a PC to a domain, I have to do it twice - with first time I get an error on a client side, second join is successful. I guess it's because master and slave are divided by

Hi Everybody, Does anybody that have it working can give me a sample of what looks like a NTConfig.POL file that changes users passwords every 45 days. I?m using samba 3.0.10 with ldap backend. Any help will be appreciated. Thank?s Gustavo

Hi, I have the following directory shared for the user "pcbadmin". He/she can mount and read/write without any difficulty: [pcbdata] comment = PCB Design Files path = /home/pcbadmin/pcbdata valid users = pcbadmin public = no writable = yes Question: How can I make the same directory only readable by the rest of the users ? TIA, Ben

Hello, I have a samba 4.1.5. I have created OUs and linked GPO to OU for account lockout policies. Account Lockout Duration: 15min Account Lockout Threshold: 5 invalid attempts Reset Account lockout counter after: 15min I have created a test account and logged in with an incorrect password more than 5 times to a machine. but the test account never locks and the computer never prompts me that

First of all, I want to say I have been using Samba AD for two years now (since just before 4.0 went stable), and it is an amazing product. We've implemented Active Directory & Group Policy for almost 50 computers and 100 users. Unfortunately, we are now being forced into switching to Windows DCs because Samba does not have an account lockout feature. Citrix (stupidly) does not have

I recently am migrating my PDC from NT4 to Samba 3.025. Apparently due to a mismatch between the capitalization of the Windows account and the Unix account (Administrator vs administrator) I managed to lock the account before catching the discrepenacy. # pdbedit -v administrator Unix username: Administrator NT username: Administrator Account Flags: [ULX Bad password count

Greetings! Is there any way to to lockout a certain machine identified by its ip address after a fix number of bad logon attempts? I'm aware of account policy option "bad lockout attempts" but that would block the whole account and not just the machine. Have a sunny day! Ferdinand

Hello I know there is a domain account lockout feature at: http://git.samba.org/?p=abartlet/samba.git/.git;a=shortlog;h=refs/heads/s4-bwdPwdCount-01 A malicious user can type in incorrect password of any domain users. Then these users will be lockout (automatically or manually) in short time. Do we have any tools (equivalent to Event Viewer on Windows Server) for monitoring these actions

I have a question about bad password lockout. Net pwsettings has settings for Complexity, Password history Length, Minimum password length, Minimum password age, and Maximum password age. But I can not see how to set a bad password login attempts. Can this be set using a group profile? Getting ready to use samba 4 for authentication purposes but really do need this ability. Everything

Hi guys, I am so thrilled by samba 4 it makes me go to bed smiling J Here is my setup. Server ************ Centos 6.5 Samba 4.1.4 Clients ************* Windows XP, 7 & 8 Question: Is account lockout supported with samba4 ? I cannot seem to get the users accounts to lock when they type their passwords incorrectly. The rest of my GPO's work. Folder redirects work

Hi all, My boss is still questioning me for an answer. I've searched thru this archive thru the beginning of the year as well as searched thru Google, but still haven't found the answer to the this question.. Is there a way in Samba to automatically disable/lockout an account if the user has tried to signon more than a set number incorrectly? As an example: if JDOE tries to sign into

Dear Samba team I followed this link: http://www.marshut.com/iptxts/samba4-domain-account-lockout.html But I don't know how to merge code into samba 4.1.6 Please help me integrated account lockout feature into lastest samba stable 4.1.6. And any commands to do it. Thank you very much! Hieu

Hi, I have just upgraded our Samba 4.1 AD servers to 4.2.2. Our AD was previously run on win2k3 and had configuration for account lockout after 3 bad passwords. This lockout obviously did not work after migration to 4.1 After the upgrade to 4.2.2 the lockout started working again, almost as expected. The current settings are Password complexity: on Store plaintext passwords: off Password

Hi All, I have setup samba 4.3.9-Ubuntu AD DC, I want to setup password policy and account lockout policy to all my domain users. How I can do that. Please somebody give me the steps. -- Vivek Patil Assistant Manager - IT Forgeahead Solutions vivek.patil at forgeahead.io *O* +91 (0) 20 66 44 5900 | *M *+91 9579 216 049 601 Zero One, Level 6, Mundhwa, Pune 411036, Maharashtra, India *W*

I'm currently using samba4 as an AD DC (domain and forest are both configured with the samba-tool command to be at the 2008_R2 functional level) for both Windows and Linux systems. I've got the default password settings set using the "samba-tool domain passwordsettings" command and I have all the GPOs configured as I need them for clients. However, I would like to configure how