similar to: Samba 4.1.7 ldapcmp msDS-NcType Error comparing DCs

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'

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

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

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... >

On 16/07/15 12:20, mathias dufresne wrote: > 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 >

What I have done bevor updating to 4.3.4 and it was working until then. I userd the map unix tab in ADUC and gave uid and gid to all users /groups but administrator. This worked until the update. Now the dcs mix up only!!! group ids with computer ids (security tab) root at s4slave exim]# getent group personal TPLK\personal:x:3000044: root at s4slave exim]# getent group reserve09$

There is a strange behaviour having two DCs joined in one Domain concerning the [home] share. The [home] is fixed on a replicating gluster volume on both DC. Now creating the users directory with ADUC ex.: \\s4master\home\%username% would do the necessary and the directory is created on both dcs. On the first DC all working fine without any issue but on the second the user cannot login their home

Hello again, no idea!? Both my DCs running now 4.3.4, but there is a strange behaviour, Ex.: First DC root at s4master wingroup]# id maurerp uid=90036(TPLK\maurerp) gid=100(users) Gruppen=100(users),3000048(TPLK\schreiben),3000038(TPLK\orbis),3000023(TPLK\ agfa),3000009(BUILTIN\users) Second DC [root at s4slave ~]# id maurerp uid=90036(TPLK\maurerp) gid=100(users)

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'

No I can not upgrade now it is a working system with x users. The master dc with the same config is working without any issues. So when I upgrade I must do the uprgade on both replicating samba server and the samba fileservers? No hint form e to repair: May 16 14:00:12 s4slave smbd[7141]: [2019/05/16 14:00:12.438121, 0] ../source3/lib/util.c:801(smb_panic_s3) May 16 14:00:12 s4slave smbd[7141]:

Originally I had a Win 2003 DC. I added a samba 4.0.0 DC to the domain, allow full replication to take place and then transferred all the roles to the samba 4.0.0 dc. Finally I removed the Windows DC from the domain. Everything has been working well. Today I upgraded from samba 4.0.0 to 4.0.3 and ran samba_upgradeprovision --full. Initially this was failing in update_present throwing an exception

Dear all, how can I solve the issue with samba 4 bind_dlz , when a windows client is joined to the domain I get this error,ex.: 4master named[2814]: client 192.168.135.126#55873: update 'tplk.loc/IN' denied Jul 31 14:29:17 s4master named[2814]: samba_dlz: cancelling transaction on zone tplk.loc I can add the client to the dns by hand: samba-tool dns add s4master tplk.loc EDV2 A

Hai Rowland. What you tried is ok, or im misunderstanding you. For me : All members give me. getent passwd myuser myuser:*:10002:10000::/home/users/myuser:/bin/bash id myuser uid=10002(myuser) gid=10000(domain users) the memberservers are or sernet samba 4.2.7 or debian samba 4.1.17 and on the DCs. ( only sernet samba 4.2.7 ) getent passwd myuser myuser:*:10002:10000:L.P.H. van

I have moved to 4.1.16 on both controllers. It did not solve my issue (though it reduced the errors as seen in the new attached ldap comparison). I am still getting the error telling me to see the administrator when trying to add a user via the Windows Active Directory Users and Computers utility. Gilbert [root at pdc ~]# /usr/local/samba/bin/samba-tool ldapcmp ldap://pdc ldap://sdc domain

Hello! I have 2 Samba 4 server (4.3.3) as VC and other Samba 4 (4.3) as Fileserver, until now all ok, but I'm one doubts, how to validate that in both servers the domain IDs of the users of this identical, a simple way to do this validation? I wanted to make sure it is a DC die fileserver has to go 100%. thank you

So after digging deep and looking into my /var/log/messages for dns and recognizing that my providers internet dns not work correctly: Mar 16 07:49:48 s4slave named-sdb[15870]: error (connection refused) resolving 'ns2.allowsread.com/AAAA/IN': 192.52.178.30#53 Mar 16 07:49:50 s4slave named-sdb[15870]: error (network unreachable) resolving 'ns2.allowsread.com/AAAA/IN':

On 16/05/2019 14:04, Mueller wrote: > I fear when I do a > 'samba-tool dbcheck' this will do the rest to kill the affected samba . Can I do it ? Just checking AD shouldn't do anything other than tell you if you have a problem or not, so yes, check it. > > > Smb.conf on Master only global: > > [global] > workgroup = TPLK > realm = tplk.loc

Dear all, I set up samba 4.1 (SlaveDC)in a test environment on CentOs 6.4. I tried to join this host to my running and provisioned MasterDC (Samba 4/CentOs 6.4). On the SlaveDC I did : samba-tool domain join tplk.loc DC -Uadministrator --realm=tplk.loc --dns-backend=BIND9_DLZ It gives me: [root at s4slave ~]# samba-tool domain join tplk.loc DC -Uadministrator --realm=tplk.loc

No idea!?? EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de -----Urspr?ngliche Nachricht----- Von: Daniel M?ller [mailto:mueller at tropenklinik.de] Gesendet: Mittwoch, 15. April 2015 14:40 An: 'samba-bounces at

Le 09/07/2015 18:20, Rowland Penny a écrit : > On 09/07/15 17:06, zorg wrote: >> But If i want my samba4 to be dns after when i ll decide to stop the >> other dc >> >> can't i keep the to dns >> >> Could you explain a bit >> >> >> >> Le 09/07/2015 17:55, Marc Muehlfeld a écrit : >>> Hello, >>> >>> Am