| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2604.1 | Can you do an NCP TELL? | FOUR62::LICAUSE | Al Licause (338-5661) | Thu Mar 26 1992 16:31 | 14 |
| I'm no expert, but I believe MCC tries to do some sort of NCP TELL command
or the equivalent.
It looks as though the error is telling you that you have no privelage to
display information on that node. What happens if you try to issue an
NCP TELL command to that node?
If it fails, you probably either need to specify access control when
registering or that node needs to have either proxy or a default account
setup.
Hope this helps.
Al
|
| 2604.2 | Should be a bug on ,address. | STRASB::EBLE | Fran�ois EBLE. EIS Strasbourg France. | Tue Mar 31 1992 12:34 | 33 |
| Hi,
>I'm no expert, but I believe MCC tries to do some sort of NCP TELL command
>or the equivalent.
I don't think so because it is only a local problem. I mean this
command should update the local NCP database on my node where I am
logged as root. So ???
>It looks as though the error is telling you that you have no privelage to
>display information on that node. What happens if you try to issue an
>NCP TELL command to that node?
No, It looks like a bug on the address qualifier ... If I do not put
this qualifier, registering is successfull.
NCP TELL command works.
>If it fails, you probably either need to specify access control when
>registering or that node needs to have either proxy or a default account
>setup.
No. It is a purely local problem. I try to specify the local username
root and password, but it does not change the problem.
I think it is the only way to insure a consistance between DECmcc node4
and NCP local database.
Is this problem already QARed or fixed ?
Help please.
|
| 2604.3 | Still there in 1.2.7 | STRASB::EBLE | Fran�ois EBLE. EIS Strasbourg France. | Wed May 13 1992 07:25 | 4 |
| This reply to say that under Version 1.2.7 I have still the same
problem described in .0
I will QAR it.
|
| 2604.4 | set up proxy | TOOK::S_KO | Hoot mon! | Tue May 19 1992 20:33 | 29 |
|
hello Fran�ois,
In order to register NODE4 entities in DECmcc (on a DEcnet Phase IV
ULTRIX system) and also add the node to your local NCP database, you
must log in as root and have decnet proxy setup for root to itself.
To setup decnet proxy for root, edit the /etc/dnet_proxy file and
add an entry for:
source::root root nml
where source is the local node name. i found you had to be actually
logged in as root - not as super user from a non-privileged account.
The reason the BY USER and BY PASSWORD qualifiers did not
help is because these qualifiers are applied to the node you
are registering NOT to the node you are operating on. For
example, if you are running DECmcc on node xyz and
registering node4 abc, the user and password qualifiers
are used to query node4 abc.
If the node is already in your NCP database, you can omit the address
argument.
Hope this is helpful.
-s
|
| 2604.5 | Can set up proxy for other accounts if you want | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Tue May 19 1992 23:43 | 9 |
| > where source is the local node name. i found you had to be actually
> logged in as root - not as super user from a non-privileged account.
I assume you mean that "sudo" did not work. That is because the DECnet
proxy mechanism works off the account that you used when you logged in.
It is perfectly possible (although dangerous from a security point of view)
to set up a proxy from any account on the system to root.
|