NCP no go

[SCC_2]

Hello All,
We have a Micro VAx 3100 vms v5.5-2 running here with Pathwork 32 Version 7.2 link to a PC server for us to transfer TxT file. We set the NCP as following
NCP-set-node-all2-1.2-all2 and this like/comment working great for years.
Now we have another PC server hook up almost the same way at NCP-set-node-all5-1.5 and we can't get it going. On the PC side we can see the file from Vax directory. But on the Vax side there is an error message as following.

%direct-e-openin, error opening all5"Vax password"::d:[Vax]*.*;* as input
-rms-e-fnd, acp file or directory lookup failed
-system-f-unreachable, remote node is not currently reachable.

Thanks !
S.C

[Volker Halle]

S.C,

this error message indicates, that the VAX does not a routing path to node ALL5.

On the VAX, try:

$MC NCP SHOW NODE all5
$MC NCP SHOW NODE 1.2

On the PC, try:

NCP SHOW EXE
NCP SHOW KNO CIRC
NCP SHOW NODE

Volker.

[Pluvier Danny]

pls add node to ncp

ncp>
def kn node xx.xx
set kn node xx.xx

exit

if you uses decnet

gr.

[SCC_2]

THanks for the reply, I have to wait till monday and pass this information to other guy to check on the pc side.

on Vax it show the following
$ ncp
ncp >show node all5
node state active delay circuit next node
link

1.5(all5) sva-0 0

ncp > show node 1.2

1.2 sva-0 0

ncp > show node all2

1.1 (all2) sva-0 0

THanks !
Sc

[Volker Halle · Accepted solution]

SC,

node ALL2 really has a DECnet address of 1.1 (as seen on the VAX). Your 'NCP-set-node-all2-1.2-all2' reference seems to imply, that this node would be 1.2 ?!

Node ALL5 has a DECnet address of 1.5 (defined on the VAX). Maybe it has a different address defined on the PC ? Check with NCP SHO EXE on the PC on monday.

On the VAX, you could try $ DIR 5:: or DIR 4:: etc. If you get system-f-unreachable, a node with this DECnet address is not actively running DECnet at the moment. If you get some other error message (e.g INVLOGIN), the node is up and running, you just need to specify a correct username and password.

Volker.

[SCC_2]

Thanks will check on monday
Sc

[SCC_2]

Sorry mistake on prev. question
The ncp was set at 1.1 all2 not 1.2 all2 to begin with and working fine.

set ncp 1.5 all5 no go, the pc can see the directory from Vax, but Vax can't get in and error message as prev.

Thanks you for the help. I will check it out on monday.

THanks !
Sc

[SCC_2]

Hello All,
Is Monday, We check the pc side was set at all5 1.5 and also the Vax.
when we test the command :
Dir all5"vax password"::d:[vax]*
The error come back as following

%direct-e-openin, error opening all5"vax password"::d:[vax]*.*;* as input
-rms=e=fnd, acp file or directory lookup failed
-system-f-invlogin, login information invalid at remore node.

Thanks !
SC

[Uwe Zessin]

The system can now talk to the remote node, but the user authentication failed. You might have used a wrong password, but it could be another reason.

[Volker Halle]

SC,

do you recognize the difference ?! Now the underlying system service status is:

system-f-invlogin !

You now have been able to successfully establish a DECnet connection to the PC (node ALL5), but you did not have the correct username/password specified.

OpenVMS is usually VERY GOOD at providing error messages.

Volker.

[Jan van den Ende]

... and "Login Information Invalid" can have several reasons.

Let your VMS System manager (if it is not you) log in to VMS and enable SECURITY privilege and
$ REPLY/ENABLE

Now try again.

Possible messages for the system manager:

- Breakin evasion in effect
- Invalid account name
- Invalid password
- You are not allowed to login from this source
(I am not sure this are all)

Now, you will know WHAT is wrong, and that is usually the biggest step in correcting it!

Success.

Proost.

Have one on me.

Jan

[SCC_2]

I am really run out of ideas how to get this going. I try all possible ways.
I check the ncp all5 1.5 is there. set to reply/enable. Ask the person who set up the pathwork, when he login into the Pc , he using the username name as Vax and password
are the same as my command. still getting the same error
-system-f-invlogin. I am very sure it got to be somewhere he/me setup wrong for usename and password.
Sc

[Jan van den Ende]

S.C.

What _IS_ the error _REPORTED BY THE VMS REPLY_ with Security priv active?

Proost.

Have one on me.

Jan

[SCC_2]

Hello,
I set it reply/enable and type the command
$dir all5"vax password"::d:[vax]*
same error system-f-invlogin

[Volker Halle]

S.C, Jan,

the INVLOGIN error is reported from the PC (or to be more exact, by the DECnet node with address 1.5). Don't waste your time looking for login failure etc. on the VAX.

I'm not familiar enough with Pathworks 32 DECnet to immediately tell you, WHERE to check or SET a valid username/password on the PC.

You can easily confirm that I'm right, if you temporarily disconnect the PC from the network and retry your DIR command, you should then get UNREACHABLE again !

Volker.

[Bojan Nemec]

S.C,

On the PC (for Windows >= 4.0) you must grant a "privilege to log on as a batch job" to all users which are used to copy from VMS to PC.
Check the documentation on the Pathworks 32 CD (Using the Job Spawner in the Users Guide).

Bojan

[SCC_2]

Thanks to all of you helping me out. The problem is fix. The guy who setup on the Pc side is not right/or missing a command
"privilege to log on as a batch job" to all users which are used to copy from VMS to PC.
Now is running find.
Thanks again
Sc