search for: ad_memb

...fail-on-empty --prefix="samba3.blackbox.smbclient_s3.SMB3.plain.member_creds." --suffix="(nt4_member)" ERROR: Testsuite[samba3.blackbox.smbclient_s3.SMB3.plain.member_creds(nt4_member)] REASON: Exit code was 1 == samba3.blackbox.smbclient_s3.NT1.plain.member_creds(ad_member) == command: /usr/src/samba-4.13.1/source3/script/tests/test_smbclient_s3.sh $SERVER $SERVER_IP $SERVER $SERVER/$USERNAME $PASSWORD $USERID $LOCAL_PATH $PREFIX /usr/src/samba-4.13.1/bin/smbclient /usr/src/samba-4.13.1/bin/wbinfo /usr/src/samba-4.13.1/bin/net --configfile=$SMB_CONF_PATH NT1 2>...

...ECRETS/SID/CHDCDOMAIN) > > but not the machine sid (probably SECRETS/SID/CLIENT). > > > > How come that machine sid is absent in the tests? Is there > > another means of retrieving it? > > This is due to the test environment you are running in. If you ran it > in ad_member:local it would be there. Yes, that was it. Thanks! > The 'client' environment (where you don't specify a :local) is used, > without the server's smb.conf or files, and doens't have a local SID. > > Also, it is only set when a source3 passdb operation happens, s...

Hi Andrew, revisiting this subject once again because I seem to have reached an impass. -<| Quoting Andrew Bartlett <abartlet at samba.org>, on Monday, 2018-09-24 07:14:48 PM |>- > On Mon, 2018-09-24 at 09:06 +0200, Philipp Gesang wrote: > > > A long time ago I posted a script to dump the machine password to > > > stdout for the benifit of an 802.1x client, but

...r/src/samba-git/samba/bin/smbd: send_all_fn: messaging_send_buf to 5946 failed: NT_STATUS_OBJECT_NAME_NOT_FOUND WARNING: The "server schannel" option is deprecated tdbsam_open: Converting version 0.0 database to version 4.0. tdbsam_convert_backup: updated /home/user/src/samba-git/samba/st/ad_member/private/passdb.tdb file. DNS update failed: NT_STATUS_UNSUCCESSFUL Doing a full scan on DC=ForestDnsZones,DC=addom,DC=samba,DC=example,DC=com and looking for deleted objects Doing a full scan on DC=DomainDnsZones,DC=addom,DC=samba,DC=example,DC=com and looking for deleted objects Doing a full sca...

Thanks for the reply, Besides the problem with source4/lib/messaging/messaging_handlers.c, Good to hear that selftest is actively used, then do I understand it right that 'make test' should succeed? My bigger problem is that it failed with lots of errors. This must be a problem with my build, then, but since this is a fresh tarball I am a bit puzzled. I would appreciate some hint on

...I find only the domain SID (e. g. SECRETS/SID/CHDCDOMAIN) > but not the machine sid (probably SECRETS/SID/CLIENT). > > How come that machine sid is absent in the tests? Is there > another means of retrieving it? This is due to the test environment you are running in. If you ran it in ad_member:local it would be there. The 'client' environment (where you don't specify a :local) is used, without the server's smb.conf or files, and doens't have a local SID. Also, it is only set when a source3 passdb operation happens, so AD DC client stuff won't trigger it (for...

...t; but not the machine sid (probably SECRETS/SID/CLIENT). > > > > > > How come that machine sid is absent in the tests? Is there > > > another means of retrieving it? > > > > This is due to the test environment you are running in. If you ran it > > in ad_member:local it would be there. > > Yes, that was it. Thanks! > > > The 'client' environment (where you don't specify a :local) is used, > > without the server's smb.conf or files, and doens't have a local SID. > > > > Also, it is only set when a...

...obably SECRETS/SID/CLIENT). > > > > > > > > How come that machine sid is absent in the tests? Is there > > > > another means of retrieving it? > > > > > > This is due to the test environment you are running in. If you ran it > > > in ad_member:local it would be there. > > > > Yes, that was it. Thanks! > > > > > The 'client' environment (where you don't specify a :local) is used, > > > without the server's smb.conf or files, and doens't have a local SID. > > > > &g...