similar to: Problem in samba-tool ldapcmp

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 >

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 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 "/usr/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run return

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 _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.domain.tld host -t SRV

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

Thank you Rowland for this. I tried using Sernet's Samba 4.2.2 and failed: All the following command were ran on DC20 samba-tool dns zonecreate dc20.ad.domain.tld 0.0.10.in-addr.arpa Password for [administrator at AD.DOMAIN.TLD]: Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for

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

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 Mathias, I am under the impression that whenChanged is one of the fields that do not replicate. Therefore we run ldapcmp like: samba-tool ldapcmp ldap://dcX ldap://dcY --filter=whenChanged Hope that helps, MJ On 09/01/2015 02:45 PM, mathias dufresne wrote: > Hi all, > > It seems "samba-tool ldapcmp" does not support too much items in Samba's > database. >

Hi Mourik, whenChanged was replicated in my test once I did replicate in both way, so it seems to me it is supposed to be replicated... Then the fact it is not always replicated seems to me an issue. Perhaps a bug report for these two issue (whenChanged not always replicated and ldapcmp hanging once DB is too much filled) would be the right way to proceed... Cheers, mat 2015-09-03 10:42

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 >

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,

On 23/04/15 16:22, Bob of Donelson Trophy wrote: > > > 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 >

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]

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

On 27/02/17 08:05, Tom Robinson via samba wrote: > On 17/02/17 07:58, Andrew Bartlett via samba wrote: >> On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: >>> Anyone? >> Can you please post a gdb backtrace --full? >> >> > Hi, > > I replied last week with a full backtrace but I didn't see my post come through. The email was only >

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

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'

On 03/09/2019 18:50, Mike Ray via samba wrote: > 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). >

Hai Bob, ah.. LDAP_INVALID_CREDENTIALS, this is not a python error, but password error.. ;-) i upped a new version of samba-check-db-repl.sh ( direct link : https://secure.bazuin.nl/scripts/samba-check-db-repl.sh) small change in the install of the mail tools section. A bit info for this version. ## Version : 1.0.3 ## release d.d. : 22-04-2015 ## moved mailx part within checks if an