similar to: Is computer's password changed and how often?

Using ldbsearch we can find needed informations if we know AD Sites names list. Sites informations are stored in CN=CONFIGURATION,DC=SAMBA,DC=DOMAIN,DC=TLD. Here there is a CN=Sites which seems to contains Sites informations. Next using a search with -b 'CN=<site-name>,CN=Sites,CN=CONFIGURATION,DC=SAMBA,DC=DOMAIN,DC=TLD' we can list object related to <site-name>. And we

Hi James, First thanks for you detailed answer and the tests you did to be able to write this. Before reading your mail I was believing MS Windows keeps only one credentials, those for last connected account. This is why I did not pushed too far authentication process. Tomorrow I'm back to work and I'll redo this test, using some others users to test than some I have already used to

2016-10-12 15:26 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Wed, 12 Oct 2016 15:06:08 +0200 > mathias dufresne <infractory at gmail.com> wrote: > > > As SSSD seems to work with others tools (SSH, SMTP auth...), as the OP > > doesn't described his error very clearly, I do think you can't say the > > error is SSSD for sure. You

As SSSD seems to work with others tools (SSH, SMTP auth...), as the OP doesn't described his error very clearly, I do think you can't say the error is SSSD for sure. You can expect the error is from SSSD, you can even be sure of that. But as this error is not clear, how dare be so sure? For 'we do not know, ask sssd' I'm not included in that "we". When I don't

And to get mentioned entries list I used: "samba_dnsupdate --verbose --all-names | grep Default-First-Site-name" This list 8 DNS records related to Default Site. Next was to change Default-First... by the name of another AD Site (sed is still working :p) I was able to create DNS entries which were missing for one of my sites. Next, test: Back on one Windows on the network associated

Hi James and everyone, There is a real issue with samba_dnsupdate and DNS records creation with Samba 4 as AD when it comes to AD Sites. Samba does not seems to create at all any Site relevant DNS record. As AD relies on DNS to find DC on the correct AD site, if no DNS entry is created related to AD Site, no usage of AD Sites. Here Win client ask for domain 11:37:28.671044 IP

On 05/11/15 09:55, mathias dufresne wrote: > Code is like books, or art (painting...). Some guy produce something, as he > likes, some others use/watch/listen it, as they like. Most of the time > these two ways are different. > > What I mean is it is not because something was not developed to be used in > some way that way of usage is not a good way of usage. > > Perhaps

AD from Samba or Microsoft is mainly a database for storing users (and associated stuffs). It comes also with stuffs (protocols) to connect and retrieve information. How the client uses these information is, as always, a choice from that specific client. Your AD client is your Squid/Squidguard(ian) server. Its job as AD client is to get some users information from AD to build system users. I

As he wrote that SSH and SMTP auth and others stuffs are working, I would say SSSD should work. As he wrote there is an issue with Samba, I'd like to understand how he is using Samba, what is the exact error and what he's doing to get that error. Samba should be able to live with other tools. We should be able to able to speak here about Samba working with other tools. But that certainly

I want something like so on login Last login: Wed Feb 1 10:47:53 Password Expires: Wed March 1 00:00:00 [myaduser at machine ~]$ I just want them to know when their password expires. On Wed, Feb 1, 2017 at 9:39 AM, mathias dufresne <infractory at gmail.com> wrote: > Plop, > > You'd like to modify .bashrc to auto-disconnect user with expired > password? I thought modern

2015-10-19 18:08 GMT+02:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > On 19/10/15 16:46, mathias dufresne wrote: > >> AD from Samba or Microsoft is mainly a database for storing users (and >> associated stuffs). It comes also with stuffs (protocols) to connect and >> retrieve information. >> >> How the client uses these information is, as always,

Hi, I've configured sssd so far as advised in the wiki: https://wiki.samba.org/index.php/Local_user_management_and_authentication/sssd getent passwd/group works. Everything seems to be fine. But now I realized, that when I use my domain admin user account to login on that server via ssh, it is not asking for a password. Normal user must authenticate with a password. Where should I look

I tried using sssd but I couldn't get it working based on the info on https://wiki.samba.org/index.php/Sssd I may give it another go anyway. Nico On Mon, Dec 7, 2015 at 1:24 PM, mathias dufresne <infractory at gmail.com> wrote: > In case of... SSSD comes also with a caching method. Using SSSD rather than > Winbind could help in certain cases... > > 2015-12-07 13:00

Hi, After more investigations I'm now believing that we have some issue on our AD site declaration. I'll be back once I would have get more information. Best regards, M. Le jeu. 8 nov. 2018 à 11:22, mathias dufresne <infractory at gmail.com> a écrit : > Hi all, > > AD version is MS 2008R2. > > smb.conf is : > [global] > workgroup = AD > security = ADS

On 12/23/2015 12:39 PM, mathias dufresne wrote: > And for Ole, the OP, to solve its own failover issue: > As there is 2 physical sites and only 2 DC. > Let's say > Site1 is 10.1.0.0/16 > Site2 is 10.2.0.0/16 > I would create 2 additional AD Sites : Site1 + Site2 > To AD site "Site1" I would associate 10.1.0.0/16 and associate also DC1 > To AD site

Or maybe better like so on login Last login: Wed Feb 1 10:47:53 Password Expires in 28 days [myaduser at machine ~]$ On Wed, Feb 1, 2017 at 12:10 PM, Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > I want something like so on login > > Last login: Wed Feb 1 10:47:53 > Password Expires: Wed March 1 00:00:00 > [myaduser at machine ~]$ > > I just want them to know

BTW, this is our smb.conf: # Global parameters [global] workgroup = mydomain realm = mydomain.local netbios name = myhostname server string = Samba AD Client Version %v security = ads password server = dc03, dc04, dc01, dc02, * server role = standalone server winbind separator = + winbind enum users = yes winbind enum groups = yes winbind use default domain = no winbind refresh tickets = Yes

If there was no UNIX/Linux client, it would have been too easy, not fun enough :) File servers will be Linux clients using SSSD for users only, groups will local to these file servers, to limit database usage (because of 4GB limit). Some Linux workstation should be added at some point into this AD, they will also use SSSD to retrieve users and groups. No idea yet about how much of these they

2015-11-05 11:17 GMT+01:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > On 05/11/15 09:55, mathias dufresne wrote: > >> Code is like books, or art (painting...). Some guy produce something, as >> he >> likes, some others use/watch/listen it, as they like. Most of the time >> these two ways are different. >> >> What I mean is it is not because

On 30/06/15 12:51, mathias dufresne wrote: > 2015-06-30 12:42 GMT+02:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > >> On 30/06/15 11:17, mathias dufresne wrote: >> >>> @Andrew: I expect these lines came from RDP issue workaround which should >>> be happening with previous Samba version. I removed all these lines as >>> now, >>>