i agree, txs for explaining
-----Ursprungliche Nachricht-----
Von: Andrew Raibeck [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 21. Marz 2002 17:39
An: [EMAIL PROTECTED]
Betreff: Re: W2000 client passwords
OK, you are running in a clustered environment... that is a clue (this is
why it is usually important to specify your particular environment).
Do you have multiple options files configured, one for cluster resources,
and another for non-clustered (local) disks? If so, are you also using
distinct node names for each? You can not use the same node name to back
up cluster resources as you use for local disks. The TSM client password
encryption uses the local machine name to encrypt the password for the
node that backs up the machine's local disks, while the cluster name is
used to encrypt the password for the node that backs up the cluster
resources. Thus if you use the client to back up local disks, then try to
use the same node name to back up cluster resources, the passwords won't
match.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Weeks, Debbie" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
03/21/2002 09:22
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: W2000 client passwords
Using this command appeared to start the service, but it never prompted
for
a password for the node. Of course, it is using the wrong options file,
but
I had the cluster node specified in the default opt file anyway. The
regular service for this node still won't start though.
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 11:15 AM
To: [EMAIL PROTECTED]
Subject: Re: W2000 client passwords
What client version are you using? There was a bug in dsmcutil at the
4.2.0
base level, as I recall.
Try updating the pw this way:
open a DOS window
CD to TSM baclient directory
type: dsmc sched
That should start the scheduler, and prompt for the password. You will
connect and get a scheduled start time. Then just kill the window.
Then repeat the same thing; the second time, it should NOT prompt for the
password, if it got saved correctly the first time.
-----Original Message-----
From: Weeks, Debbie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 11:09 AM
To: [EMAIL PROTECTED]
Subject: Re: W2000 client passwords
I had used the updatepw function. Showpw is telling me that there is no
password in the registry for that node. One of the servers having this
problem is actually a cluster node. Showpw shows a password for the
clustered servers, but not for any of the cluster group nodes. I will
have
to contact the admin of the other W2K server to have him try the command
on
that server.
-----Original Message-----
From: Ochs, Duane [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 10:45 AM
To: [EMAIL PROTECTED]
Subject: Re: W2000 client passwords
When you wrote that you tried dsmcutil, you mean you used dsmcutil showpw
/node:"nodename".
Also, verify that there is not a nodename specification in your DSM.opt
that
is different than what you are expecting.
-----Original Message-----
From: Weeks, Debbie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 9:19 AM
To: [EMAIL PROTECTED]
Subject: W2000 client passwords
I now have two W2K clients that cannot be backed up by automated backups
because somehow the password has become corrupted. I have done everything
I
can think of short of deleting or renaming the node in TSM. I have
deleted
the service, uninstalled the client software, edited the registry and
manually removed every key that I could find, and reset the password on
the
TSM server. I have changed the password to prompt instead of generate,
and
then set it to generate again, and I have tried dsmcutil. Nothing has
worked. The client GUI connects and works fine.
I can't find anything in the KB on Tivoli's site, so I thought I would try
the list. Does anyone know how I can fix this? That password must be
stored somewhere else that I haven't hit on yet.
Debbie Weeks
University of South Florida
Information Technologies/Technical Support
********
*[EMAIL PROTECTED]
*(813)974-6926*S/C 574-6926
Fax (813) 974-3054
