similar to: WInbindd Home DIrectory and Shell

On 2015-06-16 19:39, Rowland Penny wrote: > On 16/06/15 04:03, Brady, Mike wrote: >> With the switch to using winbindd on Domain Controllers in 4.2, should >> a getent passwd now be showing the home directory and shell that is in >> the RFC2307 attributes in the directory like a member server does? > > No, the 'winbindd' change hasn't altered anything

On 16/06/15 04:03, Brady, Mike wrote: > With the switch to using winbindd on Domain Controllers in 4.2, should > a getent passwd now be showing the home directory and shell that is in > the RFC2307 attributes in the directory like a member server does? No, the 'winbindd' change hasn't altered anything here. > > I all ways thought that this was a difference between

Hi, I am using samba 4.2.1 and want to clarify that do i need to start the winbindd service in AD and DC? Read form the doc https://wiki.samba.org/index.php/RFC2307_backend, it said that: Users having a ?server services? line in their DC smb.conf, need to replace the ?winbind? entry by ?winbindd?: [global] server services = ....., winbind, winbindd Users not having a

> I don't have a "server services" line see the defaults of smb.conf : testparm -vv | grep "server services" and you have your defaults. now you know what the defaults are.., now for example my DC. testparm -vv ( on the DC, samba-tool testparm -vv | grep "server services" ) gives back: server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,

On 2015-08-21 14:11, Brady, Mike wrote: > On 2015-08-21 12:52, John Gardeniers wrote: >> Hi Brady, >> >> I realise that but the only named.conf to be found on the system is my >> newly created /etc/named.conf. Either something screwed up when >> installing the Sernet RPMs, which is really pretty unlikely given that >> everything else is working, or the file

Hi Brady, I realise that but the only named.conf to be found on the system is my newly created /etc/named.conf. Either something screwed up when installing the Sernet RPMs, which is really pretty unlikely given that everything else is working, or the file was not included in the package. regards, John On 21/08/15 10:16, Brady, Mike wrote: > On 2015-08-21 11:18, John Gardeniers wrote:

I bumped the logging up. samba-tool domain level raise --domain-level=2008_R2 schema_fsmo_init: we are master[yes] updates allowed[no] schema_fsmo_init: we are master[yes] updates allowed[no] The updates_allowed[no] concerns me? On Fri, Jul 8, 2016 at 9:45 AM, Jason Waters <jason at geeknocity.com> wrote: > I'm pretty sure the domain level raise is failing on this system.

Hi, http://tools.ietf.org/html/rfc2307 It is used to pull down UNIX information from active directory (namely uid, gid, homedir, shell). Support is partial on domain controller since shell & homedir can only be set through * template parameters in smb.conf despite rfc2307 being used. Shell & homedir are correctly fetched on member servers. Regards, Le 04/06/2015 18:30, buhorojo a

Hello, I'm running Samba 4.5.0 and bind-9.8.2-0.47.rc1.el6_8.1. One DC of four, the PDC, is magnitudes slower running /usr/local/samba/sbin/samba_dnsupdate --verbose --all-names. When that is running on that DC it seems to block any queries. The load average is usually under 0.5. The DC was unsafely halted, which could have corrupted something. I ran a dbcheck with samba-tool and it

Hello there. I´ve been having problems with dynamic dns update by dhcp on my samba ADDC running on CentOS 7 on an RPI2. After a while, the dhccp_dyndns.sh stops stops being able to authenticate with named. for the longest time I was stumped with this, exploring all kinds of kerberos issues, but found out that *restartint* named did resolve the issue. I have finally traced this problem down to a

Can someone please clarify the scope of the remarks in this wiki page: https://wiki.samba.org/index.php/RFC2307_backend specifically, can you confirm that the following applies only to a Member Server, (not the DC)? https://wiki.samba.org/index.php/RFC2307_backend#Configuring_RFC2307_backend_for_Winbind > Configuring RFC2307 backend for Winbind > > Add the following to the [global]

Hi all, I am currently struggling to remove one of our Samba4 DC from the domain. Some time ago, adding a new Samba DC to our AD did not succeed and I had to demote the new server again. After removal, replication on one of the old/existing DCs got weird. /usr/local/samba/bin/samba-tool drs showrepl gives the following: Standardname-des-ersten-Standorts\dc02 DSA Options: 0x00000001 DSA object

I tried to synchronize the sysvol folders, on two dcs. Something went wrong since yesterday we have replication problems: One machine shows this, while the other one is happy. samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ourdomain,DC=com Default-First-Site-Name\DC03 via RPC DSA object GUID: af610e1a-9e3b-4cdd-a36b-c296d77a9479 Last attempt @

Thanks for the suggestion Rowland, I had already tried that though and both secondary DC's resolve.... host -t CNAME fbce444a-8707-4c69-8066-d75aacfb07f0._msdcs.mydomain.com. fbce444a-8707-4c69-8066-d75aacfb07f0._msdcs.mydomain.com is an alias for dc02.mydomain.com. host -t CNAME 04225dbe-d69c-4ea5-8930-eb8746790180._msdcs.mydomain.com.

Ok I'll try that in the morning and will get back with the resilt. On 30 September 2016 at 21:22, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Fri, 30 Sep 2016 20:24:45 +0100 > "Maton, Brett" <matonb at ltresources.co.uk> wrote: > > > Thanks for the suggestion Rowland, I had already tried that though > > and both secondary

Hi Rowland thanks for your response. I'm running samba 4.5.0rc1 on CentOS 7.2 I've dumped the DNS records, and it doesn't appear to have any SRV or NS records. Also the SOA record is pointing at the wrong server dc03 instead of dc01. I'm pretty sure it can be fixed, but I don't know how or what to do On 27 September 2016 at 07:59, Rowland Penny via samba < samba at

Hi i'm actually trying to migrate my samba 3.6 PDC NT-4 domain with openldap as backend to samba4 AD type domain witch bind_dlz so i followed the documentation https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 the command : samba-tool domain classicupgrade --dbdir=/root/sambe/ --use-xattrs=yes --realm=mydom.local --dns-backend=BIND9_DLZ

We are using Samba-4.1.11. I can run gpupdate /force without error on my machine. H:\>type \\dc01.mediture.dom\SysVol\mediture.dom\Policies\{77F82F0F-AE2B-42F3-B173-D42F4BEEC0BA}\gpt.ini [General] Version=65551 displayName=New Group Policy Object H:\>type \\dc02.mediture.dom\SysVol\mediture.dom\Policies\{77F82F0F-AE2B-42F3-B173-D42F4BEEC0BA}\gpt.ini [General] Version=65551 displayName=New

I've googled and I believe that SASL method DIGEST-MD5 is supported and I see it in the samba startup, but it doesn't work. ldapsearch -Y DIGEST-MD5 -h dc03.mediture.dom SASL/DIGEST-MD5 authentication started ldap_sasl_interactive_bind_s: Operations error (1) additional info: SASL:[DIGEST-MD5]: Failed to start authentication backend: NT_STATUS_INVALID_PARAMETER [root at dc03 ~]# samba

Is it possible to specify a list of DCs for Samba to use, rather than have it look them up dynamically via DNS? I have an issue with Kerberos, Samba, and SSSD where my machines stop authenticating after a period of time – preAuthentication errors, etc. I suspect it's because of a "DC mismatch" between the three. Because we have numerous DCs all over the world, I specifically