Bug 1135723
| Summary: | [Samba] Does not work 'force user' from a client machine Windows 8.1 x64. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | rsync <clustershell> |
| Component: | samba | Assignee: | Andreas Schneider <asn> |
| Status: | CLOSED ERRATA | QA Contact: | Robin Hack <rhack> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | alvin, asn, deamicis, gdeschner, jarrpa, jkhradil, pkulkarn, rhack, sbose, szhao |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | samba-4.1.12-2.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-05 09:22:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
rsync
2014-08-30 20:50:32 UTC
*** Bug 1128079 has been marked as a duplicate of this bug. *** Why this bug is on ON_QA since 2 months? I can also confirm that this bug exists with our CentOS 7 Samba servers that are authenticating using Winbind against a Windows 2010 AD server. Details: (1) # cat /etc/redhat-release CentOS Linux release 7.0.1406 (Core) (2) # rpm -qa | sort | grep samba samba-4.1.1-37.el7_0.x86_64 samba-client-4.1.1-37.el7_0.x86_64 samba-common-4.1.1-37.el7_0.x86_64 samba-libs-4.1.1-37.el7_0.x86_64 samba-winbind-4.1.1-37.el7_0.x86_64 samba-winbind-clients-4.1.1-37.el7_0.x86_64 samba-winbind-modules-4.1.1-37.el7_0.x86_64 (all current as at today's date) (3) # cat /etc/samba/smb.conf [global] workgroup = MYAD realm = ad.MYDOMAIN.com netbios name = server2 server string = server2 security = ads encrypt passwords = Yes password server = * hosts allow = 10.0.5. 127. log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 18 local master = No dns proxy = No winbind uid = 10000-20000 winbind gid = 10000-20000 winbind separator = + template homedir = /home/%D/%U template shell = /bin/bash winbind use default domain = yes delete veto files = no hide dot files = Yes hide files = /.*/|~*/ load printers = no [users] comment = Share to backup user common documents path = /u/users/common hosts allow = 10.0.5.27 valid users = MYAD+admin MYAD+backup public = no writable = no printable = no force user = root (4) From Windows: C:\>net view \\server2 Shared resources at \\server2 server2 Share name Type Used as Comment ------------------------------------------------------------------------------- users Disk Share to backup user common documents The command completed successfully. C:\> net view \\server2\users System error 53 has occurred. The network path was not found. C:\>dir \\server2\u The security ID structure is invalid. (5) Note: if the "force user = root" directive is omitted, the share can be accessed, but some files are not accessible because of the lack of permissions. It would be *really great* to have this working again (this is not an issue with CentOS 6 Samba servers). Thank you! We are waiting on Bodhi to release the update, why it's not released? We are also experiencing this bug with Windows 7 Professional 64 bit clients and Centos 7 server:
1) # cat /etc/redhat-release
CentOS Linux release 7.0.1406 (Core)
2) # rpm -qa|grep samba
samba-client-4.1.1-37.el7_0.x86_64
samba-4.1.1-37.el7_0.x86_64
samba-libs-4.1.1-37.el7_0.x86_64
samba-common-4.1.1-37.el7_0.x86_64
3) # cat smb.conf
[global]
workgroup = MYDOMAIN
netbios name = dev
security = domain
interfaces = 192.168.1.255/24
..snip..
[svn]
path = /home/clients/svn/home
force user = svn
force group = svn
valid users = svn @mycompany
browseable = yes
read only = no
write list = svn @developers
..snip..
I can successfully connect to the server and see the shares in Windows Explorer and with 'smbclient -L' but am unable to connect to any of them.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0409.html |