similar to: Winbind running on Samba PDC for shell logins

Hi all- In migrating from 3.0.2 to 3.0.8 on a box that's an ADS domain member, I had a relic line in smb.conf like this: winbind separator char = - With 3.0.2, users connecting wouldn't have a domain and separator char component, so spnego kerberos replies to the 2003 domain controller would be fine. In 3.0.8, users connections would have the domain and separator char for spnego

I developed a solution to the problem where you might have systems setup w/ winbind mapping GIDs and UIDs, NSS, and PAM setup so windows users can login, but winbind maps possible different UIDs/GIDs from system to system preventing unified UIDs/GIDs in your environment. I tried having one box setup with NSS winbind / PAM etc. plus I made that system an NIS master w/ a script to periodically pull

Hi all- I searched quite a bit and couldn't really come up with anything, so I'm posting to the list to hopefully find out if I have any options. I've got a production FC6 box running 3.0.24-7.fc6 build of samba server that's very stable for us. It's a member of an ADS domain w/ server 2003 domain controllers. Recent 64 bit windows XP pro boxes are having the exact problem

Hello, (I'm reposting this after my first attempt about 25 minutes ago has not come through to me. I am leaving out the looooooong debug log dump, in case the listserv didn't like the massive content, but it will be provided upon request.) I have a RHEL 6.5 server that was configured to use Samba 3.6.9-167 to authenticate against a Windows 2008 R2 Active Directory domain. The

Hello All, I am at the switch from sssd to winbind based samba domain members (Debian 9 stretch). I am using Samba 4.10.2 packages from Louis ( http://apt.van-belle.nl/ ) and rid backend for idmap. *My problem:* I am able to logon to my domain members using winbind_pam as long as my client is connected to a network where a domain controller is reachable. As soon as I shutdown and connect a

Folks, Got an odd one here that's had me scratching my head for a few days! Samba 3.3.4-31 from SuSE's RedHat repository, RHEL5 on x86. Compiled OK once I'd worked out how to force a build on the libraries I needed, I also added the code back in to support the 'winbind: ignore domains' directive in smb.conf. Discovered the hard way that 'make install' doesn't

Hello all, I currently have the following setup working nicely: A Samba PDC, with LDAP-SAM, syncs passwords between LDAP and Samba (and /etc/shadow when appropriate) correctly - either when changing them through Samba (samba has PAM support enabled and working) or through normal Unix mechanisms (/usr/bin/passwd, using pam_smbpass, pam_ldap, etc.). Several other Linux machines, running Samba,

Hi. I have some shares on a server that are offered to specific Active Directory user groups, but the business doesn't want those users to be able to login to the server. If I were to add "require_membership_of" to pam_winbind to limit logins and shut out the users I don't want, would it also have the side effect of denying those users access to the shares as well? Regards,

Hi, I am currently trying to set up a RedHat 9 Linux client to authenticate against a Windows 2000 Active Directory server. Using the Winbind documentation I have successfully authenticated however I now have a problem with gdm. Jun 18 12:18:48 jerry pam_winbind[1192]: user 'AU+Bhales' granted acces Jun 18 12:18:48 jerry pam_winbind[1192]: user 'AU+Bhales' granted acces Jun 18

Hello, on my samba AD i have set homedir to /home/users/<username>. Now i have setup a linux client with pam-winbind and nss-winbind. getent passwd <username> show /home/users/<username> as home directory. And that's dir is create on login. Why it is use the path set on AD and not the path set in smb.conf ? grep home -r /etc/pam.d/ /etc/samba/smb.conf

Everyone, We are currently seeing a very strange problem on our server. Everything will be running along smoothly and then all of a sudden, nobody will be able to login. Looking through the logs reveals the following messages... Apr 24 10:55:15 LINUX-1 httpd2-prefork: pam_winbind(httpd): pam_winbind_request: read from socket failed! Apr 24 10:55:15 LINUX-1 httpd2-prefork:

A Debian/Lenny-Server is connected to a PDC (using samba) and tries to authenticate logins via pam_winbind. User mapping and everything else needed works fine (i.e. especially getent shows all the accounts), however remote logins of domain users fail. I have: | gatekeeper:~# cat /etc/pam.d/common-auth | [...] | auth sufficient pam_unix.so nullok_secure | auth required

> We are trying to have linux authenticate to linux server running samba > 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all > authenticate to the linux server but we are having problems with blank > passwords or the user can type any password. We are using pam modules for > the authentication on the client machines. > I have included the config files for

> -----Original Message----- > From: Reed, Tameika > Sent: Monday, November 17, 2003 5:56 PM > To: 'samba@lists.samba.org' > Subject: Samba PDC trying rid null logins > > > > > We are trying to have linux authenticate to linux server running samba > 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all > authenticate to the

Hi all, I have been trying to setup authentication of users on a Linux server against Windows server 2003 using winbind. I am at the point where an su - ADUSERNAME works, but sshing as that user still doesn't work. When I try to ssh as an AD user as follows: ssh -l "RILINUX+testuser" server.domain.com I get the following output in /var/log/messages: server pam_winbind[5906]:

Hello, I am trying to get winbind up and working for logins. Here is my error message from /var/messages: Aug 20 20:59:51 aslan pam_winbind[32713]: user 'lisa.snow' granted acces Aug 20 20:59:51 aslan pam_winbind[32713]: user 'lisa.snow' granted acces Aug 20 20:59:51 aslan login[32713]: initgroups: Operation not permitted Here is my pam.d/login file: #%PAM-1.0 # orginal before

How can I fix? Oct 29 09:33:06 frenetico-mt sshd[2635]: pam_winbind(sshd:auth): getting password (0x00000000)Oct 29 09:33:06 frenetico-mt sshd[2635]: pam_winbind(sshd:auth): user 'administrator' granted accessOct 29 09:33:06 frenetico-mt sshd[2635]: pam_winbind(sshd:account): user 'XXXX\administrator' granted accessOct 29 09:33:06 frenetico-mt sshd[2635]: Accepted password for

Hi Team, We have a weird issue that we are trying to understand. We have winbind set up and working successfully for user authentication with passwords via ssh. We have pam.d/system-auth-ac and password-auth-ac (symlinked) set to require membership of a group which works great via password authentication. However, if the user has a ssh key set up, they seem to bypass the group membership

I am attempting to use winbind for Telnet authentication but winbind pam doesn't recognize ads realm or smb.conf workgroup..see error snapshot. pdtsun03 is hostname of solaris 10 ADS domain member running samba 3.0.11. "net ads join" worked..."net ads user" returns all MYADSDOMAIN users and samba shares work from both unix and NT side. one note..After make install, I

I'm running CentOS 4.3 with the most recent samba-client and samba-common rpms. I've managed to configure samba/winbind to allow me to join the box to the AD, create the UID and GID mappings, etc. However, when I try to connect via ssh, the account cannot log in. /var/log/messages says the following: Sep 5 17:15:25 kdcdmz sshd[6263]: error: Could not get shadow information for