Ref: 15990027
Title: Using XNS with 3+Open LAN Manager 2.0
Date: 12/27/90

Copyright 3Com Corporation, 1991.  All rights reserved.

The only transport protocol shipped by Microsoft with LAN Manager 2.0
is NetBEUI.  Microsoft's NetBEUI stack implements the same protocol as
3Com's NetBEUI/DLC protocol stack for 3+Open 1.1.  The only difference is
that 3Com's NetBEUI/DLC stack provides an 802.2 interface while Microsoft's
NetBEUI stack does not.  Thus, Microsoft's NetBEUI stack is much smaller on
DOS workstations than 3Com's NetBEUI/DLC stack.  Therefore, to interoperate
3+Open 1.1 and LAN Manager 2.0 machines on the same network, all you have to
do is run NetBEUI/DLC with 3+Open (referred to during installation as simply
DLC) and NetBEUI with LAN Manager 2.0.

However, few people use the NetBEUI/DLC stack with 3+Open.  Many people will
use Microsoft's NetBEUI stack, because it is the only one Microsoft provides
with 2.0, but if you are not running NetBEUI/DLC under 3+Open, there can be
no intercommunication.

3Com has a large family of transport protocols containing NetBEUI/DLC as
well as NBP, XNS, and TCP/IP.  3Com bundles NBP with 3+Open LAN Manager 2.0.
Its devices running NBP can fully communicate with 3+Open 1.1 devices running
NBP.

Many people, however, use XNS as their transport protocol for 3+Open instead
of NBP.  While NBP has many advantages--such as speed and a much smaller
driver size--you must still use XNS to access services such as 3+Open Mail.
This can be done by temporarily loading the XNS protocol, but many users
need to run XNS as their primary protocol to access both 3+Share and 3+Open
devices.  3Com will not release a XNS stack for LAN Manager 2.0 until we
release our LAN Manager 2.0 for 3Server product sometime in the first half
of 1991.  There is, however, a large demand now to be able to run XNS on a
LAN Manager 2.0 server.  The following procedure will allow you to use XNS
under LAN Manager 2.0.

   Caution:  3Com has not officially tested 3Com's XNS stack running
   under OS/2 1.2 and 2.0, and so does not support this procedure.  Use
   it at your own risk!

This procedure cannot be done fully automatically.  You will install the
stack so that it can be partially installed by the Microsoft SETUP program,
but you must also edit your configuration files manually.  If you run
SETUP again it will also remove your changes from the CONFIG.SYS
and you will have to implement the changes again after exiting the
SETUP program.


Installing the Transport Stack

1.  Create the directory C:\LANMAN\DRIVERS\PROTOCOL\XNS on your
LAN Manager 2.0 server.

2.  From the latest version of 3+Open (currently 1.1f), copy the following
files into the directory:  XNSNB.OS2, LGL.OS2, and STARTXNS.EXE.

These files can be found in the C:\3OPEN\OS2DRV\PROT\XNS directory on a
3+Open 1.1 server.

3.  Copy the entire XNS_NETBIOS section from C:\3OPEN\OS2DRV\PROTOCOL.3CM
on your 3+Open 1.1 server to a new PROTOCOL.INI file and place this new
PROTOCOL.INI in C:\LANMAN\DRIVERS\PROTOCOL\XNS on your LAN Manager 2.0
machine.

4.  Copy C:\3OPEN\OS2DRV\NETBIND.EXE on your 3+Open 1.1 server to your
C:\LANMAN\DRIVERS\PROTOCOL\XNS directory.

This is required because the binding under 2.0 is done by the redirector
itself.  We will be preventing the redirector from doing the bind function
later in this procedure so we will need to run NETBIND manually.

5.  Create an XIF file so the SETUP program can at least partially install
XNS for you.

The format of the protocol.XIF file is documented in the README.TXT file
in the C:\LANMAN\DRIVERS\XIF directory.  Enter the following information
into your XNS.XIF file:

   Model = XNS
   Path = PROTOCOL\XNS
   DeviceDriver = XNSNB.OS2
   DeviceDriver = LGL.OS2
   DeviceName = xnsnb$
   Type = NDIS_XPORT

6.  Run SETUP and attach the XNS protocol to the adapter you have selected.
Simply highlight the XNS protocol, click on the Add Protocol button, and save
the changes.

7.  Add /n to the end of the following line in your CONFIG.SYS (to prevent
the redirector from automatically doing a Netbind when it loads):

   IFS=C:\LANMAN\NETPROG\NETWKSTA.IFS /i:C:\LANMAN

8.  Add the following two lines to the beginning of your STARTUP.CMD, before
the block indicated as belonging to LAN Manager 2.0:

   DETACH C:\LANMAN\DRIVERS\PROTOCOL\XNS\STARTXNS.EXE
   C:\LANMAN\DRIVERS\PROTOCOL\XNS\NETBIND

This completes the installation of the transport stack.  If you have an
existing XNS network with a Locator and you wish to run this
machine on that network, you should be able to bring it up at this
point.  To run the Locator, follow these instructions:

1.  Copy the file LOCATOR2.3CM from C:\3OPEN\OS2DRV\PROT\XNS on your 3+Open
1.1 server to LOCATOR2.EXE in the C:\LANMAN\SERVICES directory on your LAN
Manager 2.0 server.

2.  Add the following line to the [SERVICES] section of LANMAN.INI:

   [SERVICES]
      locator = services\locator2.exe

3.  Add the following section to the end of LANMAN.INI:

   [LOCATOR]
      numnodes = 50
      numnames = 250

(Sample values are shown here.)

4.  To automatically start the Locator when the server starts, add the word
Locator to the Wrkservices line in LANMAN.INI.

You should now be able to bring up the server as an XNS machine running
Locator.


Note:  Locator may require more names per node than under 3+Open 1.1.
For 1.1 stations you will typically find three to four NetBIOS names
associated with each node, depending on (among other things) whether or
not you are running the messenger service.  Under LAN Manager 2.0, however,
a local NetBIOS name is created for every domain you want monitored.
Therefore if you have two entries for Othdomains as well as your own domain,
giving a total of three domains to monitor, you can potentially have eight to
ten NetBIOS names associated with this node.  Therefore, you may want to
set NUMNAMES to four to five times the size of NUMNODES, depending on the
configuration of domains on your network.