I was experiencing the same thing, client's password suddenly don't work. As
if it expired although I don't specify an expiration and that field is also
blank. This has happened on about 60 to 70 percent of my clients.

In looking into this I found that a "q stat" showed "Password Expiration
Period: 540 Day(s)" which is where most of my clients are at. I always
assumed that this setting was for the admin password, but it is for both
clients and server.

>From "h q stat":

Password Expiration Period

     Specifies the period, in days, after which the administrator or client

     node password expires.

So from "h set passexp":

SET PASSEXP (Set Password Expiration Date)

Use this command to set the password expiration period for administrator and

client node passwords. You can set a common password expiration period for

all administrators and client node passwords or selectively set password

expiration periods.


Hope this helps.
Mark Bertrand


-----Original Message-----
From: Joni Moyer [mailto:joni.moyer AT HIGHMARK DOT COM]
Sent: Wednesday, January 07, 2004 1:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: client password expiration


Hello All!

I have had a bizarre occurrence of a client's password not working.  When I
reset the password, the user was then able to use the backup/restore
client.  What I am wondering is if I don't specify a password expiration
and that field is blank when I query that node on the TSM server, why does
it need to be reset?  Also, a command line restore worked, but the web
client did not.

No changes were made on the server or the client when this issue occurred.

Thanks in advance!


********************************
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
joni.moyer AT highmark DOT com
********************************