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

I upped 1.0.4 of the script.. I added checks if no DC's are found, error message and exits script, so no python errors anymore, if i did it right. ;-) on both DC's do the following. and whats the output of : cat /etc/hosts cat /etc/resolv.conf and kinit Administrator SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADRESS=`hostname -i` echo "Test domainname:

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 >

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

21.06.2017 11:45, L.P.H. van Belle via samba пишет: > I suggest before you upgrade do a very good read here. > > https://wiki.samba.org/index.php/Updating_Samba#Notable_Enhancements_and_Changes > > https://wiki.samba.org/index.php/Samba_Features_added/changed_(by_release) > And a summerize version for with all parameter changes as of upgrade from 4.2 up to 4.6 >

Hai Bob. SETDNSDOMAIN='hostname -d' needs to be: SETDNSDOMAIN=`hostname -d` .. so change them all . SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADDRESS=`hostname -i` and you can ignore : >[....] Stopping domain name service...: bind9rndc: connect failed: >127.0.0.1#953: connection refused > >. ok > >[ ok ] Starting domain name service...:

My big fingers have gotten me into trouble (all be it minor, I think.) I have had a single DC and member server working for a few weeks and decided to move forward setup the second DC. When I set the hostname I inadvertently added an addition letter into the name. Unfortunately I discovered this after I had run "samba-check-db-repl.sh" which follows the script

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

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

On Sat, 22 Apr 2017 08:47:53 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2017-04-22 07:36, Bob of Donelson Trophy via samba wrote: > > > I have updated from Samba 4.5.0 to 4.6.2 on my second DC and all > > appears good, so far. > > > > On the "https://wiki.samba.org/index.php/Updating_Samba" [1 [1]] > > page

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

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

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,

Am Sa., 6. Apr. 2019 um 18:01 Uhr schrieb Rowland Penny via samba < samba at lists.samba.org>: > On Sat, 6 Apr 2019 17:21:26 +0200 > Martin Krämer <mk.maddin at gmail.com> wrote: > > > Hello Rowland, > > > > thanks for your help. > > Below my comments > > > > See here: > > > > > > http://apt.van-belle.nl/ > > >

We can login just fine but Group Policy Update is throwing an error gpupdate Updating Policy... User policy could not be updated successfully. The following errors were encount ered: The processing of Group Policy failed. Windows could not determine if the user a nd computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in

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

All- I've got 3 DCs (version 4.9.6-12) that, prior to today, were running without issue (as best I could tell). Every night I run a few commands to monitor the status of the DCs/domain. I run: * dbcheck --cross-ncs * samba-tool drs kcc <other DCs> * samba-tool ldapcmp <local DC> <other DCs> (domain|configuration|schema|dnsdomain|dnsforest) * samba-tool drs showrepl These

I have updated from Samba 4.5.0 to 4.6.2 on my second DC and all appears good, so far. On the "https://wiki.samba.org/index.php/Updating_Samba" [1] page of the documentation in section "Updating Multiple Samba Domain Controllers". The last line " . . . and always verify that the replication is working correctly." The replication discussed here. Is this the

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

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