Kbase 15913: DECnet Pathworks v6 configuration for DOS and Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
DECnet Pathworks v6 configuration for DOS and Windows
INTRODUCTION:
=============
This Knowledge Base Entry explains how to configure DECnet Pathworks
V6 for DOS, Windows 3.1, Windows 3.11 and Windows 95.
DOS, WINDOWS 3.1 AND WFW:
===========================
Pathworks V6 for DOS, Windows 3.1 and WFW has the following problem:
Does not load the volatile database, and has the following limits
for REMOTE-ADAPTER-NAMES:
1) The maximum # of REMOTE-ADAPTER-NAMES by default is 3.
To know this maximum, do: NCP> SHOW EXECUTOR CHAR
2) The maximum # of REMOTE-ADAPTER-NAMES is 256.
3) The maximum # of REMOTE-ADAPTER-NAMES allowed in volatile
database is 64.
- - -
If the volatile database is not loaded there is no way to find the
REMOTE-ADAPTER-NAMES and the connection Client/Server is not
possible.
* How to load the volatile database ?
Create a .BAT file (e.g. volatile.bat). This file may contain the
following:
NCP SET REMOTE-ADAPTER-NAME PROSV NODE MYNODE
NCP SET REMOTE-ADAPTER-NAME PROSV1 NODE MYNODE
Include a call to this .BAT at the end of the TPL file (e.g. call
volatile.bat)
* After doing this, restart Pathworks and run:
NCP> SHOW REMOTE-ADAPTER-NAMES
If PROSV, PROSV1, ... appear in the listing, the connection should
work.
* How to increase the maximum number of REMOTE-ADAPTER-NAMES in the
volatile database ?
Modify the .TPL file:
look for DNP in the last section of the TPL file you are using and
change:
DNP to DNP / REM:64
WINDOWS 95:
===========
If you have customers trying to get a connection from a PC running
Windows 95 over Pathworks for Windows 95, who are receiving the
error:
NETBIOS call to server <server> returns error 18. Retrying. (1998)
and/or
NETBIOS call to server <server> returns error 20. Retrying. (1998)
they need to contact their local Digital Service center and request
the file: DECDNP.VXD version 1.0.31 (or higher).
The problem is due to Windows 95/Pathworks for Windows 95 being
written for 32 bit. What is happening is that they are sending the
padding characters at the end of the hex value generated when you
define the REMOTE-ADAPTER-NAMES. We cannot work with these as we
use 16bit NetBIOS calls.
Pathworks settings for Windows 95:
1) The maximum # of REMOTE-ADAPTER-NAMES by default is 3.
To know this maximum do: NCP> SHOW EXECUTOR CHAR
2) The maximum # of REMOTE-ADAPTER-NAMES is 256.
3) The maximum # of REMOTE-ADAPTER-NAMES allowed in volatile
database is 64.
* How to increase the number of maximum REMOTE-ADAPTER-NAMES in the
volatile database ?
NCP> DEFINE EXECUTOR REMOTE 64
After this you need to restart Pathworks.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
Kb entitled: "How to connect PC with DECNet DOS pathworks -
Configuration"
Pathworks for DOS and Windows, version 6. Client installation and
configuration guide.
Progress' Networks Guide.
Progress Software Technical Support Note # 15913