search for: dc03

...his, 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 *reload* of named.conf, that occurs as part of a logrotate. When I issue "*systemctl reload named*" I get this log: ... Jan 09 15:28:52 dc03.rvx.is named[15585]: reloading configuration succeeded Jan 09 15:28:52 dc03.rvx.is named[15585]: reloading zones succeeded Jan 09 15:28:52 dc03.rvx.is named[15585]: all zones loaded Jan 09 15:28:52 dc03.rvx.is named[15585]: *samba_dlz: shutting down* Jan 09 15:28:52 dc03.rvx.is named[15585]: runnin...

...DSA object GUID: c60bca82-df6e-409e-85c5-e2cc733691da Last attempt @ Thu May 8 14:49:28 2014 CEST was successful 0 consecutive failure(s). Last success @ Thu May 8 14:49:28 2014 CEST DC=samdom,DC=loc Standardname-des-ersten-Standorts\dc03 via RPC DSA object GUID: 94534f65-5d06-41f5-844d-a58a0bc03c93 Last attempt @ Thu May 8 14:49:24 2014 CEST was successful 0 consecutive failure(s). Last success @ Thu May 8 14:49:24 2014 CEST DC=ForestDnsZones,DC=samdom,DC=loc...

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

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 @ Fri Mar 27 12:58:42 2015 CET failed, result 121 (WERR_SEM_TIMEOUT) 126 consecutive failure(s). Last success @ Fri Mar 27 03:40:24 2015 CET DC=ForestDnsZones,DC=ourdomain,DC=com De...

...dc = false ticket_lifetime = 24h renew_lifetime = 7d forwardable = true default_keytab_name = FILE:/etc/krb5.keytab [realms] MEDITURE.DOM = {); if ($random >= 4) { print $krb5_conf_fh " kdc = dc01.mediture.dom\n"; print $krb5_conf_fh " kdc = dc03.mediture.dom\n"; print $krb5_conf_fh " kdc = dc02.mediture.dom\n"; print $krb5_conf_fh " kdc = dc04.mediture.dom\n"; } else { print $krb5_conf_fh " kdc = dc03.mediture.dom\n"; print $krb5_conf_fh " kdc = dc01.m...

..., running on two of the DCs. Is this correct? Finally, dynamic NDS updates from the DHCP server seem to take some 8 or nine seconds, during which time a cliend does not get a DHCPD ack. Sometimes the client gives up waiting. I'm currently looking into this, but here is a log: Nov 30 14:48:32 dc03.rvx.is dhcpd[15712]: Commit: IP: 192.168.53.20 DHCID: 1:0:20:85:ed:5:d0 Name: ups208 Nov 30 14:48:32 dc03.rvx.is dhcpd[15712]: execute_statement argv[0] = /etc/dhcp/bin/dhcp-dyndns.sh Nov 30 14:48:32 dc03.rvx.is dhcpd[15712]: execute_statement argv[1] = add Nov 30 14:48:32 dc03.rvx.is dhcpd[15712]:...

...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 Group Policy Object H:\>type \\dc03.mediture.dom\SysVol\mediture.dom\Policies\{77F82F0F-AE2B-42F3-B173-D42F4BEEC0BA}\gpt.ini [General] Version=65551 displayName=New Group Policy Object H:\>type \\dc04.mediture.dom\SysVol\mediture.dom\Policies\{77F82F0F-AE2B-42F3-B173-D42F4BEEC0BA}\gpt.ini [General] Version=65551 displayName=New G...

...AME 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. 04225dbe-d69c-4ea5-8930-eb8746790180._msdcs.mydomain.com is an alias for dc03.mydomain.com. On 30 September 2016 at 19:52, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Fri, 30 Sep 2016 19:44:36 +0100 > "Maton, Brett via samba" <samba at lists.samba.org> wrote: > > > I think I'm missing some SRV records... > &g...

...t; 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. > > 04225dbe-d69c-4ea5-8930-eb8746790180._msdcs.mydomain.com is an alias > > for dc03.mydomain.com. > > > > Try restarting samba on dc02 and dc03, if that doesn't work, reboot > dc02 and then dc03 > > Rowland > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/s...

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 (samba-tool fsmo show) lists everything as being owned by dc01 Thanks ag...

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 this setup and since all of the VM's hosting the DC's are orchestrated externally, I decided to come up with the...

....example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote01-dc01.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote01-dc02.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote02-dc01.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote02-dc03.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote03-dc01.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote03-dc02.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote04-dc01.example.domain.com [0, 100, 88] ads_dns_parse_rr_srv: Parsed remote04-...

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 lists.samba.org> wrote: > On Mon, 26 Sep 2016 22:44:36 +0100 > "Maton, Brett via samba" <samba at lists.samba.or...

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 -i -M single -d3 lpcfg_load: refreshing parameters from /usr/local...

I think I'm missing some SRV records... Calling nsupdate for SRV _ldap._tcp.Default-First-Site-Name._ sites.ForestDnsZones.mydomain.com dc03.mydomain.com 389 (add) Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.mydomain.com. 900 IN SRV 0 100 389 dc03.mydoma...

...- 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 ### DC3 127.0.0.1 localhost 10.10.10.13 01-dc01.intern.preiss.network 01-dc03 As mentioned , I've installed a 3rd DC without any issues from http://www.corpit.ru/mjt/packages/samba/. Now the 3rd DC has the same Problem as the 2nd one. Only the 1st DC has no issues. /var/log/syslog [...] Jun 23 06:05:20 01-dc03 samba[87230]: [2024/06/23 06:05:20.132829, 0] source4/rpc_...

...ple.domain.com [0, > 100, 88] > > ads_dns_parse_rr_srv: Parsed remote01-dc02.example.domain.com [0, > 100, 88] > > ads_dns_parse_rr_srv: Parsed remote02-dc01.example.domain.com [0, > 100, 88] > > ads_dns_parse_rr_srv: Parsed remote02-dc03.example.domain.com [0, > 100, 88] > > ads_dns_parse_rr_srv: Parsed remote03-dc01.example.domain.com [0, > 100, 88] > > ads_dns_parse_rr_srv: Parsed remote03-dc02.example.domain.com [0, > 100, 88] > > ads_dns_parse_rr_srv: Parsed remo...

Found the problem. There is a DNS Problem on one machine. This happend because I was testing some samba AD settings in a virtual machine, without knowing that NAT isn't shielding this properly - this vm propagated the "new" IP to one of the dcs. DC04> ping DC03 gives wrong IP! This should be fixable with the samba-tool dns update? On 03/27/2015 01:14 PM, Johannes Amorosa | Celluloid VFX wrote: > I tried to synchronize the sysvol folders, on two dcs. Something went > wrong since yesterday we have replication problems: > One machine shows this,...

On Sun, 23 Jun 2024 09:34:46 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Now the 3rd DC has the same Problem as the 2nd one. > Only the 1st DC has no issues. > > /var/log/syslog > [...] > Jun 23 06:05:20 01-dc03 samba[87230]: [2024/06/23 06:05:20.132829, 0] > source4/rpc_server/dnsserver/dcerpc_dnsser > > ver.c:1076(dnsserver_query_zone) > Jun 23 06:05:20 01-dc03 samba[87230]: dnsserver: Invalid zone > operation IsSigned > Jun 23 06:05:21 01-dc03 samba[87230]: [2024/06/23 06:...

...MAIN\administrator]: INFO 2023-10-25 11:56:41,616 pid:403032 /usr/local/samba/lib/python3.10/site-packages/samba/join.py #1614: workgroup is MYDOMAIN INFO 2023-10-25 11:56:41,617 pid:403032 /usr/local/samba/lib/python3.10/site-packages/samba/join.py #1617: realm is mydomain.special.de Adding CN=DC03,OU=Domain Controllers,DC=mydomain,DC=special,DC=de Adding CN=DC03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=special,DC=de Adding CN=NTDS Settings,CN=DC03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=special,DC=de DsAddEntry fa...