ADSM-L

Re: Authentication error

2003-10-16 10:34:21
Subject: Re: Authentication error
From: "Brian L. Nick" <BRIAN.NICK AT PHOENIXWM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 16 Oct 2003 10:29:41 -0400
Bill,

 You can still ask IBM/Tivoli questions regarding TDP 1.1. If the issues is
a know problem they will support you. We just upgraded our TDP 1.1 server
to TDP 5.1 and IBM/Tivoli did support questions for us, they won't research
new problems in TDP 1.1.

 The password command you are looking for needs to be executed from the
baclient directory. The command is 'dsmcutil showpw /node:yournodename'

 Hope that this helps.

 - Brian


Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  Brian.Nick AT phoenixwm DOT com
PHONE:   (860)403-2281



                      "William Rosette"
                      <Bill_Rosette@PAP         To:       ADSM-L AT VM.MARIST 
DOT EDU
                      AJOHNS.COM>               cc:
                      Sent by: "ADSM:           Subject:  Re: Authentication
error
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>
                      10/16/2003 10:03
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"




Here is the problem.  I had to load 1.1 TDP Lotus Domino, because I am
awaiting the approval of upper management to approve the IBM maintenance so
that I can get the CD with the new license and new 5.2 Domino.  The client
is Win2000 which shouldn't be a problem since I have 1.1 working on other
Win2000 clients.  Since I have 1.1, I also have no support (can't call
IBM/Tivoli).  The Authentication error seems to be from the previous
passwordaccess generate.  My thinking is that the stored password is
incorrect and I need to reset it somehow.  I did have a command that ran in
baclient that would display the current passwordaccess generate password,
but can not find as of now.  I also removed the service to see if that
would work to no avail.  My next step will probably be an uninstall and
reinstall, (hopefully the uninstall will clear the password generate).
Another question would be is, I have 2 client nodes on the same client.  1
is doing the normal (nondatabase) stuff, and 2. the Domino one is suppose
to do the Domino only.  Both have dsm.opt files (in separate directories
(baclient & domino)) with passwordaccess generate, is this an issue?

Thank You,
Bill Rosette
Data Center/IS/Papa Johns International
WWJD



                      rbs AT bu DOT edu
                                               To:
Bill_Rosette AT PAPAJOHNS DOT COM
                      10/16/2003 09:37         cc:
                      AM                       Subject:  Re: Authentication
error






>Thanks Del, I tried but same error message.  I had been trying domdsmc q
>adsm -adsmpwd=password and getting the same error.  I even tried
>capitalization and still no effect (never know)

Bill - I've seen keyboard problems be the issue with password rejections.
       Often times, passwords use chars which are not normally used in
every day typing.  Using a text editor or the like, enter your password
and see if it appears as it should.  Watch out for "dead keys" or keys
which generate multiples when pressed once.  You may find a piece of
pizza gumming up the works.  :-)

   Richard







***********************************************************************************
CONFIDENTIAL: This communication, including attachments, is intended only for
the exclusive use of addressee and may contain proprietary, confidential
and/or privileged information.  If you are not the intended recipient, you are
hereby notified that you have received this document in error, and any use,
review, copying, disclosure, dissemination or distribution is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately by return e-mail, delete this communication and destroy any and
all copies of this communication.

***********************************************************************************

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