similar to: dsdb_access Access check failed on CN=Configuration

Displaying 20 results from an estimated 2000 matches similar to: "dsdb_access Access check failed on CN=Configuration"

2019 May 22
2
dsdb_access Access check failed on CN=Configuration
----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: > Try again with : > > samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST > As in dc5.your.dns.domain.tld ... > > Whats the result.? The failure is still present -- no change in the output of the command: # samba-tool ldapcmp dc3.domain.local dc5.domain.local DNSFOREST ERROR(ldb):
2019 May 22
0
dsdb_access Access check failed on CN=Configuration
Try again with : samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST As in dc5.your.dns.domain.tld ... Whats the result.? If it fails, please tell os your: OS? Content of /etc/hosts /etc/resolv.conf /etc/nsswitch.conf /etc/samba/smb.conf > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mike > Ray via samba >
2019 May 22
2
dsdb_access Access check failed on CN=Configuration
----- On May 22, 2019, at 11:07 AM, samba samba at lists.samba.org wrote: > On 22/05/2019 16:29, Mike Ray via samba wrote: >> ----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: >> >>> Try again with : >>> >>> samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST >>> As in dc5.your.dns.domain.tld ...
2019 May 22
0
dsdb_access Access check failed on CN=Configuration
On 22/05/2019 16:29, Mike Ray via samba wrote: > ----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: > >> Try again with : >> >> samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST >> As in dc5.your.dns.domain.tld ... >> >> Whats the result.? > The failure is still present -- no change in the output of the command:
2019 Sep 03
2
4.9.12 operation unavailable without authentication
I have Samba in production (4.9.6-12 on Ubuntu 18.04) which is working well. However, we are several releases behind so I am gearing up to upgrade to the latest 4.9 release. As part of the preparations (and for other reasons), I spun up an upgraded DC cluster in our development environment (4.9.12-15 on Ubuntu 18.04). The initial setup seemed to work and now I have two DCs that appear to be
2019 May 22
2
dsdb_access Access check failed on CN=Configuration
Poking around on this further, I believe the LMHOSTS error does not matter. The smb directive "name resolve order" defaults to "lmhosts wins host bcast" -- so I believe the file no found error is just because it's trying lmhosts first, not finding the file and then moving on. Eventually it hits "host" resolution and uses /etc/hosts to resolve the name. Changing
2019 May 01
2
Replication failures
Hai Mason,   I had a look at the debug output.   on 1) why around 15-16 second, that i really dont know. im trying to figure that out. on 2) if DNS is inconsistance, that everything is unrelayable. This is really the first the that needs fixing. then we look again at the replication.   The debug output still shows several messages about zones in flat files. I still do believe also that this
2019 Apr 29
4
Replication failures
Hai, I snapped this part of you logs. > Successful AuthZ: [DCE/RPC,krb5] user [COMPANY]\[DC6$] [S-1-5-21-2660373802-310620142-1895175072-6626] at [Fri, 26 Apr 2019 10:16:20.224329 PDT] Remote host [ipv4:10.14.16.11:35006] local host [ipv4:10.12.16.11:49153] > [2019/04/26 10:16:23.503632, 0] ../../source4/lib/cmdline/popt_common.c:74(popt_s4_talloc_log_fn) > Bad talloc magic value
2015 Jul 16
3
4.2.2 as AD with 2 DCs: database incoherency
On my site with samba 4.18 on centos 6: 'samba-tool ldapcmp ldap://DC1 ldap://DC2 -Uadministrator' failed with this result msDS-NC Type failed : [root at s4master ~]# samba-tool ldapcmp ldap://s4master ldap://s4slave -Uadministrator Password for [TPLK\administrator]: * Comparing [DOMAIN] context... * Objects to be compared: 606 Comparing: 'CN=Builtin,DC=tplk,DC=loc'
2015 Jul 16
2
4.2.2 as AD with 2 DCs: database incoherency
Here I obtained: --------------------- * Comparing [DOMAIN] context... Failed search of base=DC=ad,DC=domain,DC=tld ERROR(ldb): uncaught exception - LDAP client internal error: NT_STATUS_UNEXPECTED_NETWORK_ERROR File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File
2019 Jun 25
2
One DC cannot authenticate off of another DC
Hello Samba Friends, I have a single DC (we'll call it, "DC1") that simply will not take my password when I run this command:? #samba-tool ldapcmp ldap://dc2 ldap://dc3 -Uadministrator? Or this command:? #samba-tool ldapcmp ldap://dc1 ldap://dc2 -Uadministrator? I basically get this:? > Password for [SAMDOM\administrator]:? > Password for [SAMDOM\administrator]:?
2019 Jun 26
4
One DC cannot authenticate off of another DC
Thank you, Louis, for your reply. By simply asking me to provide outputs of the aforementioned files, I found the cause of my first problem (auth failing). It was my /etc/hosts file on dc1. All of them should look like this, and indeed DC2 and DC3's *did* look like this: # cat /etc/hosts > 127.0.0.1 ? ? ? localhost.samdom.mycompany.net ?localhost > 192.168.3.201
2015 Jul 16
2
4.2.2 as AD with 2 DCs: database incoherency
Am 16.07.2015 um 17:18 schrieb Rowland Penny: > On 16/07/15 13:27, Reindl Harald wrote: >> >> Am 16.07.2015 um 14:02 schrieb Rowland Penny: >>> /etc/hosts should be: >>> >>> 127.0.0.1 localhost.localdomain localhost >> >> uhm no - you want 127.0.0.1 normally resolved to localhost and hence >> 127.0.0.1 localhost
2015 Sep 01
2
ldapcmp issue
Hi all, It seems "samba-tool ldapcmp" does not support too much items in Samba's database. Playing for a while with DB I was never able to run ldapcmp successfully. So yesterday I installed a platform to fill piece by piece my two small DCs and to run ldapcmp. The process follows. Test platform: 2 DCs using Debian 8.1 "net install" with only system tools, up to date,
2019 May 22
0
dsdb_access Access check failed on CN=Configuration
On 22/05/2019 18:24, Mike Ray wrote: > Poking around on this further, I believe the LMHOSTS error does not matter. > > The smb directive "name resolve order" defaults to "lmhosts wins host bcast" -- so I believe the file no found error is just because it's trying lmhosts first, not finding the file and then moving on. > > Eventually it hits "host"
2015 Apr 23
3
samba-check-db-script python failure
I went and got the newest (upped recently) script. No love. I removed the email address line to get more command line output. root at dc01:~# ./samba-check-db-repl.sh Running with with console output Running : /usr/bin/samba-tool ldapcmp --filter='whenChanged' ldap://dc01 ldap://dc02.dtsh***m.dt. Please wait.. this can take a while.. Failed to bind - LDAP error 49
2019 Jun 26
4
Samba 4.10 member: SMB login no longer working
Hai, And Omg... Your right, its my fault. :-/ I didnt say to you, you needed make the changes, to change what Rowland showed. Im really sorry.. ;-) when im in austria i'll buy you a beer. Or if you want teach you snowboarding.. I have an other guy in austria that cant ski/board. Im going to teach him also. .. So funny a dutch guy teaching to austria guys.. :-) And how is it running
2015 Jul 23
2
4.2.2 as AD with 2 DCs: database incoherency
On 23/07/15 16:23, mathias dufresne wrote: > Hi all, > > I tried "samba-tool ldapcmp" several times to solve this issue, without > success. > > On DC acting as full FSMO: > dc20:~# samba-tool ldapcmp ldap://dc00.ad.dgfip.lan > ldap://dc20.ad.dgfip.lan domain > ERROR(ldb): uncaught exception - ldb_wait: Time limit exceeded (3) > File
2019 May 22
2
dsdb_access Access check failed on CN=Configuration
----- On May 22, 2019, at 1:00 PM, samba samba at lists.samba.org wrote: > On 22/05/2019 18:24, Mike Ray wrote: >> Poking around on this further, I believe the LMHOSTS error does not matter. >> >> The smb directive "name resolve order" defaults to "lmhosts wins host bcast" -- >> so I believe the file no found error is just because it's trying
2019 Oct 02
3
Removed a DC but...
Hai, The steps shown here dont work? https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC If that is the case and you besides that free of errors. Then upgrade, and try again once your on at least samba 4.9 or 4.10. As im hoping you are upgrade straight to Buster. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens