similar to: Winbindd Strangeness

On 23/06/15 13:32, David Minard wrote: > I've Set up a DC and a Member Server for a file server. Both are running on Centos7 and samba version 4.2.2. The Member Server is running smbd and winbindd. > > I've followed the wiki and for the most part it's working. However, after stuffing up the ranges, then fixing them up, when I create new accounts, adding all the

> > On 24/06/15 02:55, David Minard wrote: >> On 23/06/15 13:32, David Minard wrote: >> >>> I've Set up a DC and a Member Server for a file server. Both are >>> running on Centos7 and samba version 4.2.2. The Member Server is >>> running smbd and winbindd. >>> >>> I've followed the wiki and for the most part

On 25/06/15 13:44, David Minard wrote: >> On 24/06/15 02:55, David Minard wrote: >>> On 23/06/15 13:32, David Minard wrote: >>> >>>> I've Set up a DC and a Member Server for a file server. Both are >>>> running on Centos7 and samba version 4.2.2. The Member Server is >>>> running smbd and winbindd.

On 01/07/15 03:30, samba-request at lists.samba.org wrote: > Message: 17 > Date: Mon, 29 Jun 2015 08:30:52 +0100 > From: Rowland Penny<rowlandpenny at googlemail.com> > To:samba at lists.samba.org > Subject: Re: [Samba] Winbindd Strangeness > Message-ID:<5590F42C.8050002 at gmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On

Thank you Felix. On 02/07/15 16:18, Felix Matouschek wrote: > Hi David, > > I experienced this issue as well, it's currently a limitation of Samba 4.2.2. > Samba 4.2.2 DCs do not support pulling home directories and login shells from AD via rfc2307. > > I solved this issue with the "template homedir" and "template shell" directives. > You lose some

G'day All, I'm running Centos 7, Samba4.2.2. (SSSD is NOT running (not even installed on the Member Server)) /etc/nsswitch on both: passwd: files winbind group: files winbind the winbind libs have been sym-linked as described in the tiki. All seems to be working well on both the DC and Member Server. Both smb.fonfs have: idmap config *:backend = tdb idmap

G'day All, I'm running up Samba4.2.3 with 4 DCs on Centos7. There are no changes to the default smb.conf file that gets created at provision/DC join. "samba-tool drs showrepl" show all DC replicating in and out. "samba-tool dbcheck" shows no errors. See below for named.conf. I'm having two issues. 1) After bind first starts up

Hi David, > Just to clarify, is it only the DC that doesn't return desired values of HomeDirectory and Shell? Yes, it is only the DC that doesn't pull HomeDirectory and Shell via rfc2307. (when using winbindd) Member servers with winbindd do pull the desired values without problems, I have it setup like this and it works without problems. I have only two ideas to solve your problem:

G'day All, I have 4 DCs on Centos 7.1. Everything was working really well for years, including replication. Then I decided that the OS needed updating. Did the yum update on one of the DCs, rebooted. That server is now running Centos 7.4. Samba seemed to start okay. However, samba-tool drs showrepl gives this error on all 3 of the other DCs, and shows success on the updated DC.

Thanks Carlos, The thing is, that I did not upgrade the version of Samba - that is the next step, so the ports used would not have changed. I only updated the OS. > On 21/03/2018, at 10:04 PM, Carlos Alberto Panozzo Cunha <carlos.hollow at gmail.com> wrote: > > Hi, > I have same problem after update for samba. > I allow new ports in firewall. > >

Hi, I know there've been some workarounds on this topic, however I'm missing the reason for winbind to behave differently on a DC and on a member server (I also had to work around that problem and I'd really like it fixed). If there's a technical reason for it, it'd be nice to know about it. If there isn't, then it's just a bug that should be fixed. Could someone of

hello, Le 23/10/2019 ? 12:45, Rowland penny via samba a ?crit?: > On 23/10/2019 10:51, nathalie ramat via samba wrote: >> Hello, >> >> I have an server ad? - everything seems ok >> I have a windows client and a linux client . The users must to >> connect on windows or on linux with the same home. >> >> when I join my client linux with the command net

Hello, I have an server ad? - everything seems ok I have a windows client and a linux client . The users must to connect on windows or on linux with the same home. when I join my client linux with the command net ads join -U administration I have after the following message net ads join -U administrator Enter administrator's password: Error reading password from file descriptor 0: empty

Hi all, I have just added a DC to our existing AD. Join did work without any error messages but now I have recognized that only inbound replication from old DCs is working outbound list is empty. Samba version is: Version 4.2.0pre1-GIT-cff0f8e here is the output of samba-tool drs showrepl: DSA Options: 0x00000001 DSA object GUID: 94534f65-5d06-41f5-844d-a58a0bc03c93 DSA invocationId:

On 13/06/15 16:33, Jonathan Hunter wrote: > Hi buhorojo, > > I *think* I have a stable system for the moment... so thank you :-) > > On 13 June 2015 at 12:50, buhorojo <buhorojo.lcb at gmail.com> wrote: >>> I now set in smb.conf: >>> >>> server services = -dns +winbind -winbindd >>> >>> I stopped samba, then removed

Le 16/10/2019 ? 09:33, Rowland penny via samba a ?crit?: > On 16/10/2019 07:56, nathalie ramat via samba wrote: >> Hello, >> >> I need help you to understand my error. >> >> I have juste generate samba ad with the following command >> >> samba-tool domain provision --use-rfc2307 --interactive >> Realm:?? SAMBADOM.CALAIS.FR >> Domain

Le 16/10/2019 ? 11:17, Rowland penny via samba a ?crit?: > On 16/10/2019 09:43, nathalie ramat wrote: >> >> I put the trace of the script : > OK, only two problems, one minor, one possibly catastrophic ;-) >> >> Collected config?? --- 2019-10-16-10:23 ----------- >> >> ???????????? Checking file: /etc/hosts >> >> 127.0.0.1?????? localhost

G'day All, We are trying to set up SCCM-5.0. Our AD test is Samba-4.8.5. SCCM requires schema changes, and Samba is rejecting these. Anyone tackled this? Ideas on how to proceed? The output thrown by the SCCM exe (extadsch.exe) is: Microsoft System Center Configuration Manager v5.00 (Build 8634) Copyright (C) 2011 Microsoft Corp. Failed to extend the Active Directory schema. Your

Guys, I have a up and running Samba4 as an AD DC, along side with 3 Domain Controllers, like like: 1- Master - ubuntu-ad-1.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 2- Slave - ubuntu-ad-2.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 3- Slave - ubuntu-ad-3.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 4- Slave - pdwad-1.sambadom.company.com -

Hi, My goal is to make use of samba 4 and freeradius to authenticate user to use wifi network (WPA2 enterprise). The setup is to setup Samba 4.0.3 in machine A and setup freeradius in machine B. By reading: Document A: http://wiki.samba.org/index.php/Samba4/beyond Document B: https://wiki.samba.org/index.php/Samba4/HOWTO/Virtual_Private_Network Document C: