Ref: 16530021
Title: How Sessions Are Handled Across Multiple Networks
Date: 9/28/90

Copyright 3Com Corporation, 1991.  All rights reserved.

What is the relationship between the SESSIONS= parameter in the netx= line
of the LANMAN.INI file and the MAXUSER= parameter?

MAXUSERS should equal the aggregate total of sessions in all the netx= lines.
For example, in the following configuration, MAXUSERS=250.  (100+50+100.)

net1=nbp$,0,,100,150,16
net2=xns$,0,,50,150,16
net3=dlc$,0,,100,150,16

(Note:  This is not currently a supported configuration.  These parameters
are used as an example only.)

MAXUSERS defines the maximum number of NCBs that can be outstanding (and
hence the maximum number of sessions).  The table that handles and manages
the NCBs is in a shared memory region, so MAXUSERS must be the aggregate
total of sessions across all the netx= lines.

For each netx= line, LAN Manager posts one NCB listen to receive incoming
calls.  There is no reason to have more than one or two NCBs outstanding
since only one call-receive can be handled at a time.

This requires the LAN administrator to know approximately how many users will
be accessing the server on any given protocol.  If the administrator
underestimates the number of sessions on a given protocol and sets the netx=
line to less than the number in MAXUSERS, the administrator runs the risk of
seeing NCB errors in the error log that point to the local session table
being full.  Thus, it is a good idea to keep a buffer of 5-10 sessions on
the netx= line, in case someone boots on another protocol.
