Well Jerry, you've had an interesting week!
We're seeing the same problem.
Happened with a bunch of Win2K machines after we pushed out the 3.7.2 client
(to replace the 3.7.1 client) to about 90 machines.
What we think happened is that next time their password expired, instead of
getting a good new password generated, the clients flooded our server with
the invalid password messages. When several hit at once it took the server
down several days in a row because the recovery log filled because there was
stuff flooding the activity log too fast.
We got a PMR open, but it hasn't happened lately, and I don't think we ever
got far enough with Tivoli to figure out what doc is needed for them to
pursue it. We can't reproduce it on demand, so I don't know how we would do
a trace. And it didn't happen to EVERY client we upgraded, just some of
them.
Our desktop support people just tracked down the runaway machines and fixed
the passwords as necessary to get our server running again. If we can get a
handle on how to nail one (before it takes our server down) we will pursue
it with Tivoli.
Our server is AIX, 3.7.2.
.
-----Original Message-----
From: Lawson, Jerry W (OTSD, IT) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 2:15 PM
To: [EMAIL PROTECTED]
Subject: Runaway logon with invalid password
Date: February 22, 2001 Time: 2:13 PM
From: Jerry Lawson
The Hartford Insurance Group
860 547-2960 [EMAIL PROTECTED]
----------------------------------------------------------------------------
-
Has anyone seen problems with TSM 3.7.2 clients "running away" when the
client tries to logon with an invalid password?
Here is the scenario:
Both the client and the server are running 3.7 - the server is MVS,
3.7.40, the client is an NT client with the 3.7.2 code installed. The
password has expired; it was last changed approximately 135 days ago.
The client dials in via Shiva, and gets a connection to our network.
The connection is made, and a message is logged that the password has
expired. The session is ended, and immediately, a retry is attempted. The
same results occur, of course. This happens at approximately 2 attempts per
second. I have not talked to the client, but it appears that it is coming
from the scheduler service.
I found it, took a swag at what was expected as a password, changed it, and
the problem stopped. I can only assume that I changed the password
correctly, but it's highly unlikely I'm that good.
Any suggestions or experience here?
----------------------------------------------------------------------------
-
Jerry
Insanity is doing the same thing over and over....and expecting the results
to be different - Anon.
