SQL30082N Attempt to establish connection failed with security reason "24"

SQL30082N Attempt to establish connection failed with security reason "24"

Post by David Sarg » Thu, 10 Jul 2003 22:16:21


I have a DB2 8.1.2 (fixpack 2) client connecting to a DB2 7.2.7 (fixpack 9)
server. The DB2 7.2.7 instance is configured with the following security
settings:

authentication CLIENT
trust_allclnts DRDAONLY
trust_clntauth SERVER

Whenever I try connecting (connect to dbname user db2admin using password)
from an 812 client to the 727 server with the aforementioned security
settings, I receive the following:
SQL30082N Attempt to establish connection failed with security reason "24"

If I change authetication back to server (with trust_allclnts and
trust_clntauth set appropriately), the connection works fine. Is the
DRDAONLY trust_allclnts setting deprecated in 812, or is this a bug? (I
have tried this both on a linux and windows client and server, w/the same
results.)

Thanks in advance,

--
David Sarge
Enterprise Technology Partners, Inc.
DB2 Certified DBA
Oracle Certified DBA
 
 
 

SQL30082N Attempt to establish connection failed with security reason "24"

Post by edmundleun » Sat, 15 Jul 2006 11:55:11

It is found that a DB is setup for sometime.

One day, the user suddenly cannot connect to DB.
We found that the case is as follow:

1. User can connect to DB by issuing command

db2 connect to <DB>

2. However, when the user connect to DB by using

db2 connect to <DB> user <user id>
Enter current password for pws01ua1:

and will go following error.

SQL30082N Attempt to establish connection failed with
security reason "24"
("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

We have checked that the password is not expired and the account is not
locked by the system. So, we are not sure about the solution.

Our system information is as follow:

Platform: AIX 5.3
DB Version: 8.2 FP 3

Thanks

 
 
 

SQL30082N Attempt to establish connection failed with security reason "24"

Post by Knokman » Sat, 15 Jul 2006 21:25:18

This is known problem when using DB2 8.2 and AIX5.3
(don't know if already fixed in newer fix packs)
If you use this db2set setting and restart the instance the problem is
"solved":
db2set DB2_NUM_CKPW_DAEMONS=0

Knokmans