I've been running two samba servers on a network having a bunch of XP Home boxes. I recently added an XP Pro box, and wanted to set samba to grant and deny access, etc., based on users. I've figured out (using webmin) how to add Unix users to the samba box and how to convert those users to samba users. The weird thing is, when I add users to samba, none of my XP Home boxes can access the samba shares. I get an "access denied . . .you may not have permission" (or something like that) message. As soon as I delete all my users from samba, leaving only "nobody", everything is peachy. I'd love some help, if anyone has any idea where I might begin debugging this. TIA - Jeff
> The weird thing is, when I add users to samba, none of my XP Home > boxes can access the samba shares. I get an "access denied . . .you > may not have permission" (or something like that) message. As soon as > I delete all my users from samba, leaving only "nobody", everything > is peachy. > I'd love some help, if anyone has any idea where I might begin > debugging this.At a rough guess I suspect that when the user exists, the XP box connects as that user and then discovers that it has no access to the underlying filesystem. Once the users are deleted, Samba treats the user as "nobody" which does have access to the underlying files. Cheers, Adam.
> Thanks for the info. Is there any way to see who the XP box is > connecting as?Running "net config workstation" from a command prompt on the XP box will tell you the username, then checking your 'username map' file (if any) will tell you which UNIX user this name is being mapped to, then checking your smbpasswd file will tell you whether that username has a password. You could try running "chmod ugo+rwx folder" on a shared directory to see if it is a filesystem issue, however if you run "\\hostname" on the XP box and can't even get a list of shares up then it sounds like the XP user doesn't exist in the smbpasswd file. Either way, you *should* get exactly the same behaviour by running (on the Samba box) "smbclient -L localhost -U username" and putting in the correct password. This may assist with debugging. Also, make sure you don't have a "map to guest" option in smb.conf, as this can also cause this sort of behaviour if you don't know exactly what it's doing. Cheers, Adam.