Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Pathworks 32 V7.0 and VMS 5.5 and Pathworks Server V5

Jim_309
Occasional Visitor

Pathworks 32 V7.0 and VMS 5.5 and Pathworks Server V5

Hi,

I have a Vaxstation 4000-60 running VMS 5.5-2H4 and Pathworks Server for Lan Manager v5.

I also have a PC running Windows NT4 SP6a and Pathworks 32 V7.0.

I am trying to set up the above configuration such that the Vaxstation can share out data which the PC can access via a network share over Decnet.

The PC has both TCP/IP and Decnet but the Vaxstation does not have TCP/IP.

I have two Pathworks related license PAKs which are loaded on the Vax :-

PWXXWINAT07.00 and PWLMDOSCC05.00

And I am running the Pathworks license server on the Vax.

However when I attempt to connect to a Pathworks share on the Vax I receive the following messages on the PC :-

(1) Connection attempt denied; JMTEST (vaxstation name) failed to authenticate a license for BE200618 (PC name in NT NOT Decnet node name which is JMPC1)

(2) No more connections can be made to this remote computer at this time because there are already as many connections as this computer can accept.

Also the pathworks (client pc) event logger reports the following message twice each time I try to map to the VAx share :-

PNLT003N License "DEC-PWXXWINAT07.00" presented to server "JMTESTR01"

Can anyone cast some light on the cause of my problem ?

Thanks in advance,

Jim

3 REPLIES
faris_3
Valued Contributor

Re: Pathworks 32 V7.0 and VMS 5.5 and Pathworks Server V5

Hi,

-Are you requesting the PWLMDOSCC05.00
in the client's licence requestor ?

(it is needed to connect to shares)

- also check on the server by the license manager that your license points are not allocated to other clients.


- you should check that you are running
V5.0F ECO 2

hth
HF
Jim_309
Occasional Visitor

Re: Pathworks 32 V7.0 and VMS 5.5 and Pathworks Server V5

Hi Faris,

Thanks for the reply.

"-Are you requesting the PWLMDOSCC05.00
in the client's licence requestor ?"

I don't know - how do I check on the Client ?

Thanks again,

Jim
Antoniov.
Honored Contributor

Re: Pathworks 32 V7.0 and VMS 5.5 and Pathworks Server V5

Jim,
the license manager of V5 is SYS$SYSTEM:PWRK$LICENSE_MANAGER.EXE and you could activate it with follow commands:
$ ADMLICENSE="$PWRK$LICENSE_MANAGER"
$ ADMLICENSE
I think you have enable manually client license manager on PC running PNLCG and then PNLR32 to acquire license.
If doesn't work, enable NetBios protocol on PC (property in MyNetwork) and on VAX typing ADMIN/CONFIG or @SYS$MANAGER:PWRK$CONFIG (may be @SYS$UPDATE:PWRK$CONFIG).

Good luck
Antonio Vigliotti
Antonio Maria Vigliotti