Re: pam/winbind user not found problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Thursday 16 July 2009 01:20:01 am Andreas Schneider wrote:
> On Wednesday 15 July 2009 19:01:19 Gary Greene wrote:
> > You haven't got nscd running have you? If you do, turn it off. It causes
> > weird auth issues with Winbind.
> In large environments you don't want to disable nscd. However on new
> systems winbind should work just fine with nscd. I know large environments
> where it works like a charm.
> Cheers,
> 	-- andreas

NSCD conflicts with Winbind's own caching and will cause you not to be able to 
authenticate randomly/odd credential dropping/etc, even with new releases of 
Samba and GLibC.

Here's the documentation directly from the Samba project:

The name service caching daemon (nscd) is a primary cause of difficulties with 
name resolution, particularly where winbind is used. Winbind does its own 
caching, thus nscd causes double caching which can lead to peculiar problems 
during debugging. As a rule, it is a good idea to turn off the name service 
caching daemon.

Gary L. Greene, Jr.
Sent from:
 08:23:58 up 73 days, 50 min,  4 users,  load average: 0.93, 0.79, 0.74
Developer and Project Lead for the AltimatOS open source project
Volunteer Developer for the KDE open source project
See and for more information

Please avoid sending me Word or PowerPoint attachments.

Attachment: signature.asc
Description: This is a digitally signed message part.

Pam-list mailing list

[Index of Archives]     [Fedora Users]     [Kernel]     [Red Hat Install]     [Linux for the blind]     [Gimp]

  Powered by Linux