search for: nt_status_no_user_session_key

We just went through a massive renumber, and cleanup of some services. I went to rejoin our main Samba server to the domain and I get: error setting trust account password: NT_STATUS_NO_USER_SESSION_KEY I've deleted the machine account on the domain, I've double checked the smb.conf to make sure I have the right domain controller set, and I'm issuing: smbpasswd -j CORP -r DOMAINMACHINE -U CORP\+Administrator I have done this on another machine already--it worked fine (same command...

...: -client -fileserver -NT4-style DC with OpenLDAP backend. I must make this work in order to figure out the upgrade path to Samba AD. However, connecting from client to the FS fails because FS is unable to perform user password check. I even try to rejoin the FS to domain to no avail - I get weird NT_STATUS_NO_USER_SESSION_KEY error. Strangely enough, connecting client directly to DC's NETLOGON folder works fine, that means, that username/password is being resolved well between Samba DC and OpenLDAP. It seems that the whole problem is between FS and DC. Please, is there anybody who has NT4-style Samba 4 DC running...

2016-06-13 18:27 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 13/06/16 13:13, mathias dufresne wrote: > >> I loved to find out how to achieve that. >> >> I did looked for information, all I found was that: >> >>