search for: infractori

On Thu, 31 Aug 2017 16:27:12 +0200 mathias dufresne <infractory at gmail.com> wrote: > PS: the short way to explain %u is adding domain/workgroup to > username is the fact we are using trust relationship? > Probably, what you have to get your head around is this: The users 'fred', 'DOMAINA\fred' and 'DOMAINB\fred' are all different users. Winbind will

2017-08-30 16:15 GMT+02:00 mathias dufresne <infractory at gmail.com>: > > > 2017-08-30 16:05 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org> > : > >> On Wed, 30 Aug 2017 15:01:05 +0200 >> "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: >> >> > Small addition. >> > >> > > have in

2016-10-19 8:56 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Wed, 19 Oct 2016 08:47:25 +0200 > mathias dufresne <infractory at gmail.com> wrote: > > > > > > > > > The domain member will ask its nameserver (which should be an AD > > > DC), > > > > > > > The client send request to its resolver, which

from both DC: dig google.com dig @8.8.8.8 google.com First dig will use resolvers declared into /etc/resolv.conf. Second dig forces usage of 8.8.8.8. Both commands should reply the same things, on all DC. 2016-06-30 15:58 GMT+02:00 lingpanda101 at gmail.com <lingpanda101 at gmail.com>: > On 6/30/2016 9:57 AM, Garland McAlexander wrote: > >> nslookup google.com

nslookup google.com ;; Got recursion not available from 192.168.1.236, trying next server Server: 192.168.1.235 Address: 192.168.1.235#53 Non-authoritative answer: Name: google.com Address: 172.217.4.78 Interesting little bit about the "Recursion not available" On Thu, Jun 30, 2016 at 9:52 AM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: >

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

PS: I could share information about what should be modified to modify the very same GPO, I didn't yet as I'm not sure anyone there would be interested and because that would work only for that kind of GPO. 2016-07-06 17:08 GMT+02:00 mathias dufresne <infractory at gmail.com>: > Context: several teams have to manage only a a bunch of the company's > computers, so these

All DC are running same Samba version : 4.4.2. All DC are hosted on same Centos 7. On broken server(s): wbinfo -i mdufresne failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user mdufresne On working servers: wbinfo -i mdufresne AD.DOMAIN\mdufresne:*:12104:100:Mathias Dufresne (TEMP):/home/AD.DGFIP/mdufresne:/bin/false The smb.conf is:

On Tue, Jul 12, 2016 at 10:13 AM, mathias dufresne <infractory at gmail.com> wrote: > Could you simply try to modify type=forking to type=notify and test again? > Perhaps your old has disappeared (they do sometimes, not often enough)... Seems to work for starting smbd and nmbd (although Type=forking has been running flawlessly for many months) on my Gentoo system. In my Debian LXC

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

bus-ny-dc-01 ~]# dig google.com ; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7_2.3 <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 779 ;; flags: qr rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:;

On Wed, 5 Oct 2016 12:04:53 +0200 mathias dufresne via samba <samba at lists.samba.org> wrote: > I just tested on some DC running also 4.4.5 and "getent group > my_group" does not show groups content. > > I read here > http://serverfault.com/questions/625416/samba-4-group-members-not-shown-in-getent-group > a proposal to use samba-tool as a replacement but

On Wed, Nov 4, 2015 at 11:09 AM, mathias dufresne <infractory at gmail.com> wrote: > Hi, > > Once you have installed Samba to be able to run it as Active Directory you > would have samba-tool available. > > # which samba-tool > /usr/bin/samba-tool > # file /usr/bin/samba-tool > /usr/bin/samba-tool: Python script, ASCII text executable > # locate ldapcmp.py >

Hi Jonathan, Thank you for that, that solved the issue. Unfortunately I get another issue: on one DC id <user> gives "no such user". Adding domain (id ad.domain\\<user>) does not help. Adding the whole domain (id ad.domain.tld\\<user>) does not help more. I did checked PAM, NSS and Samba configurations, this server is using same configurations as the two working DC.

On 6/30/2016 9:57 AM, Garland McAlexander wrote: > nslookup google.com <http://google.com> > ;; Got recursion not available from 192.168.1.236, trying next server > Server: 192.168.1.235 > Address: 192.168.1.235#53 > > Non-authoritative answer: > Name: google.com <http://google.com> > Address: 172.217.4.78 > > > Interesting little bit

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 27 January 2016 at 17:40, mathias dufresne <infractory at gmail.com> wrote: > Hi, > > Samba DC generates a krb5.conf into private directory, where the database > is hold. > > Its content should be that: > [libdefaults] > default_realm = SAMBA.DOMAIN.TLD > dns_lookup_realm = false > dns_lookup_kdc = true > > Should only as I get

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

If my messages seems somehow unreadable - I sent it from Gmail Web UI. mathias dufresne, read my 2 or 3 last messages. I wrote about mounting \\server\share as disk and risky fo viruses crypting files. Also read messages other, who does not work in AirBus. And more over, it' s your oppinion. But I see useless of more discussion at atll. If you want to combine your efforts to help with

You do what you want! The point is the clients must resolve everything. You have two options: A - client resolver is non-DC DNS server: here the non-DC DNS server must be configured to forward DNS requests about AD to AD DNS servers (to DCs) B - client resolver is AD DNS server: here AD DNS server(s) used as resolver(s) must be configured to forward any non-AD DNS request to non-DC DNS server.