similar to: 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'

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

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

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)

On 15/07/15 14:31, mathias dufresne wrote: > 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

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

On 24/07/15 13:53, mathias dufresne wrote: > The following commands work on both DC: > host -t A <short_hostname_of_other_DC> > host -t A <fqdn_hostname_of_other_DC> > > hostname and hostname --fqdn are working on both DC.The simplest way > is to not declare external IP /etc/hosts > > > SRV DNS entries which are working are: > host -t SRV >

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

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

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

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]:

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

Hello all, I managed to install an extra DC. The first DC is comsrv01a with ip 192.168.0.200. I run Samba 4.1.9 and BIND 9.8.1-P1. The new DC is srv01ham with ip 172.16.32.222. I use the internal DNS. I run Samba 4.1.9. I use a permanent LAN-2-LAN VPN via my Draytek routers. The first DC (comsrv01a, 192.168.0.200) is my primary DNS server. This is configured in all my routers and DHCP servers.

Hello all, we are currently running several samba 3 services to give CIFS access to shares (mostly homedirs). Well, access to the shares are controlled by our LDAP service (not AD, OpenLDAP). Our servers are using sssd + pam to check wether or not a user is allowed to mount the share (on some old servers we also use the pam_ldap module for pam). Now, we just want to run samba 4 as simply as

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

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

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