
APAR= II09020
IBM LAN CLIENT AND CLIENT ACCESS/400 COEXISTENCE

                                             LAST UPDATE 1/2/97

This Informational APAR contains data on Client Access
400 for Windows (CA400WIN) and Client Access for DOS with
Extended Memory (CA400EXTDOS) coexistence with the IBM LAN
Client product. A FAQ (Frequently Asked Questions)
is listed below.

Client Access should run across any 802.2 protocol stack.
Communication problems specific to a particular stack
are the responsibility of the stack provider.

Client Access development has tested specific
configurations of LAN Client 2.0 / 2.1 and Client Access.
The following is a list of environments that have been
tested.  Support for any Client Access problem unique
to running Client Access over LAN Client 2.x is provided
by LAN Client Support.

Client Access for DOS with Extended Memory is NOT
currently supported using IBM LAN Client 2.0 or 2.1.  Users
may experience intermittent PC hangs or communication
errors, particularly when using Work Station Function(WSF).
Performing the STARTFLR function leads to a General Protection
Fault when switching from the Novell drive to the hard drive
and it also will not load up Windows 3.1 if Novell is installed
on the PC.  If Novell is not installed on the PC, Windows 3.1
will load up; however, the PC will softlock when attempting to
browse a system folder using File Manager or when copying
files to and from the shared folder.

Client Access for Windows 3.1, CA400WIN, is
not currently supported via ANYNET over the
LAN Client 2.0 TCP/IP protocol stack.
See II08755 for the current list of supported
TCP/IP stacks.

Client Access for Windows 3.1, CA400WIN, has not
been tested for Novell coexistence over LAN Client
2.0 protocol stacks.  Client Access for Windows 3.1,
CA400WIN, has been tested for Novell coexistence
only over LAN Client 2.1 protocol stacks as indicated
in the supported adapter list.

Client Access for Windows 3.1 V3R1M1 has successfully
been tested with Lan Client 2.0 stand-alone
802.2 stack, subject to the restrictions in the
LAN Client lnclient.txt file.
The following subset of LAN Client 2.0 supported adapters
were tested with Client Access for Windows 3.1
R311.
- IBM Auto LANStreamer PCI Adapter(card p/n 04H8095)
- IBM Auto 16/4 Token-Ring ISA Adapter(card p/n 92G7632)
- IBM Auto 16/4 Token-Ring MC Adapter(card p/n 92G7682)
- IBM Token-Ring 16/4 Adapter/A(card p/n 74F9410)

The following subset of LAN Client 2.1 supported adapters
were tested with Client Access for Windows 3.1
R311 (including Novell).
- IBM Turbo 16/4 Token-Ring Adapter(card p/n 72H3482)
- IBM Auto Wake Token-Ring Adapter(card p/n 55H6760)
- IBM Token-Ring 16/4 ISA-16 Adapter(card p/n 73G2032)
- IBM PCI Token-Ring Adapter(card p/n 41H8900)
- IBM Token-Ring Auto 16/4 Credit Card Adapter(card p/n 04H6922

All testing was performed with PC DOS 7.0 with EMM386.EXE
at version 4.50.

If you experience problems, please consult your LAN
Client documentation.  Some common errors:
- Your LAN Adapter is not one of the supported adapters.
- You do not have EMM386 version 4.49.  Note that MS DOS
  6.22 contains an EMM386 version of 4.48.
- You do not have enough extended memory.  Although
  LAN Client reduces conventional memory usage, it
  requires significantly more extended memory then
  LAN Support Program.  LAN Client memory usage
  varies from 877K to 2.4Mb.  Consult the LAN Client
  documentation for specific memory requirements.

Frequently asked questions (FAQ):
Q1) What is IBM Lan Client?
A1) IBM LAN Client provides support for network application
    programs, including Client Access/400, using selected IBM
    Token Ring adapters.  It provides support for the IEEE 802.2
    (SNA), NetBIOS, TCP/IP, and IPX/SPX  network protocols
    via an ODI driver.  It supports communication with both
    IBM LAN Server (Version 3.0 and 4.0) and
    Novell NetWare Servers (Version 2.15c and higher).
    Also included is the new Netware Client-32 code.

Q2) What adapters are supported?
A2) Only certain IBM adapters are supported.
    Please refer to the IBM LAN Client documentation
    for a complete list.

Q3) How do I obtain Lan Client?
A3) Release 2.1 is now available, and includes
    support for Novell, NetBIOS, 802.2 and
    TCP/IP protocols.

    To obtain the latest version of IBM LAN Client you
    can get the package named LANCLNT by:

  o Downloading updated diskette images using anonymous
    FTP from either:

    - The IBM PC Bulletin Board System at ftp.pcco.ibm.com,
      directory  pub/network

    - The IBM LAN Support BBS at lansupport.raleigh.ibm.com,
      directory  pub/products/lanprods/software.

  o Using the World Wide Web to access URL
    http://www.raleigh.ibm.com/trl/trlclnt/html#diskettes.
    Download the .dsk files and create the diskettes
    using LOADDSK.  Once the diskettes are created,
    refer to the README.1ST file on
    the LANCLNT1 diskette for further assistance.


  o Using the dial-in BBS to download files.  Call
    1-919-517-0001 and set your modem to 8 data bits,
    no parity, and 1 stop bit.  Provide the
    requested information, or answer "yes" to all
    prompts to register with the BBS and reach the
    main screen.  You should then type REFDISK to
    access the Licensed Software areas.  Then type
    S LAN CLIENT to find IBM LAN Client files.

Q4) Why should I use IBM Lan Client instead of Lan
    Support Program (LSP)?
A4) IBM Lan Client uses an ODI driver instead of
    an NDIS driver.  Client Access users that are
    also running IPX/SPX (Novell) protocol stack
    no longer have to run 'shims' such as ODINSUP
    or LANSUP.  The IBM LAN Client marketing announcement
    states: "With LAN client, device drivers
    in a Novell client environment also running 802.2
    (SNA), shrinks from over 100Kb of conventional
    memory to a tiny 4KB.

Q5) How do I obtain support for LAN Client 2.x?
A5) Technical support for this release is available
    by calling IBM support at following numbers:

         In the USA, 1-800-426-7299

         In Canada, 1-800-565-3344
