Displaying 5 results from an estimated 5 matches for "4e94".
Did you mean:
494
2018 May 09
2
Fwd: Re: DsGetNCChanges 2nd replication on different
...c:1657(dcesrv_drsuapi_DsGetNCChanges)
May 9 15:36:34 dzeta samba[22387]:
../source4/rpc_server/drsuapi/getncchanges.c:1657: DsGetNCChanges 2nd
replication on different DN
CN=Schema,CN=Configuration,DC=XX,DC=XXX,DC=XXX,DC=XX
CN=Configuration,DC=XXX,DC=XXX,DC=XX,DC=XXX (last_dn
CN=b04efd5a-4691-4e94-87d6-2a1a3cf3a08c,CN=NTDS
Settings,CN=DCYYY,CN=Servers,CN=YYYY,CN=Sites,CN=Configuration,DC=XXX,DC=XXX,DC=XXX,DC=br)
Regards;
-------- Forwarded Message --------
Subject: Re: [Samba] DsGetNCChanges 2nd replication on different
Date: Wed, 9 May 2018 12:37:17 -0300
From: Carlos <carlos.ho...
2018 May 09
2
DsGetNCChanges 2nd replication on different
On Wed, 9 May 2018 11:02:45 -0300
Carlos via samba <samba at lists.samba.org> wrote:
> Thanks;
>
> but, i can use same name ou change name ?
Upgrading in situ, then yes you can use the same data and to be honest,
you should, but if you demote a DC, NEVER user the same name again
(well not until you are 100% positive there are no traces of the old
name in AD, probably at least 6
2016 Sep 23
6
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
...ls me
SOLDC2 becomes an island without anyway to replicate.
One strange thing is 'samba-tool drs showrepl' begs to differ.
root at soldc2:~# samba-tool drs showrepl
site-b\SOLDC2
DSA Options: 0x00000001
DSA object GUID: 25055641-49e7-4b3f-a7e3-9d206375306c
DSA invocationId: d11890e8-6b90-4e94-aca4-6d7a940f47b5
==== INBOUND NEIGHBORS ====
CN=Configuration,DC=domain,DC=local
site-b\SOLDC1 via RPC
DSA object GUID: 55e069f5-4f47-415b-8fa4-a398948235aa
Last attempt @ Fri Sep 23 14:40:18 2016 EDT was successful
0 consecutive failur...
2016 Sep 24
0
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
...anyway to replicate.
>
> One strange thing is 'samba-tool drs showrepl' begs to differ.
>
> root at soldc2:~# samba-tool drs showrepl
> site-b\SOLDC2
> DSA Options: 0x00000001
> DSA object GUID: 25055641-49e7-4b3f-a7e3-9d206375306c
> DSA invocationId: d11890e8-6b90-4e94-aca4-6d7a940f47b5
>
> ==== INBOUND NEIGHBORS ====
>
> CN=Configuration,DC=domain,DC=local
> site-b\SOLDC1 via RPC
> DSA object GUID: 55e069f5-4f47-415b-8fa4-a398948235aa
> Last attempt @ Fri Sep 23 14:40:18 2016 EDT was
> successful...
2016 Sep 22
2
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
On 9/21/2016 11:32 PM, Garming Sam wrote:
> I would have assumed that deleting all the NTDS connections for all the
> DCs would have remedied this issue. I'll write a patch to try to avoid
> this error in any case.
>
> Ignoring this error and answering your earlier question, it's often hard
> to tell if the KCC is doing what is expected or not. To figure that out,
>