|
HP OpenVMS Systemsask the wizard |
|
The Question is: Hello, When trying to do a DIR from a VAX4000 (e.g. DIR 29.998::) to a PC with Pathworks 7.1 installed, I get the error message $ dir 29.998:: %DIRECT-E-OPENIN, error opening 29.998::*.*;* as input -RMS-E-FND, ACP file or directory lookup failed -SYSTEM-F-REJECT, connect to network object rejected also, doing $ mc ncp tell 29.998 sho exec %NCP-F-CONNEC, unable to connect to listener -SYSTEM-F-REJECT, connect to network object rejected I can log on to the VAX from the PC using Powerterm, and also using Patherworks FTP I can see the VAX from the PC Any ideas? The Answer is :
The OpenVMS Wizard would assume that there is no FAL server presently
available on the DECnet system at address 29.998 -- the usual numeric
address syntax does not include the ".".
In the case of DECnet on the PATHWORKS client -- and since the REJECT
error message is received for both the 'DIRECTORY' and 'NCP' commands
-- the behaviour reported would tend to indicate the PATHWORKS client
system (PC) has received the request, but was unable to service it.
When a DECnet service request arrives at a PATHWORKS client system,
the Network Job Spawner (SPAWN32.EXE) initially services the request,
passing control to FAL32 (for an incoming DIRECTORY) or NML (for an
incoming NCP command) to process the request -- the specific task is
determined based on the requested object name or the object number,
and the information stored in the object database (PWOBJ.DAT). When
the request arrives, the Network Job Spawner verifies user access via
the Windows NT access information or via the PWINACC.DAT file.
The Wizard would recommend confirming the specification of the
username and password, and would recommend the following chapters of
the PATHWORKS 32 User's Guide:
Chapter 11: Configuring Your DECnet Executor Node
Chapter 15: Using the Job Spawner
From the OpenVMS HELP/MESSAGE utility:
REJECT, connect to network object rejected
Facility: SYSTEM, System Services
Explanation: A request to connect to an object at a remote node failed for
one of the following reasons:
o The object requested does not exist.
o The access control information specified is invalid.
o The partner NSP has no resources.
o The partner task exited during the connect sequence.
o The partner task rejected the connect.
User Action: Determine which reason caused the failure and try to correct
the condition.
|