| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2281.1 | You probably need a password | TOOK::MINTZ | Erik Mintz, DECmcc Development | Thu Feb 06 1992 09:58 | 8 |
| This implies that someone has tried to connect to a password protected
task object, without the correct password.
If the task object on the system you are trying to reach has a password
on the task object, you will have to specify by user, by password
for any MCC command that attempts to use that task.
-- Erik
|
| 2281.2 | Or proxy access. (better) | TOOK::MCPHERSON | Scientific progress goes 'Boink!' | Thu Feb 06 1992 10:20 | 2 |
|
|
| 2281.3 | appears during booting | ZUR01::SCHNEIDERR | | Thu Feb 20 1992 04:51 | 9 |
| Hello,
This message happens during booting of the DECmcc machine. I think there is a
synchronisationproblem. (Refer to .0)
After MCC_DNA4_EVL is proper working. Maybe some of you have seen this, too.
Roland
|
| 2281.4 | same results but due to priv problems | TOOK::CALLANDER | MCC = My Constant Companion | Thu Feb 20 1992 19:26 | 4 |
| I have seen similar problems when attempting to start the dna evl
process from an account without the required system privs, note
these must be default privs and not setpriv.
|
| 2281.5 | List of things to check to prevent 'Login info invalid' | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Mon Feb 24 1992 00:27 | 24 |
| Here are a few things to check in order to ensure that you do not get a
"Login information invalid at remote node" error message.
1. $ MCR AUTHORIZE SHOW DECNET ! to be sure you have a DECNET account
2. $ SET PROCESS/PRIV=BYPASS ! to be able to see passwords in NCP
$ MCR NCP SHOW EXEC CHAR ! Look for DECNET non-priv account,
! user, and password.
3. $ MCR AUTHORIZE MOD DECNET/PASS=same_as_in_ncp_above
4. $ MCR NCP SHOW KNOWN OBJECT ! If the NML object has a username and
! password associated with it, you
! will get the INVLOGIN error unless
! they match the account from which
! you are trying to gain access. To
! verify this, you can CLEAR them and
! test to see if you can avoid the
! error, then put them back correctly.
5. $ MCR AUTHORIZE SHOW/PROXY * ! Check to make sure you have proxy
! access.
Note: All of the above should be checked on the node from which you
wish to get network information, be it the remote or local node.
-Dan
|