similar to: GSSAPI - Server not found errors

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

Thanks Rowland, You saved me from a world of pain, I've now got named back up and running and also accessible via windows DNS GUI. the SOA record still says ns=dc03.. which is strange and the only place dc03 exists in the ouput of samba-tool dns query localhost mydomain.com @ ALL Is this something I can fix in the windows DNS GUI or do I need to do something with like FSMO ? Which btw

Hi, I removed a couple of dead DC's from my domain using this command: samba-tool domain demote --remove-other-dead-server=<dc name> I then restarted named on the remaining server, but it failed to start with the following errors in messages: named[30255]: samba_dlz: configured writeable zone 'x.x.x.in-addr.arpa' named[30255]: samba_dlz: configured writeable zone

Hello, I would like to know how to know if a classification tree is predictive or not ? Is it sufficient to analyse results of cross validation? Thanks for your help Laure Maton

I''ve configured puppet to use storedconfigs and puppetDB, If I start the puppet master using the init script puppetmaster I get a permission denied error when a node connects: Master: [root@puppet ~]# service puppetmaster start Starting puppetmaster: [ OK ] Node: [root@puppet-slave ~]# puppet agent --test err: Could not retrieve catalog from remote

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

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 @

I'm having a bit of trouble joining / starting an additional DC. OS: CentOS 7,2 Samba: 4.5.0 I've run through the steps on the wiki page: https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory I did have to manually add the DNS entries. When I start samba I see the following errors in /var/log/messages:

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

Hi All, In my environment, I have a total of 4 DCs (Samba 4.7.6) running in VMs. Their uptime schedule goes like this: dc00 : usually 100% unless there's a failure. dc01 : same as above dc02 : a few days per week. dc03 : a few days per month. This has the consequence that a DNS A lookup on the AD domain shows 4 IPs, 2 of which are usually not up. Because I don't have shared storage in

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, - I have changed my /etc/resolv.conf for all my three DCs. ### DC 01-03 nameserver 10.10.10.11 nameserver 10.10.10.12 nameserver 10.10.10.13 search intern.preiss.network - In the next step I changed my /etc/hosts for each DC ### DC1 127.0.0.1 localhost 10.10.10.11 01-dc01.intern.preiss.network 01-dc01 ### DC2 127.0.0.1 localhost 10.10.10.12 01-dc02.intern.preiss.network 01-dc02

I was wondering how to configure the puppet clients to only listen, not to periodically pull configs down from the puppetmaster. I''d rather push the configs out from the puppetmaster with puppetrun... At a guess I need to set runinterval to 0 in /etc/puppet/puppet.conf? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

You believe that SSSD is bypassing Samba entirely and going direct to Kerberos? That’s possible. At the moment, to the best of my understanding, Samba is only being used to join the domain. There are no file/printer/etc. shares happening; this is just basic domain join/membership and keytab generation and after that it’s done. The question was still specific to Samba itself: can I specify the DCs