








                    Citrix
                    WinView
                    Application Notes


                    FTP PC/TCP 1.3 for OS/2






                    This application note is
                    for informational use only
                    and Citrix makes no
                    representations or
                    warranties with respect to
                    the contents or use of
                    this document or of any of
                    third-party products
                    discussed within.







July 19, 1994



Citrix Systems
210 University Drive
Suite 700
Coral Springs, FL 33071
(305)755-0559
FAX: (305)341-6880


Overview
--------

     This application note discusses the use of the FTP PC/TCP 1.3 for
OS/2 product (referred to as PC/TCP) with the Citrix WinView Application
Server (referred to as WinView) product. PC/TCP provides WinView the TCP/IP
stack and tool set. In and of itself, this product works very well within
WinView without many configuration changes. However, since the program was
initally written for OS/2, it only has a PM (Presentation Manager) install.
Included within this document are the instructions for installing this
software manually, circumventing the PM install. This provides the WinView
server with access to any TCP/IP network running, including the Internet.

     The intended audience for this document is an engineer who has
had hands on experience with WinView, TCP/IP, and other FTP products.

     The scenarios described in this document have been tested by
Citrix with PC/TCP software on WinView. Other variations to the
scenarios described in this document may work fine, however they have
not specifically been tested by Citrix.  In order to maximize your
chance for success, you should use the specified revision levels of
all software products described in this document and stay within the
bounds of the features and functions described in this document.

     Please note that this application note is a living document and
will be modified as new information and versions of the software
described herein become available.  Make sure you have the latest
version of this document before you begin.  The latest version is
always available in the Citrix Forum on CompuServe.


Benefits of the WinView/FTP PC/TCP solution
-------------------------------------------


    The PC/TCP product gives many advantages to the WinView user, two of
which are mentioned here. First and perhaps most importantly, Windows
apps (using winsock), and DOS apps (using PC/TCP) gain access to the
TCP/IP stack for moving data and querying for information from TCP/IP
networks. Secondly, the WinView server will now support OUTBOUND
services to TCP/IP networks, such as telnet, ftp, email, and ping.


Requirements
------------

     To use PC/TCP on a WinView application server you will need to
have the following:

     Software Requirements
          - Citrix WinView 2.2 or 2.21
          - FTP PC/TCP 1.3 for OS/2

     Hardware Requirements
          - WinView server
               > 486DX-25 CPU or larger
               > 12 meg memory or more
               > NetWare supported network adapter


Configuration Notes
-------------------

    Since the basic model of the WinView Application Server
doesn't change with the addition of PC/TCP, the desired number of
concurrent PC/TCP users will still determine the hardware
configurations of the WinView server. The maximum number of concurrent
PC/TCP users supported on a single WinView server is determined by the
hardware specifications of that WinView server. Memory is the most
critical resource for the WinView server in determining the number of
users.  Use the following rule of thumb: 8 megabytes base memory plus
3 megabytes per Windows session, plus 1 megabyte per DOS session, and
.5 megabytes per OS/2 session. For example, a 5 user system might
require the following:

        User    Average sessions                Mem.Required
        ----    ----------------                ------------
        1       1 Windows                       3.0 Mb
        2       1 OS/2                          0.5 Mb
        3       1 DOS                           1.0 Mb
        4       1 Windows, 1 OS/2               3.5 Mb
        5       2 OS/2, 2 DOS, 1 Windows        6.0 Mb
        ----------------------------------------------------
        Total suggested memory required:        14 Mb ( 16 Mb )
        NOTE: Round up to the next number divisible by 8.

Remember, to go beyond 16 megabytes, you will need either a EISA
system or a 32-bit MCA system.  Also, you should increase the CPU size
as the user count goes up.


Limitations of PC/TCP under WinView
-----------------------------------

     As previously mentioned, the installation of PC/TCP is a Presentation
Manager install. Since PM isn't supported under Citrix WinView, a manual
installation is required, and is detailed below. Also, in the
configuration described below, the telnetd INCOMING service daemon is
NOT supported.

     As new features and functionality are tested, they will be included in the
latest version of this document.


Installation
------------

        The following 11 step process is required in order to fully and
properly install PC/TCP:

    1) Create a subdirectory
        Login as the administrator on the CONSOLE of WinView. Go to an
        OS/2 prompt, and issue the following command:
                MD C:\PCTCP
        This directory can be created on any local drive, so C: and
        above are valid.

    2) XCOPY the diskettes to subdirectory
        The diskettes should be copied in order from 1 to 5. Since the
        diskettes contain subdirectories, XCOPY must be used. Insert
        diskette 1 into the drive A: drive, and at the OS/2 prompt,
        issue the following command:
                XCOPY A: C:\PCTCP /S /E
        After the copy is done, repeat the command for the next four
        diskettes.

    3) Modify CONFIG.SYS
        Using the system editor (E.EXE), make the following changes to
        the CONFIG.SYS file:
                  I) Add C:\PCTCP\DLL to end of LIBPATH statement
                 II) Add C:\PCTCP\BIN to end of PATH statement
                III) Add C:\PCTCP\ETC to end of DPATH statement
        In addition, at the end of the CONFIG.SYS (after the Netware
        statements:
                 IV) Add the following lines:
                     SET PCTCP=C:\PCTCP\ETC\PCTCP.INI
                     DEVICE=C:\PCTCP\DRV\PROTMAN.OS2 /I:C:\PCTCP\DRV
                     DEVICE=C:\NETWARE\ODINSUP.SYS
                     DEVICE=C:\PCTCP\DRV\INT61VDD.SYS
                     DEVICE=C:\PCTCP\DRV\SOCKET.OS2
                     IFS=C:\PCTCP\DRV\NFSIFS2.SYS
                     RUN=C:\PCTCP\BIN\NETBIND.EXE

    4) Create or modify STARTUP.CMD
        Make sure the STARTUP.CMD file has the following line:
                tcpmgr start
        NOTE: the 'start' option to tcpmgr MUST be lowercase

    5) Modify all AUTOEXEC.BAT files:
        All AUTOEXEC.BAT files should contain the following lines:
                C:\PCTCP\BIN\INST61
                SET PCTCP=C:\PCTCP\ETC\PCTCP.INI
        The INST61 TSR adds support for FTP FOS and Windows
        applications. In addition, the PATH should include
        'C:\PCTCP\DLL' for Windows TCP/IP DLLs.

    6) Modify NET.CFG
        Modify C:\NETWARE\NET.CFG to support NDIS to ODI translation
        (ODINSUP). This involves adding a new section for ODINSUP, as
        well as adding new frame types for the link driver.

        Listed below is an example for the 3c507 adapter (3COM):

                link driver 3c507
                   int 10
                   port 330
                   frame ETHERNET_II                ; add this line
                   frame ETHERNET_802.3
                   frame ETHERNET_802.2             ; add this line
                   frame ETHERNET_SNAP              ; add this line
                   protocol IPX 0 ETHERNET_802.3    ; add this line
                link support
                   buffers 20 1514
                protocol stack ipx
                   sockets 100
                protocol stack spx
                   sockets 100
                netware requester
                   sessions 30
                   Directory Services Off
                protocol ODINSUP                    ; add this line
                   bind 3c507                       ; add this line

        Here is another example for a token-ring adapter:

                link driver token
                   slot 4
                   frame token-ring_snap        ; add this line
                   frame token-ring
                   protocol IPX e0 token-ring   ; add this line
                link support
                   buffers 20 1514
                protocol stack ipx
                   sockets 100
                protocol stack spx
                   sockets 100
                netware requester
                   sessions 30
                   Directory Services Off
                procotol ODINSUP                ; add this line
                   bind token                   ; add this line

    7) Create PCTCP.CMD
        Create C:\PCTCP\BIN\PCTCP.CMD with the following lines:

                ifconfig nd0 193.7.30.65 netmask 255.255.255.0
                ifconfig lo0 localhost
                route add default 193.7.30.1 1
                hostname winview.citrix.com
                minstart VDD_D

        193.7.30.65 is an example IP address and 255.255.255.0 is an
        example mask. These values should be the desired IP address
        and netmask of the Citrix WinView machine. The hostname
        'winview' is also an example, and should be replaced with what
        you specified as HOSTNAME during the WinView installation.

    8) Create PROTOCOL.INI
        Create C:\PCTCP\DRV\PROTOCOL.INI file with the following
        lines:
                [SOCKET]
                drivername=$SOCKET
                bindings=X3C507

                [3C507]

        Note that this example is for the 3C507 adapter. The bindings
        section requires an X for link drivers starting with a number.
        3C507 should be replaced by the link driver from the NET.CFG.
        Also be sure the enter a blank line after the [3C507] line.

    9) Create PCTCP.INI
        Create C:\PCTCP\ETC\PCTCP.INI with the following lines:

                [pctcp addresses]
                ip-address-1 = 193.7.30.65
                network-mask-1 = 255.255.255.0
                network-router-1 = 193.7.30.1
                hostname = winview
                domain = citrix.com
                name-server-1 = 193.7.30.67
                name-server-2 = 193.7.30.1

                [pctcp general]
                user=winview
                etc-dir = c:\pctcp\etc
                time-zone = EST5EDT

                [pctcp daemons]
                inetd = yes

        Again, please note that the ip-address-1, network-mask-1, and
        network-router-1 are example addresses and mask. Hostname and
        user should be set to the Citrix WinView HOSTNAME. The
        time-zone depends on location. Domain should be set to your
        network domain.

    10) Create HOSTS file
        Create C:\PCTCP\ETC\HOSTS to contain addresses of other hosts
        on the network. The format of the file is as follows:

        # address       hostname                alias

        127.0.0.1       loopback
        193.7.30.65     winview.citrix.com      winview

    11) Create RESOLV.CON
        Create C:\PCTCP\ETC\RESOLV.CON if you have a Domain Name
        Server (DNS). The RESOLV.CON file tells PC/TCP where the name
        server is. The format of the file is:

        domain CITRIX.COM
        nameserver 193.7.30.67
        nameserver 193.7.30.1


Operation
---------

    The operation of PC/TCP should be invisible to the user once
installed. From a Windows application using Winsock, communcation with
those services provided should execute without problems. In addition,
the new OS/2 tools (ftp, telnet, etc) will then be available as normal
commands at the OS/2 prompt.


Compatibility
-------------

     There are no known hardware incompatibilities when using
PC\TCP and WinView at this time.  When selecting a hardware
platform for WinView, make sure you choose from the list of
supported hardware devices in the "Citrix Compatibility Guide".


Diagnosing Problems
-------------------

Common problems (and solutions):

        1) Can't find any other hosts by name - Check to see that the
           nameserver information is correct in RESOLV.CON. Invalid
           information in this file will prevent this from happening.

        2) Path problems - be sure to provide your OWN values for the
           values in different PC/TCP supporting files. This includes
           ip-address values, nameserver values, hostnames, and most
           importantly the drive letter you installed the software on.

        3) Strange error message about NFSIFS2.SYS - Be sure that the
           line added to the CONFIG.SYS file was an 'IFS=' line, and
           not a 'DEVICE=' line for the NFSIFS2.SYS.

        4) Can't get outside of local network - be sure to have
           included the 'route add default' line to the PCTCP.CMD
           file.

        5) Network errors or problems - be sure that the ORDER of the
           frame types in the NET.CFG file are correct, as they appear
           in this document.

        6) Couldn't load network - Make sure that the /I: in the
           PROTMAN.OS2 device line in the CONFIG.SYS file is in
           uppercase.

    When no further progress can be made, contact FTP Technical
Support for assistance. They will have the most complete information
about their own product. If they can't help, contact Citrix Technical
Support.
