Originally Posted by
Mark_Fish
nasadmin is a mortal user. I've set up the machine so that the user "generic" is automatically logged in at startup.
Does the user generic have an Ubuntu password at all.
I only have the "nasadmin" user created so that the "Other" directory is locked and cannot be accessed by anyone but nasadmin.
This doesn't seem quite right. The directory is open to all users as shown in red
Code:
drwxrwxrwx 20 root root 4096 Oct 26 19:00 Other
The red is the others group which is by definition "all other users on this host" There is no Samba share authentication at this level based on your posted smb.conf file.
So the smbusers file is just for converting usernames for when connecting from windows? If my understanding is correct then that may be what is causing the issue. I'll try deleting the file's contents to see if that has any effect.
The smbusers file is used when you need to map a Windows user with a different username to a Linux user. If the username is the same Linux Windows and Samba then you don't need the file mapping at all. Just as @morbius has said.
Both users (generic and nasadmin) have had Samba users created using "sudo smbpasswd -a".
Some how I'm missing what you are trying to do here. The [Data] share with the directory: /media/generic/RaidData is setup as a guest share (any Samba user has access (no authentication))
Code:
[Data]
comment = All Data on the NAS
path = /media/generic/RaidData
read only = no
writeable = yes
browseable = yes
guest ok = yes
public = yes
force user = generic
; valid users = generic
...The guest ok =yes means no prompt for access. The directory that is shared has Linux authorization (permissions) for the user generic only.
All users are authenticated as the user nobody which is why you have to use the force user = generic parameter. If you truly want only the user generic authenticated get rid of the guest user = ok and the public = ok which is a synonym for guest ok anyway. In their place uncomment the valid users = generic. This makes the prompt come up and the only Samba user that is authorized is the user generic. The Linux directory permissions authorize the Linux user generic to read and write to the directory. This means the Samba user generic is only authenticated (who are you) and the Linux user generic is authorized (has permissions)> This is why it's a good habit for the user names to be the same. It just makes it simpler. In any case a share that restricts what user should use it should not use the guest parameter.
[QUOTE]
See below for results of the commands that you asked to be run:
Code:
generic@NewFishNAS ~ $ ls -l /media/generic
total 8
drwxrwxrwx 20 root root 4096 Oct 26 19:00 Other
drwxrwxrwx 10 generic generic 4096 Nov 6 23:16 RaidData
generic@NewFishNAS ~ $ ls -l /media/generic/RaidData
total 32
drwxr-xr-x 26 generic generic 4096 Oct 26 13:37 Anime
drwxr-xr-x 4 generic generic 4096 Oct 24 14:09 CloneZilla Backups
-rw-r--r-- 1 generic generic 2610 Nov 6 19:56 Forum post
drwxr-xr-x 19 generic generic 4096 Oct 24 13:24 Games
drwxr-xr-x 8 generic generic 4096 Oct 22 18:26 General Data
drwxr-xr-x 74 generic generic 4096 Nov 7 13:44 Movies
drwxr-xr-x 31 generic generic 4096 Oct 26 20:52 Music
drwxr-xr-x 18 generic generic 4096 Oct 10 19:47 TV Series
ls -l /media/generic/Other
total 92
drwxrwxrwx 4 generic generic 4096 Oct 12 14:10 *
drwxrwxrwx 5 generic generic 4096 Oct 12 14:04 *
drwxrwxrwx 3 generic generic 4096 Oct 12 15:16 *
drwxrwxrwx 5 generic generic 4096 Oct 12 14:01 *
drwxrwxrwx 4 generic generic 12288 Oct 12 15:06 *
drwxrwxrwx 3 generic generic 4096 Oct 12 14:02 *
drwxrwxrwx 3 generic generic 4096 Oct 12 15:16 *
drwxrwxrwx 2 generic generic 4096 Oct 22 17:41 *
drwxrwxrwx 2 root root 16384 Oct 10 00:41 lost+found
drwxrwxrwx 12 generic generic 4096 Oct 22 21:17 Misc
drwxrwxrwx 3 generic generic 4096 Oct 12 15:18 Network Trash Folder
drwxrwxrwx 5 generic generic 4096 Oct 12 14:01 *
drwxrwxrwx 4 generic generic 4096 Oct 12 14:06 *
drwxrwxrwx 3 generic generic 4096 Oct 12 15:16 *
drwxrwxrwx 3 generic generic 4096 Oct 12 15:06 *
drwxrwxrwx 52 generic generic 4096 Oct 26 19:00 *
drwxrwxrwx 3 generic generic 4096 Oct 12 15:16 *
(I'd rather not post the actual names of the folders in Other)
The [Other] share doesn't look right either for much the same reasons. See below in red
Code:
[Other$]
comment = Hidden Stuff
path = /media/generic/RaidData/Other$
read only = no
writeable = yes
browseable = no
valid users = fish
In this case you have the user fish as the only authenticated user and some how that users authentication (user/pass) is not correct. I see the user in the pdbedit listing so I wonder if the password is incorrect. IMHO you should do a little house cleaning as all the user and groups are for the user generic on this share. Why is that. Have you thought of using a common group for this if you have two users using this share?
Bookmarks