RHEL7

christr · 08-15-2017, 09:27 PM

I'm having trouble with a Linux Samba share after migrating a system from RHEL 5 to RHEL 7.

My current configuration is below.

Code:

[global]
workgroup = DOCS
security = share
[data]
comment = Data
path = /export
read only = yes
guest ok = yes
browsable = yes

In RHEL7 the service will fail to start. I can get the service to start if I change it to "security = user", but that's not what I want because it will force users trying to connect for logins. I need this share to be completely open, and Windows users can't be prompted for a username or password whatsoever. Has anyone run into this, or know of a work around?

I see in the new man page that "security = user" is deprecated. However, I must have the share completely wide open to guests.

Thanks

wpeckham · 08-16-2017, 06:18 AM

If you are running RHEL, then you must have an RHEL license. Why not ask Red Hat support on those forums?

christr · 08-16-2017, 08:01 AM

I already opened a case with Red Hat, but it seems this may be something the community can help answer. I can't imagine I'm the first to have run into this. All my google and forum searches have come up empty.

TB0ne · 08-16-2017, 09:03 AM

Quote:

Originally Posted by christr

I'm having trouble with a Linux Samba share after migrating a system from RHEL 5 to RHEL 7. My current configuration is below.

Code:

[global]
workgroup = DOCS
security = share
[data]
comment = Data
path = /export
read only = yes
guest ok = yes
browsable = yes

In RHEL7 the service will fail to start. I can get the service to start if I change it to "security = user", but that's not what I want because it will force users trying to connect for logins. I need this share to be completely open, and Windows users can't be prompted for a username or password whatsoever. Has anyone run into this, or know of a work around?

I see in the new man page that "security = user" is deprecated. However, I must have the share completely wide open to guests.

Try

Code:

public = yes

for your "must be open to guests" needs. Also, check selinux status as well, if you're having other issues. Anything in the logs? Any other info?

christr · 08-16-2017, 10:02 AM

Thanks for the suggestion. I've been trying a number of things, but still no luck so far. This is what I have currently.

Code:

[root@server1 samba]# cat smb.conf
# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.

[global]
        workgroup = SAMBA
        security = user

        passdb backend = tdbsam

        printing = cups
        printcap name = cups
        load printers = yes
        cups options = raw

[xfer]
   comment = Files for transferring
   path = /export
   public = yes
   guest ok = yes
   writable = no

[root@server1 samba]#

michaelk · 08-16-2017, 10:40 AM

I believe you meant to post that security=share is deprecated.

Code:

FYI public == guest ok

This information is fairly old and might depend on what samba version you are running.
http://beginlinux.com/blog/2010/01/c...hare-on-samba/

You need to add map guest = bad user to the global section of your smb.conf file to enable . By default the guest account is nobody which may not have sufficient permissions. The posted link creates a special guest account and then creates the public directory that it owns.

christr · 08-16-2017, 11:15 AM

Thank you Michaelk. Before I had a chance to see your post I ended up solving this problem on my own. I discovered the same thing you said.

I finally found this in the documentation, and that solved my problem. The security modes for Samba changed in RHEL7.