similar to: LDAPcmp show errors (serverState, subRefs)

Dear all, Running samba-tool ldapcmp on my both DCs samba 4.1.7 leads to the output : Attributes found only in ldap://s4master: msDS-NcType serverState FAILED How to deal with this? I am missing something? [root at s4slave ~]# samba-tool ldapcmp ldap://s4master ldap://s4slave -Uadministrator domain Password for [TPLK\administrator]: * Comparing [DOMAIN]

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'

Hi, I am running a Windows Domain based on 2 Samba AD servers. The setup is running mostly fine but I have the impression that the 2 DC's are not syncing their information. For instance: - I added a Windows pc to the domain last week, when I started 'Active directory users and computers' today on a windows pc I could not see that pc, after rebooting one of the DC's the pc

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

27.06.2016 18:45, mathias dufresne: > Perhaps you don't have yet duplicate objectSid as that's not supposed to be > possible. > Rather than scripting something to look for objectSid used twice I would > start with dbcheck and other tools to verify that your database is > consistent and identical on all servers. [root at pdc ~]# samba-tool dbcheck Checking 3346 objects

Hello, I had posted this in another topic, but because the problem is different, I decided to create a new topic. Conf: - Primary DC/pdc Emulator as DC3 - Second DC as DC4 After an upgrade from schema 45 to 69 in DCs, when adding a computer in the domain and if the domain to respond is DC4 the synchronization for DC3 is not done. I already did several tests that I already knew and also new

Hai, Since your getting. finddcs: No matching server found > ERROR: Invalid IP address '3(NXDOMAIN)'! There is something wrong in the base of you setup. Check all DC's for ipnumbers (A) and PTR records. Dont forget to create the reverse zone yourself. https://wiki.samba.org/index.php/Samba_AD_DC_Troubleshooting

Ok just to verify. DC name= ad41.dc.samges.ru dnsdomain= dc.samges.ru Kerberos domain ?? Im guessing you kerberos to dnsdomain mapping is wrong. Can you post the /etc/hosts /etc/resolv.conf /etc/krb5.conf And, can you post this line u used for provisioning? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Mike Lykov [mailto:combr at samges.ru] > Verzonden:

Hello, I have three DC's in an environment, and ldapcmp is failing. How can I figure out either what went wrong, or how to resolve the issue so that the databases are truly in sync? * Comparing [DOMAIN] context... * Objects to be compared: 2277 Comparing: 'CN=Builtin,DC=ad,DC=domain,DC=com' [ldap://192.168.10.81] 'CN=Builtin,DC=ad,DC=domain,DC=com'

Help, my Samba DC's refuse to sync :-( I have 2 Samba 4.1.17 DC servers. I made some changes via Active Directory USer and Computers on Windows. However even after a weekend the changes do not appear on the second DC. If I run samba-tool ldapcmp ldap://dc1 ldap://dc2 -Uadministrator --filter=msDS-NcType,serverState,subrefs I see:

On 16/07/15 07:19, Daniel Müller wrote: > 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... >

Hello Team, Good Morning!! This is Vishnu Prasanth doing my master's thesis on improving llvm compiler optimization. Currently I am trying to build dragon egg and when I gave take, it is not getting recognized for ARM machine. Can you please help me with. Below are the errors when I gave the below command inside dragon egg directory GCC=GCC_DIR/gcc

Hi all! Today, after two years of production, I get this error: samba-tool user create test20160627 testpassword ERROR(ldb): Failed to add user 'test20160627': - ../lib/ldb/ldb_tdb/ldb_index.c:1216: Failed to re-index objectSid in CN=test20160627,CN=Users,DC=ad... - ../lib/ldb/ldb_tdb/ldb_index.c:1148: unique index violation on objectSid in CN=test20160627,CN=Users,DC=ad... Help me

Hi, I am having problems establishing an adsl connection in dom0 (but ONLY in dom0, without xen everything is ok). Following is my setup/situation: 1. Installed clean Fedora 7 (with virtualization option selected) 2. Booted with the non-xen kernel & setup adsl. Adsl connection works without any problems. 3. Rebooted with xen kernel into dom0. 4. adsl connection can no longer be activated

Hi all, I'm having a test AD domain composed with 2 DC, using Sernet's version of Samba 4.2.2. These two DC are Centos 6.6 (dc20) and Debian 7.8 (dc00). These two are using TDB as a backend (as we have no other choice at this stage of Samba's development). *dc20*:~# ldbsearch -H $sam '(objectclass=group)' dn | tail -3 # returned 27392 records # *27389* entries # 3 referrals

Hello, gaia ~ # uname -a Linux gaia 6.1.12-gentoo-x86_64 #1 SMP Thu Mar 9 19:57:24 CST 2023 x86_64 Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz GenuineIntel GNU/Linux gaia ~ # dovecot --version 2.3.20 (80a5ac675d) gaia ~ # cat /proc/self/status | wc --bytes See attached for example content of /proc/self/status and the dovecot.conf through 'dovecot -n' I am re-sending this message because

I'm understand, why I get error about unique index violation on objectSid: samba-tool fsmo show RidAllocationMasterRole owner: CN=NTDS Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ad,... Last created object have objectSid S-1-5-21-763247336-2482037999-3416227170-2001 (it is record for computer) Last symbols is 2001, and last assigned RID is 2001: [root

Hi! This requires a code change, which is currently in progress. It does require you to patch Dovecot yourself if you want to use it, once it's ready. Aki > On 26/03/2023 05:22 EEST Elisamuel Resto Donate <sam at samresto.dev> wrote: > > > Hi, > > At this point I have resorted to add the error message to be ignored by the syslog daemon to at least keep it out of

Aki, Thank you! Regards, -Sam > On Mar 26, 2023, at 04:00, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > ?Hi! > > This requires a code change, which is currently in progress. It does require you to patch Dovecot yourself if you want to use it, once it's ready. > > Aki > >> On 26/03/2023 05:22 EEST Elisamuel Resto Donate <sam at

Hello, Writing to get some insight as to how I might rid myself of a the pesky error message on the subject. Every binary throws out that error, every LMTP delivery... basically every time any dovecot binary is executed. I am unsure if this is configuration related or not, but intuition says it is an issue with a kernel feature or compiler issue. I saw the error message in the source code