search for: lmpwdhistori

Hi, We are (again) looking at syncing our samba AD to the azure AD cloud. I installed a win2016 server domain member server and set it up for syncing, including password hashes, so users can login azure/O365 using their on-prem passwords. We're using microsoft's latest tech: the new "Azure AD Connect cloud provisioning". We made sure to check "password hash sync".

Hi, Thank you for this answer, unfortunately I was not able to re-hash password as they are hashed into LDB database. First I retrieved the hash: ldbsearch -H $sam '(cn=some user)' unicodePwd # record 1 dn: CN=some user,OU=Users Management,DC=ad,DC=example,DC=com unicodePwd:: COwwLgiqqaHRyhy4HxWp4A== This "unicodePwd" attribute comes from a quick search into "user"

Hi, Meanwhile we have discovered this bug report: https://bugzilla.samba.org/show_bug.cgi?id=10635 where Andrew is asking to test again with modern versions as a first step towards a solution. So I will start upgrading our DCs to latest in de coming period, to see if that helps anything. Strange also that the reporter of bug 10635 is seeing all kinds of error messages logged in azure, and

hee hee, jean francois is going to be annoyed. this code is still under "definite alpha" status, but i really, really wanted to get it in there asap. so, the latest cvs checkin adds the ability to use an ldap schema for the passwords, not that i know what one of those actually is (only kidding: i've just never set one up yet). here it is: Subject: LDAP schema objectclass

On Wed, 7 Feb 2018 16:30:56 -0000 Roy Eastwood via samba <samba at lists.samba.org> wrote: > Hi, > First some background: > ================== > I had a test environment which had two samba DCs (running v 4.8.0rc2) > and 1 Windows Server 2008R2 DC. The samba DCs had been upgraded > from v 4.6x and the secrets database was not encrypted (as far as I > know). I

On 18/06/15 12:04, mathias dufresne wrote: > Hi, > > Thank you for this answer, unfortunately I was not able to re-hash password > as they are hashed into LDB database. > > First I retrieved the hash: > ldbsearch -H $sam '(cn=some user)' unicodePwd > # record 1 > dn: CN=some user,OU=Users Management,DC=ad,DC=example,DC=com > unicodePwd::

Hi all, I was wondering what kind of password encryption is used into LDB file to store user's password. Our users are authenticating against some OpenLDAP tree to access their applications. We would like to add some field on this OpenLDAP to generate Samba4 valid password when users are connecting against it, to be able then to copy this field into our Samba4 users for they have same

Hi, First some background: ================== I had a test environment which had two samba DCs (running v 4.8.0rc2) and 1 Windows Server 2008R2 DC. The samba DCs had been upgraded from v 4.6x and the secrets database was not encrypted (as far as I know). I decided to downgrade one of the samba DCs to v 4.7.4. On re-starting samba after the downgrade the log shows: ldb: unable to dlopen

Release Announcements ===================== This is the second release candidate of Samba 4.8. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.8. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run "samba-tool drs showrepl" without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]

Release Announcements ===================== This is the first release candidate of Samba 4.8. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the first release candidate of Samba 4.8. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.8. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.8. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.8 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Thanks for your help. > On the Windows DC can you check that the A record is actually created? Yes, it is, and it persists after join failure. Another sign of presence of SRVAD-NEW on the old DC is the new computer account, created in "Domain controllers" folder in "Active Directory Users and Computers" at the beginning of join procedure then automatically removed just

Tested again to join, now clearing both Kerberos, Samba config and Samba private folder. The new log now has some more details (resolve_lmhosts: Attempting lmhosts lookup for name SRVAD-OLD.SAMDOM.LOCAL<0x20>), but I'm still not able to join. Wonder why is it trying to do an lmhosts lookup, 4.6 is not. An identical server (with same hostname and IP) with Samba 4.6 joins without

Hey folks, Has anything changed with 4.8.0 with respect to replication with a Win2KR2 server? In particular, can Samba 4.8 join a Windows 2012R2 domain (schema 69) as a DC? Will replication work properly? Thank You! ----- Mail original ----- De: "Karolin Seeger via samba" <samba at lists.samba.org> À: samba-announce at lists.samba.org, samba at lists.samba.org, samba-technical

Can you specify the full DN of the DNS record in question? Afterwards, maybe you can also try deleting that DNS record and retry the join? Failed to find machine account is almost certainly an unrelated debug message. I don't think it has any relation to your issue. Cheers, Garming On 26/02/18 00:28, Claudio Nicora via samba wrote: > Tried again to join, now with full cleanup of

It seems I'm talking to myself... anyway another test here: Added the existing DC IP config to /etc/hosts and the join now shows a more explicit LDAP error: --- Wrong username or password: kinit for SRVAD-NEW$@SAMDOM.LOCAL failed (Preauthentication failed) SPNEGO(gssapi_krb5) creating NEG_TOKEN_INIT for ldap/SRVAD-OLD.SAMDOM.LOCAL failed (next[ntlmssp]): NT_STATUS_LOGON_FAILURE Got