Bug 11938 - Failed to access samba share via the AD user who is set as valid user in smb.conf
Failed to access samba share via the AD user who is set as valid user in smb....
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services
4.4.2
All Solaris
: P2 critical
: ---
Assigned To: Samba QA Contact
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-27 05:45 UTC by jinyunshuai
Modified: 2016-05-27 05:50 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jinyunshuai 2016-05-27 05:45:49 UTC
Unix OS: Soaris11 Sparc and HPUX 11.31 IA (LatPatch)
Build samba-4.4.2

Procedures/Results:

1. build and configure stock samba well

2. Set samba share "lav" under /usr/local/samba/etc/smb.conf 
 --------------
 bash-4.2# cat /usr/local/samba/etc/smb.conf
[lav]
 path = /lav
 public = no
 valid users = domain_name\test1
 writable = yes
 --------------

3. Access lav via valid user test1
 --------------
 bash-4.2# smbclient -U test1%password //host_ip/lav
 Domain=[domain_name] OS=[Windows 6.1] Server=[Samba 4.4.2]
 tree connect failed: NT_STATUS_ACCESS_DENIED

4. Comment valid users and repeat step3
 --------------
 bash-4.2# cat /usr/local/samba/etc/smb.conf
[lav]
 path = /lav
 public = no
 #valid users = domain_name\test1
 writable = yes
 bash-4.2# smbclient -U test1%password //host_ip/lav
 Domain=[domain_name] OS=[Windows 6.1] Server=[Samba 4.4.2]
 smb: \>
 <----Access successfully if not set valid user
 ---------------
Comment 1 jinyunshuai 2016-05-27 05:50:00 UTC
Found the issue does not exist on samba-4.2.3, 
So I change the samba-4.4.2' lookup_name() almost the same to samba-4.2.3's
and the change can fix the issue.

So the issue should be caused by the change on new samba.