Ref: 11640040
Title: Creating a 3+Open XNS Netconnect Server
Date: 10/2/89

Copyright 3Com Corporation, 1991.  All rights reserved.

The 3+Open product line does not have a XNS Netconnect product,
basically because the XNS protocol stack built on the Network
Driver Interface Specification (NDIS) already has this feature
built in.  Following is a step-by-step procedure explaining how
to build a XNS Netconnect Server.

Caution:  The following procedure is not officially supported by
3Com.  Use it at your own risk!

Any of 3Com's supported adapter cards can use this feature.
Remember that two cards will be required in the Netconnect
server, but there will be only one protocol stack.  In the
following example, the LanMan Compaq has the two network
interface cards; an Ethernet card for the primary network, and a
Token Ring card for the secondary network.

                 +--------+
                 | Compaq |
+---------+      | LanMan |                       +---------+
| 3Server |      | 3   3  |                       | 3S/400  |
| Locator |      | C   C  |                       | Locator |
| File/Pr |      | 5   6  |       +----------+    | LanMan  |
| Name    |      | 0   0  |       | Compaq   |    | Name    |
| Mail    |      | 5   3  |       | Portable |    | Mail    |
+-^-------+      +-^---^--+       +----------+    +--^------+
  |                |   |            |                |
 <+----------------+> <+------------+----------------+>
  Network #00040030      Network #00040050


Following is the CONFIG.SYS listing:

DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\PROTMAN.OS2 /I:C:\3OPEN\SERVER\LANMAN
\DRIVERS
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\tlnk.os2
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\elnkpl.os2
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\xnsnb.os2
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\lgl.os2 -m50


1.  Set the adapter cards for the correct DMA, Interrupt, and I/O
addressing.

2.  Change to the \3OPEN\SERVER\LANMAN\DRIVERS\PROTOCOL.INI
subdirectory and edit the ADAPTERS file to reflect the hardware
settings.  (Default settings are shown at the end of this procedure.)

3.  Edit the Protocols section of the PROTOCOL.INI file as shown in
steps a-d.  (Default settings are shown at the end of this procedure.)

a.  In the BINDINGS statement, type the primary adapter card name
after the = sign.  Delimit with a space, then continue the
BINDINGS statement type in the secondary adapter card, in this
example TOKENLINK.

b.  In the STOREFORWARD statement, type the word YES after the =
sign to enable the forwarding of packets in the protocol stack.

c.  In the ROUTE1 statement, type the network number of the
primary adapter after the = sign.  The default for this parameter
is a decimal value. If you want to enter a hex value, type a
leading '0x' before the hexadecimal number.

d.  In the ROUTE2 statement, type the network number of the
secondary adapter after the = sign.  The default for this
parameter is a decimal value.  If you want to enter a hex value,
type a leading '0x' before the hexadecimal number.

4.  Reboot your system.  You now have a XNS Netconnect server.

For your workstation to communicate with a LanManager on the other
side of a Netconnect, use the 3NB command to register
yourself on the second network and a 3NB USE command to access a
server on the other network.  3+Open Name and 3+Open Mail operate the
same as in a 3+ environment with Netconnect.  The Name services must be
informed about the remote networks.

;**********************************************************
;%VER Protocol Manager Initialization File Template, v.1.0d
;The following are default sections for various adapters and
;protocols.
;***********************************************************

;ADAPTERS

; 3Com 3C603 adapter
[TOKENLINK]
  DRIVERNAME = TLNK$
  Interrupt = 2
  IOAddress = 0x310
  DMAChannel = 0

; IBM Token Ring
[TOKEN_RING]
  DRIVERNAME = IBMTOK$
  RECVBUFS = 2
  RECVBUFSIZE = 256
  XMITBUFS = 1
  XMITBUFSIZE = 2040

; 3Com 3C501
[ETHERLINK]
  DRIVERNAME = ELNK$
  INTERRUPT = 3
  IOADDRESS = 0x300
  DMACHANNEL =

; 3Com 3C505
[ETHERLINK_PLUS]
  DRIVERNAME = ELNKPL$
  INTERRUPT = 5
  IOADDRESS = 0x300
  DMACHANNEL = 7

; 3Com 3C503
[ETHERLINKII]
  DRIVERNAME = ELNKII$
  INTERRUPT = 3
  IOADDRESS = 0x300
  DMACHANNEL = 1
  XMITBUFS = 1

; 3Com 3C523
[ETHERLINK/MC]
  DRIVERNAME = ELNKMC$

; 3Com 3Server on-board ethernet adapter
[3SERVER]
  DRIVERNAME = E3S386$
  RECVBUFS = 32


;PROTOCOLS

; 3Com XNS protocols
[XNS_NETBIOS]
  DRIVERNAME = XNSNB$
  BINDINGS = ETHERLINK_PLUS TOKENLINK
  MAXSESS = 32
  MAXNCB = 32
  MAXDGBUF = 2
  MAXSNBUF = 8
  MAXRECVBUF = 12
  RECVWINDOW =
  XMITWINDOW =
  MAXCACHE = 2
  MAXREMMAP = 2
  MAXLCLMAP = 2
  STOREFORWARD = YES
  HARDWAREBUF = NO
  LOCATOR = NO
  ROUTE1 = 0x40030
  ROUTE2 = 0x50030
  ROUTE3 =
  ROUTE4 =
  ROUTE5 =
  ROUTE6 =
  ROUTE7 =
  ROUTE8 =

; NetBEUI ; works with DLC Protocols
[NETBEUI]
  DRIVERNAME = MNETB$
  BINDINGS = DLC

; DLC Protocols
[DLC]
  DRIVERNAME = MDLC$
  BINDINGS =

;**** END OF FILE ****
[XNSICM]
  DRIVERNAME = XNSICM$
  BINDINGS = XNS_NETBIOS


rem                        CONFIG.SYS

rem This file contains system information used when the system is
rem booted up.  See the MS OS/2 setup manual for a description of
rem each command.

buffers=30
shell=c:\os2\rbin\command.com /P /e:1024 c:\os2\rbin
protshell=c:\os2\pbin\shell.exe C:\OS2\PBIN\cmd.exe /k c:\os2init.cmd

rmsize=640
protectonly=YES
break=OFF
fcbs=16,8
threads=100
iopl=YES
libpath=C:\3OPEN\SERVER\LANMAN\NETLIB;c:\;c:\os2\lib
memman=SWAP,MOVE
DISKCACHE=384
maxwait=3
swappath=C:\

rem mouse options: 00 - Mouse Systems, 01 - Visi-On, 02 - Microsoft serial
rem                03 - Microsoft Bus, 04 - Microsoft Inport
rem             ps2mou - PS/2 Microsoft, ps2gmou - PS/2 generic

rem device=c:\os2\dev\mousea03.sys
device=c:\os2\dev\pointdd.sys
rem use either com01 (AT) or com02 (PS/2)
rem EGA.SYS will not load if protectonly is set to yes
rem device=c:\os2\dev\ega.sys
rem device=c:\os2\dev\ansi.sys
rem Use the LAN Manager spooler instead
rem run=c:\os2\bin\spool.exe c:\os2\spool /o:lpt1 /d:lpt1

rem The rest of the file may contain commented-out lines.  Delete the
rem word "rem" from the begining of the command lines if that feature
rem is wanted.

rem The following lines enable the Code Page support drivers.

rem devinfo=scr,ega,c:\os2\dev\viotbl.dcp
rem devinfo=kbd,US, c:\os2\dev\keyboard.dcp
rem codepage=437,850
devinfo=lpt1,5202,c:\os2\dev\5202.dcp,rom=(437,850)
rem device=c:\os2\dev\vdisk.sys 256 512 16

REM **LM** ======================== OS/2 LAN MANAGER ========================
REM =========================== Do not modify this block ====================
REM **LM** <net1|XNS|Host-Based XNS protocols><ELNKPL|EtherLink Plus 3C505-B>
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\PROTMAN.OS2 /I:C:\3OPEN\SERVER\LANMAN\DRIVERS
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\tlnk.os2
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\elnkpl.os2
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\xnsnb.os2
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\lgl.os2 -m50
REM **LM** <net1|XNS|Host-Based XNS protocols><ELNKPL|EtherLink Plus 3C505-B>
DEVICE=C:\3OPEN\SERVER\LANMAN\NETPROG\NETWKSTA.SYS /I:C:\3OPEN\SERVER\LANMAN
DEVICE=C:\3OPEN\SERVER\LANMAN\NETPROG\NAMPIPE.SYS /I:C:\3OPEN\SERVER\LANMAN
REM **LM** ==================================================================
device=\3open\server\lanman\drivers\com01a.sys
DEVICE=\3OPEN\SERVER\LANMAN\drivers\xnsicm.os2
