[Samba] Re: Cannot log in to domain

Edward Luck ed.luck at gmail.com
Thu Jan 5 12:38:41 GMT 2006

Hm, well I fixed this problem.  For some *bizarre reason*, my
/etc/passwd file had been chmod'ed to 640 (rw-r-----) - when it should
be 644 (rw-r--r--).  Samba was unable to read the file when a user
logs into the domain because the user that the smbd process was
running as had no access to the passwd file.

I literally wasted about 12 hours on this, all for a stupid file
permission problem. D'oh is me.

On 1/5/06, Edward Luck <ed.luck at gmail.com> wrote:
> Hi folks,
> Just yesterday, my Samba installation on OpenSlug suddenly stopped
> working, out of the blue.  Now, users on my WinXP SP2 systems cannot
> under any circumstances log in to the domain.  Local Windows users
> however can map shares with no problem.
> When a domain user attempts to log on to a domain member PC (joining
> the domain works fine, by the way), they are denied with the generic
> Windows XP message of "The system could not log you on, make sure your
> username and password are correct".
> At the same time, the log.<computer name> file reports the following:
> [2006/01/05 13:59:34, 1] auth/auth_util.c:make_server_info_sam(840)
>   User blah in passdb, but getpwnam() fails!
> [2006/01/05 13:59:34, 0] auth/auth_sam.c:check_sam_security(324)
>   check_sam_security: make_server_info_sam() failed with
> This is basically telling me that Samba can't see the user in the
> passwd file.  But it works for Local windows users though, which is
> just bizarre.
> This is the C code in auth_util.c that is causing the problem:
> if ( !(pwd = getpwnam_alloc(pdb_get_username(sampass))) )  {
>                 DEBUG(1, ("User %s in passdb, but getpwnam() fails!\n",
>                           pdb_get_username(sampass)));
>                 free_server_info(server_info);
>                 return NT_STATUS_NO_SUCH_USER;
> I can only assume that for some reason, this particular C function is
> trying to run getpwnam() and an error is being returned.  But the same
> process happens for Local windows users connecting to shares, so I'm
> totally stumped.
> What's also very odd is that this problem just
> suddenly...well...happened.  And I don't recall making any changes to
> my Linux server.  It's a Linksys NSLU2 running OpenSlug 2.7 beta, and
> has been rock solid up until this point.
> --
> Keep flying, and stay shiny.

Keep flying, and stay shiny.

More information about the samba mailing list