Home / ubuntu / Questions / 160558
In Process
rlemon
Asked: 2012-07-07 09:43:14 +0800 CST

Samba fileshare playing nice with windows users and accounts

  • 772

I have been reading article after article and asking around in the chats for help on why this is not working :(

Here is what I've done so far:
I have installed samba following the server guide in the first link posted.
I have edited my smb.conf file.. here is (what I think) is the relevant part of that for you to see..

[homes]
   comment = Home Directories
   browsable = no
   writable  = yes
   valid users = %S
   valid users = MYDOMAIN\%S
   create mask = 0755
   directory mask = 0755

I have created a user running sudo adduser wks. This successfully adds the user and creates the home folder with group and user permissions set to "wks". Now I add that same user to samba smbpasswd -a wks no errors all seems to go well.

Ok so from here I should be at the very least be able to goto a windows machine, open up the network computers, find the server, and open the home folder for "wks"??
At the moment I can do all of these things but access the home folder (even with the username and password I set in the previous steps).

Have I missed something trivial? Was that a bad tutorial to read from? I am confused how to proceed from here.

TO summarize: the user wks (this happens to also be the windows credentials.) with the supplied password still does not have permission to access the home folder while accessing it with windows.

edit

I double checked on windows to make sure I was seeing it in the workgroup... I am not. Is there a step I missed? in smb.conf I have workgroup = DMSI and the windows computers are all part of that workgroup.

permissions

1 Answers

  1. Check out these Samba Troubleshooting links:

    Also, check the manual with this console command:

    • man smb.conf

    The "valid users" option accepts user names or group names. I don't think it can be listed twice, and it may not be able to interpret the %S value.

    Edit: trying to enable security while creating a new setup will always complicate the troubleshooting process. For example, is the problem with the initial setup, or that your security is blocking the user? So remove the "valid users" until you get the connection working. Later, you can add security back into the process, and you will know that the "valid users" syntax is the only portion you'll need to troubleshoot.

    • 2