Displaying 20 results from an estimated 20000 matches similar to: "Wrong message "Your password has expired""
2006 Feb 01
0
SAMBA 3.0.21b expired password issue for Solaris 9 - perhaps a bug in winbind or /etc/pam.conf misconfigure
All,
The SAMBA version 3.0.21b expired password pam_winbind.so section
perhaps might still have an issue. It seems to just be in some kind of
loop and
never completes the section in pam_winbind.c of pam_sm_chauthtok.
See ssh (Solaris 4.2.p1 ssh) sequence below:
ssh hermione
Password:
Changing password for leeraym
(current) NT password:
Re-enter new Password:
Password:
Password:
2006 Aug 01
2
[HELP] Samba 3.0.23a pam_winbind says password expired
hi,
i just do some tests with a fresh compiled samba 3.0.23a.
trying to authenticate against PAM with pam_winbind gives:
Aug 1 09:59:21 humevo36 pam_winbind[27853]: pam_winbind:
pam_sm_authenticate (flags: 0x0000)
Aug 1 09:59:23 humevo36 pam_winbind[27853]: Verify user `gasch'
Aug 1 09:59:23 humevo36 pam_winbind[27853]: enabling cached login flag
Aug 1 09:59:23 humevo36
2006 Jan 26
1
pam_winbind.so user expired password config for Solaris /etc/pam.conf
I'm trying to configure my Solaris 9 pam.conf for CDE login/password
expiration using
ADS security on W2003. If my AD account password is in good standing,
my config works great in /etc/pam.conf. However - I'm having trouble
getting it to recognize that my password in AD has expired to ask me
to reset it on the CDE screen. With the config below - it just tells
me "login
2009 Mar 13
1
PAM_WINBIND problem with sambaPwdMustChange
Hi People!
I use pam_winbind for authentication in my computer workstation using
Debian Lenny 5.0, Stable Version.
I configure my user with this option "sambaPwdMustChange: 0", and I
logon in GDM without asking to change password. Who knows what can be?
I use Samba PDC with Heimdal Kerberos, but, I configure PAM with only
pam_winbind for tests...
Client versions:
ii
2009 May 01
2
pam_winbind: user needs new password
Hi,
I just upgraded from Mandriva 2009.0 (Samba 3.2.3) to Mandriva 2009.1
(Samba 3.3.2), keeping all the same config files I had before. I use
pam_winbind to authenticate users against MS Active Directory.
Everything was working perfectly prior to the upgrade, and now
everything seems to be fine except for one thing: no user can have
access due to the following errors (taken from auth.log):
May
2006 Mar 28
3
Error compiling samba 3.0.21c, AIX 52 ML7 gcc 3.3.2
Can anyone help with the following error I get whilst comiling samba,
configured with following flags:-
./configure --prefix=/opt/samba-3.0.21c --with-ldap --with-ads --with-krb5
--with-pam --with-winbind
heimal kerberos heimdal-0.7.2
openldap openldap-2.3.20
[WMSTRAIN:root]/appfs2/samba/samba-3.0.21c/source> make && make install
Using FLAGS = -O -D_SAMBA_BUILD_ -I./popt
2007 Jan 08
0
pam_winbind + password never expires [re-post]
Sorry for the repost, but I've not gotten any response and the problem
persists. Does anyone have any idea how to fix?
===================================
I read a few posts in the archives about this problem and that it was to
be fixed in 3.0.23c. Currently I'm running 3.0.23d-2+b1 on a debian
system and am getting the following:
$ ssh -l testuser fileserver
Password:
Your password
2007 Jan 04
0
pam_winbind + password never expires
I read a few posts in the archives about this problem and that it was to
be fixed in 3.0.23c. Currently I'm running 3.0.23d-2+b1 on a debian
system and am getting the following:
$ ssh -l testuser fileserver
Password:
Your password has expired
Here's what auth.log shows:
Jan 4 11:46:26 tmcsamba1 pam_winbind[14309]: user 'DOMAIN1+testuser' OK
Jan 4 11:46:26 tmcsamba1
2009 Jun 24
0
winbind authentication mystery
Greetings,
I'm running Fedora 11 (Samba 3.3.2) and am trying to configure winbind
authentication against a Windows 2003 server.
I've run kinit and net join successfully, and can wbinfo -u, -g, and -t
successfully, as well as getent passwd and getent group successfully. I
can even use passwd to change domain user passwords.
However, when I try to log in via gdm, ssh, or even su, I do not
2009 Dec 31
0
winbind authentication mystery
Hi Chris,
Were you able to solve this.
Regards,
David.
Greetings,
I'm running Fedora 11 (Samba 3.3.2) and am trying to configure winbind
authentication against a Windows 2003 server.
I've run kinit and net join successfully, and can wbinfo -u, -g, and -t
successfully, as well as getent passwd and getent group successfully. I
can even use passwd to change domain user passwords.
However,
2009 Nov 29
0
password expiration
Greetings. I have problem with password expiration problem i cannot
handle myself, so i wrote in this list.
Recently i discovered that a newly created samba account has already
expired password.
smbldap-useradd -a -d /home/tommy -G education -s /bin/bash -M tommy -c
"Tommy T." tommy
smbldap-passwd tommy
getent shadow
user:*:::::::0
user2:*:::::::0
user3:*:::365::::0
2010 Jan 25
0
don't show "Wrong Password" message
Hi all,
I notice that when a user is entering a wrong password on a domain user.
I get a message
Wrong Password
Incorrect Login.
Is there a way to configure pam_winbind.so not to show Wrong Password
message?
I tried pam_winbind.so silent but is didn't work.
2023 Oct 29
1
Samba AD DC: users cannot change expired passwords
On Fri, 2023-10-27 at 10:44 +0200, Kees van Vloten wrote:
> Hi Andrew,
>
>
> Op 27-10-2023 om 02:22 schreef Andrew
> Bartlett:
>
>
>
> >
> > I'm sorry to say that from here you really need to work
> > closely with a Samba developer (eg via a commercial support
> > provider) or do a deep
2005 Aug 16
0
FW: Error:The semaphore timeout period has expired
UPDATE:
We found out that there was still an entry in /etc/rc.local to start up
the old SAMBA after upgrading and setting up to run from inetd.conf.
Once the /etc/rc.local entry was removed, we no longer receive the
"semaphore timeout period has expired" messages and we are able to
connect to the shares.
Ben Burruel
Sr. Systems Manager
Metrics & Mainframe Capacity Planning
San
2023 Oct 27
2
Samba AD DC: users cannot change expired passwords
Hi Andrew,
Op 27-10-2023 om 02:22 schreef Andrew Bartlett:
> I'm sorry to say that from here you really need to work closely with a
> Samba developer (eg via a commercial support provider) or do a deep
> dive into debugging yourself.
>
> Ideally if you have time, do a git bisect between the last known
> working version and the first failing one. ?That may find the
>
2011 May 11
3
[Bug 1904] New: sshd refuses certificate-based authentication if password has expired
https://bugzilla.mindrot.org/show_bug.cgi?id=1904
Summary: sshd refuses certificate-based authentication if
password has expired
Product: Portable OpenSSH
Version: 4.3p2
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo:
2008 Jan 20
1
winbind forced password change requires interactive shell
We've discovered that although Winbind supports password changes when the
account password is expired, this only works with *interactive* shells.
This is a major problem for us. Use case 1: SSH tunnels:
$ ssh user2@localhost -N -L 4711:localhost:22
user2@localhost's password:
<trying to use the tunnel>
channel 2: open failed: administratively prohibited: open failed
As you can
2018 Nov 11
1
The SSL certificate of repo.dovecot.org has expired.
Yes. Sorry about this.Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Masaki Nemoto <itml at ma3ki.net> Date: 11/11/2018 10:00 (GMT+02:00) To: dovecot at dovecot.org Subject: The SSL certificate of repo.dovecot.org has expired. HiThe SSL certificate of https://repo.dovecot.org has expired.Do you have plans to update it?
-------------- next part
2003 May 12
1
[Bug 562] sshd and password has expired (password aged)
http://bugzilla.mindrot.org/show_bug.cgi?id=562
Summary: sshd and password has expired (password aged)
Product: Portable OpenSSH
Version: 3.6.1p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
2015 Aug 12
0
kinit succeeded but ads_sasl_spnego_krb5_bind failed: The context has expired : Success
Hai,
i compaired your config with my own..
Looks the same and correct to me.
try it without these 2 in krb5.conf:
>ticket_lifetime = 24h
>renew_lifetime = 7d
and in smb.conf i dont have
> idmap cache time = 5
> idmap negative cache time = 5
> winbind cache time = 5
so i suggest first remove the 2 lines in krb5.conf and test.
then if needed the other 2.
and your did