Homes directories

[AstroDroid]

My Homes directories are not working. I can see the share for %user% but when I go to access it, I get asked for a password. The current user password doesn't work. I am using encrypted passwords and user level security.

[homes]
comment = Home Directory for %S
path = /home/users/%u
valid users = %u
force user = %u
writeable = yes
read only = No
create mask = 0664
directory mask = 0775
browseable = No

I have changed the unix permisions to 2777 and I still can't access it. Yes I did add the user smbadduser, that doesn't help. It doensn't matter if it's a 9x or 2k machine.

What is difficult to understand is why I can see the share, but can't access it even though browesable is set to NO. If I don't have access then why can I see it.

[baldguy]

You should probably put samba in the title of your post ...

What sharelevel are you using? user, server, or domain?

[Bokkenka]

I have "valid users = %S".

I don't think you need the path statement... Homes is a special share that Samba knows about, and sets the path to the user's standard home.

If that doesn't work, try the bare minimums...

[homes]
comment = Home Directories
browseable = no
writable = yes

Then work your way up to what you want.

<< edit >>

Almost forgot... Be sure to restart Samba after every config change, or it won't be implemented.

[cowanrl]

Originally posted by AstroDroid
[B[
What is difficult to understand is why I can see the share, but can't access it even though browesable is set to NO. If I don't have access then why can I see it. [/B]

That is typical when you browse any Microsoft network. You can see many resources on the network whether you actually have access to them or not. The only way to find out if you have access to them is to click on them in Windows Explorer or try to map drive letters to them.

You can change the location of the directories in your HOMES share if you want. When you set the HOMES share to "browseable = no", the only one you will see when you browse the network is the share for your own home directory. If you set it to "brwoseable = yes" you will see all the home directories when you brwose.

Your problem looks like one of authentication, not permissions. If you have an authentication problem, you will usually be prompted for a password but it will never work. If you have a permission problem, you will usually receive an error message stating you don't have permission to perform a certain act.

The first thing I would try is take out the line "force user = %u". That shoud be a username, not a variable. That is used so that every user that connects to a share connects as the same user. That is not something you would normally want in your HOMES share.

If that doesn't change anything, it could be related to your use of the smbadduser script. Depending on how old the script is, it could be updating the wrong smbpasswd file for Linux. I would try setting the Samba password using the smbpasswd command directly. You must be root to do this. The syntax is:

smbpasswd -a username

where username is a user account name that already exists on the Linux machine. Enter a password when prompted. It does not have to be the same password as the Linux login password.

I would change the %u to %S in the following lines:

path = /home/users/%S
valid users = %S

If that doesn't help, then I agree with Bokkenka. Use the 3 lines he shows in his post and let Samba take care of all the details for the HOMES share. By default, it uses the home directories for users listed in the /etc/passwd file