Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Ok here is what I have done so far created my group added the users to the group, created the share directory in /home/samba/share, changed share group to one I created, changed permission on share dir to rwxrwx---. went into swat and created the share restarted samba.
Here is the problem from my WinXP box I can see my home directorie for the users I have added no problem, but for the shared folder no of my users can access it. Instead I get this error message.
"\\fileserver is not accessible. you might ont have permission to use this network resource. contact the administrator of this server to find out if you have access permissions.
The specified network name is no longer available."Here is my smb.conf file
[global]
workgroup = workgroup
netbios name = FILE SERVER
encrypt password = yes
server string =
log file = /var/log/samba/%m.log
max log size = 50
os level = 2
dns proxy = No[homes]
comment = Home Directories
read only = No
browseable = No[share]
path = /home/samba/share/
valid users = @cooper
write list = @cooper
read only = No
hosts allow = 192.168.1/255.255.255.0
case sensitive = No
strict locking = No
msdfs proxy = noPlease help not sure if is the permissions on the share or in the smb.conf file..

If you typed this correctly, you are missing the last octet in the IP address of the hosts allow line.
Search Engines Are Your Friends ☺
Morpheus: There is a difference between
knowing the path and walking the path. "The Matrix"

I am fairly new to linux but from my understanding is that having it like that is the same as 192.168.1.*/255.255.255.0 allowing all host on that subnet access to server let me know if I am mistaken as I would like to get this running soon...

Figured out the issue I was having.. had to do with the permissions set for the group on the samba folder. Once I changed that everyting is working great..

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |