/pam_winbind.conf
with the following format:
[global]
require_membership_of=GROUP1
require_membership_of=GROUP2
and this worked just fine ..
-Original Message-
From: Gerald (Jerry) Carter [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2008 6:53 AM
To: Glenn Bailey
Cc: samba@lists.samba.org
Hello folks,
Been beating my head with an winbind and pam just behaving oddly. I have
following
various HOW-TO's, wiki's, and docs, and just can't seem to get past a wall.
Here a
some of the issues:
- the 1st attempt at ssh'ing to a server gives me a 'Wrong Password' in the
logs. Here's
an
Hello all,
I did a fresh compile of 3.0.30, deploy'd it to a couple of servers, and then
would
get the following errors in my logs:
pam_winbind(sshd): pam_winbind_request: write to socket failed!
This would happen about 5 minutes after restarted smbd, nmbd, and winbindd. For
the
1st 5 minutes
This issue was not occurring with my 3.0.28a compile :-(
Any ideas?
Known bug we discovered after ship, we'll be doing a bugfix release this week,
sorry :-(.
Ok, thought it was something weird with my compile. Thanks for the information!
--
To unsubscribe from this list go to the following
Howdy folks,
I'm having a weird issue here. I have winbind running on several other servers
on our domain, and they are working fine. From what I can tell the configuration
is identical, as I custom rolled my own RPM that set's all the config
parameters.
What's happening is when I try to ssh to
Of Glenn Bailey
Sent: Wednesday, May 14, 2008 4:02 PM
To: samba@lists.samba.org
Subject: [Samba] windbind locks out domain account
Howdy folks,
I'm having a weird issue here. I have winbind running on several other servers
on our domain, and they are working fine. From what I can tell
Howdy folks,
I'm having an issue with sudo not recognizing nested groups
via AD and winbind. I have an AD group called UnixAdmins and
when I ad and AD account *directly* into this group, I am able
to use sudo just fine as it is in the sudoers. *but* say I
have a nested group in UnixAdmins like
I'm having an issue with sudo not recognizing nested groups via AD and
winbind. I have an AD group called UnixAdmins and when I ad and AD
account *directly* into this group, I am able to use sudo just fine as
it is in the sudoers. *but* say I have a nested group in UnixAdmins
like
