ADSM-L

Re: client direct login on 5.1.6.2 TSM

2003-06-09 10:52:14
Subject: Re: client direct login on 5.1.6.2 TSM
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 9 Jun 2003 07:51:45 -0700
Joni, from an Admin CLI, issue this command:

   query status

And look at the line for "Authentication". Does it say "On" or "Off" ? If
it is off, then somehow authentication was disabled on your server. Use
the command

   set authentication on

to re-enable authentication.

If that is not the problem, then try this test:

1) Register a new test node on your TSM server, i.e.:

   register node jonitest xxxxx

(xxxxx is the password for node jonitest.)

2) From your workstation (presumably you have a workstation, and have TSM
installed on it!   :-), create a new options file named dsm.opt.jonitest
like this:

   commmethod tcpip
   tcpserveraddress your.tsm.server.address
   tcpport nnnn
   nodename jonitest

Note: tcpport is needed only if your TSM server uses a port other than the
default of 1500.

3) Run a TSM command from an OS prompt and see whether you are prompted
for a password:

   dsmc query session -optfile=dsm.opt.jonitest

Are you prompted for a password? If so, then the clients who are not
prompted for passwords are almost certainly using passwordaccess generate.

Note that the client scheduler service on Windows will use passwordaccess
generate regardless of whether you explicitly put it in dsm.opt.

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.




Joni Moyer <joni.moyer AT HIGHMARK DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/09/2003 07:36
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: client direct login on 5.1.6.2 TSM



Mark,

I am not very familiar with the client side of TSM, but the user told me
that the passwordaccess generate wasn't enabled.  Is there any other way
that it would generate the password?  Is there a parameter on the TSM
server that would override this parameter?  Thanks again!

(This occurred at the client 4.1.5 level and the 5.1.5 level.)

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338



                      "Stapleton, Mark"
                      <stapleto@BERBEE.        To: ADSM-L AT VM.MARIST DOT EDU
                      COM>                     cc:
                      Sent by: "ADSM:          Subject:  Re: client direct
login on 5.1.6.2 TSM
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      06/09/2003 10:07
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






From: Joni Moyer [mailto:joni.moyer AT HIGHMARK DOT COM]
I have a TSM server 5.1.6.2 on os/390 2.10 and users backup their PC's to
TSM.  Previously they were asked for a userid and password to access TSM
for restores, backups, etc.  but now when they go to do this it is
directly
connecting to the TSM server.  I have recently upgraded this server from
4.1.5 to 5.1.6.2, but we are using an exact copy of the opt file for the
tsm server.  Does anyone have any ideas/suggestions as to why this may be
occurring?  Thanks!

The line

passwordaccess generate

in the dsm.opt file allows the TSM client to store an encrypted copy of
their TSM password in the Windows registry. That's why they don't have to
authenticate.

<Prev in Thread] Current Thread [Next in Thread>