When configured in an MSCS environment, there should be one node for each
machine to manage each machine's local disk resources; and there should be
another node for the cluster resources. When connecting with the cluster
node name, make sure your options file has CLUSTERNODE YES in it; and when
connecting with the machine's local node name, make sure you are using
CLUSTERNODE NO. MIsmatching the node name and CLUSTERNODE settings can
cause the authentication problems you see.

If this doesn't help, then it would be useful to see the client options
files you are using, the *complete* output from dsmc.exe showing the
failure, any dsmerror.log messages that coincide with the time that you
tried to connect to the TSM server, your dsmcutil command(s) and
*complete* output.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 12/14/2004
12:07:18:

> We have a Windows2000 cluster servers.   TSM 5.6.1 client is installed
> on all.  All was working ok till I tried to create an archive backup.
> I keep getting a authentication error ANS1025E (RC137)  Session
> rejected: Authentication failure.   I have updated the password by way
> of dsmcutil, but it keeps getting corrupted with the error.Error 2
> occurred attempting to obtain registry password.    It is like the
> registry password keeps getting corrupted.   Has anyone run across this
> problem before.   I can supply more details.  I am just not sure what to
> supply.   I have looked in manual and google.  Just not having any luck.