Hmmm. I've determined long ago that the single best way to track down
your error is to post your problem publicly. Clearly, my smbpasswd
command line in my original post (re-created below in its glory) is
incorrect. *sigh* However, I -am- still convinced I'm having some sort
of issue that's related to authentication of some sort. For example:
----------------------------------------------------------------------
[From W2K machine that's a member of the domain:]
C:\>cacls \\freedom\shared\it\rfc
\\freedom\shared\it\rfc :F
:F
Everyone:R
:(OI)(CI)(IO)F
:(OI)(CI)(IO)F
Everyone:(OI)(CI)(IO)R
C:\>cacls \\freedom\shared\it\rfc /g fred:f
Are you sure (Y/N)?y
processed dir: \\freedom\shared\it\rfc
C:\>cacls \\freedom\shared\it\rfc
\\freedom\shared\it\rfc :F
:F
Everyone:R
:(OI)(CI)(IO)F
:(OI)(CI)(IO)F
Everyone:(OI)(CI)(IO)R
------------------------------------------------------------------------
And here is the corresponding output from log.scanner1 off of freedom:
------------------------------------------------------------------------
[2002/06/10 01:15:00, 0] smbd/posix_acls.c:create_canon_ace_lists(775)
create_canon_ace_lists: unable to map SID
S-1-5-21-3724628487-1952136730-75335
2548-2036 to uid or gid.
[2002/06/10 01:15:22, 0] smbd/posix_acls.c:create_canon_ace_lists(775)
create_canon_ace_lists: unable to map SID
S-1-5-21-3724628487-1952136730-75335
2548-2036 to uid or gid.
-------------------------------------------------------------------------
There is also a slew of
[2002/06/09 23:58:47, 0] passdb/pdb_smbpasswd.c:pdb_getsampwnam(1367)
unable to open passdb database.
though these don't appear to crop up at the same time that the cacls
command is issued.
Sorry for the goof-up; that's what I get for trying to figure things out
after 1:00 a.m. after a long weekend...
-Ken
On Mon, 2002-06-10 at 01:04, Ken D'Ambrosio wrote:
> I've been having some trouble getting ACLs to work under my Samba 2.2.4
> client (talking to my 2.2.4 "PDC"). Finally, I checked the log and
> realized that it wasn't able to map SIDs to UID/GIDs. Further checking,
> and I realized that the client never made the request to the server.
> Here's some output from smbpasswd:
>
> smbpasswd -D 4 fred
> Initialising global parameters
> params.c:pm_process() - Processing configuration file
> "/usr/local/samba/lib/smb.conf"
> Processing section "[global]"
> doing parameter workgroup = XANOPTIX
> doing parameter netbios name = freedom
> handle_netbios_name: set global_myname to: FREEDOM
> doing parameter server string = Samba Server
> doing parameter password server = polaris <-- PDC -is- listed...
> doing parameter encrypt passwords = true
> doing parameter security = DOMAIN
> doing parameter log file = /usr/local/samba/var/log.%m
> doing parameter max log size = 50
> doing parameter local master = No
> doing parameter domain master = False
> doing parameter dns proxy = No
> doing parameter printer admin = @ntadmin, kend, root
> pm_process() returned Yes
> New SMB password:
> Retype new SMB password:
> startsmbfilepwent_internal: unable to open file
> /usr/local/samba/private/smbpasswd. Error was No such file or directory
> unable to open passdb database.
> Failed to find entry for user fred.
> Failed to modify password entry for user fred
>
> So, despite the fact that:
> a) the PDC is explicitly listed (I've also tried "*") in the "password
> server" paramater, and
> b) there is no "smb passwd file" heading,
>
> it's still trying to go there. Methinks this is a bug. Clearly
> something I've done has triggered it, though I'm not sure what. If it's
> of any help, this is also configured --with-acl-support for XFS.
>
> Thanks for any info that could help me sort this out...
>
> -Ken
>
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
