On Wed, Aug 6, 2008 at 9:37 AM, Roger Searle <[EMAIL PROTECTED]> wrote:
> Nick Rout wrote:
>>
>> On Wed, Aug 6, 2008 at 8:58 AM, Roger Searle <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>> Hi, I have set up some users with passwords using the kubuntu user
>>> management tool, created a file share via webmin and added those users as
>>> valid users for the share. As root used "smbpasswd -a" to (do what ever
>>> that
>>> does) for each user using the same password.  When that user attempts to
>>> connect to that share from an XP box, they can not do so with that
>>> username,
>>> the only user that can do so is my own username which was created prior
>>> to
>>> the serving machine booting.
>>> So I'm thinking something needs to be restarted on the server, have
>>> restarted samba, and that's not enough.  I can see the users listed as
>>> "valid users" for the share in smb.conf.  What have I missed?
>>>
>>> Cheers,
>>> Roger
>>>
>>
>> permissions on the shared directories/files?
>>
>
> Permissions appear good for the user.  On the XP box I'm getting "incorrect
>  or unknown username for \\machine\share" . . .


man smbpasswd, hidden amongst many  other proverbs, he says:-

 password -a
          This option specifies that the username following should be added to
          the local smbpasswd file, with the new password typed (type  <Enter>
          for  the  old password). This option is ignored if the username fol‐
          lowing already exists in the smbpasswd file and it is treated like a
          regular change password command. Note that the default passdb back‐
          ends require the user to already exist in the system  password  file
          (usually /etc/passwd), else the request to add the user will fail.

          This option is only available when running smbpasswd as root.

My interpretation of that 'glorious prose' means that the users of the
shares on the samba server also have to be users on that server.

Are they?

As the root user

cat /etc/passwd to find out.

HTH, YMMV etc

-- 
Sincerely etc.
Christopher Sawtell

Reply via email to