From: dragon@NSCVAX.PRINCETON.EDU (Mighty Firebreather)
Newsgroups: comp.os.vms
Subject: RE: Invalid Login Information questoin (SAK 92_13)
Date: 4 Sep 92 13:56:12 GMT
Organization: The Internet


	Sal Kabalani <SK0001@ACAD.DRAKE.EDU> writes:
>
>   In March of 91, we upgraded VMS from 5.2 to 5.4-2, and our VAX hardware to
>   the setup shown below. here is our current setup:
>
<irrelevant configuration info omitted>
>
>      Since the upgrade, we have experience some strange phenomena. I am
>      listing them below. Can anyone help me diagnose and rememdy the
>      situation ? Thank you all in advance.
>
>   1- MAIL from KIRK to SPOCK and SPOCK to KIRK no longer displays receipt
>      notification at the terminal.
>
>   2- MAIL to SPOCK::USER from KIRK, or KIRK::USER from SPOCK no longer works.
>      It returns the errors:
>      "%MAIL-E-LOGLINK, error creating network link to node KIRK",
>      "-SYSTEM-F-INVLOGIN, login information invalid at remode node".
>
>   3- PHONE from SPOCK to KIRK and KIRK to SPOCK no longer works. Phoning
>      KIRK::USER from spock results in the "Establishing DECnet link..."
>      Message, the PHONE utility returns the error "login information invalid
>      at remode node"
>
>   4- The DCL command REPLY/USER does not ALWAYS display a message on the
>      user's terminal on KIRK on occasion. I was unable to detect a pattern of
>      success or failure for this oepration.
>
>   5- SHOW PROCESS/CONTINUOUS and SHOW PROCESS/ACCOUNTING no longer work if the
>      requestor process is on a different CPU than the target process.
>

	Problems 1, 2, and 3 are simply solved.  I'm assuming a VAX Cluster 
with a common UAF.  On any node in the cluster do:

$ SET PROCESS /PRIVILEGE=ALL
$ MCR NCP
NCP> SHOW OBJECT MAIL CHARACTERISTICS
 
 
Object Volatile Characteristics as of  4-SEP-1992 09:43:58
 
Object = MAIL
 
Number                   = 27
File id                  = MAIL_SERVER.EXE
User id                  = MAIL$SERVER
Password                 = GOBBLEDEGOOK
Proxy access             = outgoing
Alias outgoing           = Enabled

 
NCP> EXIT
$ MCR AUTHORIZE
UAF> MODIFY MAIL$SERVER /PASSWORD=GOBBLEDEGOOK
UAF> EXIT

	Now, for *EACH* other node on the cluster do:
$ MCR NCP
NCP> SET OBJECT MAIL PASSWORD GOBBLEDEGOOK
NCP> DEFINE OBJECT MAIL PASSWORD GOBBLEDEGOOK
NCP> EXIT

	This should take care of problems 1, and 2.  For problem 3, repeat 
the above, substituting PHONE and PHONE$SERVER where appropriate.

	This problem arises when the upgrade runs NETCONFIG.COM on each 
node and sets new passwords for all the DECNet objects.  Only the last 
password gets saved in the UAF.  You probably have the same problem with 
any other DECnet objects you have.

*************************************************************************
*                                                                       *
*                        Here, there be dragons!                        *
*                      dragon@nscvax.princeton.edu                      *
*                                                                       *
*                                                Richard B. Gilbert     *
*************************************************************************