I can see my Samba share but cannot access it.

newnewbie · 04-25-2009, 08:12 AM

I have five users on the server. I want to run this as a stand alone server. I am not using this as a domain controller. All the users have samba passwd so I think they would be authenticated through the samba passwd file. I have commented out that unix password sync line out. I don't get that error message again when I run testparm, but now when I try to access the share by entering the user name and passwd I get that error message.

pics is not accessible. You might not have permissions to use this network resource. contact the network administrator of this server to find out if you have access permissions.

Multiple connections to a server or shared resource by the same user, using more that one user name are not allowed. Disconnect all previous connections to the server or share and try again.

billymayday · 04-25-2009, 04:05 PM

Time to test without SELinux. Turn it off (setenforce 0). Test. Turn it back up (setenforce 1). Let us know how you go.

newnewbie · 04-26-2009, 04:49 PM

Same result. I get the dialog box to enter the username and passwd. Enter the user name and passwd and I get that same error message.

chitambira · 04-27-2009, 04:03 AM

@jschiwal

Quote:

I don't agree with modifying the line to "Security = Share". That technology is for Windows 95 and obsolete.

Check Samba 3 Manual properly:
http://us3.samba.org/samba/docs/man/....html#SECURITY

Quote:

security (G)

This option affects how clients respond to Samba and is one of the most important settings in the smb.conf file.

The option sets the "security mode bit" in replies to protocol negotiations with smbd(8) to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.

The default is security = user, as this is the most common setting needed when talking to Windows 98 and Windows NT.

The alternatives are security = share, security = server or security = domain .

In versions of Samba prior to 2.0.0, the default was security = share mainly because that was the only option at one stage.

There is a bug in WfWg that has relevance to this setting. When in user or server level security a WfWg client will totally ignore the username and password you type in the "connect drive" dialog box. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as.

If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use security = user. If you mostly use usernames that don't exist on the UNIX box then use security = share.

You should also use security = share if you want to mainly setup shares without a password (guest shares). This is commonly used for a shared printer server. It is more difficult to setup guest shares with security = user, see the map to guestparameter for details.

chitambira · 04-27-2009, 04:33 AM

please repost your complete smb.conf
also /etc/pam.d/system-auth

I suggest you follow correctly my first post and add to your smb.conf

Quote:

passwd program = /bin/passwd %u

newnewbie · 04-27-2009, 04:25 PM

I did reconfigured my smb.conf file. When I rum the command setenforce 0
I can see all the files and folders. When I revert to setenforce 1 I can't see anything here is my smb.conf file.

#
workgroup = cleus
server string = Samba Server
security = user
host allow = 192.168.15.1/24 127.0.0.1

[homes]
; comment = Home Directories
; browseable = yes
; writeable = yes
; valid users = %S
; valid users = MYDOMAIN\%S

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
; guest ok = no
; writeable = no
printable = yes
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
; [Profiles]
; path = /var/lib/samba/profiles
; browseable = no
; guest ok = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
; [public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = +staff

[pics]
comment = all our photos
path = /pics
read only = yes

billymayday · 04-27-2009, 04:48 PM

When you say you can't see anything with SELinux on, do you mean just in pics?

Can you show "ls -lZ /pics"

chrism01 · 04-27-2009, 07:51 PM

You can check the SELinux booleans:

Code:

getsebool -a|egrep -e sam -e smb

and file contexts

Code:

semanage fcontext -l|egrep -e sam -e smb

newnewbie · 04-27-2009, 09:11 PM

Hey Billy when I turn selinux I cannot see anything whatsoever. I can see the folders but cannot get into them. When I turn it off again I can see the mbox file in the home directories and all the files in the /pics share. Here is the output of the command you ask to run ls -lZ /pics

[root@fileserver ~]# ls -lZ /pics
-rwxr-xr-x root root root

bject_r:user_home_t 1001704456_l.jpg
-rwxr-xr-x root root root

bject_r:user_home_t aimon's toast2.jpg
-rwxr-xr-x root root root

bject_r:user_home_t cake1.jpg
-rwxr-xr-x root root root

bject_r:user_home_t cake 2.jpg

billymayday · 04-27-2009, 09:22 PM

Can you also show "ls -lZd /pics"?

First I'd change the ownerships to something other than root (chown user:user_group /pics/* - substitute suitable user and user_group names).

Then "chcon user_u

bject_r:user_home_t /pics/*"

See how you go. You may also need to "chcon -t samba_share_t /pics"

BM

newnewbie · 04-30-2009, 08:15 AM

Hey Billy,

I have been working on it and I figured out it was a problem with the ownership of the files. I did what you said, the command chcon whatever way I try to run it I get an error message. I am not too familiar with it. I check out the info pages but could make much out of it so I tried running it like this chcon user_object_r:user_home_t /pics/*" then got and error saying chcon: invalid context: user_object_r:user_home_t. Tried it again. Tried another this way and got chcon -u cleus /pics
chcon: failed to change context of /pics to cleus

bject_r:samba_share_t: Invalid argument

I have created a group placed all the user into the group and changed the ownership of the files. This is what it all looks like.

-rwxrwxr-x cleus family root

bject_r:user_home_t sarah.jpg
-rwxrwxr-x cleus family root

bject_r:user_home_t Sarah.jpg
-rwxrwxr-x cleus family root

bject_r:user_home_t Simon & Shanti 2.jpg
-rwxrwxr-x cleus family root

bject_r:user_home_t Simon&Shanti3.jpg
-rwxrwxr-x cleus family root

bject_r:user_home_t Simon & Shanti.jpg

Thanks for all the help so far

newnewbie · 05-02-2009, 08:33 PM

Seems like everyone forgot about this post here. I am still not able to get this thing to run as it should. I still have to setenforce to 0. Can someone help.

Hey Billy,

I have been working on it and I figured out it was a problem with the ownership of the files. I did what you said, the command chcon whatever way I try to run it I get an error message. I am not too familiar with it. I check out the info pages but could make much out of it so I tried running it like this chcon user_object_r:user_home_t /pics/*" then got and error saying chcon: invalid context: user_object_r:user_home_t. Tried it again. Tried another this way and got chcon -u cleus /pics
chcon: failed to change context of /pics to cleusbject_r:samba_share_t: Invalid argument

I have created a group placed all the user into the group and changed the ownership of the files. This is what it all looks like.

-rwxrwxr-x cleus family rootbject_r:user_home_t sarah.jpg
-rwxrwxr-x cleus family rootbject_r:user_home_t Sarah.jpg
-rwxrwxr-x cleus family rootbject_r:user_home_t Simon & Shanti 2.jpg
-rwxrwxr-x cleus family rootbject_r:user_home_t Simon&Shanti3.jpg
-rwxrwxr-x cleus family rootbject_r:user_home_t Simon & Shanti.jpg

Thanks for all the help so far