similar to: UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT

Displaying 20 results from an estimated 500 matches similar to: "UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT"

2015 May 28
2
RES: UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT
[2015/05/28 14:41:18.977544, 0] ../source4/smbd/server.c:370(binary_smbd_main) samba version 4.1.16 started. Copyright Andrew Tridgell and the Samba Team 1992-2013 [2015/05/28 14:41:19.173118, 0] ../source4/smbd/server.c:488(binary_smbd_main) samba: using 'standard' process model [2015/05/28 14:41:19.196917, 0] ../lib/util/become_daemon.c:136(daemon_ready) [2015/05/28
2015 Jun 01
0
RES: UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT
On 05/28/2015 11:54 AM, EDGARD B SOUZA wrote: > [2015/05/28 14:41:18.977544, 0] ../source4/smbd/server.c:370(binary_smbd_main) > samba version 4.1.16 started. > Copyright Andrew Tridgell and the Samba Team 1992-2013 > [2015/05/28 14:41:19.173118, 0] ../source4/smbd/server.c:488(binary_smbd_main) > samba: using 'standard' process model > [2015/05/28
2018 May 18
3
Dcs Replication
On Thu, 17 May 2018 20:24:06 -0300 Carlos <carlos.hollow at gmail.com> wrote: > Thank  very much you for the explanations!! > I'm sorry for one more question... > What is wrong in DCs in mode " full mesh topology" ? I don't > understand why not... Nothing, except that you are using an openvpn link between sites (not that this really matters, it would be the
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
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 Feb 08
2
Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375
Hello,I'm using samba ad dc about a year. I have 2 DCs, One is DC1 with FSMO role. And another is DC2. there's a error in DC1 when i use dbcheck tool. And samba-tool dbcheck --cross-ncs--fix can't fix that. And I made a big mistake ! In DC2 I use "tdbbackup -s .bak /var/lib/samba/private/sam.ldb" create a bak file. and using that bak file replace the sam.ldb
2018 May 17
2
Dcs Replication
On Thu, 17 May 2018 16:58:13 -0300 Carlos via samba <samba at lists.samba.org> 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
2018 May 18
2
Dcs Replication
On Fri, 18 May 2018 08:50:44 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > Thanks very much agian, but a really think is "good"  all dcs > replication(full  mesh). > > I read more about "sites"(link send for you). > > But i dont understand msg the erro: > > ------------------- > > May 17 16:54:44 dc2
2019 May 15
2
self compiled 4.10.3 replication failure.
Hi, I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an existing samba AD domain that has 2 existing DCs. One of the existing DCs is running 4.8.7 and the other is running 4.7.7. Everything looks OK except that when I run samba-tool drs showrepl on the new DC (VDC4) I get the following output: (vdc4 pts4) # samba-tool drs showrepl Default-First-Site-Name\VDC4 DSA Options:
2013 Nov 18
5
How to keep samba4 dc work fine when windows dc offline?
I'm testing a samba4 server join AD (had 1 win2003 dc) as dc. Version: Samba4 DC: samba 4.1.1 with ubuntu (172.16.3.8) Win2003 DC: Win2003 SP2 (172.16.3.3) AD domain name: dotest.com The samba server had joined to AD as DC. When win2003 dc online, it seems works fine. When I test win2003 dc online, simulate the win2003 DC was failue, found the samba4 DC can't work fine along. The AD
2016 Apr 01
4
Samba suddenly restart and replication does not works anymore
Hello Samba team ! On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) : -> One PDC : pdc01 -> Two "slave" DC : sdc02, sdc03 I don't know why, but sometimes Samba receive the SIGTERM signal and restart even if I remove it from the logrotate configuration. On "pdc01" I see : ---------- pdc01 (log.samba) ---------- SIGTERM: killing children
2017 Dec 27
2
AD replication problem "WERR_DS_DRA_ACCESS_DENIED" - need help debugging
We have 3 ADCs based on Samba-4.7.4 (compiled from source,internal DNS)/ CentOS7: dcdo1,dcnh1 and dcge1. dcge1 holds all FSMO roles. The 3 ADCs are on different locations connected via IPSec based VPN. No traffic is filtered out. All 3 ADCs replicate fine except dcdo1 -->dcnh1. Symptom: [root at dcdo1 ~]# samba-tool drs replicate dcnh1.ad.kdu.com dcdo1.ad.kdu.com dc=ad,dc=kdu,dc=com
2011 Jun 07
1
removing windows 2003 from samba4
Hello! I've setup last version of samba on git repositories, Samba version 4.0.0alpha16-GIT-43ab5aa and joined a windows 2003 as a additional domain controller, but when i try to remove these domain controller with dcpromo command appears the following error on log.samba: [2011/06/07 00:18:55, 0] ../source4/dsdb/repl/drepl_out_helpers.c:765(dreplsrv_update_refs_done) UpdateRefs failed
2019 May 20
4
self compiled 4.10.3 replication failure.
On Sat, 18 May 2019, Nico Kadel-Garcia wrote: > On Wed, May 15, 2019 at 4:32 PM Tom Diehl via samba > <samba at lists.samba.org> wrote: >> >> Hi, >> >> I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an >> existing samba AD domain that has 2 existing DCs. One of the existing DCs is >> running 4.8.7 and the other is running
2017 Dec 27
2
AD replication problem "WERR_DS_DRA_ACCESS_DENIED" - need help debugging
On Wed, 27 Dec 2017 13:00:05 +0100 "Dr. Johannes-Ulrich Menzebach via samba" <samba at lists.samba.org> wrote: > There is additional info in the logs of the source DC (dcdo1, log > level 2, manually triggered another replication): > ==================== > [2017/12/27 12:31:29.695121,  2] >
2018 May 09
4
DsGetNCChanges 2nd replication on different
On Wed, 9 May 2018 08:37:38 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > More information: > > samba -v (compilated) > > Version 4.4.4 > > Totla Dcs = 16 > > smb.conf: > > [global] >         workgroup = XXXX >         realm = XXXX.xxxxx.com.br >         netbios name = upsilon >         server role = active
2016 Apr 04
1
Samba suddenly restart and replication does not works anymore
>> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba receive the SIGTERM signal and >> restart even if I remove it from the logrotate configuration. On >>
2024 Feb 10
1
kcc_periodic output
Hi samba list!!! Douglas, /usr/sbin/samba_kcc is made in python. Does it have a link to source4/dsdb/kcc/kcc_periodic.c which is made in C? The errors that appear in my DCs have their output in the C code. Correct me if I'm wrong, but I read in some old posts on the list that samba would have a new code for kcc (python code?), which would be closer to what M$ uses. Could this have anything
2018 May 09
2
Fwd: Re: DsGetNCChanges 2nd replication on different
HI ! I demote dc "same" name and rename dc, but same IP adresss. But erro persiste... DC "new name" May  9 15:34:39 dcXXX-NEW samba[12278]:   UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT code 0xc0002105 for 37ba1799-307a-49ef-a6df-3657da7c4c98._msdcs.XXXX DC=DomainDnsZones,DC=XXX,DC=XXX,DC=XXX,DC=XX 37ba1799-307a-49ef-a6df-3657da7c4c98 = dcXXX-NEW Any  ideia ?
2016 Apr 03
1
Samba suddenly restart and replication does not works anymore
2016-04-01 23:36 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 30/03/16 13:35, Prunk Dump wrote: >> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba