search for: samaccount

...The LDAP server is succesful connected pdb backend ldapsam:ldap://10.0.0.1/ has a valid init Attempting to find an passdb backend to match guest (guest) Found pdb backend guest pdb backend guest has a valid init smbldap_search_suffix: searching for:[(&(&(uid=machine_name$)(objectclass=sambaSamAccount))(objectclass=samba SamAccount))] ldapsam_getsampwnam: Unable to locate user [machine_name$] count=0 Finding user machine_name$ Trying _Get_Pwnam(), username as lowercase is machine_name$ Trying _Get_Pwnam(), username as uppercase is MACHINE_NAME$ Checking combinations of 0 uppercase letters in mac...

...see no evidence of the rules being invoked. i.e. Same output in the apache error log regardless. This then appears to get passed on for use in subsequent ldap authorisations (apache mod_authnz_ldap). This does not work for us as we need to authorise against stripped user names (Active Directory sAMAccount or similar; our userPrincipalName is a different format: Test12 at Q.Y.Z, so can't workaround using that). I previously posted a similar messages to kerberos at mit.edu but got no feedback. Hopefully this list might be more appropriate. Grateful for any advice, Ewae.

Can someone explain what's required to join a linux computer to the windows domain and what the benefits would be? Rick B.

...g like this: 'ACCOUNTNAME' uses "msDS-SupportedEncryptionTypes": 31 (0x0000001f) [X] 0x00000001 DES-CBC-CRC [X] 0x00000002 DES-CBC-MD5 [X] 0x00000004 RC4-HMAC [X] 0x00000008 AES128-CTS-HMAC-SHA1-96 [X] 0x00000010 AES256-CTS-HMAC-SHA1-96 -------- ^^^^ already on wiki ----- A sAMAccount name can be the hostname of a computer Then you use: net ads enctypes set HOSTNAME$ ! Point of attention: HOSTNAME$. The hostname in "how its defined in your smb.conf, and after you checked the current keytab file. (klist -ke  or klist -ke /path_to/your.keytab_file)   If the hostname is lo...

...ap_open_connection: connection opened ldap_connect_system: succesful connection to the LDAP server The LDAP server is succesfully connected pdb backend ldapsam:ldap://127.0.0.1/ has a valid init smbldap_search_ext: base => [dc=bcn,dc=teamlog,dc=com], filter => [(&(uid=hr)(objectclass=sambaSamAccount))], scope => [2] init_sam_from_ldap: Entry found for user: hr Opening cache file at /var/cache/samba/login_cache.tdb Looking up login cache for user hr Found login cache entry: timestamp 1161796734, flags 0x23a30010, count 1, time 1161796734 ldap time is 1161729143, cache time is 1161796734,...

Everytime I try to login using windows credentials to my db instance I get the error: ORA-12638: Credential retrieval failed. Looking at my alert log I find: ns main err code: 12638 which means the database is not able to connect the domain controller. The database connector makes use of NTLM protocol to authenticate. Is it supported by samba4 (4.1.16)? I'm unable to find any