similar to: PAM authentification problem

I've added the pam changes that use winbind to authenticate users against the domain controller. I see all of the domain users in the graphical login, but when a user logs in who hasn't logged in before, the new home directory (/etc/DOMAIN/<userid>) isn't either being created or it's being created with permissions that don't allow files to be written under the user id.

Hi, we are running Samba 2.2.5 using LDAP und pam_ldap (pam_unix2 with auth+account+password=use_ldap) as PDC out of the SuSE 8.1 distribution. It runs very well: Login f?r Unix&Samba ok, Passwort-Change for Samba via smbpasswd Ok and we are able to manipulate the Linux Password in LDAP using the GQ Client. The only thing that doesn't work is "passwd" itself: venezuela:/home/tdm

Hi all, I am having a problem with pam_winbind.so. Is there any documentation that tells exactly what each module with pam_winbind.so does? In other words, what does the auth section do, what does the account section do??? When I try to authenticate, the auth section in login pam seems to pass successfully, but the account section seems to fail. Here is my login module auth required

Hi All, I am trying to get authentication against AD using Winbind and Samba 3. We use Kerberos 5 as well. I know that winbind is running properly because when I run wbinfo -a, I get success messages. The problem seems to be when I try to play with the pam modules. For kicks, here is the pam module for sshd: #%PAM-1.0 auth sufficient pam_winbind.so debug auth sufficient pam_unix2.so # set_secrpc

I'm working on a PAM setup that will ignore winbind/AD completely for users listed in /etc/passwd, and do the samba thing for all other users. Mostly it seems to work, but there's one weird side-effect. For non-AD users (only), an AD group "BUILTIN+users" is being added as a secondary group. If I kill winbind, it still gets added, although only the gid is available (no name).

Hello List, I have successfully integrated samba 3 to ADS Domain, and now i want to allow domain-users to access services on my linux box. For testing i chose /etc/pam.d/login and tried to allow ADS Users access to the console. But i always get the following errors: Mar 12 12:45:59 cuba90 pam_winbind[9011]: user 'r-ermer+mfeilner' granted acces Mar 12 12:45:59 cuba90 login[9011]: User

This is in the winbind documentation We divide the unified logon problem for UNIX machines into three smaller problems: 1. Obtaining Windows NT user and group information 2. Authenticating Windows NT users 3. Password changing for Windows NT users The winbind system provides a simple and elegant solution to all three components of the unified logon problem. First two things are explained,

I use pam_require.so to limit access to services via pam. Here is how I limit access to my pure-ftpd server to a specific group (GLFTPAccess). You can also limit access to specific users, like I did with the user root. auth sufficient pam_winbind.so auth required pam_unix2.so # set_secrpc auth required pam_nologin.so auth required pam_env.so account required pam_nologin.so account

Hi Gurus! Hope you can help me - I'm trying to get my SLES 10 SP2-box to authenticate users against Windows AD using Winbind, but I can't get it to work as I want. I have configured smb, winbind and Kerberos, and kinit, list, net ads join, wbinfo etc. works fine - but when I try to login, user xx.xx.admin, it fails. This is what I got in my /var/log/warn: eb 6 12:15:09

Hi, I am unable to login to a samba system that uses kerberos to authenticate to ADS if the users password has expired on the ADS system or if "User must change password at next login" is checked on the ADS.. I get a "login incorrect" message on the linux system and the log file gives the following error: pam_winbind[3647]: request failed: Must change password, PAM error

Okay, I started over from scratch with my samba server rebuild, but I am still getting some weird issues. Here are my config files of importance: --------------/etc/samba/smb.conf-------------------- # Samba Configuration File [global] workgroup = WAYNE realm = WAYNE.LOCAL server string = Samba Server security = ADS password server =

If I use any of the binary packages for SuSE SLES9 greater than 3.0.7 I can not see some of my NT4 trust domain via winbind. We have 5 regular NT 4 domains that trust each other. Two of them our within our LAN (local subnet), one of these domains the samba machine is within ... security = domain. There's another 5 domains that are setup for our AD enviroment for exchange, mixed mode. Using

Hi I'Ve set up winbind with Suse 9.0 and Samba 3.0.1 Everything i working fine exepct pam configuration How can I use pam_winbind and pam_unix2 ? > auth sufficient pam_winbind.so > auth required pam_unix2.so use_first_pass null_ok unix-users can login with correct password. NT-users can login with any password, even wrong passwords! > auth required

Hi I have winbind setup and authentication is OK. auth_check_password_send: Checking password for samba4 log: unmapped user [ALTEA]\[lynn2]@[HH30] auth_check_password_send: mapped user is: [ALTEA]\[lynn2]@[HH30] Linux log: Aug 12 09:05:00 hh30 su: pam_winbind(su:auth): getting password (0x00000000) Aug 12 09:05:01 hh30 su: pam_winbind(su:auth): user 'ALTEA\lynn2' granted access Aug 12

hi @ll this is working smb.conf samba beta 3 cvs version 22 jun from ftp.suse.com suse 8.2 minimal inst with additional glib locale , client win2000 serv pack 3 german umlauts work in windows ( after all for ? you see on linux etc) the name of machine is linux.linux.org a bind 9 is on the linux machine too to make dns resolving login domain works roaming profile works netlogon script works

Greets ... I am not getting it. I have samba (old one, 3.0.22-11-SUSE-CODE10) in an ADS-context, winbind works OK ... I am trying to connect vsftpd to winbind via PAM, this works TOO GOOD ;-) currently I am able to login to vsftpd with ANY password, that's bad. I am not understanding that PAM-stuff and I have some pressure to get that ftp-server up, so please would someone help me out? My

Sorry for the OT question; I'm hoping someone else has a similar setup and ran into this same problem? For some reason, not sure what I changed, my vmware server is no longer accepting the root login for the management console or web mui interface. I'm certain the password is correct, and I've even reset root's password to make sure. VMware seems to be running ok, I can access

http://bugzilla.mindrot.org/show_bug.cgi?id=938 Summary: "AllowGroups" option and secondary user's groups limit Product: Portable OpenSSH Version: 3.9p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: PAM support AssignedTo: openssh-bugs at

hello, please help me, I'm nearly going crazy :(( I tried to authenticate postfix (smtp-auth) via pam_smbpass.so. This doesn't work, it works with ssh and imap, but not with postfix, darn (pam_unix is working with postfix) Then I tried pam_winbind.so, which somebody has told me to use it instead of pam_smbpass.so. But this is not working in any way I am trying :( The PDC server

Hi all I would like to setup SAMBA 3 with LDAP, on Redhat Enterprise server 4.0 . So i am configuring PAM, to include pam_unix2.so . i don't have any file called pam_unix2.so, i have only pam_unix.so. so how do i go about it. Regards Niranjan