Samba server problem
p.echols at comcast.net
Tue Nov 17 04:10:07 UTC 2009
On 11/16/2009 04:04 PM, Tom H wrote:
>> I have a server and have attempted to make a share available to windows users.
>> My problem is that a windows user "Janice" can login to her "home" share.
>> But cannot log in to the "Windata" share.
>> patton at tome:~$ ls -l /raid/Windata
>> total 40
>> drwxrw-r-- 9 patton users 4096 2009-09-19 22:11 All Users
>> One thing about this. When I created the user account,
>> I did not add janice to the group "users".
>> I did that and am able to connect from the "janice" account
>> on the ubuntu desktop machine.
>> But it still does not connect from her windows machine.
>> patton at tome:~$ cat /etc/samba/smb.conf
>> workgroup = HOME
>> server string = %h server (Samba, Ubuntu)
>> map to guest = Bad User
>> obey pam restrictions = Yes
>> passdb backend = tdbsam
>> passwd program = /usr/bin/passwd %u
>> passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>> unix password sync = Yes
>> syslog = 0
>> log file = /var/log/samba/log.%m
>> max log size = 1000
>> printcap name = cups
>> dns proxy = No
>> wins support = Yes
>> usershare allow guests = Yes
>> panic action = /usr/share/samba/panic-action %d
>> comment = Home Directories
>> read only = No
>> browseable = No
>> comment = Home File Archives
>> path = /raid/Windata
>> read only = No
>> guest ok = Yes
> Run "smbclient -L 127.0.0.1" to make sure that Windata is shared out.
> Add "log level = 3" to your global section, remove "guest ok = Yes"
> from your windata section, restart samba, and check /var/log/samba/
> after a logon failure by janice.
This reply is three things, first problem solved, second a duplicate,
third may seem out of place in the thread. It has been pointed out that
some of my posts appeared to be in separate threads. So for future
readers with the same problem, here is my solution .
On 11/16/2009 06:11 PM, Christopher Chan wrote:
> That is very strange. You have permissions 764 set and so nobody except
> patton would be able to see anything under those directories shown.
> Also, you did not give us the actual permissions of /raid/Windata.
> 'ls -ld /raid/Windata' please
Uhhh, ok I just learned something. I had thought that you were
*supposed* to set permissions on "data" that are not intended to be
executable to "rw" and not "x". Though now that I look for it, I can't
find a reference for why I "Knew" that. But setting permissions fixed
it. A couple of questions if you don't mind.
Would it be better practice to have the directory "owned" by the group
"users" (if you can even to that) and set the permissions to 700, or to
do as it is now, files are "owned" by me, but permissions are 770?
So following chmod -R 770 /raid/Windata everything is set to:
drwxrw-r-- 9 patton users 4096 2009-09-19 22:11 Windata
More generically, why all the permission levels if you can't touch the
files w/o the correct "rwx" permissions? or am I missing something
critical? I suppose this question really should be added to my reading
list for future reference.
Thanks for the heads up.
(Since Gary pointed out that I had been posting badly, I am going to
copy a shortened version in the original thread to make it easier find.
He makes a good point that someone else looking for the answer to this
will read that part and maybe not here.)
More information about the ubuntu-users