Displaying 20 results from an estimated 20000 matches similar to: "our dns replication: working or not?"
2014 Jul 23
1
problems after lowering tombstone...
Hi all,
Seems we're in much more trouble now... Yesterday I lowered the dn
stombstone lifetime from 180 to 60, to reduce the size of
DC=DomainDnsZones, and ever since, things have become terrible...
The situation now:
I have separate fileserver, and three DC3's, all on the same subnet, kvm
virtual machines, all running sernet-samba. (4.1.7 and 4.1.9)
== on DC3 ==
DNS queries for my
2018 May 17
1
Dcs Replication
On 5/17/2018 3:58 PM, Carlos wrote:
>
> Hi!
>
> In "NTDS settings" created new connection for:
>
> DC2 ->DC3
>
> DC3 -> DC2
>
> All OK,
>
> I tested with option
>
> kccsrv:samba_kcc=No
>
> is ok too.
>
> But in my DC2, a received one erro:
>
> May 17 16:54:44 dc2 samba[10421]: [2018/05/17 16:54:44.543336, 0]
>
2018 May 17
0
Dcs Replication
Hi!
In "NTDS settings" created new connection for:
DC2 ->DC3
DC3 -> DC2
All OK,
I tested with option
kccsrv:samba_kcc=No
is ok too.
But in my DC2, a received one erro:
May 17 16:54:44 dc2 samba[10421]: [2018/05/17 16:54:44.543336, 0]
../source4/dsdb/repl/drepl_out_helpers.c:1087(dreplsrv_update_refs_done)
May 17 16:54:44 dc2 samba[10421]: UpdateRefs failed with
2014 Jul 24
0
Fwd: Re: Fwd: dnsdomainzone replication failure
-------- Original-Nachricht --------
Betreff: Re: Fwd: dnsdomainzone replication failure
Datum: Thu, 24 Jul 2014 13:32:56 +0200
Von: C.Kindler <kindc1 at gmail.com>
An: Achim Gottinger <achim at ag-web.biz>
Many thanks! I didnt thought about Microsoft Admin Tools :-) - Yes with
this is much easier:
Now the replication goes a little forward:
in the logs there are now such
2014 Jul 24
0
Fwd: dnsdomainzone replication failure
Am 24.07.2014 10:53, schrieb C.Kindler:
>
> Hello Achim,
>
> having similar troubles as mentioned on
> https://lists.samba.org/archive/samba/2014-July/182916.html in our domain
>
>
> How to solve the replication error?
>
> Many thanks,
> Chris
>
> ---------- Forwarded message ----------
> From: *C.Kindler* <kindc1 at gmail.com <mailto:kindc1 at
2014 Jul 01
1
sudden replication failures
Hi all,
Samba (sernet) 4.1.7, and we're getting high cpu usage on dc1, and on
dc2 (my 'secondary' dc):
root at dc2:~# samba-tool drs showrepl
Default-First-Site-Name\DC2
DSA Options: 0x00000001
DSA object GUID: 5e93a102-2963-496a-af16-0c51eebb2e31
DSA invocationId: 82b24c02-16cb-4ed1-b68b-a047c26886a9
==== INBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=samba,DC=domain,DC=com
2018 May 17
3
Dcs Replication
Hi!
In Option "Inter-Site Transports", i have only one the name
"DEFAULTIPSITELINK" , in properties
Sites in this link:
Matriz
Filial
Matriz -> site with DC1 and DC2
Filail -> site With DC3
Regards;
On 17-05-2018 13:12, lingpanda101 wrote:
> On 5/17/2018 12:07 PM, Carlos wrote:
>> Hi!
>>
>> Thanks for answer.
>>
>> But, i allowed
2024 Oct 15
0
Problems replacing a DC
Hi all!
I have an AD domain with two DC's, DC3 (samba 4.20.4 from backports in a VM running debian 12) and DC2 (samba 4.18.9 in a VM running slackware 15.0) who holds the FSMO roles and I tried to replace DC2 with another host named DC2 (samba 4.20.5 from backports in a VM running debian 12).
What I did was (in this order):
* Shutdown both DC's
* Snapshot both DC's disks
* Brought
2017 May 10
0
Kcc connection
Ok here is the output:
If the output of the other DCs is needed let me know. On the other DCs there are kcc connections for all other DCs. Just not on dc1.
[root at dc1 ~]# samba-tool drs showrepl
Default-First-Site-Name\DC1
DSA Options: 0x00000001
DSA object GUID: 1781607c-77e8-405d-8c3a-b7e142dd30c4
DSA invocationId: dc096a8a-773d-4a63-8e2a-288ab747557b
==== INBOUND NEIGHBORS ====
2018 May 17
2
Dcs Replication
Hi!
Thanks for answer.
But, i allowed all ports in my firewall...
I tested, shutdown my DC1
DC2 dont comunication with DC3
I create user in DC2, dont replication with DC3...
I waited more in 20 minutes
Why ??
Regards;
On 17-05-2018 12:01, lingpanda101 wrote:
> On 5/17/2018 10:30 AM, Carlos via samba wrote:
>> Hi!
>>
>> I have 2 DC, now add one more DC, but all dcs
2018 May 17
3
Dcs Replication
Hi!
I have 2 DC, now add one more DC, but all dcs dont view between they.
New DC is "DC2"
DC1 - vlan10 -> OK to DC3(Connectad by openvpn)
DC1 -> vlan10 -> OK to DC2(vlan50)
DC2-> vlan50 -> OK to DC1(vlan10)
DC2-> Openvpn -> Dont "see" DC3
DC3 -> Openvpn -> OK to DC1(vlan10)
DC3 -> Openvpn -> Dont "view" DC2(vlan50)
All version
2018 Nov 21
0
Samba4 multiple DCs replication
Le 19/11/2018 à 15:00, Julien TEHERY via samba a écrit :
> Le 19/11/2018 à 12:33, Julien TEHERY via samba a écrit :
>> Le 19/11/2018 à 11:14, Marco Gaiarin via samba a écrit :
>>> Mandi! Julien TEHERY via samba
>>> In chel di` si favelave...
>>>
>>>> Is there a good pratice when adding new remote DCs in terms of
>>>> replication
2018 May 17
0
Dcs Replication
On 5/17/2018 12:07 PM, Carlos wrote:
> Hi!
>
> Thanks for answer.
>
> But, i allowed all ports in my firewall...
>
> I tested, shutdown my DC1
>
> DC2 dont comunication with DC3
>
> I create user in DC2, dont replication with DC3...
> I waited more in 20 minutes
>
> Why ??
>
> Regards;
>
>
> On 17-05-2018 12:01, lingpanda101 wrote:
>>
2019 Aug 11
2
Can't replicate DCs
Hi list,
I'm running into issues with Samba 4.5.16-Debian. I am trying to get 3 DCs
to talk to each other and replicate. DC1 and DC3 are on the same subnet;
DC2 is on another subnet, accessible by IP. Currently, no firewalls on any
of the DCs.
Issue 1 - When I run "samba-tool drs showrepl", I get various results:
DC1 -
Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2
2018 Nov 21
2
Samba4 multiple DCs replication
Cordialement,
Doe Corp
<https://www.openevents.fr/>
<https://www.facebook.com/OPENevents-172305449504004/>
<https://twitter.com/SocOPENevents>
<https://www.linkedin.com/company/openevents/>
Julien Téhéry
Ingénieur Systèmes & Réseaux | OPENevents
15 avenue de l'Europe
86170 Neuville de Poitou
phone : +33 5 49 62 26 03 <tel:+33549622603>
mail :
2016 Dec 18
0
Replication with Multiple Sites in a Hub and Spoke Topology
Hi,
It seems unlikely that the KCC is the cause of these issues. The KCC is
only responsible for telling who to connect (and when) and doesn't
actually affect any underlying network connectivity. Connectivity
between the spokes should not be required and the communication between
them is usually just some stale data. But none of that should affect
either of these commands.
Unless the DRS
2016 Dec 16
2
Replication with Multiple Sites in a Hub and Spoke Topology
Samba 4.5.1 (started with this version as well)
I started with 3 domain controllers, DC1 and DC2 at the hub, and another,
DC3 as a spoke. Everything was running smoothly with this config. No
problems with 'samba-tool drs showrepl'. As soon as I started adding more
'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs
showrepl' command. I believe
2016 Sep 09
0
drs showrepl - Failed to bind to UUID - Undetermined error
Quick, befor i get my beer here..
>> Failed to connect host 127.0.1.1
Check you hosts file for this one, you got 127.0.1.1 there from an install with dhcp.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Jonathan Hunter
> via samba
> Verzonden: vrijdag 9 september 2016 16:25
> Aan: samba
> Onderwerp:
2017 Oct 04
0
Upgrade to 4.7.0 Replication fails on DC2
Hello Community,
after an upgrade from samba 4.6.7 to samba 4.7.0, now i have a
replication issue on my second domain controller. When i type
"samba-tool drs showrepl" all correctly synced, except the following:
==== INBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mydomain,DC=de
Default-First-Site-Name\DC1 via RPC
DSA object GUID: 2abe9f52-9cd5-43c8-9fc2-a67eba27f551
Last attempt @ Wed
2014 May 12
1
errors in replication after adding dns records. ( 4.1.7 )
Hai,
?
Im getting errors now im filling the dns ( through windows tools and samba-tool )
( OS : Debian wheezy, Sernet samba 4.1.7 )
?
On my AD DC, im seeing the following in the log file when i restart samba.
?
May 12 10:59:36 dc1 samba[2170]:?? enteddnsserver: zone operation 'DeleteNode' not implementeddnsserver: zone operation 'DeleteNode' not implementeddnsserver: zone