May 10, 1994

I have developed this document due primarily to the fact that there
has been a LOT of discussion in this forum about user's needing
Virtual NetBIOS support, and in SOME cases actully having to
choose another product due to lack of Virtual NetBIOS support in the
Citrix products!

The purpose of this document is to describe the Citrix WinView or
Citrix Multi-User configuration required to support Virtual IPX
and Virtual NetBIOS under Citrix using a combination of the IBM
NTS/2 (Network Transport Service) Lan Adapter & Protocol Support
(LAPS) + Citrix NetConnect products.  (LAPS is READILY available thru
All IBM channels)

The fundamentals of this configuration are that LAPS manages the
multiple protocol support, providing support for IPX/SPX, NetBIOS and
TCP/IP (if desired) through the NDIS stack while Netware ODI support
converted to the NDIS stack via the ODI2NDI.SYS device driver.

In our environment, this configuration provides the support for IBM
MCA LANStreamer and Madge EISA Token-Ring Adapters, that initially
were not supported with OS/2 ODI Drivers.  We have been using this
configuration for many months in a production mode, and although we do
not have a NEED for Virtual NetBIOS under Citrix, (though we have used
it in test-mode) it is the EXACT same configuration we use for our OS/2
workstations which DO use Virtual NetBIOS sessions.  While we have not
yet tested it, we are optimistic that the LAPS NDIS drivers will allow
us to run PC/Support under Citrix in the same fashion that it can be
run in a DOS VBM under OS/2!  This too is discussed in a ReadMe.nts file
which is shipped with LAPS.

The following sections of this document detail the new Config.Sys
and Net.CFG statements, as well as the Protocol.ini file which will be
created by the NTS/2 LAPS install for a Token-Ring Configuration.  If
you are using Ethernet, there will be a bit more work required, but
hopefully the basics are covered well enough that you will be able to
convert this config. to an Ethernet one relatively easily. One IMPORTANT
fact to be noted, is that since Citrix does not support PM apps, you
cannot run the LAPS install under Citrix.  The way that we configured it
(and the way I would recommend you do as well) is to install LAPS on an
OS/2 workstation (it will be easiest with the EXACT SAME brand/type NIC,
but not required), and then just move the appropriate files and configuration
statements to your Citrix server, and you're set!  The LAPS
documentation will provide the installation details, and will enable
you to make the proper configuration changes to match YOUR
environment.


ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ ORIGINAL NetConnect CONFIG.SYS statements: ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
LIBPATH=C:\NETWARE;C:\OS2\DLL;C:\OS2\DLL\CTX;C:\;C:\OS2\MDOS;C:\OS2\DLL\CTXNET
SET PATH=C:\OS2;C:\OS2\CTX;C:\OS2\CTX\OPS;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\NETWARE;
SET DPATH=C:\OS2;C:\OS2\CTX;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\NETWARE;

REM ***** NetWare Requester Statements BEGIN **********

REM **************************************************
REM ***** All NetWare lines below begin with *********
REM ***** an extra REM. Remove first REM     *********
REM ***** from each line once the correct    *********
REM ***** LAN adapter device driver is set.  *********
REM **************************************************

REM
REM NETWORKRESOURCES=USER
REM REM --- NetWare Required Statements
REM DEVICE=C:\NETWARE\LSL.SYS
REM RUN=C:\NETWARE\DDAEMON.EXE
REM REM
REM REM --- LAN Adapter DEVICE Statement
REM DEVICE=C:\NETWARE\OTHER.SYS
REM REM
REM DEVICE=C:\NETWARE\IPX.SYS
REM REM
REM REM --- SPX Support For OS/2 Sessions
REM DEVICE=C:\NETWARE\SPX.SYS
REM RUN=C:\NETWARE\SPDAEMON.EXE
REM REM
REM REM -- Named Pipes Client Support
REM REM DEVICE=C:\NETWARE\NMPIPE.SYS
REM REM RUN=C:\NETWARE\NPDAEMON.EXE
REM REM
REM REM -- Named Pipes Server Support
REM REM DEVICE=C:\NETWARE\NMPIPE.SYS
REM REM DEVICE=C:\NETWARE\NPSERVER.SYS
REM REM RUN=C:\NETWARE\NPDAEMON.EXE CS410-1
REM REM
REM REM --- NetWare Requester Modules
REM DEVICE=C:\NETWARE\NWREQ.SYS
REM IFS=C:\NETWARE\NWIFS.IFS
REM RUN=C:\NETWARE\NWDAEMON.EXE
REM REM
REM REM --- NetBIOS Emulation For OS/2 Sessions
REM REM DEVICE=C:\NETWARE\NETBIOS.SYS
REM REM RUN=C:\NETWARE\NBDAEMON.EXE
REM REM
REM REM --- NetWare Support for DOS and WINDOWS Applications
REM DEVICE=C:\NETWARE\VIPX.SYS
REM DEVICE=C:\NETWARE\VSHELL.SYS
REM REM
REM REM --- Driver for printing under DOS with NetWare
REM REM
REM DEVICE=C:\OS2\MDOS\LPTDD.SYS
REM REM
REM ***** NetWare Requester Statements END **********
FILES=169
LASTDRIVE=H

====================================================================

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³New LAPS Config.sys section:³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
REM --- START NETWARE / LAPS SECTION ---

DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM - LAPS Message Device Driver
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM - Protocol Manager
DEVICE=C:\IBMCOM\PROTOCOL\LANDD.OS2 - NetBIOS Driver
DEVICE=C:\IBMCOM\PROTOCOL\LANDLLDD.OS2 - NetBIOS Driver
DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2 - ??
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2 - Virtual NetBIOS Driver

REM --- NetWare Required Statements
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE

DEVICE=C:\IBMCOM\PROTOCOL\ODI2NDI.OS2 - Converts all ODI Calls to/from the
                                        NDIS Protocol Stack

DEVICE=C:\NETWARE\ROUTE.SYS - Only required for Token-Ring LAN using
                              Source Routing
REM --- IPX Support for OS/2 Sessions
DEVICE=C:\NETWARE\IPX.SYS

REM --- SPX Support For OS/2 Sessions
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE

DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS GLOBAL

REM --- LAPS NetBIOS Drivers
DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 - NetBEUI driver
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2 - NetBIOS driver

REM --- LAN Adapter DEVICE Statement
DEVICE=C:\IBMCOM\IBMTRDB.OS2 ==Ä¿  NIC Driver for IBM MCA LanStreamer Card
                                ³-- OR
DEVICE=C:\IBMCOM\SMARTND.OS2 ==ÄÙ  NIC Driver for Madge EISA Smart RingNode

REM -- Named Pipes Server Support                                                                                                        EISA Token-Ring Card
REM DEVICE=C:\NETWARE\NMPIPE.SYS
REM DEVICE=C:\NETWARE\NPSERVER.SYS
REM RUN=C:\NETWARE\NPDAEMON.EXE NPserver-name

RUN=C:\IBMCOM\PROTOCOL\LANDLL.EXE - ??
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE - Binds Protocol to NIC Device Driver
RUN=C:\IBMCOM\LANMSGEX.EXE - Uses LANMSGDD.OS2 and writes status messages to
                             LANTRAN.LOG file as devices bind and/or load

REM --- NetWare Requester Modules
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE

REM --- Driver for printing under DOS with NetWare
DEVICE=C:\OS2\MDOS\LPTDD.SYS

REM --- END NETWARE / LAPS SECTION ---
====================================================================

New NET.CFG:

preferred server xxxxx
link support
   buffers 14 4096
Link driver IBMTRDB (or SMARTND)
   max frame size 4096
   int 10
protocol stack ipx
   sockets 200
protocol stack spx
   sessions 200
netware requester
   cache buffers 16
   sessions 30
   Directory Services Off
   preferred xxxx-xx
   file handles 80
protocol route
   source route
==========================================

Minimal C:\IBMCOM\PROTOCOL.INI file for an IBM LANStreamer Card:  The
PROTOCOL.INI generated by the LAPS install be be MUCH larger, but for
our needs, this is all that is required, and makes the list of
configuration statements a bit more manageable in size.

[PROT_MAN]

   DRIVERNAME = PROTMAN$

[IBMLXCFG]

   IBMTOKDB_nif = IBMTOKDB.nif
   LANDD_nif = LANDD.NIF
   ODI2NDI_nif = ODI2NDI.NIF

[ODI2NDI_nif]

        DriverName = ODI2NDI$
        Bindings = IBMTRDB_NIF
        NetAddress = "xxxxxxxxxxxx"
        Token-Ring = "yes"
        Token-Ring_SNAP = "no"

[IBMTRDB_NIF]

        DriverName = IBMTRDB$
        NetAddress = "xxxxxxxxxxxx"
        xmitbufsize = 4208


Well, that's it!  Once configured, you should experience no real
changes in the way that Citrix works, EXCEPT for the fact that in our
configuration, when using an IBM LanStreamer card in a IBM MCA-based
Citrix server, ONLY IPX sessions are supported!!  Using a Dell
EISA-based Citrix Server with a Madge SmartNode Adapter BOTH IPX & SPX
sessions work fine!  Using Either adapter, VERY good Network
throughput is acheived (somewhere in the neighborhood of 700-900Kbs
for a single Citrix session, with aggregate throughput rates of
1500-2000Kbs!)

I have read comments in this forum that the configuration listed above
is currently unsupported by Citrix, but it is MY feeling that LAPS is unsup-
ported due to the fact that it has not been tested, rather than for reasons
based-upon Results of testing...  I sincerely hope that the Citrix
development staff will test this configuration, and if necessary, make
changes to NetConnect to resolve problems which may appear in user's
environments (or our own, in terms of SPX traps using the
LanStreamer card) making Citrix an even BETTER environment to run our
remote applications!!

I am willing to answer specific questions about our development of the
LAPS/Netware configuration, but I don't LIVE on C-Serve, and may not
be very prompt at responding to your questions.  I will also be unable
to answer questions which pertain to how this configuration might be
expected to function in YOUR environment beyond the generalities of the
initial LAPS/Netware setup.  While I KNOW that this may Sound like I
am unwilling to assist, I wouldn't have spent SEVERAL Hours developing
this document if I were not honestly trying to promote the advancement
of Citrix! (No, I am not related to anyone working at Citrix <grin>).

Many thanks to James Gill & Don Elledge for the initial development of
the LAPS/Netware configuration in our OS/2 environment, which was then
adapted to the higher-speed NICs in our Citrix Servers.  They are the
TRUE brains behind this configuration!!

Damian Sigman
Central Soya Co. Inc.
Fort Wayne, Indiana

Mail ID's:
72350,3114
dsigman@censoya.attmail.com --> checked daily...