

System Messages  219

a p p e n d i x

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993

  A System Messages

This chapter includes system messages and explanations for all
NetWare  Requester v2.01 drivers and daemons. Messages for the
NetWare Tools or the  Network Printer (NPRINTER.EXE) programs are
not included. For  information about messages for those modules,
see System Messages.

REQ0106: An error occurred during attempt to get shared memory.
Explanation DD AEMON.EXE attempted to access the daemon's shared
memory, but  failed. At this point, the program has verified that
the shared memory exists,  but is unable to access it. This may be
an internal program error.  Action Try rebooting your system. If
the problem persists, call your Novell  Authorized Reseller.

REQ0107: An error occurred during attempt to allocate a shared
segment.  Explanation DD AEMON.EXE tried to create shared memory,
but none is available. This  error usually occurs when the device
drivers and applications currently running  on your system require
more memory than your system has available.  Action Try adding
RAM, reducing your configuration options in the CONFIG.SYS  file
(for example, reducing the size of DIRCACHE), removing optional
device  drivers from the CONFIG.SYS file, and freeing up some hard
disk space by  deleting unnecessary programs. If you are using
multiple disk partitions,  consider moving the OS/2 swapper file
to a larger partition. Disk compression  utilities may also be
available that can help resolve this problem. After  completing
these actions, shut down OS/2; then reboot the system. If the
problem persists, contact your Novell Authorized Reseller.

REQ0108: The daemon cannot access the Link Support Layer. Error:
<code>.  Explanation DD AEMON.EXE cannot find the Link Support
device driver LSL.SYS.  Action Make sure that the device driver
LSL.SYS has been properly entered in the  CONFIG.SYS file. If so,
check the messages displayed by the LSL for any


220 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



errors or warnings, and correct the problems indicated. Try again.
If this error  persists, call your Novell Authorized Reseller.

REQ0109: The DDAEMON is already loaded.  Explanation DD AEMON.EXE
tried to create shared memory for the first time, but the  memory
already exists. Another daemon is already running. The attempt to
create shared memory is terminated.  Action Make sure that you are
not trying to run multiple copies of the daemon.  Typically the
daemon is run from the CONFIG.SYS file at system startup and  does
not need to be executed again.

REQ0204: The system does not have enough memory for socket tables.
Explanation OS/2 lacks sufficient system memory for IPX to
allocate memory for its socket  tables.  Action Try adding RAM,
reducing your configuration options in the CONFIG.SYS  file (for
example, reducing the size of DIRCACHE), removing optional device
drivers from the CONFIG.SYS file, and freeing up some hard disk
space by  deleting unnecessary programs. If you are using multiple
disk partitions,  consider moving the OS/2 swapper file to a
larger partition. Disk compression  utilities may also be
available that can help resolve this problem. After  completing
these actions, shut down OS/2; then reboot the system. If the
problem persists, contact your Novell Authorized Reseller.

REQ0205: The LAN support module could not be installed.
Explanation Either the LSL.SYS driver failed to load, or the
"DEVICE=" statement is  missing from the CONFIG.SYS file. Action
Either correct the problem that kept the LSL.SYS driver from
loading  (indicated in an error message preceding this one), or
add the "DEVICE="  statement to the CONFIG.SYS file.

REQ0206: The IPX MLID could not be installed.  Explanation Either
the Multiple Link Interface Driver (MLID) specified in the
CONFIG.SYS failed to load, or the "DEVICE=" statement for an MLID
is  missing from the CONFIG.SYS file.  Action Either correct the
problem that kept the MLID from loading (indicated in an  error
message preceding this one), or add the "DEVICE=" statement to the
CONFIG.SYS file.


System Messages  221

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0207: The configured LAN-A driver does not support IPX.
Explanation The Multiple Link Interface Driver (MLID) to which
IPX.SYS attempted to  bind does not support IPX-based data
transmissions.  Action Bind IPX to an MLID that supports IPX-based
data transmissions.

REQ0208: The IPX protocol handler cannot be registered.
Explanation IPX cannot register with the LSL.SYS driver because
the LSL is servicing its  maximum number of protocol stacks.
Action Remove the "DEVICE=" statements for any unnecessary
protocol stacks from  the CONFIG.SYS file.

REQ0209: The IPX entry point cannot be initialized.  Explanation
The IPX and link support layer (LSL) versions may not be
compatible  versions. Action Make sure that the IPX.SYS driver and
LSL.SYS driver are compatible. If they  are not, obtain compatible
drivers from your Novell Authorized Reseller. If this  is not the
problem, contact your Novell Authorized Reseller for customer
assistance.

REQ0210: An internal error occurred. The IPX router socket cannot
be opened.  Explanation IPX was unable to open the router socket
due to an internal program error.  Action Try again. If the
problem persists, contact your Novell Authorized Reseller.

REQ0211: An internal error occurred. A router selector cannot be
allocated.  Explanation IPX was unable to allocate an OS/2 router
selector due to an internal program  error.  Action Try again. If
the problem persists, contact your Novell Authorized Reseller.

REQ0212: The system has insufficient memory to allocate a router.
Explanation OS/2 cannot access sufficient system memory for IPX
routing purposes.  Action Try adding RAM, reducing your
configuration options in the CONFIG.SYS  file (for example,
reducing the size of DIRCACHE), removing optional device  drivers
from the CONFIG.SYS file, and freeing up some hard disk space by
deleting unnecessary programs. If you are using multiple disk
partitions,  consider moving the OS/2 swapper file to a larger
partition. Disk compression


222 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



utilities may also be available that can help resolve this
problem. After  completing these actions, shut down OS/2; then
reboot the system. If the  problem persists, contact your Novell
Authorized Reseller.

REQ0213: Router memory is exhausted.  Explanation IPX did not have
enough memory previously allocated for routing purposes.  Action
Increase the size of the IPX router memory in the NET.CFG "ROUTER
MEM"  statement.

REQ0214: An internal error prevented CGroup variable
initialization.  Explanation An internal program error has
occurred. IPX was unable to initialize internal  variables.
Action Try again. If the problem persists, contact your Novell
Authorized Reseller.

REQ0215: An internal error prevented DosHlp variable
initialization.  Explanation OS/2 internal variables were either
incomplete or invalid.  Action Try again. If the problem persists,
contact your Novell Authorized Reseller.

REQ0216: IPX cannot register with OS/2 for PDD-to-VDD
communications.  Explanation This is an internal program error.
IPX cannot register with OS/2 for VIPX.SYS  driver support.
Action Try again. If the problem persists, contact your Novell
Authorized Reseller.

REQ0217: The IPX device driver is not running.  Explanation Either
IPX.SYS encountered a fatal error during system initialization, or
the  "DEVICE=[path]IPX.SYS" statement was missing from the
CONFIG.SYS  file. If the problem is a fatal error, another message
should precede this one that  identifies the specific error that
occurred. Action Either resolve the fatal problem (indicated in a
preceding message), or add the  "DEVICE=" statement to the
CONFIG.SYS file; then try again. If the problem  persists, contact
your Novell Authorized Reseller.

REQ0231: The default protocol configuration option is not used for
IPX.  Explanation IPX cannot be configured as a default protocol
stack.


System Messages  223

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



Action Remove this option statement from the NET.CFG file.

REQ0232: The prescan protocol configuration option is not used for
IPX.  Explanation IPX cannot be configured as a prescan protocol
stack.  Action Remove this option statement from the NET.CFG file.

REQ0233: The OS/2 version number cannot be found; OS/2 v2.0 is
assumed.  Explanation IPX's query of OS/2 for the version number
returned a value that did not match  the value it expected to
receive.  Action Make sure the OS/2 version installed on the
machine is v2.0 or later.

REQ0304: An LSL error occurred. NET.CFG buffers are too big for
ECB pool. Explanation The configured buffer size for the Link
Support component is too large. Total  available buffer space is
around 60 KB, but the Link Support Layer (LSL) is  unable to
allocate even one buffer of the requested size in its buffer
space. See  "Link Support Layer" in Concepts for more information
about LSL. Action Reduce the Link Support component's buffer size
in the NET.CFG file. It is  more important to have several smaller
buffers available than one large one. It  is a waste of system
memory to configure buffers much larger than the  communications
media can support.

REQ0305: The Link Support module (LSL) could not install the AES
timer. Explanation The Link Support Layer (LSL) could not register
its timer handler with the  operating system because the maximum
number of handlers have already been  installed. This timer
handler is a critical component of the Requester, and none  of the
Novell-supplied communication handlers can be expected to work
properly without it. See "Link Support Layer" in Concepts for more
information about LSL. Action Previously installed device drivers
(those entered before LSL.SYS in the  CONFIG.SYS file) have used
all available timer resources. Identify those  device drivers and
either remove or reconfigure them. Since the Requestor's
communications handlers all use a common timer service in the LSL,
only one  available timer handler is required for proper
operation. If you are unable to  resolve this problem, contact
your Novell Authorized Reseller.


224 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0306: The Link Support module could not initialize its call
gate. Explanation The Link Support module could not register its
entry point with the operating  system. This entry point is vital
to most of the Requester's communications  components, and its
absence will cause them to fail. The most likely cause of  this
error is a previously loaded device driver that is using too many
kernel  resources.  Action Try removing application device drivers
installed before LSL.SYS in the  CONFIG.SYS file. It is highly
unlikely that a device driver from the OS/2 base  system has
caused this error. If the problem persists, contact your Novell
Authorized Reseller.

REQ0404: NetBIOS error occurred. Link Support module cannot be
installed.  Explanation NetBIOS could not open or communicate with
the Link Support LINKSUP_  device driver. This can happen if the
Link Support Layer (LSL) driver has not  been properly installed
or if you are using the wrong version of the driver. See  "Link
Support Layer" in Concepts for more information about LSL. Action
Make sure that the device driver LSL.SYS has been properly entered
in the  CONFIG.SYS file. If so, check the messages displayed by
the LSL for any  errors or warnings, and correct the problems
indicated. If the Link Support  device driver is initializing
properly, the problem is with incompatible versions  of the
software. NetBIOS and Link Support are usually installed together
from  a single installation diskette. Try reinstalling them. If
the problem persists,  contact your Novell Authorized Reseller.

REQ0405: NetBIOS error occurred. The IPX module is not installed.
Explanation NetBIOS could not open or communicate with the Link
Support LINKSUP_  device driver. This can happen if the Link
Support Layer (LSL) driver has not  been properly installed or if
you are using the wrong version of the driver. See  "Link Support
Layer" in Concepts for more information about LSL. Action Make
sure that the device driver LSL.SYS has been properly entered in
the  CONFIG.SYS file. If so, check the messages displayed by the
LSL for any  errors or warnings, and correct the problems
indicated. If the Link Support  device driver is initializing
properly, the problem is with incompatible versions  of the
software. NetBIOS and Link Support are usually installed together
from  a single installation diskette. Try reinstalling them. If
the problem persists,  contact your Novell Authorized Reseller.


System Messages  225

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0406: The NetBIOS call gate cannot be initialized.  Explanation
This is an internal program error.  Action Try again. If the
problem persists, contact your Novell Authorized Reseller.

REQ0407: NetBIOS error occurred. The program cannot initialize
local NCBs.  Explanation Insufficient memory is available for the
NCBs requested. Usually this error is  caused by incorrect
configuration information in the NET.CFG file. However,  the
underlying problem could also be a lack of global system resources
in the  OS/2 Global Descriptor Table.  Action Reduce the number of
commands in the NetBIOS section of the CONFIG.SYS  file. (The
default number of commands is 12; the maximum allowed is 25.) You
also might be able to reduce the number of node names (possible
range is 0- 126). Additional possibilities include adding RAM,
reducing your  configuration options (for example, reducing the
size of DIRCACHE) or  removing optional device drivers from the
CONFIG.SYS file, and freeing up  some hard disk space by deleting
unnecessary programs. If you are using  multiple disk partitions,
consider moving the OS/2 swapper file to a larger  partition. Disk
compression utilities may also be available that can help resolve
this problem. After completing these actions, shut down OS/2 and
then reboot  the system. If the problem persists, contact your
Novell Authorized Reseller.

REQ0408: NetBIOS emulator parameters are too large for the memory
pool.  Explanation Insufficient memory is available for all of the
control tables needed by the  NetBIOS emulator.  Action The amount
of table space available to the NetBIOS emulator cannot be
increased. The only way to solve this problem is to reduce the
number of  NetBIOS resources you are requesting. You can do this
by modifying the  NETBIOS parameters in the NET.CFG file. If the
problem persists, contact  your Novell Authorized Reseller.

REQ0409: Incompatible versions of OS/2 and NetBIOS are running.
Explanation You are attempting to run NetBIOS v2.01 on some
version of OS/2 earlier than  OS/2 v2.0.  Action Either install
OS/2 v2.0 to run with NetBIOS v2.01, or install a different
version of NetWare NetBIOS to match your OS/2 version.


226 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0504: The SPX module is not installed.  Explanation The
NMPIPE.SYS driver could not open or communicate with the SPX.SYS
driver.  Action Make sure that the SPX.SYS driver has been
properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated; then try again. If the  problem
persists, contact your Novell Authorized Reseller.

REQ0505: The IPX module is not installed.  Explanation NMPIPE.SYS
could not open or communicate with the IPX.SYS driver.  Action
Make sure that the IPX.SYS driver has been properly entered in the
CONFIG.SYS file. If so, check the messages displayed by the driver
for any  errors or warnings, and correct the problems indicated;
then try again. If the  problem persists, contact your Novell
Authorized Reseller.

REQ0519: An incorrect OS/2 version is being used.  Explanation
Either the DosGetVersion call failed (an internal program error),
or the OS/2  version currently running is not v2.0 or later.
Action Make sure the client OS and NMPIPE.SYS driver are
compatible versions. If  the problem persists, contact your Novell
Authorized Reseller.

REQ0520: The driver cannot register the PDD for VDD-to-PDD
communications.  Explanation NMPIPE.SYS could not register IPX as
a PDD so that PDD to VDD  communication may take place.  Action
Make sure the IPX.SYS driver has been properly entered in the
CONFIG.SYS  file. If so, check the messages displayed by the
driver for any errors or  w arnings, and correct the problems
indicated. Also make sure the OS/2 version  is v2.0 or later; then
try again. If the problem persists, contact your Novell
Authorized Reseller.

REQ0613: Invalid characters were specified in COMPUTERNAME.
Explanation The Named Pipes server name specified after
NPDAEMON.EXE is invalid.  Action Make sure the server name is not
more than 15 characters and is composed of  letters, numbers, and
these special characters: !#$%&()-.@^_`{}~


System Messages  227

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0614: An error occurred during attempt to initialize NPCALLS
.DLL.  Explanation The NPDaemon could not initialize NPCALLS.DLL.
Action Make sure the NPCALLS.DLL file in the NetWare Requester
directory is  included in the LIBPATH statement of the CONFIG.SYS
file. If you are  running Named Pipes, make sure the NMPIPE.SYS
driver and  NPSER VER.SYS are correctly configured in the
CONFIG.SYS file.

REQ0615: The Named Pipes daemon could not be registered. Error:
<code>.  Explanation The NPDaemon could not open or communicate
with the NMPIPE.SYS driver.  Action Make sure the NMPIPE.SYS
driver has been properly entered in the  CONFIG.SYS file. If so,
check the messages displayed by the driver for any  errors or
warnings, and correct the problems. Try again. If the problem
persists,  contact your Novell Authorized Reseller.

REQ0616: An error occurred during attempt to allocate shared
memory.  Explanation The NPDaemon could not allocate shared
memory.  Action Try adding RAM, reducing your configuration
options in the CONFIG.SYS  file (for example, reducing the size of
DIRCACHE), removing optional device  drivers from the CONFIG.SYS
file, and freeing up some hard disk space by  deleting unnecessary
programs. If you are using multiple disk partitions,  consider
moving the OS/2 swapper file to a larger partition. Disk
compression  utilities may also be available that can help resolve
this problem. After  completing these actions, shut down OS/2;
then reboot the system. If the  problem persists, contact your
Novell Authorized Reseller.

REQ0617: An error occurred during attempt to allocate the ECB
pool.  Explanation The NPDaemon could not allocate memory for the
ECB pool.  Action Try adding RAM, reducing your configuration
options in the CONFIG.SYS  file (for example, reducing the size of
DIRCACHE), removing optional device  drivers from the CONFIG.SYS
file, and freeing up some hard disk space by  deleting unnecessary
programs. If you are using multiple disk partitions,  consider
moving the OS/2 swapper file to a larger partition. Disk
compression  utilities may also be available that can help resolve
this problem. After  completing these actions, shut down OS/2;
then reboot the system. If the  problem persists, contact your
Novell Authorized Reseller.


228 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0618: An error occurred during attempt to create a system
semaphore.  Explanation A DosCreateSem call failed. An internal
program error may have occurred.  Action Try again. If the error
persists, contact your Novell Authorized Reseller.

REQ0619: An error occurred during attempt to create a thread.
Explanation A beginthread call failed. An internal program error
may have occurred. Action Try again. If the error persists,
contact your Novell Authorized Reseller.

REQ0620: A dynamic socket could not be opened. Error: <code>.
Explanation The NPDaemon failed to open a dynamic socket.  Action
Increase the socket count specified in the NET.CFG file; then
reboot the system  and try again. If the problem persists, contact
your Novell Authorized Reseller.

REQ0621: A well-known socket could not be opened. Error: <code>.
Explanation The NPDaemon could not open Netware's registered Named
Pipe socket; the  socket may already be in use.  Action Increase
the SPX socket count in the NET.CFG and shut down OS/2; then
reboot the system.

REQ0622: The NPDaemon cannot get the internet address. Error:
<code>.  Explanation An IpxGetInternetworkAddress call failed.
Action Make sure the IPX.SYS driver has been properly entered in
the CONFIG.SYS  file. If so, check the messages displayed by the
driver for any errors or  w arnings, and correct the problems
indicated. Also make sure the  IPXCALLS.DLL file is in the NetWare
Requester directory; then try again. If  the problem persists,
notify your Novell Authorized Reseller.

REQ0623: The NPDaemon cannot get the local target. Error: <code>.
Explanation An IpxGetLocalTarget call failed.  Action Make sure
the IPX.SYS driver has been properly entered in the CONFIG.SYS
file. If so, check the messages displayed by the driver for any
errors or  w arnings, and correct the problems indicated. Also
make sure the  IPXCALLS.DLL file is in the NetWare Requester
directory; then try again. If  the problem persists, contact your
Novell Authorized Reseller.


System Messages  229

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0624: The service advertising function failed. Error: <code>.
Explanation An IpxSend call to advertise this workstation as Named
Pipe Server failed.  Action Make sure the IPX.SYS driver has been
properly entered in the CONFIG.SYS  file. If so, check the
messages displayed by the driver for any errors or  w arnings, and
correct the problems indicated. Also make sure the  IPXCALLS.DLL
file is in the NetWare Requester directory; the try again. If  the
problem persists, contact your Novell Authorized Reseller.

REQ0625: The broadcast socket cannot be opened. Error: <code>.
Explanation The broadcast socket cannot be opened. This is a
registered socket by which  SAPs can be received. Possibly this
socket has already been opened.  Action Increase the socket count
in the NET.CFG file and shut down OS/2 and then  reboot the
system. If the problem persists, contact your Novell Authorized
Reseller.

REQ0626: An error occurred during attempt to get code page
information.  Explanation A call to DosGetCtryInfo failed. This
may be an internal program error.  Action Make sure the OS/2 is
version 2.0 or later. If so, and the problem persists,  contact
your Novell Authorized Reseller.

REQ0628: Memor y cannot be allocated for turbo buffers.
Explanation The NPDaemon could not allocate memory for turbo
buffers.  Action Try adding RAM, reducing your configuration
options in the CONFIG.SYS  file (for example, reducing the size of
DIRCACHE), removing optional device  drivers from the CONFIG.SYS
file, and freeing up some hard disk space by  deleting unnecessary
programs. If you are using multiple disk partitions,  consider
moving the OS/2 swapper file to a larger partition. Disk
compression  utilities may also be available that can help resolve
this problem. After  completing these actions, shut down OS/2;
then reboot the system. If the  problem persists, contact your
Novell Authorized Reseller.

REQ0629: A connection thread died abnormally. Error: <code>.
Explanation The connection controller thread died unexpectedly.
Action Make sure that the SPX.SYS driver has been properly entered
in the  CONFIG.SYS file. If so, check the messages displayed by
the driver for any  errors or warnings, and correct the problems
indicated. Also make sure all of


230 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



your Named Pipe drivers are within the same major version (for
example,  v2.x); then try again. If the problem persists, contact
your Novell Authorized  Reseller.

REQ0630: The specified computer name is already registered on the
internet.  Explanation The Named Pipes server name specified in
the CONFIG.SYS file has already  been used on the network.  Action
Use a different server name.

REQ0631: The receive buffer manager died abnormally. Error:
<code>.  Explanation The receive buffer manager thread died
unexpectedly.  Action Make sure that your Named Pipes drivers are
within the same major version  (for example, v2.x). If so, try
adding RAM, reducing your configuration  options in the CONFIG.SYS
file (for example, reducing the size of  DIRCA CHE), removing
optional device drivers from the CONFIG.SYS file,  and freeing up
some hard disk space by deleting unnecessary programs. If you  are
using multiple disk partitions, consider moving the OS/2 swapper
file to a  larger partition. Disk compression utilities may also
be available that can help  resolve this problem. After completing
these actions, shut down OS/2; then  reboot the system. If the
problem persists, contact your Novell Authorized  Reseller.

REQ0632: An error occurred checking for nondedicated server.
Explanation The NPDaemon could not open or communicate with the
NWREQ.SYS driver.  Action Make sure that the NWREQ.SYS driver has
been properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated. Make sure  NWREQ.SYS is version
2.0 or greater. Try again. If the problem persists,  contact your
Novell Authorized Reseller.

REQ0633: An error occurred allocating memory for nondedicated SAP
buffer.  Explanation NPDaemon could not allocate memory.  Action
Try adding RAM, reducing your configuration options in the
CONFIG.SYS  file (for example, reducing the size of DIRCACHE),
removing optional device  drivers from the CONFIG.SYS file, and
freeing up some hard disk space by  deleting unnecessary programs.
If you are using multiple disk partitions,  consider moving the
OS/2 swapper file to a larger partition. Disk compression


System Messages  231

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



utilities may also be available that can help resolve this
problem. After  completing these actions, shut down OS/2; then
reboot the system. If the  problem persists, contact your Novell
Authorized Reseller.

REQ0634: The NPDaemon could not obtain a server list.  Explanation
The Named Pipes daemon failed in its attempt to obtain a list of
servers from  the NetWare for OS/2 server running on the same
machine.  Action Make sure you are running the latest version of
the NetWare for OS/2 server.  If the problem persists, contact
your Novell Authorized Reseller.

REQ0704: The SPX module is not installed.  Explanation The Named
Pipes daemon could not open or communicate with the SPX.SYS
driver.  Action Make sure that the SPX.SYS driver has been
properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated; then try again. If the  problem
persists, contact your Novell Authorized Reseller.

REQ0705: The IPX module is not installed.  Explanation The Named
Pipes daemon could not open or communicate with the IPX.SYS
driver.  Action Make sure that the IPX.SYS driver has been
properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated; then try again. If the  problem
persists, contact your Novell Authorized Reseller.

REQ0719: An incorrect OS/2 version is being used.  Explanation The
DosGetVersion call failed (which would indicate an internal
program  error) or the OS/2 version currently running is not v2.0
or later.  Action Make sure that the client OS and NMPIPE.SYS
driver are compatible; then try  again. If the problem persists,
contact your Novell Authorized Reseller.

REQ0806: The program cannot get code page information. Error:
<code>.  Explanation The OS/2 system is not returning code page
information. This may be an  internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.


232 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0807: The Requester device driver and daemon are incompatible
versions.  Explanation The most likely cause of this problem is
that NWDAEMON.EXE and  NWREQ.SYS driver were not installed from
the same installation disk.  Action Install the Requester driver
again, making sure it is from the correct installation  disk.

REQ0808: The worker DLL cannot be registered. Error: <code>.
Explanation The NWW ORKER.DLL could not register with the
Requester. This may be an  internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.

REQ0809: The broadcast handler cannot be registered. Error:
<code>.  Explanation This may be an internal program error.
Action Try again. If the problem persists, contact your Novell
Authorized Reseller.

REQ0810: The program cannot get system information. Error: <code>.
Explanation The OS/2 system is not returning system information.
This may be an internal  program error.  Action Try again. If the
problem persists, contact your Novell Authorized Reseller.

REQ0811: The janitor thread priority cannot be set. Error: <code>.
Explanation The janitor thread is set to run at regular priority.
The system had trouble  setting the priority.  Action Ignore the
error.

REQ0812: The janitor daemon cannot be registered. Error: <code>.
Explanation This may be an internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.

REQ0813: The program cannot get the current drive map. Error:
<code>.  Explanation The OS/2 system is not returning the current
drive map. This may be an  internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.


System Messages  233

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0814: The program cannot set the current drive map. Error:
<code>.  Explanation The OS/2 system is not setting the current
drive map. This may be an internal  program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.

REQ0815: The program cannot get the connection ID. Error: <code>.
Explanation The Requester tried to locate a NetWare server when it
initialized. Either no  servers are currently running or a cabling
problem exists.  Action Make sure the NetWare server is running
and functioning properly. Also make  sure the OS/2 machine has a
working connection to the network; then try again.  If the problem
persists, contact your Novell Authorized Reseller.

REQ0816: An error occurred during attempt to initialize the cache.
Explanation The caching function is not working. This may be an
internal program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ0817: The daemon could not boost the thread priority.
Explanation The thread is set to run at a greater priority. The
system had trouble setting the  priority.  Action Ignore the
error.

REQ0818: The daemon could not register the DosBox handler.
Explanation This may be an internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.

REQ0820: Not enough memory for diagnostic daemon. Error: <code>.
Explanation The NWDaemon program tried to allocate memory from the
system for the  diagnostic thread to use as a stack, but the
system returned an error.  Action Try adding RAM, reducing your
configuration options in the CONFIG.SYS  file (for example,
reducing the size of DIRCACHE), removing optional device  drivers
from the CONFIG.SYS file, and freeing up some hard disk space by
deleting unnecessary programs. If you are using multiple disk
partitions,  consider moving the OS/2 swapper file to a larger
partition. Disk compression  utilities may also be available that
can help resolve this problem. After


234 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



completing these actions, shut down OS/2; then reboot the system.
If the  problem persists, contact your Novell Authorized Reseller.

REQ0821: The diagnostic daemon cannot be started. Error: <code>.
Explanation The NWDaemon tried to start the diagnostic thread but
the system encountered  an error condition. The system may have
too many threads already running, or  this may be an internal
program error.  Action Try closing other applications that are
currently running. If the problem  persists, contact your Novell
Authorized Reseller.

REQ0822: The diagnostic daemon priority cannot be changed. Error:
<code>.  Explanation The diagnostic thread is set to run at
regular priority. The system had trouble  setting the priority.
Action Ignore the error.

REQ0823: Not enough memory to start a new thread. Error: <code>.
Explanation The NWDaemon could not allocate memory from the system
to create a thread  for a new task.  Action Try adding RAM,
reducing your configuration options in the CONFIG.SYS  file (for
example, reducing the size of DIRCACHE), removing optional device
drivers from the CONFIG.SYS file, and freeing up some hard disk
space by  deleting unnecessary programs. If you are using multiple
disk partitions,  consider moving the OS/2 swapper file to a
larger partition. Disk compression  utilities may also be
available that can help resolve this problem. After  completing
these actions, shut down OS/2; then reboot the system. If the
problem persists, contact your Novell Authorized Reseller.

REQ0824: The SPX send thread cannot be started. Error: <code>.
Explanation This may be an internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.

REQ0825: The SPX receive thread cannot be started. Error: <code>.
Explanation This may be an internal program error.  Action Try
again. If the problem persists, contact your Novell Authorized
Reseller.


System Messages  235

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ0826: The SFT 3 handler cannot be registered.  Explanation This
may be an internal program error.  Action Try again. If the
problem persists, contact your Novell Authorized Reseller.

REQ0827: Packet Burst cannot be initialized.  Explanation This may
be an internal program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ0843: Not enough memory for a network management thread (<error
code>).  Explanation The NWDaemon tried to allocate memory from
the system for a thread to  initialize network management, but
memory was not available. Network  management cannot be
initialized.  Action Try adding RAM, reducing your configuration
options in the CONFIG.SYS  file (for example, reducing the size of
DIRCACHE), removing optional device  drivers from the CONFIG.SYS
file, and freeing up some hard disk space by  deleting unnecessary
programs. If you are using multiple disk partitions,  consider
moving the OS/2 swapper file to a larger partition. Disk
compression  utilities may also be available that can help resolve
this problem. After  completing these actions, shut down OS/2;
then reboot the system. If the  problem persists, contact your
Novell Authorized Reseller.

REQ0844: A named pipe cannot be started for network management
(<error code>).  Explanation The NWDaemon could not allocate a
named pipe. Network management will  not be supported until the
computer is rebooted. This error could result from a  variety of
causes. Named Pipes or SPX may not be loaded, one of your drivers
may have opened too many Named Pipes already, you may not have
enough  memory or disk space, or it may be an internal program
error.  Action Make sure that Named Pipes and SPX are loaded and
that your system has  enough memory. (If you suspect a memory
problem, see the discussion for  message 843.) After completing
these actions, reboot the system and try again.  If the problem
persists, contact your Novell Authorized Reseller.

REQ0845: Not enough memory to run network management (<error
code>).  Explanation The NWDaemon program tried to allocate memory
from the system to run  network management, but memory is not
available. Network Management will  not run until memory is
available and the system is rebooted.


236 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



Action Try adding RAM, reducing your configuration options in the
CONFIG.SYS  file (for example, reducing the size of DIRCACHE),
removing optional device  drivers from the CONFIG.SYS file, and
freeing up some hard disk space by  deleting unnecessary programs.
If you are using multiple disk partitions,  consider moving the
OS/2 swapper file to a larger partition. Disk compression
utilities may also be available that can help resolve this
problem. After  completing these actions, shut down OS/2; then
reboot the system. If the  problem persists, contact your Novell
Authorized Reseller.

REQ0904: The NWREQ.SYS driver is not loaded.  Explanation The
Requester cannot be initialized until the driver is loaded.
Action Load the NWREQ.SYS driver.

REQ0914: The program cannot allocate selectors for the workspace
table.  Explanation All available memory selectors are being used
by the system or by previously  loaded device drivers.  Action
Remove optional or unneeded device drivers from the CONFIG.SYS
file and  try again. If the problem persists, contact your Novell
Authorized Reseller.

REQ0915: The program cannot allocate memory for the workspace
table.  Explanation All available system memory is in use. The
Requester cannot load properly.  Action Try adding RAM, reducing
your configuration options in the CONFIG.SYS  file (for example,
reducing the size of DIRCACHE), removing optional device  drivers
from the CONFIG.SYS file, and freeing up some hard disk space by
deleting unnecessary programs. If you are using multiple disk
partitions,  consider moving the OS/2 swapper file to a larger
partition. Disk compression  utilities may also be available that
can help resolve this problem. After  completing these actions,
shut down OS/2; then reboot the system. If the  problem persists,
contact your Novell Authorized Reseller.

REQ0917: Memor y is not available for the cache table. Caching is
disabled.  Explanation All available system memory is in use by
the system. The Requester cannot  load properly.  Action Try
adding RAM, reducing your configuration options in the CONFIG.SYS
file (for example, reducing the size of DIRCACHE), removing
optional device  drivers from the CONFIG.SYS file, and freeing up
some hard disk space by  deleting unnecessary programs. If you are
using multiple disk partitions,


System Messages  237

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



consider moving the OS/2 swapper file to a larger partition. Disk
compression  utilities may also be available that can help resolve
this problem. After  completing these actions, shut down OS/2;
then reboot the system. If the  problem persists, contact your
Novell Authorized Reseller.

REQ0919: An incorrect OS/2 version is being used.  Explanation The
major versions of the Requester and OS/2 do not match.  Action
Upgrade the Requester or OS/2.

REQ0937: The Requester driver version does not match the IFS
version.  Explanation NWIFS.IFS and NWREQ.SYS were not installed
from the same installation  disk.  Action Install the Requester
again. If the problem persists, contact your Novell  Authorized
Reseller.

REQ1004: The LAN support module is not installed.  Explanation The
Requester driver requires the LSL.SYS driver to be running when it
loads.  Either the "DEVICE=C:\NETWARE\LSL.SYS" line is missing
from the  CONFIG.SYS file or the LSL encountered an error while
loading.  Action Check the CONFIG.SYS file for the LSL.SYS driver.
If this is not the problem,  contact your Novell Authorized
Reseller.

REQ1008: A NetWare server cannot be found.  Explanation The
Requester tries to locate a NetWare server when it initializes.
Either no  servers are currently running or there is a cabling
problem.  Action Make sure that the NetWare server is running and
operating properly. Also  make sure that the OS/2 machine is
connected to the network.

REQ1010: The program cannot allocate selectors for the connection
table.  Explanation All available memory selectors are being used
by the system or by previously  loaded device drivers.  Action
Remove optional or unneeded device drivers from the CONFIG.SYS
file and  try again. If the problem persists, contact your Novell
Authorized Reseller.


238 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ1011: The program cannot allocate memory for the connection
table.  Explanation All available system memory is in use. The
Requester cannot load properly.  Action Try adding RAM, reducing
your configuration options in the CONFIG.SYS  file (for example,
reducing the size of DIRCACHE), removing optional device  drivers
from the CONFIG.SYS file, and freeing up some hard disk space by
deleting unnecessary programs. If you are using multiple disk
partitions,  consider moving the OS/2 swapper file to a larger
partition. Disk compression  utilities may also be available that
can help resolve this problem. After  completing these actions,
shut down OS/2; then reboot the system.If the  problem persists,
contact your Novell Authorized Reseller.

REQ1019: An incorrect OS/2 version is being used.  Explanation The
major version of the Requester and OS/2 do not match.  Action
Upgrade the Requester or OS/2.

REQ1021: The config file cannot be parsed. Default parameters will
be used.  Explanation The Requester driver could not read
parameters in the NET.CFG file.  Action Make sure the syntax for
the NetWare Requester section of the file is correct.

REQ1022: An unrecoverable error occurred. The driver was not
loaded.  Explanation The driver could not load properly. This is
probably an internal program error.  Action Try again. If the
problem persists, contact your Novell Authorized Reseller.

REQ1024: The program cannot allocate selectors for worker support.
Explanation All available memory selectors are being used by the
system or by previously  loaded device drivers.  Action Remove
optional or unneeded device drivers from the CONFIG.SYS file. Then
try again. If the problem persists, contact your Novell Authorized
Reseller.

REQ1038: The program cannot allocate memory for the error message
buffer.  Explanation All available system memory is in use by the
system. The Requester cannot  load properly.  Action Try adding
RAM, reducing your configuration options in the CONFIG.SYS  file
(for example, reducing the size of DIRCACHE), removing optional
device  drivers from the CONFIG.SYS file, and freeing up some hard
disk space by


System Messages  239

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



deleting unnecessary programs. If you are using multiple disk
partitions,  consider moving the OS/2 swapper file to a larger
partition. Disk compression  utilities may also be available that
can help resolve this problem. After  completing these actions,
shut down OS/2; then reboot the system. If the  problem persists,
contact your Novell Authorized Reseller.

REQ1039: The Requester could not send to NetWare server <number >
as <number >.  Explanation The Requester waits for a response from
the server after each request. If the  server does not respond
within a certain amount of time, the Requester times  out.  Action
Make sure that the server is still running and functioning
properly. Also make  sure that all routers between the workstation
and the server are still running. If  the problem persists,
contact your Novell Authorized Reseller.

REQ1040: The Requester timed out waiting for reply from server
<number >.  Explanation The Requester waits for a response from
the server after each request. If the  server does not respond
within a certain amount of time, the Requester times  out.  Action
Make sure that the server is still running and functioning
properly. Also make  sure that all routers between the workstation
and the server are still running. If  the problem persists,
contact your Novell Authorized Reseller.

REQ1041: Server <number > did not respond to a request.
Explanation The Requester waits for a response from the server
after each request. If the  server does not respond within a
certain amount of time, the Requester times  out. This error can
also occur if the server responds with an unexpected  response.
Action Make sure that the server is still running and functioning
properly. Also make  sure that all routers between the workstation
and the server are still running. If  the problem persists,
contact your Novell Authorized Reseller.

REQ1042: Connection to NetWare server <number > as <number > is
now invalid.  Explanation The Requester waits for a response from
the server after each request. If the  server does not respond
within a certain amount of time, the Requester times  out.


240 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



Action Make sure that the server is still running and functioning
properly. Also make  sure that all routers between the workstation
and the server are still running. If  the problem persists,
contact your Novell Authorized Reseller.

REQ1043: Routing to NetWare server <number > has been disrupted.
Explanation The network route to the server has been disrupted.
Action Make sure that the server is still running and functioning
properly. Also make  sure that all routers between the workstation
and the server are still running. If  the problem persists,
contact your Novell Authorized Reseller.

REQ1045: Routing to NetWare server <number > has been disrupted.
Explanation The network route to the server has been disrupted.
Action Make sure that the server is still running and functioning
properly. Also make  sure that all routers between the workstation
and the server are still running. If  the problem persists,
contact your Novell Authorized Reseller.

REQ1106: The SPDaemon cannot get the SPX version. Error: <code>.
Explanation The SpxGetVersion call failed. This may be an internal
program error.  Action Make sure that the SPX.SYS driver has been
properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated. Check for a mismatch  of driver
versions. If the problem persists, contact your Novell Authorized
Reseller.

REQ1107: The SPX driver and the SPX daemon are incompatible
versions.  Explanation The SPX.SYS driver and SPDAEMON.EXE v
ersions may not match.  Action Make sure that the client SPX.SYS
driver and SPDAEMON.EXE are  compatible versions. If the problem
persists, contact your Novell Authorized  Reseller.

REQ1108: The SPX driver entry cannot be obtained. Error: <code>.
Explanation The SPDaemon could not get a handle to the SPX.SYS
driver. This may be an  internal program error.  Action Make sure
that the client SPX.SYS driver and SPDAEMON.EXE v ersions are
compatible. If the problem persists, contact your Novell
Authorized Reseller.


System Messages  241

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ1109: The SPX daemon is already loaded. Error: <code>.
Explanation The SPDAEMON.EXE has already registered with the
SPX.SYS driver, which  means it is already loaded.  Action Make
sure that the daemon SPDAEMON.EXE has not been entered in the
CONFIG.SYS file more than once.

REQ1110: The daemon cannot register with the SPX driver. Error:
<code>.  Explanation The SPDaemon cannot communicate with the
SPX.SYS driver.  Action Make sure that the SPX.SYS file has been
properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated. Check for a mismatch  of driver
versions. If the problem persists, contact your Novell Authorized
Reseller.

REQ1111: The SPX device handle cannot be closed. Error: <code>.
Explanation The SPDeamon cannot close the device handle. This may
be an internal  program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ1112: The SPDaemon cannot wait on semaphore. Error: <code>.
Explanation A DosSemSetWait call failed. This may be an internal
program error.  Action Try again. If the problem persists, contact
your Novell Authorized Reseller.

REQ1113: System information segments cannot be obtained. Error:
<code>.  Explanation The DosGetInfoSeg call failed. This may be an
internal program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ1114: Priority for the lock thread cannot be set. Error:
<code>.  Explanation The DosSetPrty call failed. This may be
internal program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ1115: The SPX driver cannot be accessed. Error: <code>.
Explanation The SPDaemon was not able to access SPX.SYS through
the call gate.


242 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



Action Make sure that the SPX.SYS driver has been properly entered
in the  CONFIG.SYS file. If so, check the messages displayed by
the driver for any  errors or warnings, and correct the problems
indicated. Also check for a  mismatch of driver versions; then try
again. If the problem persists, contact  your Novell Authorized
Reseller.

REQ1116: Priority for an AES thread cannot be set. Error: <code>.
Explanation The DosSetPrty call failed. This may be an internal
program error.  Action Try again. If the problem persists, contact
your Novell Authorized Reseller.

REQ1117: Priority for a watchdog thread cannot be set. Error:
<code>.  Explanation The DosSetPrty call failed. This may be an
internal program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ1118: Priority for a session thread cannot be set. Error:
<code>.  Explanation The DosSetPrty call failed. This may be an
internal program error.  Action Try again. If the problem
persists, contact your Novell Authorized Reseller.

REQ1119: The SPXCALLS .DLL cannot register with the SPX driver.
Explanation The SPXCALLS.DLL cannot communicate with the SPX.SYS
driver.  Action Check to see if the SPX.SYS driver has been
properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated. Check for a mismatch  of driver
versions; then try again. If the problem persists, contact your
Novell  Authorized Reseller.

REQ1205: The driver cannot initialize the CGroup Data variables.
Explanation Normally, key data variable are stored in the driver's
CGroup for easy and  reliable access. However, in this instance
the variables could not be initialized  due to a memory-related
error.  Action Try adding RAM, reducing your configuration options
in the CONFIG.SYS  file (for example, reducing the size of
DIRCACHE), removing optional device  drivers from the CONFIG.SYS
file, and freeing up some hard disk space by  deleting unnecessary
programs. If you are using multiple disk partitions,  consider
moving the OS/2 swapper file to a larger partition. Disk
compression  utilities may also be available that can help resolve
this problem. After


System Messages  243

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



completing these actions, shut down OS/2; then reboot the system.
If the  problem persists, contact your Novell Authorized Reseller.

REQ1206: The driver cannot configure SPX.  Explanation The driver
in conjunction with the NWCONFIG.DLL failed to parse the  NET .CFG
file for the SPX parameters.  Action Make sure the format of the
NET.CFG file is correct.

REQ1207: The driver failed to get support hooks from the LSL or
IPX.  Explanation SPX could not open or communicate with either
the LINKSUP_ (LSL.SYS) or  the IPX_ (IPX.SYS) drivers. The most
likely cause of this error is that one or  both of these drivers
has been improperly installed.  Action Make sure that the device
drivers LSL.SYS and IPX.SYS have been properly  entered in the
CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems
indicated. Check  for a mismatch of driver versions; then try
again. If the problem persists,  contact your Novell Authorized
Reseller.

REQ1208: The OS/2 version cannot be obtained; OS/2 v2.0 is
assumed.  Explanation The DosGetVersion call failed (an internal
program error), or the OS\2 version  currently running is not v2.0
or later.  Action Make sure that OS/2 and the SPX.SYS driver are
compatible versions. If this  is not the problem, contact your
Novell Authorized Reseller.

REQ1209: The driver cannot get OS/2 DOS variables.  Explanation
The SPX.SYS driver could not obtain either the system or local
information  segment. This may be an internal program error.
Action Try again. If the problem persists, contact your Novell
Authorized Reseller.

REQ1210: The driver cannot initialize the SPX call gate.
Explanation The SPX.SYS driver could not register a call gate with
the LSL.SYS driver.  Action Make sure that the LSL.SYS driver has
been properly entered in the  CONFIG.SYS file. If so, check the
messages displayed by the driver for any  errors or warnings, and
correct the problems indicated. Check for a mismatch  of driver
versions; then try again. If the problem persists, contact your
Novell  Authorized Reseller.


244 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

NetWare Workstation for OS/2 v2.01  100-001413-001   23 April 1993



REQ1211: The driver cannot allocate memory for SPX use.
Explanation The system does not have enough memory to run SPX.
Action Try adding RAM, reducing your configuration options in the
CONFIG.SYS  file (for example, reducing the size of DIRCACHE),
removing optional device  drivers from the CONFIG.SYS file, and
freeing up some hard disk space by  deleting unnecessary programs.
If you are using multiple disk partitions,  consider moving the
OS/2 swapper file to a larger partition. Disk compression
utilities may also be available that can help resolve this
problem. After  completing these actions, shut down OS/2; then
reboot the system. If the  problem persists, contact your Novell
Authorized Reseller.

REQ1301: The application cannot initialize named pipes.
Explanation The application could not open or communicate with the
NMPIPE.SYS driver.  Most likely, the NMPIPE.SYS driver is not
entered in the CONFIG.SYS file.  Action Make sure that the
NMPIPE.SYS driver has been properly entered in the  CONFIG.SYS
file. If so, check the messages displayed by the driver for any
errors or warnings, and correct the problems indicated. If the
problem persists,  contact your Novell Authorized Reseller.


Temp. Rev C -



NET .CFG Options Reference  245

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

a p p e n d i x B NET .CFG Options Reference

This appendix contains an alphabetical listing of all NET.CFG
options. For  instructions on how to edit the NET.CFG file, format
requirements, and  reasons to configure, see Chapter 4, "How to
Configure Your Workstation."

All the information in this appendix is also found online in the
NetWare  Requester installation and configuration program.

Topic Page

"Using the NET.CFG Reference Pages" 246

"Daemon Configur ation" 247

"DisplayHardErrors" 248

"Link Driver" 249

"Link Support" 261

"Named Pipes" 263

"NetWare NetBIOS" 266

"NetWare Requester" 274

"Protocol ODINSUP" 281

"Protocol Stack IPX" 283

"Protocol Stack SPX" 286

"Token-Ring Source-Route Driver" 291


246 NetWare Workstation for OS/2 v2.01

Temp. Rev C -

  D R A F T

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Using the NET.CFG Reference Pages

Figure K-6 explains how to read the NET.CFG reference pages in
this chapter. Figure K-6 Format of NET.CFG  reference pages



Link support

Use this option to adjust the number and size of communication
buffers used by the Requester.*

Syntax

Settings

buffers count  [buffer_size]

link support buffers count [buffer_size]

Use this setting to specify how many and what size  communication
buffers the Requester can use. *

Usage

Defaults

Examples

Usage Replace count with a number of buffers  greater than one.
*** * Replace buffer_size with a number of bytes greater  than
576. *

Defaults Count: 20 buffers** Buffer_size: 1130 bytes*

For an Ethernet configuration:

link support buffers 20 1514

Unless your site has a particularly unique and complex network
setup, you will probably never need to use the performance  tuning
options. The defaults have already been set to produce  maximum
performance in almost all cases. *

1. Notes

NetWare Requester for OS/2    1

Square brackets* mean the * parameter* is optional

Description* of option

Setting name Description of* setting

Example of use

Replace words in* italics with * specific values

What to type

Special * considerations* when using the* option

Option name


NET .CFG Options Reference  247

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Daemon Configuration

Use this option to control the length of time network-related
error messages  stay on your screen. This option controls only
pop-up and broadcast messages.

Pop-up and broadcast messages appear in a small box on your screen
and  prompt you to "Press <Esc> to continue . . ."

Setting

message timeout

Syntax daemon configuration    message timeout  number

Replace number with a number of milliseconds that you  w ant pop-
up and broadcast messages to display on your  screen before
disappearing.

Replace number with 0 (zero) to prevent pop-up and  broadcast
messages from displaying at all.

If you leave this line out of your NET.CFG, pop-ups and  broadcast
messages are displayed until you press <Esc>.

Default Pop-up and broadcast messages display until you press
<Esc>.

Example To prevent pop-up and broadcast messages from  displaying:

daemon configuration    message timeout 0

Note


Temp. Rev C -

248 NetWare Workstation for OS/2 v2.01



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

DisplayHardErrors

Use this option to keep programs running without interaction when
a hard error  is displayed. With this option set, hard errors are
automatically returned to the  program that caused them rather
than displayed to you for further interaction.

This option is useful for sites with unattended workstations. Be
careful about  using it in other environments as you might turn
off important messages.

Hard errors display on a full screen and prompt you to choose
among several  actions. These error messages cause background
processes to suspend until  you respond to the message.

displayharderrors no

Syntax Type displayharderrors no to keep error messages from
displaying.

To display error messages, leave this line out of your  NET .CFG
file.

Default Error messages are displayed.

Example To prevent hard error messages from displaying:
displayharderrors no

Note


NET .CFG Options Reference  249

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Link Driver

Use this option to specify the hardware configuration of the LAN
drivers for  each network board in your workstation.

Use this option only if the network boards are not using the
default settings.  The settings you specify with this option
should match the hardware settings  for your boards.

If you have more than one network board in your workstation, put
this option in  your NET.CFG file for each board.

Syntax

link driver  name dma [ index ] channel frame  name int [ index ]
irq mem [ index ] starting_address  [size ] node address  number
port [ index ] starting_port  [number ] protocol  name  id frame
slot  number

Option

link driver

Use this option to specify the name of the LAN driver whose
defaults you want  to modify.

Syntax link driver  name

Replace name with the name of the driver. TableK-1 lists  some
network boards and their driver names.

Note


Temp. Rev C -



250 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

The PCN2 and PCN2L drivers cannot be used in the same workstation.

Table K-1 List of network boards and drivers

Driver name Network board

NE2 No vell Ethernet NE/2

NE2_32 No vell Ethernet NE/2-32

NE1000 No vell Ethernet NE1000

NE2000 No vell Ethernet NE2000

TOKEN IBM Token-Ring

LANSUP Boards using NDIS drivers

ODINSUP IBM Token-Ring and Ethernet Communications Manager

3C501 3Com EtherLink series 501

3C503 3Com EtherLink series 503

3C505 3Com EtherLink series 505

3C523 3Com EtherLink/MC series

PCN2 IBM PC Network II and II/A (older Novell frame format)

PCN2L IBM PC Network II and II/A (new er IBM frame format)

Default None.

Example To configure an IBM Token-Ring PC driver, type the
following with any settings from the following pages:

link driver token

Note


Temp. Rev C -



NET .CFG Options Reference  251

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Settings

DMA

Use this setting to specify which direct memory access (DMA)
channel the  network board uses.

Syntax link driver  name    dma [ index ] channel

Replace index with either #1 or #2 (optional).

The driver configuration table for each board can store the  DMA
channel number on either of two lines. The lines are  labeled #1
and #2.

Replace channel with the number of the DMA channel  used by the
board.

The channel numbers for different network boards are  recorded in
the documentation from the board  manufacturers.

Defaults Index: #1

Most boards use this default.

Channel: Set by the driver. See the documentation for the  board.

You can't change the DMA setting on 3Com Etherlink  503 boards,
and you do not need to change it on 3Com  Etherlink 505 boards.
You can change the DMA setting  on 3Com Etherlink 523 boards.

Example To set the DMA channel for a 3Com Etherlink 505 board:

link driver 3C505    dma 7


Temp. Rev C -



252 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

frame

Use this setting to specify which frame type the driver for your
network board  uses.

Use this setting only for boards that support more than one frame
type or if you  w ant multiple networks (separate network
addresses) to share the same  network board and cabling.

The frame type transmitted by the workstation should match the
type of  packets being transmitted by the servers on your network.

Syntax link driver  name    frame  name

Replace name with the name of the frame type. The  following table
lists common frame types and the network  board drivers that
support each type. This list is not  comprehensive.

Table K-2 List of frame types and drivers

Frame type Network board driver

Ethernet_802.3 NE1000, NE2000, NE2100, NE2, NE2_32,  3C501, 3C503,
3C505, 3C523, EXOS205,  EXOS215, ODINSUP

Ethernet_802.2 NE1000, NE2000, NE2100, NE2, NE2_32,  3C501, 3C503,
EXOS205, EXOS215,  ODINSUP , LANSUP

Ethernet_II NE1000, NE2000, NE2100, NE2, NE2_32,  3C501, 3C503,
3C505, 3C523, EXOS205,  EXOS215, ODINSUP

Ethernet_SNAP NE1000, NE2000, NE2100, NE2, NE2_32,  3C501, 3C503,
EXOS205, EXOS215,  ODINSUP , LANSUP

Token-Ring ODINSUP , TOKEN, LANSUP

Token-Ring_SNAP ODINSUP , TOKEN, LANSUP


Temp. Rev C -



NET .CFG Options Reference  253

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

If you are using the ODINSUP driver, you must enable multiple
frame types  for each driver. For Ethernet, enable Ethernet_802.3,
Ethernet_II,  Ethernet_802.2, and Ethernet_SNAP.

For Token-Ring, enable Token-Ring and Token-Ring_SNAP. For more
information about ODINSUP, see Chapter 8, "Sharing a Network Board
With  IBM Software."

You can specify more than one frame type statement for a single
driver. For  example, you can specify that an Ethernet NE2000
board can use both  Ethernet_802.2 and Ethernet_802.3 frame types.
802.2 is the type of  communications sent on one network, and
802.3 is the type of communication  sent on the other network.

You can use up to four frame types for one set of Ethernet
cabling. You can use  either four network boards each with one
frame type defined, or you can use  one network board with four
frames defined, or any similar combination.

IBM_pcn2_802.2 PCN2, PCN2L, LANSUP

IBM_pcn2_snap PCN2, PCN2L, LANSUP

No vell_rx-net TRXNET , TRXNET2

Default Set by the driver. See the documentation for the board.
Examples To specify the Ethernet_802.2 frame type for an NE2000
board:

link driver ne2000    frame ethernet_802.2

To specify the Ethernet_802.2 and Ethernet_802.3 frame  types for
an NE1000 board (for two logical networks):

link driver ne1000    frame ethernet_802.2    frame ethernet_802.3

Table K-2 continued List of frame types and drivers

Frame type Network board driver


Temp. Rev C -



254 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

For Token-Ring cabling, two frames types are the maximum allowed.

The default frame type for Ethernet drivers has changed to
Ethernet_802.2.   This may conflict with the frame type used on
your network. See "Specifying  Frame Types for a Driver" on page
67 for more information about specifying  frame type.

int

Use this setting to specify which interrupt line (IRQ) the network
board uses  to communicate with the driver.

Before changing the interrupt setting for your board, be sure you
know what  interrupt settings are used on other hardware (such as
monitors) that you are  using. For example, interrupts 2 and 9-15
are usually reserved, so don't use

Syntax link driver  name    int [ index ] irq

Replace index with either #1 or #2 (optional).

The driver configuration table for each board can store the
interrupt line number on either of two lines in the table.  The
lines are labeled #1 and #2.

Replace irq with the number of the interrupt line used by  the
board.

To determine the interrupt line number for your network  board,
see the documentation for the board.

Defaults Index: #1

IRQ: Set by the driver. See the documentation for the  board.

Example To set the interrupt line for an NE2000 board:

link driver ne2000    int 3


Temp. Rev C -



NET .CFG Options Reference  255

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

those numbers (especially 2) for your network board. We recommend
using 3,  5, or 7 for most network boards.

If you are using a PS/2 computer on a Token-Ring network, do not
autoconfigure with the Reference diskette. Doing so may cause
problems.

mem

Use this setting to specify what range of memory can be used by
the driver.

Syntax link driver  name    mem [ index ] starting_address  size

Replace index with either #1 or #2 (optional).

The driver configuration table for each board can store the
memory range on either of two lines in the table. The lines  are
labeled #1 and #2.

Replace starting_address with a hexadecimal memory  address that
begins the range. This address must be five  digits and the same
as the address designated for the  board by the manufacturer. (See
the documentation for  the board).

Replace size with a hexadecimal number of paragraphs in  the
memory range (optional).

Defaults Index: #1

Starting_address: Set by the driver. See the  documentation for
the board.

Size: Set by the driver. See the documentation for the  board.

Example To set the memory range for a Token-Ring board:

link driver token    mem cc000 200


Temp. Rev C -



256 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Assign each board a unique memory range. Be sure that you don't
assign a  range that is already being used by other hardware. (VGA
monitors commonly  use C6FFF and XVGA monitors commonly use
CFFFF.)

node address

Use this setting to change the node address of a network board.
This setting can  only be used with network boards that allow you
to override the preset address.

Syntax link driver  name    node address  number

Replace number with a hexadecimal address. You can  specify the
address with either the least significant bit first  (lsb format)
or the most significant bit first (msb format).

Default The address preset on the board.

Example To change the address for board that uses the ODINSUP
driver:

link driver odinsup    node address 02608c861759


Temp. Rev C -



NET .CFG Options Reference  257

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

port

Use this setting to specify which range of I/O ports the network
board uses.

Syntax link driver  name    port [ index ] starting_port  [number
]

Replace index with either #1 or #2 (optional).

The driver configuration table for each board can store
information about ports on either of two lines in the table.  The
lines are labeled #1 and #2.

Replace starting_port with a hexadecimal port number  that begins
the range. We recommend not using 2EO and  2FO since these port
numbers are normally used by  ARCnet for other functions.

Replace number with the hexadecimal number of bytes in  the range
(optional).

Defaults Index: #1

Starting_port: Set by the driver. See the documentation  for the
board.

Number: Set by the driver. See the documentation for the  board.

Example To set the memory range for board that uses the NE2000
driver:

link driver ne2000    port 300


Temp. Rev C -



258 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

protocol

Use this setting to allow LAN drivers to use protocols that have
different frame  types.

Syntax link driver  name    protocol  name  ID frame

Replace name with the acronym of an ODI-compliant  protocol.

Some common protocols are:

ARP IP IPX (the NetWare protocol) RARP

Replace ID with the hexadecimal number of the protocol  that goes
with the frame type you specify. The following  table shows common
protocols with some frame types  and hexadecimal numbers they
support.

Replace frame with the name of the frame type used with  the
protocol. The following table lists some common  frame types.


Temp. Rev C -



NET .CFG Options Reference  259

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Table K-3 List of protocols, frame types, and hexadecimal ID
numbers

Protocol Frame type Hex number

IPX Ethernet_802.3 Ethernet_802.2 Token-Ring IBM_PCN2_802.2
Ethernet_II Ethernet_SNAP Token-Ring_SNAP IBM_PCN2_SNAP No
vell_RX-Net

0 e0 e0 e0 8137 8137 8137 8137 fa

IP Ethernet_II Ethernet_SNAP Token-Ring_SNAP No vell_RX-Net

800 800 800 d4

ARP Ethernet_II Ethernet_SNAP Token-Ring_SNAP No vell_RX-Net

806 806 806 d5

RAR P Ethernet_II Ethernet_SNAP Token-Ring_SNAP No vell_RX-Net

8035 8035 8035 d6

Defaults Name: IPX

ID: 0

Frame: Ethernet_802.3

Example To specify the ARP protocol for an Ethernet II frame:

link driver NE2000    protocol arp 806 ethernet_ii


Temp. Rev C -



260 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

slot

Use this setting to tell the Requester which expansion slot an
EISA or  MicroChannel board is using.

EISA and Micro Channel boards are self-configuring, and the
Requester can  obtain all Link Driver information from the board
itself. You have to tell the  Requester which slot the board is
using or, if you only have one board of a  particular type, tell
the Requester to scan all slots until it finds that board. .

Syntax link driver  name    slot  number

Replace number with the number of the expansion slot the  board is
using or a question mark to tell Requester to scan  all slots.

Default Slot ?

Example To automatically configure the drivers for an NE/2 board
in slot 4 and an NE/2 board in slot 2: link driver ne2    slot 4
link driver ne2    slot 2

This slot setting is the only Link Driver hardware-related
setting you need to specify in this case.

To scan the slots for a Novell Ethernet NE/2 board:

link driver ne2    slot ?


NET .CFG Options Reference  261

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Link Support

Use this option to adjust the number and size of communication
buffers used  by the Requester.

Syntax

link support buffers  number  [buffer_size ]

Settings

buffers

Syntax Replace number with a number of buffers greater than 1.

Replace buffer_size with a number of bytes greater than  576.

The Requester cannot use more than 64 KB of memory  for
communication buffers. Header information takes 5  KB. This means
that the buffer number multiplied by the  buffer size (plus the
header information) cannot be greater  than 65,536 bytes. For
example, 20 buffers multiplied by  1514 bytes equals 30,280 bytes.
Defaults Number: 20 buffers

Buffer_size: 1514 bytes

Examples For an Ethernet configuration: link support    buffers 15
2800

For a Token-Ring configuration: link support    buffers 14 4210


Temp. Rev C -



262 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Notes

1. Increasing efficiency. For most efficient communication, your
link support  buffer size should be the same size as the packets
that your workstation  will receive over the network. You may want
to set the link support buffer  size equal to the largest buffer
size that the network boards in your  w orkstation will support.

2. Using the TRXNET.SYS driver. If your workstation experiences
performance problems running with TRXNET.SYS, you may need to
reconfigure the number and size of link support buffers allowed.
Set the  following values:

link support buffers 15 4202 TRXNET .SYS only supports SMC100,
110, and 120 cards.


NET .CFG Options Reference  263

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Named Pipes

Use this option to manage Named Pipes sessions.

Syntax

named pipes client sessions  number server sessions  number
service threads  number

Settings

client sessions

Use this setting to specify the maximum number of connections a
workstation  can establish with all Named Pipes servers.

Syntax named pipes    client sessions  number

Replace number with a number from 3 to 128.

You need at least one client session for each connection  from an
OS/2 application to a Named Pipes server.

Default 16 sessions.

The default is usually adequate, except with applications  that
use many Named Pipes.

Example To allow each client thirty sessions:

named pipes    client sessions 30


Temp. Rev C -



264 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

server sessions

Use this setting to specify the maximum number of connections a
Named Pipes  server can support with all Named Pipes clients at
any one time.

Syntax named pipes    server sessions  number

Replace number with a number greater than 2.

Novell's Named Pipes support is designed to handle more  than
1,000 server sessions; however, because of OS/2  requirements, the
practical upper limit is much lower  (around 400).

You must have one more  SPX session than  you have  Named Pipes
server and client sessions combined  (see  "Protocol Stack SPX"
option on page 286).

If you specify fewer SPX sessions than Named Pipes  server
sessions, the Requester will treat the SPX session  number as the
maximum number of Named Pipes server  sessions

Default 32 sessions.

Example To allow each server three hundred sessions:

named pipes    server sessions 300


Temp. Rev C -



NET .CFG Options Reference  265

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

service threads

Use this setting to specify the  number of threads the Named Pipes
server can  use to handle requests from all clients.

For an OS/2 workstation to function as a Named Pipes server or
client, you  m ust have selected Named Pipes when you installed
the Requester on that  w orkstation.  See "Installing Named Pipes
for OS/2" on page 149.

Syntax named pipes    service threads  number

Replace number with a number from 1 to 32.

If the client  application uses blocking pipes, increase this
default. If the client  application uses non-blocking pipes,  use
the default value for better performance. SQL Server  does not use
blocking pipes.

Default 3 threads

Example To increase the number of threads a Named Pipes server
can use to twenty:

named pipes    service threads 20

Note


Temp. Rev C -

266 NetWare Workstation for OS/2 v2.01



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

NetWare NetBIOS

Use this option to manage NetBIOS names and sessions or to affect
the internal  memory allocation for NetBIOS.

Syntax

netware netbios abort timeout  number broadcast count  number
broadcast delay  number commands  number internet [on|off] listen
timeout  number names  number retry count  number retry delay
number sessions  number verify timeout  number

Table K-4 Categories of NetWare NetBIOS settings

Purpose Setting Page

Name management Broadcast count Broadcast delay Internet Names

268 269 270 271

Session creation Retry count Retry delay Sessions

272 272 273

Session management Abort timeout Listen timeout Verify timeout

267 267 267

Command management Commands 270


Temp. Rev C -



NET .CFG Options Reference  267

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Settings

abort timeout

listen timeout

verify timeout

Use these settings to monitor and control your NetBIOS
connections.

When NetBIOS sessions at a sending computer do not receive any
transmissions from the receiving computer for the length of the
"verify  timeout" interval, NetBIOS sends a request-for-
acknowledgment packet to the  receiving computer.   NetBIOS then
waits the length of the "listen timeout"  interval to receive a
response.

If no response is received, NetBIOS sends another packet
requesting  immediate response. NetBIOS then waits the length of
the "abort timeout"  interval to receive a response.

If no response is received, NetBIOS terminates the session.

Syntax netware netbios    abort timeout  number    listen timeout
number    verify timeout  number

Abort timeout: Replace number with a number of  milliseconds
greater than 500.

Listen timeout: Replace number with a number of  milliseconds
greater than 200

Verify timeout: Replace number with a number of  milliseconds
greater than 100.

Syntax  continued The ratio between these settings must remain the
same.  For example, if you double the Listen timeout value, you
must also double the Abort timeout and Verify timeout  values.


Temp. Rev C -



268 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

broadcast count

Use this setting to specify how many times NetBIOS broadcasts a
query or  claim for the name being used by an application.

Defaults Abort timeout: 30,000 milliseconds Listen timeout: 6,000
milliseconds Verify timeout: 3,000 milliseconds

Examples To make NetBIOS wait longer before sending a request for
acknowledgment packet, sending the packet  requesting immediate
response, and terminating the  session:

netware netbios   abort timeout 45000   listen timeout 8000
verify timeout 4000

Syntax netware netbios    broadcast count  number

Replace number with a number of queries greater than 1.

Defaults W ith internet on: 4 times. W ith internet off: 2 times.

Example To broadcast more often:

netware netbios    broadcast count 8


Temp. Rev C -



NET .CFG Options Reference  269

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

broadcast delay

Use this setting to specify how long NetBIOS waits between query
or claim  broadcasts.

Syntax netware netbios    broadcast delay  number

Replace number with a number of milliseconds greater  than 100.

Defaults W ith internet on: 2,000 W ith internet off: 1,000

Example To wait longer between broadcasts:

netware netbios    broadcast delay 3000


Temp. Rev C -



270 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

commands

Use this setting to specify how many NetBIOS commands can be
buffered in  the NetBIOS driver at any one time.

internet

Use this setting to transmit name-claim packets to and from all
stations on the  internet, or to and from stations on the local
network only.

Name-claim packets are packets which attempt to establish the
uniqueness of  the name of the station on which NetBIOS is
running.

Syntax netware netbios    commands  number

Replace number with a number of commands from 8 to  128.

Default 32 commands

Example To run an application that requires a large number of
outstanding commands:

netware netbios    commands 128

Syntax netware netbios    internet [on|off]

Type on or off.

Default On

Example To send and receive on the local network only:

netware netbios    internet off


Temp. Rev C -



NET .CFG Options Reference  271

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

names

Use this setting to specify how many names the workstation can
have in its  name table for remote stations. When you add a name
to a station, the station  broadcasts that name to all other nodes
on the network.

Syntax netware netbios    names  number

Replace number with a number of names from 4 to 128.

You can use a name instead of a node address to refer to a  remote
station.

Default 24 names

Example To allow forty-five names:

netware netbios    names 45


Temp. Rev C -



272 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

retry count

Use this setting to specify how many times NetBIOS transmits a
request for  connection or retransmits a failed communication.

retry delay

Use this setting to specify how many milliseconds NetBIOS waits
between  transmissions while establishing a connection or
resending a data packet.

Syntax netware netbios    retry count  number

Replace number with a number greater than 0.

Default 20 times

Example To retransmit fifty times:

netware netbios    retry count 50

Syntax netware netbios    retry delay  number

Replace number with a number of milliseconds greater  than 0.

Default 500 milliseconds

Example To wait eight hundred milliseconds between  retransmission
attempts:

netware netbios    retry delay 800


Temp. Rev C -



NET .CFG Options Reference  273

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

sessions

Use this setting to specify how many simultaneous NetBIOS sessions
can be  supported by the NetBIOS driver.

Syntax netware netbios    sessions  number

Replace number with a number of sessions from 4 to 64.

Default 16 sessions

Example To allow one hundred NetBIOS sessions:

netware netbios    sessions 50


Temp. Rev C -

274 NetWare Workstation for OS/2 v2.01



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

NetWare Requester

Use this option to control network requests from your workstation
to a  NetWare server.

Syntax

netware requester cache buffers  number large internet packets off
name context  context packet burst off preferred  servername
preferred tree  treename request retries  number sessions  number
signature level  number

Settings

cache buffers

Use this setting to specify how many buffers the Requester can use
to cache  data from open files.

Cache buffers minimize read and write traffic on the network. The
more  buffers, the faster the Requester performs; however, more
buffers use up more  memory.

The Requester automatically uses the maximum buffer size permitted
by each  server to which the Requester is connected. However, the
Requester cannot use


Temp. Rev C -



NET .CFG Options Reference  275

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

more than 64 KB of total memory for cache buffers, so if the
buffer size is  large, you may not be allowed as many buffers as
you specify.

large internet packets off

Use this setting to disable large internet packets transmission.
"Improving  Speed and Security" on page 79  explains more about
large internet packets.

Syntax netware requester    cache buffers  number

Replace number with a number of buffers from 0 to 30.

To turn off caching, specify 0. Default 8 buffers

Example To allow 15 cache buffers: netware requester    cache
buffers 15

Syntax netware requester    large internet packets off

Type large internet packets off to turn off large packet
transmissions.

Default Large internet packets are transmitted.

Example To disable large packet transmission:

netware requester    large internet packets off


Temp. Rev C -



276 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

name context

Use this setting to specify the workstation's name context in the
directory  services tree.  Concepts explains more about name
contexts.

packet burst off

Use this setting to disable the packet burst feature. "Improving
Speed with  Packet Burst" on page 80 explains more about the
Packet Burst feature.

Syntax netware requester    name context  "context"

Replace context with your name context in the directory  tree.

Default At the root of the tree.

Example To specify a name context:

netware requester    name context "john.sales.novell us"

Syntax netware requester    packet burst off

Default Packet burst is enabled.

Example To disable packet burst:

netware requester    packet burst off


Temp. Rev C -



NET .CFG Options Reference  277

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

preferred server

Use this setting to specify which NetWare server you want your
workstation to  attach to when it first accesses the network.

If the server you specify is unavailable, your workstation will
attach to the first  available server.

Syntax netware requester    preferred server  servername

Replace servername with the name of a server. The server  you
specify should probably have the NetWare utilities  for OS/2
installed.

Default None

Example To attach to server FINANCE:

netware requester    preferred server finance

Note


Temp. Rev C -



278 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

preferred tree

Use this setting to specify a tree name to connect. This setting
is only for sites  with more than one directory tree.

request retries

Use this setting to specify how many times the Requester tries to
resend a  request following a communication error.

Syntax netware requester    preferred tree  treename

Replace treename with the name of your tree. Tree names  can have
up to 32 characters.

Default None.

Example To connect to  a tree named Novell:

netware requester    preferred tree novell

Syntax netware requester    request retries  number

Replace number with a number of retries greater than 5.

Default 20.

Decrease the default if you are connected to the network  over a
modem and you do not want to waste phone time  while the Requester
keeps trying to resend packets.


Temp. Rev C -



NET .CFG Options Reference  279

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

sessions

Use this setting to specify the number of connections the
Requester can have  to all servers.

Example To decrease the number of times the Requester tries to
resend a packet:

netware requester    request retries 10

Syntax netware requester    sessions  number

Replace number with a number of connections from 8 to  32.  You
must have at least three IPX sockets for each  session you allow.
(See the "sockets" setting on page  284.)

Default 8 sessions

Example To allow more server connections:

netware requester    sessions 20

You must also increase the sockets setting for the Protocol  Stack
IPX option in this case.


Temp. Rev C -



280 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

signature level

Use this setting to assign a signature level. Signature levels
help determine  security on your network. "Improving Security by
Using Packet Signature" on  page 81 explains more about signature
levels.

Syntax NetWare Requester    signature level  number

Replace number with 0, 1, 2, or 3.

Table K-5 List of NCP Packet Signature levels

Number Explanation

0 W orkstation does not sign packets

1 W orkstation signs packets only if the server requests it
(server option is 2 or higher)

2 W orkstation signs packets if the server is capable of  signing
(server option is 1 or higher)

3 W orkstation signs packets and requires the server to  sign
packets (or logging in will fail)

Default 1 (Workstation signs packets only if the server requests
signing.) Example To prevent the workstation from signing packets:

netware requester    signature level 0


NET .CFG Options Reference  281

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Protocol ODINSUP

Use this option to allow the NDIS protocol stack (used with
Extended Services  and LAN Services) to communicate using ODI
Token-Ring or Ethernet  drivers.

See "Sharing a Network Board With IBM Software" on page 95 before
using  this option.

Syntax

protocol odinsup bind  driver  [number ]

Settings

bind

Use this setting to bind the ODINSUP protocol to an ODI driver.
When  ODINSUP is bound to a driver, the network board for that
driver is the board  used for transmissions to and from the
network.

Syntax protocol odinsup    bind  driver  [number ]

Replace driver with a Token-Ring or Ethernet ODI driver  name. See
TableK-1, "List of network boards and  drivers," on page250 for a
list of common driver names.

Use number to bind ODINSUP to a particular occurrence  of a board
when you have two boards with the same name.  Replace number with
a number from 1 to 4.

For example, if you have two NE2000 network boards in  your
workstation, bind ODINSUP to each board by  typing a 2 for the
second board.

ODINSUP can be bound to a maximum of four ODI  drivers.


Temp. Rev C -



282 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Default ODINSUP binds to the first Ethernet or Token-Ring board
it locates.

Examples To bind ODINSUP to a single NE2000 board in your  w
orkstation: protocol ODINSUP    bind ne2000

To bind ODINSUP to both the first and the second  NE2000 boards in
your workstation: Protocol ODINSUP    bind ne2000    bind ne2000 2


NET .CFG Options Reference  283

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Protocol Stack IPX

Use this option to adjust IPX communication between applications
and the  LAN drivers in your workstation.

Syntax

protocol stack ipx bind  name router mem  size sockets  number

Settings

bind

Use this setting to specify the primary network board in your
workstation. By  default, the primary board is the board whose
driver loads first in the  CONFIG.SYS file. If you specify a
different board with this setting, that  default is changed. See
Chapter 5, "Network Boards and Drivers."

Syntax protocol stack ipx    bind  name

Replace name with the driver name for your network  board.

TableK-1, "List of network boards and drivers," on  page250 lists
common network boards.

Default The first driver listed in your CONFIG.SYS file.

Example To specify a 3Com Etherlink 3C503 board as primary:
protocol stack ipx    bind 3C503


Temp. Rev C -



284 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

router mem

Use this setting to specify how many bytes in the router memory
pool are  allocated for routing requests to the network.

sockets

Use this setting to specify how many sockets IPX can open at your
workstation.

Syntax protocol stack ipx    router mem  size

Replace size with a number of bytes.

Default 450 bytes

Since a size of 450 bytes accommodates up to 15 network  boards
per workstation, you should not need to increase  this default.

Example To increase the default: protocol stack ipx    router mem
500

Syntax protocol stack ipx    sockets  number

Replace number with a number of sockets between 9 and  128. If you
are running IPX with the Requester, do not set  this value below
32.

You need three sockets per server connection. The default  of 64
works for the default number of server connections  (see the
"sessions" setting on page 279).

Allow more sockets if your workstation connects to many  different
servers or runs protocols (such as Named Pipes)  that require
sockets.


Temp. Rev C -



NET .CFG Options Reference  285

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Default 64 sockets

Example To set the socket limit for a workstation connected to
several servers that is running Named Pipes and  applications that
require sockets: protocol stack ipx    sockets 128


Temp. Rev C -

286 NetWare Workstation for OS/2 v2.01



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Protocol Stack SPX

Use this option to adjust the number and characteristics of SPX
connections  between your workstation and other computers.

Syntax

protocol stack spx abort timeout  number listen timeout  number
retry count  number send timeout  number sessions  number verify
timeout  number

Settings

abort timeout

listen timeout

verify timeout

Use these settings to monitor and control SPX connections.

When SPX sessions at a sending computer do not receive
transmissions from  the receiving computer for the length of the
"verify timeout" interval, SPX  sends a keep-connection-alive
packet to the receiving computer.   SPX then  w aits the length of
the "listen timeout" interval to receive a response.

If no response is received, SPX sends another packet requesting
immediate  acknowledgment. SPX then waits the length of the "abort
timeout" interval to  receive a response.


Temp. Rev C -



NET .CFG Options Reference  287

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

If no response is received, SPX aborts the session.

Syntax protocol stack spx    abort timeout  number    listen
timeout  number    verify timeout  number

Replace number with a number of milliseconds greater  than 10.

The ratio between these settings must remain the same.  For
example, if you double the Listen timeout value, you  must also
double the Abort timeout and Verify timeout  values.

If the machine you are setting up will be a Named Pipes  server,
double the default timeout values.

Default Abort timeout: 30,000 milliseconds

Listen timeout: 6,000 milliseconds

Verify timeout: 3,000 milliseconds

Example  To make SPX wait longer before sending a keep connection-
alive packet, sending the packet requesting  immediate response,
or aborting the session: protocol stack spx    abort timeout 40000
listen timeout 8000    verify timeout 4000


Temp. Rev C -



288 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

retry count

Use this setting to specify the number of times your workstation
will resend  packets that weren't acknowledged by the receiving
computer the first time  they were sent

Some applications may set the "retry count" value. In these cases,
the  application-set value is used and the NET.CFG value is
ignored.

Syntax protocol stack spx    retry count  number

Replace number with a number of retries from 1 to 255.

If your network traffic is heavy or if you are transmitting
across routers, you may want to increase the default.

Default 15 retries

Example To increase the number of times packets are resent:
protocol stack spx    retry count 30

Note


Temp. Rev C -



NET .CFG Options Reference  289

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

send timeout

Use this setting to specify how long SPX waits between attempts to
send  packets across the network.

Syntax protocol stack spx    send timeout  number

Replace number with a number of milliseconds greater  than 500.

This default works well in almost all cases. Increase the  default
if you are using network management products  with a very large
network and you encounter many SPX  connection errors.

You may also want to increase the default for a Named  Pipes
client that is operating faster than the Named Pipes  server to
which it is connected.

Default A continually calculated value based on the time it takes
SPX to get a response from the server.

Example To increase the wait between sends: protocol stack spx
send timeout 5600


Temp. Rev C -



290 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

sessions

Use this setting to specify how many SPX connections can be open
simultaneously.

Syntax protocol stack spx    sessions  number

Replace number with a number of SPX connections  greater than 8.
Numbers higher than 1,000 may not work  in all circumstances.

If you run Named Pipes applications or other applications  that
use SPX, you may need to increase the default  number of sessions.

Default 16 sessions

Example To increase the number of SPX sessions: protocol stack spx
sessions 64


NET .CFG Options Reference  291

Temp. Rev C -



NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Token-Ring Source-Route Driver

Use this option to configure the Requester for source-routing
between Token Ring networks that are connected with source
routers. For more information  about source routing, see Chapter
7, "Using OS/2 Workstations on a Token Ring Network."

Do not use this option if your Token-Ring networks do not use
source routing.

Syntax

protocol route source route  def gbr mbr nodes  n board  n

Settings

board

Use this setting to specify the logical board (frame) of a
particular type that is  performing source routing.

Syntax protocol route    source route board  n

Replace n with a logical board (frame) number from 1 to  16.

For example, if a workstation has more than one frame  type listed
in the Link Driver option, by default only the  first listed frame
is source routed. To enable source  routing on the second or other
frames, you must explicitly  specify the second frame as logical
board 2.

Default 1

Note


Temp. Rev C -



292 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

DEF

Use this setting (default frame) to prevent frames that have
unknown  destination addresses from being sent across Single Route
IBM bridges.

u If this setting is specified, these frames are forwarded as All
Routes  Broadcast frames.

u If this setting is not specified, all frames that have addresses
not in the  w orkstation's Source Routing table are forwarded as
Single Route  Broadcast frames.

u If ROUTE.SYS has already been configured with the DEF setting,
reloading ROUTE.SYS with this setting broadcasts all subsequent
Single  Route Broadcast frames as All Routes Broadcast frames.

Example To specify that logical board 2, the Token-Ring_SNAP
frame, will also be source routed:

link driver token    frame token-ring    frame token-ring_snap

protocol route    source route board 1    source route board 2

Syntax protocol route    source route  def

Type DEF to broadcast on all routes. Omit DEF to  broadcast on a
single route only.

Default DEF  is omitted (single-route broadcast only)

Change this default when you are unsure of the stability  of one
or more routes in the network. Be aw are that using  DEF  will
substantially increase network traffic,  especially on large,
redundant ring networks.


Temp. Rev C -



NET .CFG Options Reference  293

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

GBR

Use this setting (general broadcast) to specify that all General
BRoadcast  frames are to be sent as All Routes Broadcast frames

Example To broadcast on all routes:

protocol route    source route def

Syntax protocol route    source route gbr

Type GBR to broadcast to all destinations, on all rings, by  all
routes. Omit GBR to broadcast to all destinations, on  all rings,
by a single route.

Change the default when you want to ensure successful
transmission across all possible routes. If ROUTE has  already
been configured with this setting, reconfiguring  ROUTE with this
setting broadcasts all subsequent  General Broadcast frames as All
Routes Broadcast  frames.

Default GBR is omitted (single route broadcast only)

Example To broadcast to all destinations, on all rings, by all
routes:

protocol route    source route gbr


Temp. Rev C -



294 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

MBR

Use this setting (multicast) to specify that all Multicast
Broadcast frames are  to be sent as All Routes Broadcast frames.

nodes

Use this setting to specify the number of table entries in the
source-routing  table.

Syntax protocol route    source route mbr

Type MBR to transmit multicast frames simultaneously to  a group
of destinations by all possible routes. Omit MBR  to transmit
multicast frames by a single route.

Default MBR is omitted (transmit by single route only)

If ROUTE has already been configured with the MBR  setting,
reconfiguring ROUTE with this parameter  broadcasts all subsequent
Multicast Broadcast frames as  All Routes Broadcast frames.

Example To broadcast multicast frames simultaneously:

protocol route    source route mbr

Syntax protocol route    source route nodes  n

Replace n with a number of table entries from 8 to 255. If  you
type a number less than 8, 8 will be used.

Default 16 entries


Temp. Rev C -



NET .CFG Options Reference  295

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)

Example To allow twenty-four entries in the source-routing table:

protocol route    source route nodes 24


Temp. Rev C -



296 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993 (beta)


Temp. Rev C -



Architecture Diagrams  297

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

a p p e n d i x C Architecture Diagrams

These diagrams provide a technical overview of the NetWare
Requester for  OS/2 v2.01. They can help you understand what
components are used for the  various functions the Requester
performs (for example, which components are  used to support Named
Pipes).

Specifically, the diagrams illustrate:

u The major functions of the Requester components

u The different components of the Requester

u The relationships between components

You do not need to manually load the components shown in the
diagrams .  Select the settings you want in the Requester
installation program, and the  correct components will be loaded.
To change the settings later, simply run the  installation program
again.

Topics and architecture diagrams Page NetWare Requests from OS/2
Sessions 299

NetWare Core Protocol requests 299

File system requests 300 Protocol Requests from OS/2 Sessions 301

IPX-only requests 301

SPX requests 302

Named Pipes server requests 303

Named Pipes client requests 304

Note


Temp. Rev C -



298 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Protocol Requests from OS/2 Sessions (continued) 301

NetBIOS Submit requests using only Novell NetBIOS driver 306

NetBIOS Submit requests using only Novell NetBIOS driver with
Extended Services  loaded 307

NetBIOS Submit requests using either Novell or IBM NetBIOS driver
with LAN Services  loaded 308

NB30 NetBIOS requests using either Novell or IBM NetBIOS driver
with Extended  Services loaded 309

NetWare Requests from DOS/Windows Sessions 310

DOS/Windo ws NetWare Core Protocol requests 311

DOS/Windo ws file system requests 312 Protocol Requests from
DOS/Windows Sessions 313

DOS/Windo ws SPX- or IPX-only requests 313

DOS/Windo ws Named Pipes client requests 314

DOS/Windo ws SQL client "Get Server" requests 315

DOS and Windows NetBIOS requests 316

NetBIOS Submit requests using only Novell NetBIOS driver with
Extended Services  loaded 307

Sharing a Network Board 318

NetWare Requester and IBM software using ODINSUP to share a
network board 319

NetWare Requester and IBM software using LANSUP to share a network
board 320

Topics and architecture diagrams Page


Temp. Rev C -



Architecture Diagrams  299

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

NetWare Requests from OS/2 Sessions

NetWare Core Protocol Requests

NetWare Core Protocol requests go directly to the NetWare server
without  going through OS/2. Some of the NetWare utilities issue
this kind of request.  These requests are usually accompanied by
file system requests, shown on  page 300.

Figure K-7 NetWare Core  Protocol requests OS/2 application

Ring 3 Ring 0

NWDAEMON

NWCALLS or NWNET

NWREQ IPX LSL ODI driver

to the* NetWare server

Network board


Temp. Rev C -



300 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

File System Requests

File system requests are handled by OS/2 before being passed on to
the  NetWare Requester. Any program which manipulates files on the
network  makes this kind of request. These requests are alw ays
accompanied by  NetWare Core Protocol requests, shown on page299.

Figure K-8 File system requests

NWIFS

OS/2 application

Ring 3 Ring 0

NWDAEMON

OS/2 kernel

NWREQ IPX LSL ODI driver

to the* NetWare server

Network board


Temp. Rev C -



Architecture Diagrams  301

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Protocol Requests from OS/2 Sessions

IPX-Only Requests

IPX requests are issued by IPX applications, including the
Requester.

Figure K-9 IPX-only requests OS/2 applications that make IPX calls

Ring 3 Ring 0

IPXCALLS

IPX LSL ODI driver

to the* network

Network board


Temp. Rev C -



302 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

SPX Requests

SPX requests are issued by SPX applications. Some NetWare print
utilities and  API calls use SPX.

Figure K-10 SPX requests OS/2 applications that make SPX calls

Ring 3 Ring 0

SPDAEMON

SPXCALLS

SPX IPX LSL ODI driver

to the* network

Network board


Temp. Rev C -



Architecture Diagrams  303

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Named Pipes Server Requests

Named Pipes server requests are made by Named Pipes distributed
application  servers.

Figure K-11 Named Pipes server  requests

SPXCALLS NPCALLS IPXCALLS

NPSERVER SPX

Ring 3 Ring 0

IPX LSL ODI driver

to the* network

Network board

OS/2 kernel

OS/2 Named Pipes server application

Named Pipes requests are* received from the network. Replies to
Named Pipes* requests are sent out on * the network. The Named
Pipes daemon,* if configured as a server,* advertises on the
network.

NPDAEMON


Temp. Rev C -



304 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Named Pipes Client Requests

Named Pipes client requests are issued by Named Pipes distributed
application  clients.

Figure K-12 Named Pipes client  requests

NWIFS

NPCALLS IPXCALLS

NPDAEMON

NMPIPE SPX

Ring 3 Ring 0

IPX LSL ODI driver

to the* network

Network board

OS/2 kernel

OS/2 Named Pipes client application

Named Pipes requests are* received and sent.

The Named Pipes client* receives advertisements* from Named Pipes
servers * on the network.


Temp. Rev C -



Architecture Diagrams  305

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

NetBIOS Requests

What is NetBIOS

NetBIOS is a "device-independent" protocol that lets applications
use network  boards without knowing the specifics of how the
drivers for those boards work.

NetBIOS applications issue NetBIOS commands which are routed to a
specific  network board driver. That driver handles the
transmission of NetBIOS packets  over the network.

What is the Novell NetBIOS Emulator

Novell provides a NetBIOS emulator that allows applications
running on an  IPX-based network (such as NetWare) to communicate
using NetBIOS.

This NetBIOS emulator encapsulates NetBIOS packets inside of IPX
packets.  Then an ODI driver handles transmission of the IPX
packets over the network.  While your NetBIOS application
communicates using NetBIOS commands,  the NetBIOS emulator
actually transmits IPX packets.

The Novell NetBIOS emulator can only communicate with other
emulators  that use IPX. For example, if you have one workstation
running the NetBIOS  emulator and another workstation running
IBM's NetBIOS, the two  w orkstations cannot communicate.

However, the NetBIOS emulator can run on the same OS/2 workstation
as  other NetBIOS implementations, including the NetBIOS provided
with IBM  Extended Services or LAN Services. Or, the NetBIOS
emulator can run by  itself.

NetBIOS requests are issued by applications which use Novell
NetBIOS  emulation. If Extended Services or LAN Services is
installed, requests follow  a different path. See pages 307
through 309.


Temp. Rev C -



306 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-13 NetBIOS Submit requests using only Novell  NetBIOS
driver

NETBIOS

OS/2 applications that make NetBIOS Submit calls

Ring 3 Ring 0

NETAPI.DLL (Novell)

IPX LSL ODI driver

to the* network

Network board

NBDAEMON


Temp. Rev C -



Architecture Diagrams  307

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-14 NetBIOS Submit requests using only Novell  NetBIOS
driver with Extended Services loaded

NETBIOS (Novell)

OS/2 applications that make NetBIOS Submit calls

Ring 3 Ring 0

NETAPI.DLL (IBM)*

IPX LSL ODI driver

to the* network

Network board

NETSUB.DLL (Novell)

* The NETAPI.DLL that * ships with Extended* Services v1.0 is
invalid.* You must get an updated* NETAPI.DLL from IBM.


Temp. Rev C -



308 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-15 NetBIOS Submit requests using either Novell or  IBM
NetBIOS driver with LAN Services loaded

NETWKSTA.SYS (IBM) NETBIOS (Novell)

OS/2 applications that make NetBIOS Submit calls

Ring 3 Ring 0

NETAPI.DLL (IBM )

IPX LSL ODI driver

to the* network

Network board

NETBEUI (IBM)


Temp. Rev C -



Architecture Diagrams  309

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-16 NB30 NetBIOS requests using either Novell or  IBM
NetBIOS driver with Extended Services  loaded

ACSNETB.DLL (IBM)

NETBIOS.OS2 (IBM) NETBIOS (Novell)

OS/2 applications that make NB30 NetBIOS calls

Ring 3 Ring 0

IPX LSL ODI driver

to the* network

Network board

NETBEUI (IBM)


Temp. Rev C -



310 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

NetWare Requests from DOS/Windows Sessions

When you select "Support for Virtual DOS Sessions" in the NetWare
Requester installation program, the installation program adds
lines to the  CONFIG.SYS file to load the VIPX and VSHELL
components.

The NETWARE_RESOURCES and VIPX_ENABLED properties are also
created and added to the "DOS Settings" notebook of all DOS and
Windows  icons. These properties allow you to choose global
support, private support, or  no network support for each session.

u If you choose global support, VIPX and VSHELL are enabled for
the  session.

u If you choose private support, VIPX is enabled, VSHELL is not
enabled,  and you can manually load NETX.EXE

u If you don't load NETX.EXE, you receive IPX- and SPX-only
support.

u If you choose VIPX_ENABLED OFF , then no NetWare support is
loaded.

VIPX must be enabled for either Global (using VSHELL) or Private
(using  NETX) sessions to work.


Temp. Rev C -



Architecture Diagrams  311

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-17 DOS/Windo ws NetWare Core Protocol requests

NWREQ IPX

VSHELL*

NETX *

DOS/Windows application

Ring 3 Ring 0

DOSOS/2

VIPX

* Mutually exclusive options.

LSL ODI driver Network board

to the* NetWare server

Private sessions Global sessions


Temp. Rev C -



312 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-18 DOS/Windo ws file  system requests

NWIFS NWREQ IPX

DOS/Windows application

Ring 3 Ring 0

DOSOS/2

LSL ODI driver Network board

to the* NetWare server

OS/2 kernel

DOS kernel NETX

VIPX

Private sessions Global sessions


Temp. Rev C -



Architecture Diagrams  313

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Protocol Requests from DOS/Windows Sessions

Figure K-19 DOS/Windo ws SPX-  or IPX-only requests

IPX

DOS/Windows application

Ring 3 Ring 0

DOSOS/2

VIPX *

LSL ODI driver Network board

to the* network * DOS SPX support built in


Temp. Rev C -



314 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-20 DOS/Windo ws Named Pipes client requests

NWIFS NMPIPE SPX IPX LSL ODI driver Network board

to the* network

Ring 3 Ring 0

DOSOS/2

OS/2 kernel

NPCALLS

NPDAEMON DOS application

DOS kernel NETAPI.DLL IPXCALLS

Named Pipes requests are* received and sent. The Named Pipes
client* receives advertisements* from Named Pipes servers * on the
network.

Windows application


Temp. Rev C -



Architecture Diagrams  315

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-21 DOS/Windo ws SQL client "Get Server" requests

NWIFS NMPIPE SPX IPX LSL ODI driver Network board

to the* network

Ring 3 Ring 0

DOSOS/2

OS/2 kernel

 Windows NP applications only

NPCALLS

NPDAEMON DOS/Windows application

DOS kernel NETAPI.DLL*IPXCALLS

Named Pipes requests are* received and sent. The Named Pipes
client* receives advertisements* from servers on the network. *

VIPX

SQL client requests to see* server lists are sent.


Temp. Rev C -



316 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-22 DOS and Windows NetBIOS requests

IPX

Ring 3 Ring 0

DOSOS/2

LSL ODI driver Network board

to the* network

VIPX

NETBIOS.EXE

DOS application Windows application

Windows Kernel


Temp. Rev C -



Architecture Diagrams  317

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-23 DOS and Windows NetBIOS requests with  Extended
Services loaded

Ring 3 Ring 0

Virtual DOSOS/2

LANVDD.OS2 (IBM)

DOS applications that make NetBIOS calls

LANPDD.OS2 (IBM)

NETBIOS (Novell) IPX LSL ODI driver

To the* network

Network board

NETBEUI (IBM)

NETBIOS.OS2 (IBM)

NDIS driver

To the* network

Network board


Temp. Rev C -



318 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Sharing a Network Board

Ho w Does ODINSUP W ork?

ODINSUP translates NDIS transmissions from Extended Services or
LAN  Services into a form that complies with the ODI drivers.
ODINSUP also  translates transmissions received from the network
into a form readable by  Extended Services and LAN Services.

ODINSUP functions like a default protocol stack, meaning that it
accepts  requests from the Link Support Layer (LSL) that are not
specifically marked  for another registered protocol (such as IPX
or TCP/IP). When it receives  requests, ODINSUP passes them on to
the NDIS protocol stack.

ODINSUP allows IBM's Protocol Manager (found in Extended Services
and  LAN Services) to communicate with a network board without
having to be  aw are of the details of transmission on that board
(such as frame type).

Instead, the details are handled at the ODI driver level and then
transmissions  are passed on to the Link Support Layer, which in
turn passes them on to the  correct protocol stack or to ODINSUP.
ODINSUP translates the request to a  form understood by Protocol
Manager.

"Sharing a Network Board With IBM Software" on page 95 explains
more  about using ODINSUP.

ODINSUP is for using ODI drivers. LANSUP is for using NDIS
drivers.


Temp. Rev C -



Architecture Diagrams  319

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-24 NetWare Requester and IBM software using  ODINSUP to
share a network board

Extended* Services* (IBM)

LAN* Services* (IBM)

ODINSUP protocol * (Novell)

Protocol Manager (IBM)

IPX protocol * (Novell)

NetWare* Requester* (Novell)

ODI driver

to the* network

Network board

LSL


Temp. Rev C -



320 NetWare Workstation for OS/2 v2.01

NetWare Workstation for OS/2 v2.01  100-001413-001    23 April
1993

Figure K-25 NetWare Requester and IBM software using  LANSUP to
share a network board

Extended* Services* (IBM)

LAN* Services* (IBM)

Protocol Manager (IBM) LANDD.OS2 (IBM) IPX protocol * (Novell)

NetWare* Requester* (Novell)

to the* network

Network board

LSL LANSUP protocol * (Novell) NDIS driver
