HP OpenVMS Systems

PATHWORKS DECnet Client Configuration?

» close window

The Question is:

 
I need to regularly send files from VMS to WinNT 4.0 machine via DECnet (by VMS
 COPY command). NT machine has Pathworks32 7.2 client, DECnet installed. VMS
 machine has DECnet Phase IV, it is NOT running Pathworks server but I think
 it's irrelevant. I defi
ned DECnet name and address of NT machine in VMS's NCP node database and vice
 versa. I also defined
object 17 (FAL) on NT machine. I've checked that Job Spawner service is started
 automatically. I've set up access rights on NT node(NCP DEFINE ACCESS DEFAULT
 ALL). However, every time I try to do "$ COPY FILE.TXT NTNODE::" , I get the
 message:
 
"-SYSTEM-F-UNREACHABLE, remote node is not currently reachable"
 
To test DECnet on NT, I ran NFT and eXcursion via DECnet and connected to this
 VMS node, everything worked perfectly. I can also do NCP LOOP NODE from NT
 machine to VMS (but not vice versa), it's also fine.
 
I also tried "User Manager" on that NT node to enable even more access to this
 machine. I went "Policies" -> "User Rights" menu, enabled checkbox "Show
 advanced user rights" and modified firstly "Access this computer from
network", then "Log on as batch job" - in both cases I added "Everyone" to the
 list of allowed users and groups. The error message remains
same. What's wrong? Why NT remains unreachable from VMS while VMS is perfectly
 reachable from NT? I need this file copy to be started from VMS side...
 

The Answer is :

 
  This might be as simple as having DEFINEd the client system DECnet
  nodename in NCP, but has not SET it and has not rebooted since the
  name was DEFINEd.
 
  Consider using an NCP LOOP NODE nn.nnn command from OpenVMS to the
  target system.
 
  Failing this, please contact the Compaq Customer Support Center, as
  additional investigations and additional details will be required.

  

     

     
answer written or last revised on ( 5-JAN-2001 )
     
» close window