[3742] in testers
re: Another Problems with 8.2
daemon@ATHENA.MIT.EDU (oliver thomas)
Thu Jul 9 16:45:21 1998
To: "Roger A. Roach" <rar@MIT.EDU>
Cc: oliver thomas <othomas@MIT.EDU>, testers@MIT.EDU, alexp@MIT.EDU
Reply-To: oliver thomas <othomas@MIT.EDU>
In-Reply-To: your message of Thu, 09 Jul 1998 16:27:53 -0400.
<199807092027.QAA00975@rar.mit.edu>
Date: Thu, 09 Jul 1998 16:45:15 EDT
From: oliver thomas <othomas@MIT.EDU>
hi roger,
> I tried to use ADSM to backup my workstation. I had User Accounts change my
> machine name from "rar" to "rar.mit.edu" per the directions I got. However,
> when I tried to run ADSM, I got an authenication failure. When I called the
> helpdesk, they checked the log and it was a bad password. Since this should
> be using my Kerberos ticket, it sounds very much like my problem with inc.
actually, adsm on athena stores the password encrypted in a local file
(/etc/adsm/SERVER_A) and generates a new password automatically every 90
days. it does not use kerberos authentication. i'm guessing that the old
password you have stored in that file doesn't work with the new nodename.
if this is true, a migration path for adsm from 8.1 to 8.2 that should
work would be:
1. notify the helpdesk to update the hostname to a fully qualified
one.
2. ask the helpdesk to reset the adsm password for that node name
to something known.
4. remove the encrypted password file from the /etc/adsm directory
3. run the setpass command out of the adsm locker again to change
the password and have the password stored in /etc/adsm/SERVER_A
the adsm client should work again after that. this is my best guess based
on the things i've heard about adsm on athena. i haven't actually tried
this myself. alexp might have more info on this. he set up the password
scripts in the adsm locker.
oliver
