If you want Samba help your best bet is to post your smb.conf file.
Also your ultimate goals with user's / security or anything along
those lines (tight ship to zero authentication required, etc).
Your posted server smbpasswd.conf looks fine only if your client is
going to be attempting to sign on as the root user and your smb.conf
specifies security = user (default) and you are using passdb backend =
smbpasswd (default). You mentioned a username of office for the
server, so if that is how you intend to connect then you need a
smbpasswd user to match, assuming you are using security = user and
smbpasswd passdb backend.
client smbpasswd file does not matter.
When a client connects, samba will fork a new process and change it to
run as the appropriate user on the system. So if you intend to log in
as user "office", you should have a user called "office" in your unix
(system) password database, or equivalent. The samba process for that
connection will only have the same permissions as the "office" user
would ordinarily have on your system (it's a lot more involved than
that, really, but that's the q&d explanation).
~ Daniel
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:29:40 EDT