similar to: Samba 4.2 Account Lockout logging

Hi James, We use Samba 4.2 DCs and have Linux talking to the DC fine. This is using Kerberos via SSSD on CentOS 6 and various Fedoras - Password expiry works, nested Groups work, Sudo rules and Netgroups can be placed inside the AD tree as well. A combination of the samba-tool command and pdbedit can achieve most things, however you will still need the Windows Management tools to interact with

Hello, I have a namespace / ACL problem with shared mailboxes that I can't figure out. I have a local user tam at crm.yb.lmax that shares it's INBOX and all other folders with on LDAP group. Members of that group can't create a folder under the shared local user's INBOX: [08-Apr-2015 11:43:05 +0000]: [9501] S: * MYRIGHTS tam at crm.yb.lmax lrwstipekxcd [08-Apr-2015 11:43:05

Replying back to the list :-) The Sudoers functionality is achieved by modifing the Samba schema, the sudo package itself distributes the schema change LDIF: $ rpm -ql sudo | grep schema /usr/share/doc/sudo/schema.ActiveDirectory /usr/share/doc/sudo/schema.OpenLDAP /usr/share/doc/sudo/schema.iPlanet Technically if you could find the correct schema to store autofs data in AD then it should work.

Hello, I am trying to join a third domain controller to an existing Samba 4 domain (sernet samba 4.2.1-17.el6.x86_64) and we're hitting a problem that looks like some bad replication data on certain objects. We get part way through replicating the tree and then it dies on a Sudo Rule object: [root at dc03 ~]# /usr/bin/samba-tool domain join EXAMPLE.COM DC -U Administrator

Hello, We're using Samba 4.1.11 as domain controllers and over the past two weeks I've run into several issues with unrelated Windows software, the problems of which all point to Kerberos authentication and SPNs as being somehow involved. If there are many more issues it might start to get politically difficult *not* to blame the DCs, and I don't want to point fingers at Samba. Are

----- Original Message ----- > From: "David Bear" <dwbear75 at gmail.com> > To: samba at lists.samba.org > Sent: Wednesday, 17 December, 2014 5:25:48 PM > Subject: Re: [Samba] Samba4 DC, SPNs and a complex Windows stack > > On 12/17/2014 01:35 AM, Luke Bigum wrote: > > Hello, > > > > We're using Samba 4.1.11 as domain controllers and over

Hello, This won't be a very helpful reply, but I can confirm I've had the exact same issue. I ran into this a few years ago and could not get HyperV migrations to work with a Samba DC. I even went so far as to install a Windows DC just to prove to myself that it is supposed to work, and it does, perfectly (with ADDC it even creates all the SPNs for you auto-magically). Unfortunately at

Hello, Quick observation after recently updating all DC's to 4.2.0 from 4.1.17. Several users received the notice "account is currently locked out" after entering their password once. I updated the policy to a minimum of 3 attempts before any user logged in initially. I opened Microsoft ADUC tool and clicked the box to unlock their account. This resulted in the user receiving

Hi, I've never been a Windows user, but I'm curious to see how the AD integration works in Linux, since it looks like we may need to have one or two Windows desktops and I don't realy want to start setting up Windows infrastructure. If I can have Samba as a domain controller that makes things a lot simpler. I have one question tho, the documentation suggests using the Microsoft

Samba version: 4.1.17 I want to use a Samba AD controller to manage access to both my Windows and Linux boxes. I managed to import my old Samba users using pdbedit however as I want to use the new Samba AD controller to manage access to the Linux workstations too I want to configure Unix properties on all my accounts. Unfortunately I cannot find any command-line tool on Linux that will allow me

Dear all, could someone explain in short about raising the domain function level to W 2008 R2. I thougt I did provision my samba4 DC as W2008 R2 function level, but my domain level show has an output like??: samba-tool domain level show Domain and forest function level for domain 'DC=tplk,DC=loc' Forest function level: (Windows) 2003 Domain function level: (Windows) 2003 Lowest function

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

Hi Andrew, I am deeply impressed by your speed! :D The RODC is actually Samba 4.7.4, the other DCs are still on 4.6.12. Any suggestion how I can debug this w/o setting everything on level 10? ;) Best regards Johannes Am 22.01.2018 um 20:45 schrieb Andrew Bartlett: > On Mon, 2018-01-22 at 20:36 +0100, Johannes Engel via samba wrote: >> Dear all, >> >> setting up a DMZ

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

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

Hi, im trying to setup a password policy with samba and openldap. while lockout works perfect on openldap it looks like it does not work with my samba. Ive set "sambaLockoutThreshold" to 3 and "sambaLockoutDuration" to -1 (lockout forever) within the Domain-Object in LDAP. So i expect whenever a windows user does 3 false logon attemps his samba account will be LOCKED

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

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