











                                IBM LAN DISTANCE VERSION 1.11 QUICK START GUIDE







                                                                   October 1994




                                                                Bob Spickelmier
                                                     LAN Distance Brand Manager
                                                     Personal Software Products
                                                                            IBM
                                                              11400 Burnet Road
                                                               Austin, Tx 78758

































































  OCTOBER 1994 EDITION

  This document applies to Version 1.11 of LAN Distance.


      The information contained in this document has not been sub-
      mitted to any formal IBM test and is distributed on an 'As Is'
      basis without any warranty either express or implied.  The use
      of this information or the implementation of any of these
      techniques is a customer responsibility and depends on the
      customer's ability to evaluate and integrate them into the
      customer's operational environment.  While each item may have
      been reviewed by IBM for accuracy in a specific situation,
      there is no guarantee that the same or similar results will be
      obtained elsewhere.  Customers attempting to adapt these tech-
      niques to their own environments do so at their own risk.

  IBM is a registered trademarks of the International Business Machines
  Corporation.


  Many people helped with the generation of this document.  I would like
  to give a special thank you to the following people:


      Peter Fox developed the first iteration of the Quick Start
      Guide.  David Young developed the LDCOOK - LAN Distance Cook
      Book, which is source material for many of the examples.  Lisa
      Goetz in our Support Group provided significant technical
      input and reviews.  Nancy Lenz, Rick Cole and Binh Tran pro-
      vided technical reviews of the document.  Thank's to these and
      all of the other people who helped out.










  CONTENTS
  ________





  LAN DISTANCE QUICK START GUIDE   . . . . . . . . . . . . . . . . . . . . .  1

  INSTALLING THE LAN DISTANCE CONNECTION SERVER  . . . . . . . . . . . . . .  3
  Installation Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
  Configure the Ports Tab  . . . . . . . . . . . . . . . . . . . . . . . . .  6
  Configure the Modems Tab   . . . . . . . . . . . . . . . . . . . . . . . .  6
  Configure the Address Tab  . . . . . . . . . . . . . . . . . . . . . . . .  7
  Configure the Bridge Tab   . . . . . . . . . . . . . . . . . . . . . . . .  7
  Configure the Answer Tab   . . . . . . . . . . . . . . . . . . . . . . . .  9
  Configure the Security Tab   . . . . . . . . . . . . . . . . . . . . . . .  9
  Adding, Changing or Deleting a User Account  . . . . . . . . . . . . . .   10

  INSTALLING LAN DISTANCE REMOTE WORKSTATIONS  . . . . . . . . . . . . . .   13
  Installing the LAN Distance Windows Remote   . . . . . . . . . . . . . .   13
  Installing the LAN Distance OS/2 Remote  . . . . . . . . . . . . . . . .   16
  Adding Additional Phone Book Entries   . . . . . . . . . . . . . . . . .   18
  Shuttle Feature Description  . . . . . . . . . . . . . . . . . . . . . .   19

  INSTALLING COMMON LAN APPLICATIONS   . . . . . . . . . . . . . . . . . .   23
  IBM LAN Server   . . . . . . . . . . . . . . . . . . . . . . . . . . . .   23
  Novell NetWare   . . . . . . . . . . . . . . . . . . . . . . . . . . . .   26
  Windows for Workgroups 3.11 Support  . . . . . . . . . . . . . . . . . .   32
  NTAS and Windows For Workgroup 1.11  . . . . . . . . . . . . . . . . . .   35
  Microsoft's LAN Manager  . . . . . . . . . . . . . . . . . . . . . . . .   36
  Banyan VINES   . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   41
  IBM LAN Support Program  . . . . . . . . . . . . . . . . . . . . . . . .   46
  IBM PC/3270 V3.0   . . . . . . . . . . . . . . . . . . . . . . . . . . .   48
  AttachMate Xtra  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   50
  IBM DOS TCP/IP 2.1.1   . . . . . . . . . . . . . . . . . . . . . . . . .   52
  LAN Workplace for DOS  . . . . . . . . . . . . . . . . . . . . . . . . .   54

  ADDITIONAL CONSIDERATIONS FOR WORKING WITH LAN DISTANCE  . . . . . . . .   59
  LAN Distance setup utilities   . . . . . . . . . . . . . . . . . . . . .   59
  IBM Auto/Dual LANStreamer Adapters (Token Ring Promiscuous Mode) Support   60
  WAC Adapter Setup  . . . . . . . . . . . . . . . . . . . . . . . . . . .   61
  X25 README files   . . . . . . . . . . . . . . . . . . . . . . . . . . .   62
  Country code and phone book tabs   . . . . . . . . . . . . . . . . . . .   62
  IBM7855.EXE Tool   . . . . . . . . . . . . . . . . . . . . . . . . . . .   63

  TROUBLE SHOOTING COMMON PROBLEMS   . . . . . . . . . . . . . . . . . . .   65
  Common Error Conditions  . . . . . . . . . . . . . . . . . . . . . . . .   65
  Using OS2PING  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   68
  Using LAN Adapter & Protocol Support   . . . . . . . . . . . . . . . . .   69
  MPTS   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   71
  Modem PIF File Corrections   . . . . . . . . . . . . . . . . . . . . . .   71
  NetBIOS over TCP/IP  . . . . . . . . . . . . . . . . . . . . . . . . . .   72
  Deselecting Manual Bridge Filter   . . . . . . . . . . . . . . . . . . .   72
  PCMCIA Adapter Changes   . . . . . . . . . . . . . . . . . . . . . . . .   72


                                                                  Contents  iii









  Communications Manager/2 V1.11   . . . . . . . . . . . . . . . . . . . .   72























































  iv  LAN Distance Quick Start Guide









  LAN DISTANCE QUICK START GUIDE
  ______________________________





  The object of this document is to summarize the procedures for installing the
  LAN Distance family of products.  There are two major activities in
  installing LAN Distance: installing and configuring the connection server,
  and installing the remotes.  This document takes you through the steps to
  install a basic configuration.  While a major strength of LAN Distance is the
  variety of connections it supports, this document only focuses on standard
  asynchronous connections which suits the majority of installations.  More
  advanced configurations are beyond the scope of this document and are covered
  in detail in the product documentation.


  RELATED PUBLICATIONS


  BOOKS



  IBM LAN Distance Advanced Guide (S52G-8394), included in the LAN Distance
  Connection Server Package.  This is both an administrative guide and a com-
  plete configuration guide for connection servers and remote workstations.


  IBM LAN Distance Remote Guide (S52G-8393), included in the LAN Distance
  Remote Workstation package.  This is a reference guide for remote workstation
  users and focuses on using an asynchronous, switched line connection for
  remote access to a LAN.


  IBM LAN Distance Version 1.1 Configuration and Customization Guide
  (GG24-4158-01), a separately packaged publication, provides information on
  how to set up and customize LAN Distance in a simple standalone workgroup LAN
  environment.  The document also describes customization tips for supporting
  more complex multiprotocol application requirements, security and remote
  network management.


  ONLINE INFORMATION


  Online help is an important component of the LAN Distance product documenta-
  tion.  Help can be obtained from any window at any time.  Every Help presents
  general information about the nature of a task, its purpose, and its action.


  The Task Index is an online index that organizes all of the online informa-
  tion.  It is a set of task descriptions whose purpose is to help you under-



                                              LAN Distance Quick Start Guide  1









  stand and start performing particular tasks.  It also contains references to
  important concepts and terms.


  Online Where and How help provides conceptual information about the LAN Dis-
  tance product and serves as a guide to the tasks for configuring your LAN
  Distance workstation.

















































  2  LAN Distance Quick Start Guide









  INSTALLING THE LAN DISTANCE CONNECTION SERVER
  _____________________________________________





  PREPARING TO INSTALL THE LAN DISTANCE CONNECTION SERVER


  The installation of the LAN Distance connection server can be broken down
  into three separate activities:


  1.  Installing the product diskettes onto the hard drive.

  2.  Configuring the connection server for the specific hardware.

  3.  Configuring the connection for your operating environment. This includes
      enabling security and adding users.

  Before you begin the installation process ensure that all hardware such as
  modems, adapters, and cables are installed and configured properly.  If you
  are using an ISA bus LAN adapter, you will want to note the hardware jumper
  settings for Interrupt, I/O address and RAM address.  These settings are
  required during installation by the LAN Adapter and Protocol Support (LAPS)
  program.


  IMPORTANT - The ability of LAN Distance to bridge a remote user onto the
  Local Area Network (LAN) requires the LAN adapter to support a specific
  bridging function.  At the time of publication, the following LAN adapters
  are supported:


    NON-MICRO CHANNEL NETWORK ADAPTERS

    -  IBM Token-Ring Network 16/4 Adapter
    -  IBM Auto LANStreamer ISA Adapter
    -  IBM LAN Adapter for Ethernet
    -  IBM LAN Adapter for Ethernet TP
    -  IBM LAN Adapter for Ethernet CX
    -  3Com TokenLink III 16/4 Adapter
    -  Standard Microsystems EtherCard PLUS Elite16 Adapter

    MICRO CHANNEL NETWORK ADAPTERS

    -  IBM Token-Ring Network Adapter/A
    -  IBM Token-Ring Network 16/4 Adapter/A
    -  IBM Auto LANStreamer MC 32 Adapter
    -  IBM Dual LANStreamer MC 32 Adapter
    -  IBM LAN Adapter/A for Ethernet
    -  IBM PS2 Adapter/A for Ethernet
    -  3Com TokenLink III 16/4 Adapter
    -  Madge Straight Blue 16/4 MC Adapter for Token-Ring


                               Installing the LAN Distance Connection Server  3











  Changes or additions made to the list of supported hardware are documented in
  the MODEMS.TXT and the ADAPTERS.TXT files which are available from these
  sources:


  o   CompuServe users can access the PSPAPROD forum and access these files in
      the LAN Distance product's library section.

  o   Users with access to IBMLink through OS2BBS can access these files in the
      REMOTE section of the OS/2 Software Library (3), OS/2 Selective Fixes
      (1).

  It is strongly recommended that you read the README files on LAN Distance
  Connection Server Diskette 1.  This file contains important information that
  could potentially affect your installation.  Please read this file before you
  proceed.



  INSTALLATION OVERVIEW
  _____________________

  This section summarizes the LAN Distance Connection Server installation.
  Each task is explained in detail in the next sections.


  To install the LAN Distance Connection Server product, insert LAN Distance
  Connection Server Diskette 1 in Drive A: and enter:


          A:\INSTALL

  Select a target drive on which to install the LAN Distance Connection Server
  product.


  After the installation is complete, shut down and restart your workstation.


  The LAN Distance software is now installed on the workstation.  It must be
  configured before the connection server can be used.


  Double click on the LAN Distance Connection Server product icon.  When
  started,


      -   Open the Settings notebook to configure LAN Distance.

      -   Configure the Ports tab to define your communications ports





  4  LAN Distance Quick Start Guide









      -   Configure the Modems tab (assign a modem type listed in the LAN Dis-
          tance Connection Server product then associate the configured port
          with the configured modem type).

      -   Configure the Address tab (select a LAN type).

      -   Configure the Bridge tab (hop counts, LAN segment ring number, bridge
          number, and filtering)

      -   Configure the Answer tab (place the LAN Distance Connection Server in
          answer mode to respond to incoming calls from LAN Distance Remote's).

      -   Configure the Workstation tab (choose a name for your workstation
          such as your department # or company name).

      -   Configure the Security tab (enable or disable security. Enabling
          security is optional but strongly recommended to prevent unauthorized
          access to your Local Area Network.

      -    Shut down and restart your LAN Distance Connection Server.

      -   If you enabled security, you will need to LOGIN as the Security
          Administrator when you reopen the settings notebook.


                      - The default user ID is: SECADMIN

                      - The default passphrase is: SECADMIN

                       Note:  THE PASSPHRASE IS CASE-SENSITIVE.

      -   After you restart LAN Distance, if security is enabled, you can then
          open the User Account Management notebook and set up an account for
          each user by creating a user ID.

  The LAN Distance Connection Server is now ready to process incoming calls.


  Please note, there are other tabs that allow you to perform advanced config-
  uration and tuning.  These are beyond the scope of this document and are
  covered in the LAN Distance Advanced Guide.


  The detailed steps for each activity are in the next sections.












                               Installing the LAN Distance Connection Server  5









  CONFIGURE THE PORTS TAB
  _______________________

  The Ports tab is used to define the communications ports that are available
  to LAN Distance.  The assumption in this document is that you are using
  serial ports on the Connection Server.  One thing you should check is that
  the COM ports you are defining to LAN Distance have FIFO buffering.  This is
  very important if you plan to use more than one serial port or if you expect
  to achieve optimum performance.  To check this from on OS/2 command line,
  enter MODE COMx: where x is the COM port number.  The response should contain
  BUFFER = AUTO if you have FIFO buffering.

  TO CONFIGURE THE PORTS TAB:

  1.  Select the Ports tab from the Settings notebook.

  2.  Select Add to begin port configuration.

  3.  From the Add ports window, select the COM port adapter type.

  4.  From the displayed COM tab, define the required parameters for your COM
      port.

  5.  Close the COM tab to save the settings and return to the Ports tab by
      selecting close from the system icon menu.


  CONFIGURE THE MODEMS TAB
  ________________________

  In order to make LAN Distance connections with your modem, you must assign
  your configured port to a Modem type. This lets the LAN Distance product know
  how to use your modem to make connections.

  TO CONFIGURE THE MODEMS TAB:

  1.  Select the Modems tab from the Settings notebook.

  2.  Select Assign.

  3.  Select the type of modem you want to set up from the Available modem
      types list.

      If your modem is not in the list of predefined modems, please refer to
      Appendix E of the LAN Distance Advanced Guide for information about the
      utility CFMODEM.EXE which will help you create new modem types.

  4.  Select OK.

  5.  Select Add from the Ports tab.  The Line type window displays.

  6.  The Switched choice is selected for 'line type'. Specify the local tele-
      phone number for your telephone line and modem.  Specifying the phone
      number is optional.

  7.  Select OK.


  6  LAN Distance Quick Start Guide









  8.  From the Available ports list, select the port to which your modem is
      attached.

  9.  Select OK.

  10. Close the Ports tab by selecting Close from the system icon menu.


  CONFIGURE THE ADDRESS TAB
  _________________________

  TO CONFIGURE THE ADDRESS TAB:

  1.  Select the Address tab from the Settings notebook.

  2.  Choose the LAN type: Token-Ring or Ethernet 802.3.

  3.  Select the adapter type from the adapter pull-down list.

  4.  Enter a LAN Distance logical adapter address or keep the workstation
      address automatically generated during the install process. Record this
      address for your LAN administrator.


  CONFIGURE THE BRIDGE TAB
  ________________________

  The LAN Distance bridge is used in the remote-to-LAN environment to route and
  filter data frames for the LAN and WAN segments of the LAN Distance wide area
  network.

  Filtering keeps the high-volume LAN traffic from flooding the slower async
  WAN wire.  Symptoms include the LAN Distance Connection Server's modem's TD
  (transmit or send) light is on most of the time, or your connection drops at
  different times (busy times) of the day.


  LAN Distance V1.1 implements a new type of filtering called Automatic Fil-
  tering.  This is a one-step solution to what was a demanding task of finding
  Address Filters, SAP filters, NetBIOS Names, or using the Bit mask.  When the
  LAN Distance Remote workstation dials into the LAN Distance Connection
  Server, the application using the LAN Distance Remote product sends out LAN
  traffic containing a destination name to the LAN Server. Similar techniques
  are automatically applied to applications using other protocols (e.g.,
  TCP/IP).


  The Automatic Filtering in LAN Distance will notice this address and automat-
  ically make a list of the destination names for each Remote workstation.
  Only the LAN traffic from those destinations will be transmitted back over
  the WAN wire to the Remote workstations.  With Automatic Filtering, each
  Remote workstation has it's own unique filter table which allows signif-
  icantly more efficient filtering of LAN traffic.





                               Installing the LAN Distance Connection Server  7









  Standard routing criteria and filtering criteria are still available for
  LAN-to-LAN connections and are described in the LAN Distance Advanced Guide.


  TO CONFIGURE THE LAN DISTANCE BRIDGE:


  1.  Select the Bridge tab from the Settings notebook.


  2.  On Page 1 of 3, specify a Bridge number for the LAN Distance bridge.
      Verify that the Load Bridge Support and Automatic filtering boxes are
      checked.  The Bridge number field will not be active if you are config-
      ured for an Ethernet LAN.


  3.  On Page 2 of 3, specify the LAN segment ring number.  This number is
      usually obtained from the LAN Administrator.  If this information is not
      available, the CALLBRDG utility (see below) can be used to determine the
      segment number for you.  This does not apply to Ethernet LAN configura-
      tions which use transparent bridging.


  4.  On Page 3 of 3, specify the WAN segment ring number. You may choose the
      default value unless you have multiple connection servers on your LAN.
      In that case you must choose a unique number for each connection server.
      This does not apply to Ethernet LANs.

  BRIDGE CONFIGURATION UTILITY


  The utility named CALLBRDG.EXE provides an aid to the LAN Distance Connection
  Server administrator in determining the bridge and ring (segment) numbers of
  a Token-Ring LAN attached to the LAN Distance Connection Server.  Refer to
  the file named CALLBRDG.RME for a description of this utility.


  To install the CALLBRDG utility to your hard drive, place the LAN Distance
  diskette 3 into a diskette drive and enter:


     sourceDr:INSTAPPL sourceDr: targetDr:

        - Where sourceDr is the drive letter of the diskette drive that
                         contains LAN Distance diskette 3.
        - Where targetDr is the drive letter of the hard file that
                         contains the \WAL directory.

     Example:  A:INSTAPPL A: C:







  8  LAN Distance Quick Start Guide









  CONFIGURE THE ANSWER TAB
  ________________________

  An Answer mode is a set of criteria to tell the LAN Distance product which
  incoming calls you want to answer.  For example, you can configure an answer
  mode to only accept calls on a particular port.

  TO CONFIGURE THE ANSWER TAB:

  1.  Select the Answer tab from the Settings notebook.

  2.  Select PSTN_ALL_CALLS.

  3.  Select CHANGE.

  4.  Select 'Enable Answer Mode on Startup' if you want your workstation to
      automatically answer all incoming calls when you start LAN Distance.

  NOTE: It is recommended that you select this option.  If this is not
  selected, you will need to manually start Autoanswer every time you restart
  LAN Distance.




  CONFIGURE THE SECURITY TAB
  __________________________

  TO CONFIGURE THE SECURITY TAB:

  1.  Select the Security tab from the Settings notebook.

  2.  Select Enable to turn security on.

      OR

      Select Disable to turn security off.


      NOTE:  Any user can enable security.  Only a LAN Distance security admin-
      istrator can disable security.

  If you enabled security, security will be active the next time you start LAN
  Distance.  You will have to supply a user ID and passphrase to open the Set-
  tings notebook after you restart your workstation.


       - The default user ID is: SECADMIN

       - The default passphrase is: SECADMIN

  NOTE: THE PASSPHRASE IS CASE-SENSITIVE. Also keep in mind that if the Secu-
  rity Administrators ID is disabled, you can potentially lock yourself out of
  LAN Distance Security.  It is best to have a couple of Security Administrator
  IDs so that you can have a backup in case one is disabled.



                               Installing the LAN Distance Connection Server  9












  ADDING, CHANGING OR DELETING A USER ACCOUNT
  ___________________________________________

  To add a new user account or to view, change, or delete an existing account,
  security must be enabled and you must be logged on as a LAN Distance security
  administrator.


  Before you begin adding User Accounts you will want to define the security
  policy.  This will set Passphrase length, Passphrase Age and invalid logon
  attempts.  Most often, the policy is set to match other security systems on
  the LAN.

  TO DEFINE THE SECURITY POLICY:

  1.  Open the User Account Management notebook.

  2.  Select the Policy tab.

  3.  Specify the values for the options you wish to change.

  4.  Policy option changes become effective after you close the User Account
      Management notebook, and stop and restart LAN Distance.

  TO ADD NEW USER ACCOUNTS OR TO VIEW, CHANGE, OR DELETE AN EXISTING ACCOUNT:

  1.  Open the User Account Management notebook.

  2.  Select the Account tab.

  3.  Select Add to add a new user account.

      OR, select an existing user ID from the User Accounts window and then
      select Change to change existing criteria.

      OR, select Delete to completely remove the selected user's account.

  4.  Select each of the following tabs and change or supply information as
      appropriate for the user account:

  o   Type tab

      -   User ID
      -   Comment
      -   User type
      -   Account status

  o   Passphrase tab

      -   Passphrase required
      -   Passphrase (This passphrase will have to be changed the first time
          the user logs on).


  10  LAN Distance Quick Start Guide









      -   Passphrase for verification
      -   Verify Passphrase

  If you wish increased levels of security, the following tabs may be
  configured:


  o   Interval tab

      -   Adding a Logon Time Interval
      -   Changing a Logon Time Interval
      -   Deleting a Logon Time Interval

  o   Addresses tab

      -   LAN Distance logical adapter network address

  o   Callback tab

      -   Callback required
      -   Callback type
      -   Phone Book entry name


































                              Installing the LAN Distance Connection Server  11

































































  12  LAN Distance Quick Start Guide









  INSTALLING LAN DISTANCE REMOTE WORKSTATIONS
  ___________________________________________





  The following sections describe the process of installing LAN Distance remote
  workstations.  If the workstations will be LAN attached or are already LAN
  attached, the users' applications should be installed and set up before
  installing LAN Distance.  This is because many LAN based applications look
  for the presence of LAN software before they will install.  In addition, it
  is useful to confirm that an application functions properly when LAN attached
  in the event that it does not work with LAN Distance.


  For more information on installing and tuning applications, see Installing
  Common LAN Applications or the LAN Distance product documentation.




  INSTALLING THE LAN DISTANCE WINDOWS REMOTE
  __________________________________________

  NOTE:  Before installing the LAN Distance product, install and configure all
  hardware (such as modems, adapters, cables).  If you are using ISA Bus LAN
  Adapters be sure to note the jumper settings because you might need this
  information if you have to manually configure LAPS.  For more information see
  Using LAN Adapter & Protocol Support.


   It is recommended that you install and tailor your network applications
  prior to installing the LAN Distance Remote.  This will allow the LAN Dis-
  tance installation routines to properly configure the remote settings for the
  application environment that you want to run in.  If you install LAN applica-
  tions after installing LAN Distance, you will likely need to hand edit your
  CONFIG.SYS and PROTOCOL.INI files.


  TO INSTALL AND CONFIGURE THE LAN DISTANCE PRODUCT:

  1.  Insert LAN Distance Windows Remote Diskette in Drive A: and enter
      A:INSTALL using the Windows RUN Command.

  2.  Select a target drive to install the LAN Distance product.

  3.  Select Basic Settings.

  4.  Select a Modem type (from the list of available Modem types).

      If your modem is not in the list of predefined modems, please refer to
      Appendix E of the LAN Distance Advanced Guide for information about the
      utility CFMODEM.EXE, which will help you create new modem types.

  5.  Select a COM port.


                                Installing LAN Distance Remote Workstations  13









  6.  Enter the telephone number for the LAN Distance Connection Server you
      will dial.

  7.  Select a LAN type (Token-Ring or Ethernet).

  8.  Enter your LAN Distance logical adapter network address, or select Gen-
      erate to have an address created for your workstation automatically.

  9.  Select Netware support if you are using the Netware requester.

  10. If you are installing the LAN Distance product on a workstation with a
      LAN adapter, the Shuttle function will be enabled.  You will be prompted
      to remain attached to the LAN (select "No"), or to "shuttle" to a stand
      alone, non-LAN attached environment to use the LAN Distance Remote
      (select "Yes").

  11. Shut down and restart your workstation.

  TO START THE LAN DISTANCE REMOTE:

  o   Open the Phone Book and Dial.

  o   Once a connection is established, run your LAN-based applications over
      the LAN Distance link.

  SPECIAL CONSIDERATIONS FOR WINDOWS

  PCMCIA MODEM SUPPORT

  If you have a PCMCIA modem be sure the modem is operational before you begin
  the LAN Distance installation process. If you are unsure how to install and
  configure your PCMCIA MODEM, check the modem documentation or contact the
  modem manufacturer.  Every PCMCIA modem has a different install procedure and
  there is no standard approach to this task.


  HIGH MEMORY CONSIDERATIONS

  The LAN Distance install program tries to put its drivers into high memory.
  If you have PCMCIA drivers and other TSR programs loaded high, the LAN Dis-
  tance drivers may not load when the machine boots and you will see the fol-
  lowing errors:

       DXMJ047E  Will not fit in UMB

       PRO0033E  Error in NETBIND

  You will need to reconfigure CONFIG.SYS and AUTOEXEC.BAT to maximize the use
  of high memory.  A utility such as RAMBOOST or MEMMAKER can be used to con-
  figure this memory.  See the DOS Users Guide for more information on the use
  of HIGH Memory and these utilities.

  MESSAGE WCL0589



  14  LAN Distance Quick Start Guide









  This message may indicate that your modem is not configured properly.  If you
  created a new PIF file (modem type) for your modem, make sure the AT commands
  in its initialization string are set for the configuration requirements
  described in the LAN Distance Advanced Guide.  See Appendix D, section "Cre-
  ating a New PIF File for a Modem Not in the List", step 8.


  The following should also be listed under step 8:


  VERBOSE RESPONSE MODE - Modems display responses or result codes to accept or
  reject commands.  Result codes are also sent to report on connection
  progress.  Most modems are defaulted to the report result codes as words,
  instead of numbers.  Make sure your modem is set to report responses as words
  (verbose response mode).  (For most modems, this command is V1.)


  Use the CFMODEM utility, see below, to test modems and strings.


  MODEM PIF FILES


  The PIF files installed with the LAN Distance Windows client are a subset of
  the supported modems listed in Appendix A of the LAN Distance documentation
  due to a shortage of disk space.  PIF files not installed with the LAN Dis-
  tance windows client can be copied from the LAN Distance Connection Server.


  NETHEAPSIZE IN SYSTEM.INI


  LAN Distance installation automatically updates the NetHeapSize statement in
  the Windows SYSTEM.INI to a value of 16 if it was previously set to less than
  16.  Your applications mix may require this value be greater than 16.  If you
  receive a message during Windows initialization stating that this value
  should be set higher than 16, edit the SYSTEM.INI file located in the Windows
  directory and update the value to be equal to or greater than the value dis-
  played by the Windows message.


  DELETING AND ADDING PORTS


  Ports may be deleted and added via the Settings Notebook.  Do not add or
  delete ports while a connection is currently established.  You should always
  hang up before adding or deleting any ports.


  COM PORT USAGE


  If you have other applications that use the same COM port as LAN Distance,
  you will need to remove the LAN Distance device statements from your


                                Installing LAN Distance Remote Workstations  15









  CONFIG.SYS file to make the COM port available to the other applications.  If
  you want to make the COM port used by LAN Distance available to other appli-
  cations, add "rem" (remark) to the beginning of the LAN Distance device
  statements in CONFIG.SYS.


     Example:  rem device=C:\WAL\WINAMAC.SYS


  To return the COM port availability to LAN Distance, remove the "rem" from
  the device statements in CONFIG.SYS


  CFMODEM UTILITY


  Appendix D of the LAN Distance Advanced Guide describes an OS/2 utility named
  CFMODEM that is provided as an aid to modifying and creating modem descriptor
  (.PIF) files.  A Windows version of this utility is provided and is installed
  to your WAL directory when LAN Distance is installed.  To run the Windows
  Port/Modem utility, select the Windows RUN option and type "CFMODEM.EXE".


  CFMODEM may also assist you in correcting problems such as WCL0219 or WCL0221
  during installation/configuration.


  INSTALLING THE LAN DISTANCE OS/2 REMOTE
  _______________________________________

  NOTE:  Before installing the LAN Distance product, install and configure all
  hardware (such as modems, adapters, cables).  If you are using ISA Bus LAN
  Adapters be sure to note the jumper settings because you might need this
  information if you have to manually configure LAPS.  For more information see
  How to use LAN Adapter and Protocol Support.

  TO INSTALL AND CONFIGURE THE LAN DISTANCE OS/2 PRODUCT:

  1.  Insert LAN Distance OS/2 Remote Diskette #1 in Drive A: and enter

      A:\INSTALL

  2.  Select Basic Settings.

  3.  Select a Modem type (from the list of available Modem types).

      If your modem is not in the list of predefined modems, please refer to
      Appendix E of the LAN Distance Advanced Guide for information about the
      utility CFMODEM.EXE, which will help you create new modem types.

  4.  Select a COM port.

  5.  Enter the telephone number for the LAN Distance Connection Server you
      will dial.



  16  LAN Distance Quick Start Guide









  6.  Select a LAN type (Token-Ring or Ethernet).

  7.  Enter your LAN Distance logical adapter network address, or select Gen-
      erate to have an address created for your workstation automatically.

  8.  If you are installing the LAN Distance product on a workstation with a
      LAN adapter, the Shuttle function will be enabled.  You will be prompted
      to remain attached to the LAN (select "No"), or to "shuttle" to a stand
      alone, non-LAN attached environment to use the LAN Distance Remote
      (select "Yes").

  9.  Shut down and restart your workstation.

  TO START THE LAN DISTANCE REMOTE:

  1.  Open the Phone Book and Dial.

  2.  Once a connection is established, run your LAN-based applications over
      the LAN Distance link.

  PCMCIA CARDS

  If you have a PCMCIA modem be sure the modem is operational before you begin
  the LAN Distance installation process.  The best way to determine this is the
  OS/2 MODE command.

  The result should look something like this:

       [C:\]MODE COMx:

       BAUD = 9600                PARITY = NONE
       DATABITS = 8               STOPBITS = 1
       TO = OFF                   XON = OFF
       IDSR = OFF                 ODSR = OFF
       OCTS = OFF                 DTR = ON
       RTS = ON                   BUFFER = AUTO

  Where COMx: is the port number assigned to your PCMCIA modem.  The parameter
  BUFFER=AUTO indicates the presence of a FIFO buffer which will improve the
  performance of LAN Distance.


  If you are unsure how to install and configure your PCMCIA MODEM, check the
  modem documentation or contact the modem manufacturer.  Every PCMCIA modem
  has a different install procedure and there is no standard approach to this
  task.


  If you are using the Shuttle function with PCMCIA adapters, please refer to
  the next section of this document for information regarding this proper con-
  figuration of this environment.





                                Installing LAN Distance Remote Workstations  17









  ADDING ADDITIONAL PHONE BOOK ENTRIES
  ____________________________________

  If you call multiple Connection Servers, or wish to access a Connection
  Server in different ways (ie PBX, Area Code, Credit Card), you may wish to
  add an additional phone book entry for each call type.

  TO ADD AN ADDITIONAL PHONE BOOK ENTRY:

  1.  From the Settings notebook, select the Phone Book tab.

  2.  Select Add.

  3.  For Network type, select PSTN.

  4.  For Line type, select Switched.

  5.  Select OK.

  6.  In the Entry name field, specify a name for this phone book entry.

  7.  In the Description field, specify a description for this phone book
      entry.

  8.  Select the Numbers tab.

      The first page of the Numbers tab is displayed.

  9.  Select Add.

      The Telephone number window is displayed.

  10. In the Telephone number to be dialed field, specify the telephone number
      for the workstation you want to call.

  11. In the Dialing order field, specify the position of the telephone number
      in the Phone Book entry dialing order list.

  12. Select OK to save the telephone number configuration.

  13. Select the Modem tab.

  14. Select Asynchronous connection.

  15. Close the Settings notebook.












  18  LAN Distance Quick Start Guide









  SHUTTLE FEATURE DESCRIPTION
  ___________________________

  When a workstation is physically attached to a LAN, certain system configura-
  tion files must be changed so that the workstation can function on the LAN.
  The same files must be changed again for the workstation to function as a LAN
  Distance Remote. If a LAN Distance Remote never needs to be attached to the
  LAN, then the files do not need to be changed. However, if physically
  attaching to the LAN is a requirement, then the same set of files must be
  configured differently for each environment.


  NOTE: Configuring your workstation for both environments is much easier if
  any LAN applications (such as IBM LAN Requester) are installed and configured
  before the LAN Distance Remote product is installed.


  Once the Shuttle feature is enabled, a pop-up panel is displayed each time
  you stop the LAN Distance Remote product from the user interface.  The pop-up
  panel prompts you to specify which environment your workstation will function
  in when it is restarted. If you expect to operate in one environment for a
  prolonged period, you can disable the shuttle feature so this panel will not
  display.


  If you attempt to shuttle your workstation from the remote environment to the
  LAN-attached environment, but your workstation is not yet configured as
  LAN-attached, then the LAN Distance Remote program supplies a default IBM
  Token-Ring configuration.  Once your workstation shuttles to work in a
  LAN-attached environment, you can use LAPS to change this default configura-
  tion to meet your LAN-attached requirements.


  TO ENABLE OR DISABLE THE SHUTTLE FEATURE:

  1.  Open the Settings notebook.

  2.  Select the Workstation tab.

  3.  Select Shuttle between LAN-attached workstation and remote workstation.

  4.  Close the Settings notebook and save the values.

      The Shuttle feature is now enabled.

  SPECIAL CONSIDERATIONS FOR SHUTTLE WITH PCMCIA ADAPTERS

  o   Shuttle may change the order of some of the PCMCIA DEVICE= statements in
      CONFIG.SYS.

  o   Second, shuttle may lose a parameter on the PCMCIA socket services device
      driver (IBM2SS01.SYS) or on a PCMCIA modem device driver (ESTDFM.OS2).

  For an IBM PCMCIA Token-Ring Adapter:



                                Installing LAN Distance Remote Workstations  19









  1.   Edit the \IBMCOM\MACS\IBMTOKCS.NIF file.

      o   Find the FILE section.

      o   On the "Name =" line, add device drivers that are order dependent in
          their correct order.  This will differ from one machine model to
          another and it will differ depending on what version of Card and
          Socket Services you have.  Here's an example for how to edit the file
          for an IBM ThinkPad 750C:

               Name = $ICPMOS2.SYS IBMTOKCS.OS2 IBM2SS02.SYS ICRMU02.SYS

          This will result in these device drivers being added to the end of
          CONFIG.SYS in this order.

  2.  Copy all device drivers that you placed on the "Name =" line the above
      .NIF files to the \IBMCOM\MACS subdirectory.

  For a PCMCIA asynchronous modem adapter:

  1.   Edit the \IBMCOM\MACS\PDFH.NIF file.

      o   Find the FILE section.

      o   On the "Name =" line, add device drivers that are order dependent in
          their correct order.  The following is an example for the IBM PCMCIA
          modem:

               Name = $ICPMOS2 PDFH.OS2 IBM2SS02.SYS ICRMU02.SYS

          This will result in these device drivers being added to the end of
          CONFIG.SYS in this order.

  2.  Copy all device drivers that you placed on the "Name =" line the above
      .NIF files to the \IBMCOM\MACS subdirectory if they are not already
      there.

  The required device drivers are described in your PCMCIA Adapter documenta-
  tion and included on your Adapter's installation diskette.  The device driver
  names are specific to each brand of adapter.


  The \IBMCOM\MACS\PDFH.NIF file is shipped, installed, and required by the LAN
  Distance product.  PDFH.OS2 is its associated device driver.


  NOTE: This editing technique can be used for any multiple device drivers
  adapter requiring a particular order in CONFIG.SYS.



  FIXING PARAMETER LOSS PROBLEMS DURING SHUTTLE




  20  LAN Distance Quick Start Guide









  If shuttling loses parameters on any DEVICE= statements in the CONFIG.SYS
  file, follow the example below to correct the problem:

  o   Use an ASCII text editor to edit the \WAL\WCLLOCAL.INI file.

      In the SHUTTLE section add two lines describing the name of your device
      driver and its parameter.  For example, if your SHUTTLE section looks
      like:

           OSHUTTLEt
              D1 = ESTDFM.OS2
              P1 = S1C2
              D2 = IBM2SS01.SYS
              P2 = /S0=1

      and you have a device driver named XYZ.OS2 that needs parameter /A, add
      the following lines so that your shuttle section looks like:

           OSHUTTLEt
              D1 = ESTDFM.OS2
              P1 = S1C2
              D2 = IBM2SS01.SYS
              P2 = /S0=1
              D3 = XYZ.OS2
              P3 = /A

  NOTE:  If you use LAPS to change your LAN protocol configuration, your param-
  eters may be deleted again.  If so, simply shuttle your LAN Distance remote
  workstation and the parameters will be restored.



























                                Installing LAN Distance Remote Workstations  21

































































  22  LAN Distance Quick Start Guide









  INSTALLING COMMON LAN APPLICATIONS
  __________________________________





  This section describes how to set up your LAN Distance Remote and Connection
  Server workstations to support some popular network operating systems and LAN
  Applications.  For more information, please refer to Chapter 10 in the LAN
  Distance Advanced Guide.



  IBM LAN SERVER
  ______________

  o   If you are using LAN Server or LAN Requester 3.0, install Corrective
      Service Diskette (CSD) IP07001 on:

      -   every LAN Requester 3.0 workstation using LAN Distance to establish a
          connection to a LAN Server
      -   every LAN Server 3.0 workstation that you will access using the LAN
          Distance product.

      To obtain CSD IPO7001, contact IBM Software Solutions at 1-800-992-4777
      (United States), 1-800-465-2222 (Canada), or 1-800-426-1774 (Interna-
      tional).

  o   If you are running version 2.0 or 3.0 of the DOS LAN Requester on your MS
      Windows LAN Distance Remote, you should install CSD 7003 for the DOS LAN
      Requester product.

  Because of the slower data transfer speeds over the LAN Distance connection,
  you can experience problems with large file transfers, the XCOPY command,
  session timeouts, and logging onto a LAN Server.


  To avoid these problems, make the following modifications for:


  o   every LAN Server that has resources you will access using the LAN Dis-
      tance product

  o   every LAN Requester workstation using the LAN Distance product.

  Edit LAN Server IBMLAN.INI file in the IBMLAN subdirectory:

  1.  Modify the LAN Server SRVHEURISTICS Parameter:


      Change bit 15 (marked by an A) in the SRVHEURISTICS parameter from 1 to
      any number from 2 to 8.  This sets the timeout value to the maximum value
      of 127 seconds.  If this does not improve performance, turn off the
      timeout value by setting bit 15 to 9.



                                         Installing Common LAN Applications  23









                                               1
            (bit position counter->) 0123456789012345678
                     SRVHEURISTICS = 1111014111131102133
                                                    A

  2.   Increase LAN Sever SESSTIMEOUT value from 45 to 300.

  Edit LAN Requester IBMLAN.INI file in the IBMLAN subdirectory:

  1.  Locate the WRKHEURISTICS parameter in the LAN Requester IBMLAN.INI file
      and change bits 11, 12, and 13 (marked by an A) in the WRKHEURISTICS
      parameter from 1 to 0.

                                               1         2         3
            (bit position counter->) 0123456789012345678901234567890123
                     WRKHEURISTICS = 1111111121300011110001011120111221
                                                AAA

  2.  Increase LAN Requester SESSTIMEOUT value from 45 to 300.

  Edit DOS LAN Requester DOSLAN.INI file in the DOSLAN subdirectory:

  1.  Add the following statement to the end of the file.

             /NMS:3 /NVS:2 /API

  2.  Set the /NBS parameter to match the value for the sizereqbuf parameter in
      the Server's IBMLAN.INI file.


  3.  Change the /BBS parameter so it is 1K larger the the /NBS parameter spec-
      ified in step 2.


  4.  Change the last character in the /WKS (DLR heuristics) parameter from 0
      to 1.

             /WKS:111121101021211
                                A

  DOS LAN REQUESTER PERFORMANCE PARAMETERS


  Updates to Chapter 10 of the LAN Distance Advanced Guide and Appendix B of
  the LAN Distance Remote Guide, section "Changing DOS LAN Requester Perform-
  ance Parameters".  Item 5, /WKS parameter should state "change the 4th char-
  acter to 0 and the last character to 1".


       Example:  /WKS:111021101021211
                         A          A

  ADVANCED LAN SERVER 4.0 WITH LAN DISTANCE CONNECTION SERVER



  24  LAN Distance Quick Start Guide









  When running IBM LAN Server 4.0 Advanced with IBM LAN Distance Connection
  Server you may experience problems with insufficient NETBIOS resources.  Two
  possible symptoms indicate this problem:

  o   When starting LAN Distance error message WCL554 appears stating that the
      LAN Distance product requires more NETBIOS resources than are available.

  o   The NETBIOS protocol does not load at system startup.

  If either of these symptoms occur, the following steps are recommended:

  NOTE:  Restart your workstation after each step to see if the problem is
  solved. If the problem remains, try the next step.

  1.  Remove any unnecessary NETBIOS applications.

  2.  Edit the \IBMLAN\IBMLAN.INI file.

      In the ONetworkt section, reduce the number of NCBs.  See example below:

           NETx=NETBEUI$, 0, LM10, yyy , 175, zzz
                                          A
           to

           NETx=NETBEUI$, 0, LM10, yyy , 125, zzz
                                          A

           where x   = 1,2....
                 yyy = Number of NetBIOS Sessions
                 zzz = Number of NetBIOS Names

  3.  Determine the maximum number of calls that are expected to dial into the
      LAN Distance server at any one time.

      o   Edit the \WAL\WCLLOCAL.INI file with any ASCII editor.

      o   Under OSRDDEFSt reduce the SESSIONS = parameter from 32 to the
          maximum number of calls.

          For example, if you expect a maximum of 16 calls at any one time, set
          SESSIONS = 16.

      o   Change COMMANDS = 90 to the new SESSIONS value times 3.

          For example, if the new SESSIONS value is 16, then set COMMANDS to
          48.  This reduces the number of NETBIOS resources that the LAN Dis-
          tance product will attempt to take when it is started.

           OSRDDEFSt                         OSRDDEFSt
              maxconversations = 10             maxconversations = 10
              adapter  = 2                      adapter  = 2
              sessions = 32            to       sessions = 16
              commands = 90                     commands = 48
              datagram = 6                      datagram = 6


                                         Installing Common LAN Applications  25












  NOVELL NETWARE
  ______________

  This section discusses considerations for using NetWare with the LAN Distance
  product.


  LAN Distance has been tested with the following NetWare client versions.


  o   NetWare for DOS version 4.0 plus the VLM update version 1.01.

  o   NetWare for Windows version 4.01.

  o   NetWare version 3.11, 3.12 and 4.01

  NETWARE FIXES REQUIRED TO RUN WITH LAN DISTANCE

   There are several fixes for Netware that are required to run with LAN Dis-
  tance.  These fixes are available through IBM Service and Support by refer-
  encing the IBM APAR Number.

  o   IBM APAR IC07834 - This fix resolves a couple of problems.  PBURST.EXE is
      required for the Netware 3.11 Servers to make Packet Burst work cor-
      rectly.  PBWANFIX.NLM (which requires patchman) is required for Netware
      3.12 and 4.01 Servers.  R210FT.EXE is required for the OS/2 Netware
      Client to increase the time out values to compensate for slower communi-
      cations speeds.  The specific module within this fix package that is
      required by LAN Distance is NWREQ.SYS.


  o   IBM APAR IC08000 - This fix, VLMUP1.EXE, allows Windows Clients to
      support Packet Burst. The specific module within this fix package that is
      required by LAN Distance is VLM.EXE.


  o   IBM APAR IC07995 - This fix, WINDR1.EXE resolves a problem where the
      system locks up when exiting from Windows.  The specific module within
      this fix package that is required by LAN Distance is VIPX.386.


  These Netware APAR fixes are contained in the "FIXES" Subdirectory on the LAN
  Systems Evaluation CD-ROM.


  NETWARE SERVER

  For a NetWare server to support clients using packet burst in a WAN environ-
  ment, the NetWare server must have PBURST.EXE or later fix.  PBURST.EXE has
  packet burst files with a new packet burst algorithm for WAN links to fix
  problems where:



  26  LAN Distance Quick Start Guide









  o   Burst retries could saturate WAN links due to low retry timeout values.

  o   Workstations hang when duplicate packets from a previous burst are
      received in the middle of the current burst.

  PBURST.NLM is for use on NetWare 3.11 file servers.  PBWANFIX.NLM (which
  requires patchman) is for use on NetWare 3.12 and 4.01 file servers.  This
  NetWare fix is available through IBM Support and Service by referencing APAR
  IC07834 or in the FIXES subdirectory of the LAN Systems Evaluation CD-ROM.


  In a token ring environment, make sure that ROUTE.NLM is loaded on the
  NetWare server.  Since the LAN Distance connection server is a token ring
  bridge, source level routing information must be in frames to be delivered to
  the WAN by the connection server.



  NETWARE REQUESTER FOR WINDOWS

  You can enable NetWare Requester support during LAN Distance installation or
  after you install the LAN Distance product.  The NetWare Requester product
  must be installed before you can enable NetWare Requester support.


  The following should be considered when installing the Netware Requester for
  Windows.


  o   In order to enable LAN Distance for NetWare during LAN Distance installa-
      tion or through the Settings notebook, LSL.COM and VLM.EXE must be in the
      NetWare directory.  LAN Distance requires the use of VLM.EXE.


  o   To improve performance, copy frequently used NetWare utilities to the
      NetWare requester.  For example:  LOGON.EXE, LOGOUT.EXE, MAP.EXE and
      SLIST.EXE.


  o   For a token ring environment, LAN Distance requires all frames to have
      source routing information.  This means ROUTE.NLM must be loaded on the
      NetWare server and ROUTE.COM must be loaded for the NetWare Client for
      DOS.


  o   Make sure that DOSUP9 and WINUP9 (or later) fixes have been applied for
      the NetWare Client for DOS.  After applying these fixes, the following
      fixes must also be applied.


      -   When using packet burst for the NetWare Client for DOS, the latest
          VLM.EXE is required.  This NetWare fix, VLMUP1.EXE, is available
          through IBM Support and Service by referencing APAR IC08000 or in the
          FIXES subdirectory on the LAN Systems Evaluation CD-ROM.


                                         Installing Common LAN Applications  27











      -   If you have a problem with the system locking up when you try to exit
          from Windows, you should get the latest version of VIPX.386. This
          NetWare fix, WINDR1.EXE, is available through IBM Support and Service
          by referencing APAR IC07995 or in the FIXES subdirectory on the LAN
          Systems Evaluation CD-ROM.


  To enable NetWare Requester support during LAN Distance installation:

  1.  When the NetWare Directory window displays, specify the fully-qualified
      path for the drive and directory where the NetWare Requester product is
      installed on your workstation (for example, C:\NWCLIENT).

  2.  When the NetWare Frame Type window displays, specify the type of frame
      header used by the NetWare Server.

      For Token-Ring LANs, the most common frame type is TOKEN-RING.  For
      Ethernet LANs, the most common frame type is ETHERNET_802.3.  If you do
      not know your frame type, see your LAN administrator.

  To enable NetWare Requester support after the LAN Distance product is
  installed, enable NetWare Requester support through the Settings notebook:

  1.  Open the LAN Distance group window.

  2.  Double-click on the Settings icon to display the Settings notebook.

  3.  Select the NetWare tab.

  4.  Select Enable NetWare Requester Support

  5.  In the NetWare Path field, specify the drive and directory where the
      NetWare Requester product is installed on your workstation (for example,
      c:\NWCLIENT).

  6.  In the Frame Type field, specify the type of frame header used by the
      NetWare Server.

      For Token-Ring LANs, the most common frame type is TOKEN-RING.  For
      Ethernet LANs, the most common frame type is ETHERNET_802.3.  If you do
      not know your frame type, see your LAN administrator.

  7.  Close the Settings notebook.

  8.  When the LAN Distance-Settings dialog box is displayed, select the Yes
      push button to save your changes.

  9.  Shut down and restart your workstation.

  NETWARE REQUESTER FOR OS/2




  28  LAN Distance Quick Start Guide









  The LAN Distance product supports Novell NetWare Requester for OS/2 2.0 or
  later and Novell NetWare Server 2.x, 3.1x, 4.0 or later.


  To set up your LAN Distance Remote to use the NetWare Requester for an OS/2
  product to access a NetWare Server over a LAN Distance connection:

  1.  Install the NetWare Requester product before installing the LAN Distance
      Remote product.

  2.  During installation, select the appropriate network interface card
      driver:

      o   If your NetWare Server is on an Ethernet LAN, select the appropriate
          network interface card driver for the Ethernet adapter.

      o   If your NetWare Server is on a Token-Ring LAN, select TOKEN.SYS as
          the network interface card driver.

          This places the ROUTE.SYS device driver statement in your CONFIG.SYS
          file so the Token-Ring data frames contain the source routing infor-
          mation required by the LAN Distance product.

  3.  Install the LAN Distance Remote product on your workstation.

  4.  Open the Settings notebook and select the LAPS tab, then select the LAPS
      push button to open the LAPS Configure Workstation window.

  5.  From the Current Configuration list box, select the LAN Distance Logical
      Adapter.

  6.  From the Protocols list box, select the IBM NetWare Requester Support
      protocol.

      Select Add from the Protocols list box to add IBM NetWare Requester
      Support to the protocols currently configured for the LAN Distance
      logical adapter.

  7.  In the Current Configuration field, select the LAN Distance Logical
      Adapter and select Edit.

  8.  Record the 12-character hexadecimal address displayed in the Network
      adapter address field and select Cancel.

  9.  In the Current Configuration field, select NetWare Requester Support and
      select Edit.

  10. Enter the 12-character hexadecimal value you recorded earlier in the
      Network adapter address field.

  11. Configure the frame header support to match the type of LAN frame used by
      your NetWare Server.  Type Yes in the appropriate field and select OK.




                                         Installing Common LAN Applications  29









      If you do not know the LAN frame type, see your LAN administrator.  For
      Token-Ring networks, the most common LAN frame type is TOKEN-RING.  For
      Ethernet networks, the most common LAN frame type is ETHERNET_ 802.3.

  12. To save your changes, exit LAPS, and close the Settings notebook.

      NOTE:  Before restarting your workstation to activate these changes, com-
      plete the steps listed in the next section.


  13. Restart your workstation.

  AVOIDING THE NETWARE CONNECTION ERROR


  When you restart your workstation, this NetWare message is displayed:

            NWD0115: Error getting connection ID (0X880F)

  This error occurs because the NetWare Requester is trying to locate the
  NetWare Server before a LAN Distance connection is established.

  To avoid this error message:

  1.  Use an ASCII text editor to comment out the following statement in your
      CONFIG.SYS file:

             REM RUN C:\NETWARE\NWDAEMON.EXE

  2.  Restart your workstation and establish a connection to your LAN Distance
      Connection Server.  Before logging on to the NetWare Server, type the
      following at an OS/2 command prompt:

             DETACH C:\NETWARE\NWDAEMON.EXE

  3.  Each time you restart your workstation, complete step 2 before logging
      onto the NetWare Server.  If you frequently access a NetWare Server, you
      may want to have this command executed automatically on start up.  This
      can be accomplished by using the Autostart Tab under your Phone Book
      Entry in the Settings Notebook.

  RUNNING NETWARE REQUESTER ON A LAN DISTANCE REMOTE

  Review the following considerations for running NetWare Requester on a LAN
  Distance Remote:

  COPYING UTILITIES TO THE NETWARE REQUESTER


  Because the WAN connection cannot efficiently transfer large data files, you
  should copy frequently used NetWare utilities from the NetWare Server to a
  local drive on the NetWare Requester.  Some frequently used utilities include
  LOGON.EXE, LOGOUT.EXE, MAP.EXE and SLIST.EXE.  These utilities are stored in
  the SYS:PUBLIC\ directory on the NetWare Server.  By running these utilities


  30  LAN Distance Quick Start Guide









  from a local drive on the LAN Distance Remote, you avoid the delay involved
  in loading large files over the LAN Distance connection.

  MATCHING MAXFRAME VALUES


  When NetWare Requester is installed on the LAN Distance Remote, the MaxFrame
  parameter in the OSOCKDD_MODt section of the WAL\PROTOCOL.INI file is set to
  the default MaxFrame value (1514) for the NetWare Server.  The MaxFrame
  values defined for the NetWare Requester and NetWare Server should match so
  these workstations send compatible frame sizes.

  For the NetWare Requester, make sure the MaxFrame values in the OSOCKDD_MODt
  and OCOMxt sections of the WAL\PROTOCOL.INI match.  (COMx identifies the COM
  port you are using for LAN Distance; for example, COM1 or COM2.)


  OS/2 NETWARE REQUESTER- ADDITIONAL CONSIDERATIONS

  The following recommendations are for running OS/2 NetWare Requester.  Note
  that a few of the steps only apply to a token ring environment.

  o   To improve performance, copy frequently used NetWare utilities to the
      OS/2 NetWare requester.  For example: LOGON.EXE, LOGOUT.EXE, MAP.EXE and
      SLIST.EXE.

  o   The following is a sample NET.CFG.  Use this configuration when first
      attempting to use the OS/2 NetWare requester over LAN Distance.  Do not
      use the normal buffer size of 4202 for a token ring environment, use
      1514.

           NetWare Requester
             Default Login Drive L
             cache buffers 30
             directory services off

           Link Support
             Buffers xx 1514

  o   For a token ring environment, LAN Distance requires that all frames have
      source routing information.  This means that ROUTE.NLM must be loaded on
      the NetWare server and ROUTE.SYS must be loaded for the OS/2 NetWare
      requester.


  o   The OS/2 NetWare requester must have the latest version of NWREQ.SYS.
      This NetWare fix, R210FT.EXE, is available through IBM Support and
      Service by referencing APAR IC07834 or in the FIXES subdirectory on this
      CD-ROM.


      The OS/2 NetWare requester has a fixed timeout value for resending frames
      when there has been no response from the server.  Over a slow link this



                                         Installing Common LAN Applications  31









      can cause frames to be retransmitted several times causing slow perform-
      ance and REQ1040 and REQ1039 error messages from NETWARE.

      The NWREQ.SYS fix increases the timeout value.  There is a side effect of
      this fix.  When the LAN Distance connection is dropped, it will take
      several minutes for NetWare to destroy the default drive due to the
      longer timeout value.  You may notice this when you are trying to shut-
      down OS/2.

      This NetWare fix is available through IBM Support and Service by refer-
      encing APAR IC07834.

  o   Make sure the OS/2 NetWare requester is version 2.1.  Otherwise NWDAEMON
      must be executed after the LAN Distance connection has been established
      by issuing DETACH C:\NETWARE\NWDAEMON.


  WINDOWS FOR WORKGROUPS 3.11 SUPPORT
  ___________________________________

  This section describes important information for setting up the LAN Distance
  Remote product for Windows to run on Windows for Workgroups 3.11.


  READ THE FOLLOWING BEFORE YOU BEGIN SETUP STEPS


  o   The Windows for Workgroups product and any Windows applications that you
      are using should operate correctly in the LAN environment BEFORE you
      install the LAN Distance product.


      NOTE: Do not configure Windows for Workgroups to LOGON to the LAN on
      startup.  Do not attempt to logon to the LAN until your LAN Distance con-
      nection has been established.


  o   After any upgrades, you must open and close the Settings notebook.
      Select Yes to save default changes to the system configuration files.


  o   Both LAN Distance installation and Network Setup for Windows for
      Workgroups prompt you to restart your workstation to make configuration
      changes active.


      It's only necessary to restart your workstation ONCE, after you complete
      the setup steps that follow.


  o   This problem has been resolved on the LAN Systems Evaluation CD-ROM but
      exists in the production level of the LAN Distance 1.11 code.





  32  LAN Distance Quick Start Guide









      There is a problem where we are getting an error WM10008E, ERROR RECEIVED
      LOADING WINAMAC.SYS, when running on a machine with Windows for
      Workgroups installed. The workaround for this problem is to NOT use high
      memory to load device drivers, that is do not use DOS=UMB.  To resolve
      this limitation, you should call IBM Service and request the fix for IBM
      APAR IC08468.


      This APAR fix has been integrated into the LAN Systems Evaluation CD-ROM.


  o   You may experience the following NetBEUI incompatibility problem when
      using the version of NetBEUI provided with Windows for Workgroups.  Only
      use the IBM NetBEUI if you see this problem:

      -   After you dial the LAN Distance Connection Server, the connection
          status never changes from "connecting" to "connected".


      -   After about 30 seconds, this message is displayed:


          WCL0338:  A processing error occurred in the LAN Distance connection
          software.  The call to 'your phonebook entry name' cannot be com-
          pleted.


          The return code from Dial Services was 'a'.

      If you experience this problem, you may need to manually adjust NetBEUI
      parameters in PROTOCOL.INI to the following recommended values:


                 NETBIOSTIMEOUT=2000
                 NETBIOSRETRIES=4
                 DLCRETRIES=5

      Other possible configuration problems are described in Step 3, "Other
      Possible PROTOCOL.INI Changes".

  SETUP STEPS TO RUN ON WINDOWS FOR WORKGROUPS 3.11


  After installing LAN Distance, follow these steps to setup LAN Distance to
  run on Windows for Workgroups 3.11:


  STEP 1 - NETWORK SETUP  (**REQUIRED**)


  o   Delete any defined physical LAN adapter configuration.





                                         Installing Common LAN Applications  33









  o   LAN Distance provides an OEMSETUP.INF file that allows you to add the
      "LAN Distance Logical Adapter" to the list of adapters that you can
      select for Windows for Workgroups.


      If the "LAN Distance Logical Adapter" is not in the list of adapters that
      Network Setup supports, select "Unlisted or updated network adapter",
      then enter the LAN Distance path (i.e., C:\WAL), in the Install Driver
      window.  This adds the LAN Distance Logical Adapter to the list of sup-
      ported adapters.


  o   For general information about configuring network adapters and protocols
      for Windows for Workgroups, see the "Windows for Workgroups Resource Kit"
      (sold separately).

  STEP 2 - LAN DISTANCE SETTINGS (**OPTIONAL**)


  If you did not complete Basic Settings during LAN Distance installation, you
  will need to do additional configuration through the Settings notebook.


  Otherwise, continue with STEP 3 below.


  For assistance configuring the LAN Distance product, see the LAN Distance
  publications.


  STEP 3 - OTHER POSSIBLE PROTOCOL.INI CHANGES (**OPTIONAL**)


  If you experience performance problems on a LAN workstation that you are
  accessing from a Windows LAN Distance Remote, add the following timer state-
  ments to the NetBEUI section of the PROTOCOL.INI file for this LAN work-
  station.


                TI=60000
                T1=10000
                T2=2000
                NETBIOSTIMEOUT=2000
                NETBIOSRETRIES=4
                DLCRETRIES=5

  If you receive LAN Distance error message WCL0310 at the LAN Distance Remote
  before you finish dialing the LAN Distance Connection Server, change the
  MaxFrame value in the COMx section (i.e.  COM1) of the PROTOCOL.INI file to
  1536.


  STEP 4 - RESTART YOUR WORKSTATION  (**REQUIRED**)



  34  LAN Distance Quick Start Guide









  After completing Steps 1 and 2, and making any other necessary changes
  described in Step 3, restart your workstation.



  NTAS AND WINDOWS FOR WORKGROUP 1.11
  ___________________________________

  This section discusses considerations for a Windows for Workgroups client
  going over LAN Distance to access data on NTAS (Microsoft NT Advanced
  Server).


  1.  Ensure that the Client can connect to the NT Advanced Server, LAN
      Attached, before attempting install the LAN Distance.


  2.  Make sure that you have the LAN Distance Corrective Service installed or
      that you are using LAN Distance 1.11.


  3.  Follow the Windows For Workgroup installation and configuration
      instructions closely (see Windows for Workgroup section).


  4.  At this point you should be able to remotely connect to the NT Advanced
      Server.

  If you have a problem, at this point, with the LOSS OF NETWORK CONNECTIONS:


  o   At the Windows for Workgroup 3.11 Client:

      1.  Make sure you have the Corrective Service Diskette applied.

      2.  Edit the protocol.ini in the windows directory and make sure the
          NetBIOS timers are correct(60000,10000,2000).

      3.  Set maxframesize to 1526 for ethernet or 2048 for token ring.

  o   At the Microsoft NT Advanced Server:

      1.  Edit the NTAS registry local_machine system currentctlset services
          lanmanserver parameters:

          -   Add value "EnableRaw"

          -   Set value "EnableRaw" = 0

      2.  Edit the local_machine system currentctlset services nbf parameters:

          -   Set value "DefaultTITimeout" = 600000000   (decimal)

          -   Set value "DefaultT1Timeout" = 12000000    (decimal)



                                         Installing Common LAN Applications  35









          -   Set value "DefaultT2Timeout" =  3000000    (decimal)

  o   If you expect to run ISDN or VFAST then you might try running with RAW
      I/O enabled.

  NETWORK CONNECTIONS should be stable at this point.



  MICROSOFT'S LAN MANAGER
  _______________________

  If you are using Microsoft's LAN Manager with LAN Distance, complete the
  setup and tuning steps in the following sections.

  OS/2 - LAN MANAGER REQUESTER

  o   Install LAN Manager Requester for OS/2

      NOTE: Because LAN Distance requires OS/2 version 2.0 or higher, you must
      install Microsoft LAN Manager Requester version 2.2.

      When the LAN Manager Requester installation program prompts you for your
      LAN adapter type, select your LAN adapter type from the list.  If your
      workstation does not have a LAN adapter, select ANY LAN adapter type in
      the list.  Do not select "No adapter".  This is the easiest way to get
      LAN Manager Requester set up.

  o   Copy your CONFIG.SYS to CONFIG.LAN. (optional)

      Copy this file if you have a LAN adapter in your workstation and you
      intend to use LAN Manager in both a LAN-attached environment and in a
      remote environment with LAN Distance. You will use the (.LAN) file when
      you are in a LAN-attached environment.

      You can also copy your \LANMAN\LANMAN.INI file to \LANMAN\LANMAN.LAN at
      this point.  Keeping a separate copy of this for your LAN-attached envi-
      ronment will give you slightly improved performance when you are directly
      attached to the LAN.

  o   Edit your CONFIG.SYS:

      1.  Delete or REM the PROTMAN.OS2 device statement from your CONFIG.SYS:

             REM DEVICE=C:\LANMAN\PROTMAN\DRIVERS\PROTMAN.OS2

      2.  Delete or REM the DEVICE= statement for your LAN adapter.  Perform
          this step EVEN if you have a LAN adapter in your workstation.  For
          example, if you selected IBM Token Ring adapter when you installed
          LAN Manager Requester, delete or REM the IBMTOK.OS2 driver statement
          in your CONFIG.SYS:

             REM DEVICE = C:\...\IBMTOK.OS2

  o   Edit your STARTUP.CMD:


  36  LAN Distance Quick Start Guide









      (Temporarily) remark out the starting of the LAN Manager Requester:

         REM NET START WORKSTATION
         REM NET LOGON ...

  o   Edit LANMAN.INI:

      1.  If you are using LAN Manager with NetBEUI, edit your net statement to
          look like the following:

               net1 = netbios$, 0, nb30

          LAN Distance cannot start unless you make this change.

      2.  Add/change the wrkheuristics parameter in the Oworkstationt section
          to look like the following:

               Oworkstationt
               ;                   0         1         2         3
               ;                   01234567890123456789012345678901234
                   wrkheuristics = 11111111213000111110010111200112211

          If you already have a wrkheuristics parameter, the only changes that
          you need to change for LAN Distance are to change the 11th, 12th, and
          13th bits (counting from 0) from a 1 to a 0. These are the RAW data
          transfer protocol bits.  See the Microsoft LAN Manager Administra-
          tor's Reference for a full description of these heuristics.

      3.  Edit/add the sesstimeout value in the Oworkstationt section as
          follows:

               Oworkstationt
                  sesstimeout = 300

  o   Install the LAN Distance Remote for OS/2 product and use the Basic Set-
      tings Option to configure your initial setup.

  o   Edit CONFIG.SYS

      Check/edit statements in your CONFIG.SYS to make sure they look like the
      following.  Make sure they appear in this relative order.

         LIBPATH=C:\IBMCOM\DLL;C:\LANMAN\NETLIB;....

                                              ;only want IBMCOM version of this
         DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
                                              ;only want IBMCOM version of this
         DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2
         RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
         RUN=C:\IBMCOM\LANMSGEX.EXE
                                              ;only want IBMCOM version of this
         DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
         DEVICE=C:\WAL\WCLVPCM.OS2
         DEVICE=C:\IBMCOM\MEMMAN.OS2


                                         Installing Common LAN Applications  37









         DEVICE=C:\IBMCOM\VLAN.OS2
         RUN=C:\IBMCOM\VLANINIT.EXE
         DEVICE=C:\IBMCOM\MACS\PDFH.OS2
         DEVICE=C:\IBMCOM\MACS\MACFH.OS2
         DEVICE=C:\IBMCOM\MACS\WCLCPMAC.OS2

                                                  ; have to move these to here
         DEVICE=C:\LANMAN\NETPROG\RDRHELP.SYS
         IFS=C:\LANMAN\NETPROG\NETWKSTA.SYS /i:C:\LANMAN
         DEVICE=C:\LANMAN\NETPROG\NETVDD.SYS

      NOTE: If you install LAN Distance before you install LAN Manager
      Requester, your CONFIG.SYS will look quite a bit different than this.
      You may notice multiple versions of PROTMAN.OS2 and NETBEUI.OS2 being
      loaded. Be sure to REM out the versions in the \LANMAN paths, and use the
      versions in the \IBMCOM path.

  o   Copy your CONFIG.SYS to CONFIG.REM. (optional)

      Copy this file if you have a LAN adapter in your workstation and you
      intend to use LAN Manager in both a LAN-attached environment and in a
      remote environment with LAN Distance. You will use the (.REM) file when
      you are using LAN Distance in a remote environment.

      If you are keeping a separate copy of \LANMAN\LANMAN.INI for your LAN
      environment, you must copy \LANMAN\LANMAN.INI to \LANMAN\LANMAN.REM.

  o   Complete steps further below under "LAN Manager Server".

  o   "SHUTTLING" on an OS/2 Workstation

      The Shuttle feature in the LAN Distance Remote for OS/2 does not work
      with LAN Manager Requester.  The steps above have enabled you to manually
      "shuttle" between a LAN-attached and a remote environment.

      When you are LAN-attached, simply copy your CONFIG.LAN to CONFIG.SYS and
      LANMAN.LAN to LANMAN.INI (if appropriate) and restart your workstation.

      When you are in a remote environment, copy your .REM files and restart
      your workstation.

  o   TCP/IP NOTE:

      The LAN Manager TCP/IP protocol does not work with LAN Distance.

  LAN MANAGER REQUESTER FOR DOS


  o   Install the LAN Manager Requester for DOS.


      When the LAN Manager Requester installation program prompts you for your
      LAN adapter type, select your LAN adapter type from the list.  If your
      workstation does not have a LAN adapter, select ANY LAN adapter type in


  38  LAN Distance Quick Start Guide









      the list.  Do not select "No adapter".  This is the easiest way to get
      LAN Manager Requester set up.


      If you have a LAN adapter, your workstation will be enabled for shuttling
      between your LAN-attached environment and your remote environment after
      you complete this list of steps.


      Do not restart your workstation.


  o   If you installed an MSDOS Enhanced workstation, add the following line to
      the Oworkstationt section in your LANMAN.INI file:


                Oworkstationt
                ;                 0         1
                ;                 0123456789012345
                  wrkheuristics = 1111211012112000

      If you had already added this line to tune other heuristics, the only
      change necessary for running with LAN Distance is to change bit 14 from a
      1 to a 0. See the Microsoft LAN Manager Administrator's Reference for a
      full description of these heuristics.


  o   Install the LAN Distance Remote for Windows and choose the Basic Settings
      option to configure your initial setup.


      When LAN Distance installation completes, it will ask you if you want to
      be shuttled as a remote workstation or a LAN-attached workstation.  If
      your workstation does not have a LAN adapter, select "Yes" to be shuttled
      for remote connectivity.


  o   Restart your workstation.


  o   If you do not have a LAN adapter in your workstation, disable the LAN
      Distance Shuttle feature:


      1.  Open the LAN Distance program group.

      2.  Open the Settings icon in the LAN Distance program group.

      3.  Turn to the Workstation tab.

      4.  Deselect the "Enable Shuttling Between LAN and Remote Workstation"
          checkbox.

      5.  Close the Settings window.


                                         Installing Common LAN Applications  39











  o   Complete steps further below under "LAN Manager Server".

  SHUTTLE NOTE:


  When you use LAN Manager Requester in the remote environment, the
  PROTOCOL.INI file in your \WAL subdirectory becomes your active PROTOCOL.INI
  file.


  If you use the LAN Distance Shuttle feature to shuttle your workstation back
  to a LAN attached environment, then the PROTOCOL.INI file in your \LANMAN.DOS
  subdirectory becomes the active PROTOCOL.INI file.


  TCP/IP NOTE:


  The LAN Manager TCP/IP protocol does not work with LAN Distance.


  LAN MANAGER SERVER

  Complete the following tuning steps so that the LAN Manager server can work
  with the slower LAN Distance WAN connections:

  o   Edit the LANMAN.INI file:

      1.  Edit the sesstimeout value in the Oworkstationt section as follows:

               Oworkstationt
                  sesstimeout = 300

      2.  Add a srvheuristics parameter (or change the current one) in the
          Oservert section:

               Oservert
                ;                 0         1
                ;                 01234567890123456789
                  srvheuristics = 11110151111211021331

          If you already have a srvheuristics parameter, the only change neces-
          sary for LAN Distance is to change bit 15 from a 0 to a 2.  This will
          increase the Opportunistic Lock Timeout.  See the Microsoft LAN
          Manager Administrator's Reference for a full description of these
          heuristics.

  o   If you are running the NETBIOS protocol over a LAN Distance WAN con-
      nection, edit the PROTOCOL.INI file:





  40  LAN Distance Quick Start Guide









      The NETBIOS timer values must be relaxed to handle the slower WAN con-
      nection.  Add or the change the following parameters in the NETBEUI_XIF
      section:

           ONETBEUI_XIFt
              TI = 60000
              T1 = 10000
              T2 = 2000


  BANYAN VINES
  ____________

  This section discusses Banyan VINES fixes and setup information to run Banyan
  VINES with the LAN Distance product.

  BANYAN FIXES

  The following Banyan fix is in the Banyan Maintenance release 5.54(5).  If
  this release is not available, then contact your Banyan SE.


  Two modifications to the Banyan VINES protocol drivers were required for
  Banyan VINES and LAN Distance to work together correctly:


  1.  Adjustable metrics were added for the NDIS protocol.  This required mod-
      ification to the server and client side drivers.  The server side is
      adjusted dynamically; therefore, no configuration is required.  On the
      client side an additional parameter was added for the NDIS configuration:

         METRIC=xx
            - where xx is the configured metric for the client interface

      If the metric parameter is not used, NDIS will default to 2 for Ethernet
      and 16Meg token ring, 4 for 4 Meg token ring. This metric is a timeout
      value for determining when to retransmit a frame.

      The following summarizes metric parameters values:

      SERIAL PORT SPEEDS                  METRIC VALUES
      9600, 19,200                       90
      38,400                             80
      57,600 AND HIGHER                  45

      This parameter goes in the PROTOCOL.INI OVINES_XIFt section:

         OVINES_XIFt
            DRIVERNAME=NDISBAN$
            BINDINGS="SOCKDD_MOD"
            LANABASE=0
            METRIC=90

  2.  For the DOS/Windows Client only A PACEMODE parameter was added to prevent
      buffer overflow when multiple SPP connections are in use at the same


                                         Installing Common LAN Applications  41









      time.  PACEMODE=0 is the default which allows windowing of SPP packets,
      PACEMODE=1 puts the SPP connection into single packet mode.


      This parameter goes in the PROTOCOL.INI OVINES_XIFt section.


      Additionally, the DOS/Windows Banyan client was changed to allow Banyan
      to start when the network does not exist.  Over LAN Distance the network
      does not exist until the LAN Distance connection is established.

  BANYAN DOS WORKSTATION SETUP


  Use the following steps for setting up the Banyan DOS workstation:


  1.  Install Banyan on the DOS workstation.


  2.  Install LAN Distance and configure the remote workstation for connecting
      to the connection server.


  3.  Run PCCONFIG.  Set the default Network Card settings for either the NDIS
      token ring or NDIS Ethernet drivers.  Specify SOCKDD_MOD as the
      PROTOCOL.INI bindings.  For the NDIS token ring driver, end node source
      routing must be enabled.


      Select the NDIS token ring or NDIS Ethernet driver as the default commu-
      nications driver.


  4.  Edit PROTOCOL.INI and add the following lines:

             OVINES_XIFt
                DRIVERNAME=NDISBAN$
                BINDINGS="SOCKDD_MOD"
                PACEMODE=0
                LANABASE=0
                METRIC=90

      Additionally, make sure that the MAXFRAME parameter is set to 1524 in the
      COM port and SOCKDD_MOD sections of PROTOCOL.INI.


  5.  Edit AUTOEXEC.BAT and add the following lines in the following order for
      an Ethernet configuration:

               BAN /NC
               NDISBAN
               c:\WAL\DOSBIND
               REDIRALL


  42  LAN Distance Quick Start Guide









               WIN

      NOTES:

      a.  For token ring use NDTOKBAN instead of NDISBAN.


      b.  Do not run the ARSWAIT program which is normally run with NDIS
          drivers under VINES.

  6.  Reboot the workstation.  When AUTOEXEC.BAT is executed, you will see the
      following message which is normal:


      No Network Interface enabled . . .


  7.  Establish a LAN Distance connection.  At this point the Z drive will
      exist and you can login to the Banyan server.


  8.  Note that frequently used executables such as login should be copied to
      the local Banyan vines directory.  See chapter 10 in the LAN Distance
      Advanced Guide for the section on additional tips for using Banyan vines
      over LAN Distance.

   SAMPLE CONFIGURATION FILES FOR BANYAN VINES DOS CLIENT

  CONFIG.SYS - BANYAN VINES

       DEVICE=C:\DOS\HIMEM.SYS
       DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
       DOS=HIGH,UMB
       DEVICE=C:\DOS\SETVER.EXE
       FILES=30
       BUFFERS=10
       STACKS=9,256
       DEVICE=c:\WAL\protman.dos /I:c:\WAL
       DEVICEHIGH=c:\WAL\taplf.dos
       DEVICEHIGH=c:\WAL\dxmj0mod.sys
       DEVICEHIGH=c:\WAL\DOSVMAC.SYS
       DEVICE=c:\WAL\WINAMAC.SYS
       DEVICEHIGH=c:\WAL\PCMDD.SYS

  AUTOEXEC.BAT - BANYAN VINES











                                         Installing Common LAN Applications  43









       C:\WINDOWS\SMARTDRV.EXE
       @ECHO OFF
       PROMPT $p$g
       PATH=c;C:\WINDOWS;c:\vines;C:\;C:\DOS
       SET TEMP=C:\DOS
       C:\DOS\MOUSE.COM
       cd vines
       BAN /nc
       NDTOKBAN
       c:\WAL\DOSBIND
       redirall
       cd ..

  PROTOCOL.INI - BANYAN VINES










































  44  LAN Distance Quick Start Guide









       OPROTOCOL_MANAGERt
          DriverName=PROTMAN$
          Bindings=SOCKDD_MOD

       OVINES_XIFt
          DRIVERNAME=NDISBAN$
          BINDINGS="SOCKDD_MOD"
          PACEMODE=0
          LANABASE=0
          METRIC=90

       ONETBEUIt
          DriverName=NETBEUI$
          Bindings=SOCKDD_MOD
          NCBS=32
          Sessions=32
          Names=17
          MaxDatarcv=4168
          MaxTransmits=6
          TI=60000
          T1=10000
          T2=2000

       OSOCKDD_MODt
          DriverName=VLANMAC$
          LanType="TokenRing"
          Mode="FLOWS"
          NetAddress="t4000321D6AB5"
          MaxFrame=1524

       OCOM1t
          DriverName=COM1MAC$
          MAXFRAME=1524
          PCMSUPPORT="yes"
          MACTYPE="802.5"
          CONN_TYPE="Switched"
          TX_FIFO_SIZE=7
          PCMCIA="no"
          PORTNAME="COM1"

       OPDFH_nift
          DriverName=PDFH$

  BANYAN OS/2 WORKSTATION SETUP

  See the LAN Distance Advanced Guide, Chapter 10, section "Configuring the LAN
  Distance Remote for Banyan VINES" for setting up a Banyan OS/2 workstation
  with LAN Distance. The following are 2 additional steps that are required for
  a token ring environment:

  1.  In a token ring environment, run PCCONFIG and make sure End Node Source
      Routing is enabled.




                                         Installing Common LAN Applications  45









  2.  Optionally, the Banyan Server can be configured to use Source Level
      Routing (SLR). This is done under the Manage Communications option.
      However, the server will use SLR in all responses to clients that are
      using SLR.


  IBM LAN SUPPORT PROGRAM
  _______________________

  You only need install LAN Support Program if you need to add 802.2 protocol
  support with Windows. LAN Distance Remote for Windows includes NDIS, NetBIOS,
  ODI2NDI support.  LAN Distance Remote for OS/2 also includes the 802.2
  support.


  You could have installed the LAN Support Program device drivers before
  installing LAN Distance, this is what the LAN Distance books recommend.
  However, if you choose to install LAN Distance first, it will make installing
  LSP a little trickier, but you will understand what it is doing a bit more.


  Before you start, shutdown LAN Distance and stop Windows.  YOu will be using
  LAN Support Program 1.35, which is the latest as of the writing of this docu-
  ment. Insert LSP diskette in the A: drive and follow the installation
  instructions.  You should keep the following in mind:


  o   C:\LSP is the target drive for LSP

  o   You Want to Update CONFIG.SYS and AUTOEXEC.BAT

  o   SOCKDD_MOD is the Primary Adapter (this is the LAN Distance Driver)

  o   You want to add the additional 802.2 protocol for NDIS

  At the end there is an Information panel that says there were no NDIS drivers
  added to CONFIG.SYS. Actually several files are sort of messed up and you
  will need to fix them.


  1.  First you will need to fix CONFIG.SYS. Use your favorite editor and edit
      CONFIG.SYS.


      o   Change the PROTMAN.DOS and DXMJ0MOD.SYS statements to point to C:\WAL
          instead of C:\LSP.

      o   Move the DXMJ0MOD.SYS before the DXME0MOD.SYS.

      o   Remove the comments about adding or removing drivers.

      See Appendix B of the LAN Distance Remote Users Guide for more details if
      you need them;




  46  LAN Distance Quick Start Guide









      Here is how the CONFIG.SYS will look:


              BREAK=ON
              BUFFERS=30
              FILES=40
              STACKS=9,256
              DEVICE=C:\DOS\ANSI.SYS
              DEVICE=C:\DOS\HIMEM.SYS
              DOS=HIGH,UMB
              DEVICE=C:\DOS\EMM386.EXE NOEMS
              DEVICE=C:\WAL\PROTMAN.DOS /I:C:\WAL
              DEVICE=C:\LSP\DXMA0MOD.SYS 001
              DEVICE=C:\WAL\DXMJ0MOD.SYS
              DEVICE=C:\LSP\DXME0MOD.SYS
              DEVICEHIGH=c:\WAL\dosvmac.sys
              DEVICEHIGH=c:\WAL\winamac.sys
              DEVICEHIGH=c:\WAL\pcmdd.sys

  2.  Now you will need to make one change to the AUTOEXEC.BAT. Use your
      favorite editor to edit AUTOEXEC.BAT and remove the \LSP\NETBIND state-
      ment.


      This will leave the C:\wal\dosbind to do the protocol binding.  Here is
      what the AUTOEXEC.BAT looks like:


              c:\WAL\DOSBIND
              @ECHO OFF
              set TEMP=C:\dos
              path=c:\WAL;c:\windows;c:\dos;
              PROMPT $P$G
              lh doskey

  3.  Finally you will need to update the PROTOCOL.INI file. LAN Distance uses
      C:\WAL\PROTOCOL.INI and LSP used C:\LSP\PROTOCOL.INI. DXMAID did not
      update the PROTOCOL.INI in the C:\WAL subdirectory so you need to do that
      manually.  Edit the C:\WAL\PROTOCOL.INI file and add:


              ODXME0_NIFt
                 DriverName = DXME0$
                 Bindings = SOCKDD_MOD

      You can add it near the top. Here is the complete PROTOCOL.INI file:










                                         Installing Common LAN Applications  47









              OPROTOCOL_MANAGEt
                 DriverName=PROTMAN$
                 Bindings=SOCKDD_MOD

              ODXME0_NIFt
                 DriverName = DXME0$
                 Bindings = SOCKDD_MOD

              ONETBEUIt
                 DriverName=NETBEUI$
                 Bindings=SOCKDD_MOD
                 NCBS=32
                 Sessions=32
                 Names=17
                 MaxDatarcv=4168
                 MaxTransmits=6
                 TI=60000
                 T1=10000
                 T2=2000

              OSOCKDD_MODt
                 DriverName=VLANMAC$
                 LanType="TokenRing"
                 Mode="Flows"
                 NetAddress=T40000B4C1AAA
                 MaxFrame=1080

              OCOM1t
                 MaxFrame=1080
                 MACTYPE="802.5"
                 DRIVERNAME="COM1MAC$"
                 PCMSUPPORT="YES"
                 CONN_TYPE="SWITCHED"
                 PORTNAME="COM1"
                 TX_FIFO_SIZE=7

  When this is complete, reboot the system. You should see a lot of driver mes-
  sages and finally a message MS DOS LAN Manager Netbind v1.1 and no failure
  messages after that. If there is a failure, recheck the files. Also refer to
  the LAN Distance Documents for help.



  IBM PC/3270 V3.0
  ________________

  To install Personal Communications/3270 V3.0 for Windows, you need to
  remember that PC/3270 uses the 802.2 interface which requires that LSP be
  installed.  When configuring PC/3270 the following should be considered:


  o   You will configure PC/3270 for a LAN connection using 802.2





  48  LAN Distance Quick Start Guide









  o   You will need to get YOUR host gateway address from your Systems Adminis-
      trator.  This will be something like 400079991001 and if it is not
      entered correctly you will get a COM 686 error message.  Keep in mind,
      this is not YOUR workstation address, it is the address of your host
      gateway.


  o   The default PIU size is 265.  It might be better to increase this to
      1033. It should match the MAXDATA= value for your host.  If this value is
      too large, you will get a COM 682 Error.  If it is too small, you can get
      COM 685 or 510 errors.


  o    You will need YOUR individual workstation identifier.  You must have
      been given a value by your systems administrator. This must be accurate
      or you will not get a connection.  This must be unique or you will not
      get a connection (COM 685). See Help for more information.


  o    The Block ID is used in combination with the PUID to form your work-
      stations' identification to the host gateway. 05D is the value that is
      used for OS/2 Communications Manager, and is quite common. 061 is the
      default for PC/3270. 017 is an older one that is common. Get this from
      your systems administrator. It must be accurate or you will not get a
      host connection (COM 685)


  When you start LAN Distance and PC/3270 you might have to wait up to 35
  seconds for the logo.  You should get a 3270 session. If you did not, check
  out these error codes and their causes:


  o   COM 686 - Destination Gateway Not responding at all. Either invalid
      address, gateway is down, or LAN Distance is not connected.


  o   C0M 685 - Workstation found gateway, but the gateway did not acknowledge
      the Block ID/PU ID. Either you entered wrong Block ID and PU ID, or
      someone else is using your values.


  o   COM 682 - PIU size it too large. It must fit into the MaxFrame= value in
      the PROTOCOL.INI file (default of 1080, there is a header also). 1033
      fits into a 1080 buffer.


  o   COM 680/510/686 blinking. Your PIU size is too small for what is config-
      ured at the host. Either have the host people make the MAXDATA= on the PU
      statement smaller, or increase the PIU size and the MaxFrame= value in
      the PROTOCOL.INI file .






                                         Installing Common LAN Applications  49









  ATTACHMATE XTRA
  _______________

  This section discusses configuration file changes you must make to use
  AttachMate Xtra Versions 3.4 and 4.0 with LAN Distance.


  USING ATTACHMATE XTRA VERSION 3.4


  o   The sample configuration files in section 7.1 below demonstrate a working
      configuration for using Xtra Version 3.4 and IBM DOS LAN Requester with
      the LAN Distance Remote product.


  o   NOTE:  You need to make two important changes in the \WAL\PROTOCOL.INI
      file if you are dialing in to a Token Ring LAN.  If you are dialing in to
      an Ethernet LAN, the changes are not necessary but the sample files may
      be helpful in getting your workstation memory optimized so that both pro-
      grams may load.

  USING ATTACHMATE'S XTRA VERSION 4.0


  o   If you are using AttachMate's Xtra version 4.0, you will not need the
      following line in your AUTOEXEC.BAT:


      C:\EXTRAWIN\DLCINTFC /I=265 /M /E


  o   Edit your SYSTEM.INI file to change the VATMDLC_ETHERNETNETWORK parameter
      to YES.  Do this regardless of whether you are dialing in to a Token Ring
      or Ethernet LAN.


  o   You may need to increase your NETHEAP parameter to use AttachMate Xtra
      with LAN Distance.

  SAMPLE CONFIGURATION FILES FOR ATTACHMATE XTRA

  CONFIG.SYS - ATTACHMATE XTRA















  50  LAN Distance Quick Start Guide









       BREAK=ON
       buffers=42
       FILES=30
       rem DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
       DEVICE=C:\DOS\HIMEM.SYS
       dos=high,umb
       DEVICE=C:\DOS\SETVER.EXE
       DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
       rem device=c:\dos\ramboost.exe load
       STACKS=9,256
       SHELL=C:\COMMAND.COM /E:2000 /P
       LASTDRIVE=Z
       DEVICEHIGH=c:\WAL\protman.dos /I:c:\WAL
       DEVICE=c:\LSP\dxma0mod.sys
       DEVICEHIGH=c:\WAL\dxmj0mod.sys
       DEVICE=c:\LSP\dxme0mod.sys
       DEVICEHIGH=c:\WAL\dosvmac.sys
       DEVICEHIGH=c:\WAL\WINAMAC.SYS
       DEVICEHIGH=c:\WAL\PCMDD.SYS

  AUTOEXEC.BAT - ATTACHMATE XTRA

       c:\WAL\DOSBIND
       REM C:\WINDOWS\SMARTDRV.EXE
       @ECHO OFF
       PROMPT $p$g
       PATH c:\WAL;C:\DOSLAN;C:\EXTRAWIN;C:\WINDOWS;C:\DOS;
       SET TEMP=C:\DOS
       C:\DOS\MOUSE.COM
       doskey
       REM ***********************************************************************
       REM
       REM                    DLC Interface Module Description
       REM
       REM /I=#### number is the IFrame size values are 265, 521, 1033, 2042, 3964
       REM
       REM /S  use a Small Buffer Pool
       REM /M  use a Medium Buffer Pool
       REM /L  use a Large Buffer Pool
       REM
       REM /U  unload the DLC interface module
       REM
       pause
       REM
       REM Note, the /I=265 below may not work in all environments.
       REM
       C:\EXTRAWIN\DLCINTFC /I=265 /M /E

  PROTOCOL.INI - ATTACHMATE XTRA







                                         Installing Common LAN Applications  51









       OPROTOCOL_MANAGEt
          DriverName=PROTMAN$
          Bindings=SOCKDD_MOD

       ONETBEUIt
          DriverName=NETBEUI$
          Bindings=SOCKDD_MOD
          NCBS=32
          Sessions=32
          Names=17
          MaxDatarcv=4168
          MaxTransmits=6
          TI=60000
          T1=10000
          T2=2000

       ODXME0_NIFt
          DriverName = DXME0$
          Bindings = SOCKDD_MOD

       OSOCKDD_MODt
          DriverName=VLANMAC$
          LanType="TokenRing"
          Mode="FLOWS"
          NetAddress="t40001F960227"
          MaxFrame=1536                <--- changed for Token Ring environment

       OCOM1t
          MaxFrame=1536                <--- changed for Token Ring environment
          MACTYPE="802.5"
          DRIVERNAME="COM1MAC$"
          PCMSUPPORT="YES"
          CONN_TYPE="SWITCHED"
          PORTNAME="COM1"
          TX_FIFO_SIZE=7

       OPDFH_nift
          DriverName=PDFH$


  IBM DOS TCP/IP 2.1.1
  ____________________

  You could have installed TCP/IP before you installed LAN Distance, this is
  what the LAN Distance Books recommend.  However, if you choose to install LAN
  Distance first, it will make installing LAN Distance a little trickier, but
  you will understand what it is doing a bit more.  You should keep in mind the
  following when configuring DOS TCP/IP:


  o   You will configure TCP/IP to use the LAN, NDIS, interface.

  o   If you install LAN Distance first, you will need to select a real adapter
      as the "bound" adapter. After configuration this will be corrected.



  52  LAN Distance Quick Start Guide









  o   You will need to get your IP Address, Subnet Mask, Router IP address in
      order to configure TCP/IP.

  Once you have configured TCP/IP you will need to make some changes manually.
  We have to check the CONFIG.SYS and modify AUTOEXEC.BAT and
  C:\WAL\PROTOCOL.INI.


  The following is a sample CONFIG.SYS with TCP/IP support installed:



          BREAK=ON
          BUFFERS=30
          FILES=40
          STACKS=9,256
          DEVICE=C:\DOS\ANSI.SYS
          DEVICE=C:\DOS\HIMEM.SYS
          DOS=HIGH,UMB
          DEVICE=C:\DOS\EMM386.EXE NOEMS
          DEVICE=C:\WAL\PROTMAN.DOS /I:C:\WAL
          DEVICE=C:\LSP\DXMA0MOD.SYS 001
          DEVICE=C:\WAL\DXMJ0MOD.SYS
          DEVICE=C:\LSP\DXME0MOD.SYS
          DEVICEHIGH=c:\WAL\dosvmac.sys
          DEVICEHIGH=c:\WAL\winamac.sys
          DEVICEHIGH=c:\WAL\pcmdd.sys
          LASTDRIVE=Z
          DEVICE=C:\TCPDOS\BIN\DOSTCP.SYS

  You need to edit AUTOEXEC.BAT and remove the c:\TCPDOS\BIN\NETBIND statement
  at the top. We want to use the c:\WAL\DOSBIND program.


  Here is the AUTOEXEC.BAT for PC/3270, DLR and TCP/IP:


          c:\WAL\DOSBIND
          @ECHO OFF
          PROMPT $P$G
          path=c:\doslan;c:\wal;c:\dos;c:\windows;C:\TCPDOS\BIN;
          SET TEMP=C:\DOS
          SET ETC=C:\TCPDOS\ETC
          doskey
          NET START
          CALL TCPSTART
          WIN

  In the C:\WAL\PROTOCOL.INI we need to add the TCP/IP section.  This is the
  highlighted section in this complete PROTOCOL.INI as follows:






                                         Installing Common LAN Applications  53









          OPROTOCOL_MANAGEt
             DriverName=PROTMAN$
             Bindings=SOCKDD_MOD

          OTCPIP_V21t               <=====TCP/IP SECTION
             Drivername=DOSNDIS$
             Bindings = SOCKDD_MOD

          ODXME0_NIFt
             DriverName = DXME0$
             Bindings = SOCKDD_MOD

          ONETBEUIt
             DriverName=NETBEUI$
             Bindings=SOCKDD_MOD
             NCBS=32
             Sessions=32
             Names=17
             MaxDatarcv=4168
             MaxTransmits=6
             TI=60000
             T1=10000
             T2=2000

          OSOCKDD_MODt
             DriverName=VLANMAC$
             LanType="TokenRing"
             Mode="Flows"
             NetAddress=T400027927F65
             MaxFrame=1080

          OCOM1t
             MaxFrame=1080
             MACTYPE="802.5"
             DRIVERNAME="COM1MAC$"
             PCMSUPPORT="YES"
             CONN_TYPE="SWITCHED"
             PORTNAME="COM1"
             TX_FIFO_SIZE=7


  LAN WORKPLACE FOR DOS
  _____________________

  After installing LAN Workplace for DOS and then LAN Distance, follow the
  steps below.

  1.  Edit WAL\PROTOCOL.INI and add the following ODI2NDI section:

           OODI2NDI_modt
              DRIVERNAME=ODI2NDI$
              BINDINGS=SOCKDD_MOD
              NetAddress="t400010FD0DFA"
              TOKEN-RING=YES
              TOKEN-RING_SNAP=YES


  54  LAN Distance Quick Start Guide









  2.  Edit the NET.CFG file and change the Link Driver line to Link Driver
      SOCKDD_MOD:

           Link Driver SOCKDD_MOD
                   Frame TOKEN-RING_SNAP
                   Protocol IP 800 TOKEN-RING_SNAP

      NOTE:  Currently, the DOS implementation of ODI2NDI only supports one
      protocol at a time. Therefore, it is not possible to support IPX and IP
      at the same time.  This restriction does not apply for LAN Distance
      Remote for OS/2.  If you need to run both TCP/IP and the NetWare client,
      you will need a NDIS based TCP/IP program such as IBM DOS TCP/IP.


  3.  Edit LANWP.BAT and change the token driver to ODI2NDI and add the
      C:\WAL\DOSBIND statement after the ODI2NDI line.


  4.  Edit AUTOEXEC.BAT and remove the C:\WAL\DOSBIND statement.


  5.  In a token ring environment, make sure ROUTE is loaded in LANWP.BAT.  LAN
      Distance requires that source level routing information be in all frames.
      Add the following ROUTE statement before the TCPIP.EXE line in LANWP.BAT:


                  c:\net\nwclient\route

  SAMPLE CONFIGURATION FILES FOR LAN WORKPLACE FOR DOS

  CONFIG.SYS - LAN WORKPLACE FOR DOS

       DEVICE=C:\DOS\HIMEM.SYS
       DEVICE=C:\WINDOWS\EMM386.EXE noems
       DOS=HIGH,UMB
       DEVICE=C:\DOS\SETVER.EXE
       FILES=30
       BUFFERS=30
       STACKS=9,256
       SHELL=C:\COMMAND.COM /E:2000 /P
       LASTDRIVE=Z
       DEVICE=C:\DOS\ansi.sys
       DEVICE=c:\WAL\protman.dos /I:c:\WAL
       DEVICE=c:\WAL\dxmj0mod.sys
       DEVICE=c:\WAL\dosvmac.sys
       DEVICEHIGH=c:\WAL\winamac.sys
       DEVICEHIGH=c:\WAL\pcmdd.sys

  AUTOEXEC.BAT - LAN WORKPLACE FOR DOS







                                         Installing Common LAN Applications  55









       @ECHO OFF
       PROMPT $p$g
       path=c:\WAL;c:\doslan;c:\windows;c:\dos;
       SET TEMP=C:\TEMP
       LH DOSKEY
       CALL C:\NET\bin\lanwp.bat

  LANWP.BAT - LAN WORKPLACE FOR DOS

       C:\NET\bin\yesno "Do you want to load the networking software? y/n"
       if errorlevel 1 goto noload
       PATH C:\NET\BIN;%path%
       C:\NET\nwclient\lsl.com
       C:\WAL\ODI2NDI
       c:\WAL\DOSBIND
       c:\net\nwclient\route
       tcpip.exe
       set name=rcp
       break on
       :noload

  PROTOCOL.INI - LAN WORKPLACE FOR DOS


































  56  LAN Distance Quick Start Guide









       OPROTOCOL_MANAGEt
          DriverName=PROTMAN$
          Bindings=SOCKDD_MOD

       ONETBEUIt
          DriverName=NETBEUI$
          Bindings=SOCKDD_MOD
          NCBS=32
          Sessions=32
          Names=17
          MaxDatarcv=4168
          MaxTransmits=6
          TI=60000
          T1=10000
          T2=2000

       OSOCKDD_MODt
          DriverName=VLANMAC$
          LanType="TokenRing"
          Mode="Flows"
          NetAddress=T400010FD0DFA
          MaxFrame=1514

       OCOM1t
          MaxFrame=1514
          MACTYPE="802.5"
          DRIVERNAME="COM1MAC$"
          PCMSUPPORT="YES"
          CONN_TYPE="SWITCHED"
          PORTNAME="COM1"
          TX_FIFO_SIZE=7

       OODI2NDI_modt
          DRIVERNAME=ODI2NDI$
          BINDINGS=SOCKDD_MOD
          NetAddress="t400010FD0DFA"
          TOKEN-RING=YES
          TOKEN-RING_SNAP=YES

  NET.CFG - LAN WORKPLACE FOR DOS
















                                         Installing Common LAN Applications  57









       Link Support
               Buffers 4 2202
               MemPool 4096

       Link Driver SOCKDD_MOD
               Frame TOKEN-RING_SNAP
               Protocol IP 800 TOKEN-RING_SNAP

       Protocol TCPIP
               ip_router       129.35.16.1
               ip_netmask      255.255.240.0
               ip_address      129.35.19.173
               PATH LANG_CFG   C:\NET\LANG
               PATH SCRIPT     C:\NET\SCRIPT
               PATH PROFILE    C:\NET\PROFILE
               PATH LWP_CFG    C:\NET\HSTACC
               PATH TCP_CFG    C:\NET\TCP







































  58  LAN Distance Quick Start Guide









  ADDITIONAL CONSIDERATIONS FOR WORKING WITH LAN DISTANCE
  _______________________________________________________





  This section discusses additional items for the LAN Distance product that are
  not covered in the version 1.1 publications.



  LAN DISTANCE SETUP UTILITIES
  ____________________________

  The third diskette of the LAN Distance package contains two utilities that
  are not copied to your hard file when LAN Distance is installed.  For non-US
  versions, a third utility is also on the third diskette.

  The utility named CFMODEM.EXE is an aid in creating new modem types if your
  modem is not listed as a predefined modem. Refer to Appendix D of the LAN
  Distance Advanced Guide for a description of this utility.

  The utility named CALLBRDG.EXE provides an aid to the LAN Distance Connection
  Server administrator in determining the bridge and ring (segment) numbers of
  a Token-Ring LAN attached to the LAN Distance Connection Server. Refer to the
  file named CALLBRDG.RME for a description of this utility.

  For non-US versions only, the third utility named OS2PING.EXE is a multi-
  purpose program that aids in Token-Ring LAN configuration and problem deter-
  mination. View OS2PING.INF for a description of this utility.

  To install these utilities to your hard file, place the third diskette of the
  LAN Distance package into a diskette drive and enter:

     sourceDr:INSTAPPL sourceDr: targetDr:

        - Where sourceDr is the drive letter of the diskette drive that
                         contains LAN Distance diskette 3.
        - Where targetDr is the drive letter of the hard file that
                         contains the \WAL directory.

     Example:  A:INSTAPPL A: C:

  CFMODEM may also assist you in correcting problems such as WCL0219 or WCL0221
  during installation/configuration.












                    Additional Considerations for Working With LAN Distance  59









  IBM AUTO/DUAL LANSTREAMER ADAPTERS (TOKEN RING PROMISCUOUS MODE) SUPPORT
  ________________________________________________________________________

  The LAN Distance product supports the following IBM Auto or Dual LANStreamer
  Adapters:

  o   IBM Auto LANStreamer MC 32 Adapter
  o   IBM Dual LANStreamer MC 32 Adapter
  o   IBM Auto LANStreamer ISA Adapter

  NOTE:  Before using these adapters you will need the latest version, Version
  4.01.00, of the IBMMPC.NIF and IBMMPC.OS2.  Please contact IBM Support and
  Service to obtain the updated device drivers.  This device driver is also
  contained in the FIXES Subdirectory of the LAN Systems Evaluation CD-ROM.


  To use the above IBM Auto or Dual LANStreamer Adapters for bridging on a LAN
  Distance Connection Server, do the following:

  1.  Install the LANStreamer adapter according to the adapter installation
      instructions.

  2.  If using the ISA version of the adapter, configure the adapter with the
      adapter installation diskette.

  3.  If using the MC Adapter, configure the adapter with the reference
      diskette.

  4.  Use LAPS to install the adapter device driver and configure the adapter
      for LAPS.

  5.  Edit your \WAL\WCLLOCAL.INI file and add the following lines (it doesn't
      matter where these lines are added):

         OTOKENRINGMACSt
            IBMTOK.NIF
            IBMMPC.NIF

         OIBMMPC.NIFt
            LLCONLY = "YES"
            LOOPBACK = "NO"

  6.  Start LAN Distance

  7.  Open the Settings Notebook

  8.  Select the Address/LAN tab

  9.  After the Settings Notebook has finished initializing, you will see a
      list of adapters available for bridging in the "Adapter for Bridging"
      listbox.  Find the "IBM Streamer Family adapter (IBMMPC.OS2)" entry and
      select it.





  60  LAN Distance Quick Start Guide









  10. When you close the Settings Notebook, your LAN Distance Connection Server
      will be set up for bridging with the IBM Auto or Dual LANStreamer
      adapter.  Shutdown and restart the workstation.


  WAC ADAPTER SETUP
  _________________

  NOTE: The WAC Adapter must be configured through LAPS in LAN Distance.  DO
  NOT configure this adapter through LAPS outside of LAN Distance.

  After installing the WAC Adapter, the ROM address will be displayed on your
  screen while your workstation is restarting.  Write this ROM address down and
  enter it during LAPS configuration.

  To configure the WAC Adapter:

  1.  Open the Settings notebook

  2.  Select the LAPS tab

  3.  Select LAPS

  4.  Edit or add the WAC adapter to the list of already-installed adapters.

  5.  On the WAC Adapter configuration panel, note the following items:

      o   Enter the ROM address of the WAC Adapter recorded above.

      o   For "Line Mode" enter 0 for Constant RTS.

      o   For "MAC Type Description" enter HDLC.

      o   When selecting NRZ vs NRZI, be consistent with the way you configured
          your modem in LAN Distance.  If you used V.35 connection, select NRZ
          by entering 0 for No. If you used generic synchronous switched or
          synchronous leased line, select NRZI by entering 1 for Yes.

          NOTE:  You may also use NRZ for generic synchronous switched or syn-
          chronous leased line.  However, you must carefully configure LAN Dis-
          tance to use it:

          -   Edit WCLNET.INI after all other installations to change the
              encoding scheme from NRZI to NRZ.

          -   Make changes in Settings notebook to Phonebook and Answer Cri-
              teria

              FOR SYNCHRONOUS SWITCHED:

              -   In the Settings notebook Phonebook tab, select Add.
              -   Select the Modem tab
              -   Change the Encoding Scheme to NRZ.

              FOR SYNCHRONOUS LEASED LINE:


                    Additional Considerations for Working With LAN Distance  61









              -   In the Settings notebook Phonebook tab, select Add.
              -   Select the Connect tab
              -   Change the Encoding Scheme to NRZ.
              -   In the Settings notebook Answer Criteria tab, select Add.
              -   Select the Connect tab
              -   Change the Encoding Scheme to NRZ.

      o   For "ANDIS PCM Support" enter 1 for YES.

      o   For "Slot Number" enter the slot number in which the adapter is
          inserted.

      o   For "Port Number" enter the port for which the adapter is configured.
          The upper port is the one farthest from the system board; the lower
          port is the one closest to the system board.

      o   For "Link Connection type" enter 1 for switched or 0 for non-switched
          (leased line) connections.

      o   For "Portname displayed in the PPAT table" enter a name to identify
          the adapter to the port connection manager.

      o   Typically, you can use default values for the rest of the parameters.


  X25 README FILES
  ________________

  The file named "README.X25" is available on diskette number 3 and may be
  copied to your disk by placing the third diskette of the LAN Distance OS/2
  package into a diskette drive and entering the command:

     sourceDr:PKUNZIP2 sourceDr:\WAL\X25RME.ZIP targetDr:README.X25

        - Where sourceDr is the drive letter of the diskette drive that
                         contains LAN Distance diskette 3.
        - Where targetDr is the drive letter of the disk that is to
                         contain the files.

     Example:  A:PKUNZIP2 A:\WAL\X25RME.ZIP C:README.X25


  COUNTRY CODE AND PHONE BOOK TABS
  ________________________________

  If your country code is not US or Great Britain, tabs will not appear in the
  Phone Book window.  You may see references to these tabs in the Phone Book
  helps, but they will not appear if your country code is not US or Great
  Britain.









  62  LAN Distance Quick Start Guide









  IBM7855.EXE TOOL
  ________________

  The IBM7855.EXE tool used to externally configure the IBM 7855 Modem is
  available from these sources:

  o   CompuServe users can access the PSPAPROD forum and access this file in
      the LAN Distance product's library section.

  o   Users with access to IBMLink through OS2BBS can access this file in the
      REMOTE section of the OS/2 Software Library (3).














































                    Additional Considerations for Working With LAN Distance  63

































































  64  LAN Distance Quick Start Guide









  TROUBLE SHOOTING COMMON PROBLEMS
  ________________________________





  COMMON ERROR CONDITIONS
  _______________________

  LISTED BELOW ARE SOME COMMON ERROR MESSAGES/CONDITIONS YOU MAY RECEIVE.

  o   WCL0221: LAN Distance could not initialize the modem.  Select Help for
      additional information.

      This message usually indicates there may be problems with the:

          -   Modem string
          -   Modem cable
          -   Modem hardware configuration
          -   Non-FIFO COM port.

      For details on how to configure a modem not found in the Available modem
      types list box, please refer to the CFMODEM command in the LAN Distance
      Advanced Guide.

  o   WCL0336: The called workstation did not respond to requests to exchange
      information with the LAN Distance product.

      This problem indicates there may be problems with the:

          -   Modem string. The problem could be that you have a modem string
              that is adequate to establish a LAN Distance connection, but not
              designed to allow a LAN Distance session to pass data between two
              LAN Distance workstations.  If you are using a modem listed in
              the Available modem types list box, you should verify that you
              have correctly identified the modem.  If you have constructed new
              modem string, or have modified one of the provided modem strings,
              your string may be incorrect. As with error message WCL0221
              select: you should review the information on the CFMODEM Utility
              to help you build and test your modem string.


          -   Modem cable may be defective

          -   Modem hardware configuration may be incorrect or defective

          -   A "Connect to a non LAN Distance destination" mismatch.  The LAN
              Distance workstation receiving this message has not selected
              "Connect to a non-LAN Distance destination" and the dialed-to
              workstation has selected this parameter.  One of the two work-
              stations must be re-configured to create a match for this param-
              eter.  If "Connect to a non LAN Distance destination" is
              selected, security will be disabled.

  o   SYMPTOM: CANNOT CONNECT AND UNEXPECTED DISCONNECTION.


                                           Trouble Shooting Common Problems  65









          -   WCL0317 - Unable to establish data carrier with the remote modem.
          -   WCL0310 - The call to xxxx has disconnected.
          -   WCL0356 - The LAN type configured for your workstation conflicts
              with the LAN type configured for the called workstation.
          -   WCL0358 - The LAN segment ring numbers are the same.

      These error messages occur when the LAN Distance product is configured
      incorrectly and connections cannot be established or established con-
      nections are lost.  Select help for each of these messages for detailed
      solutions.  Solutions include:

          -   Verify the workstation has a FIFO COM port.
          -   Verify the "Connect to a non-LAN Distance destination" check
              boxes on both workstations are in the same state.
          -   Verify the LAN Distance Connection Server is in Auto Answer mode.
          -   Verify the LAN types (Token-Ring or Ethernet) match between the
              two workstations.
          -   Verify the LAN segment ring numbers are identical for the two
              workstations.
          -   Verify the WAN segment ring numbers are not identical for the two
              workstations.
          -   Verify the filtering on the LAN Distance Connection Server is
              configured so the LAN Distance WAN connection is not flooded from
              unnecessary LAN traffic.

  o   NET3406, SYS1719, NET3060 OR ACS2390:


      IBM LAN Requester fails on the LAN Distance Remote with the following
      messages:


      -   Net3406 An error occurred while opening network device driver
          NET1=NETBUIU$.

      -   SYS1719 The file "C:\IBMLAN\NETWKSTA.200" specified in the IFS
          command on line (94) of the CONFIG.SYS file does not contain a valid
          device driver or file system driver.

      IBM LAN Requester starts with the following error message:

      -   The REQUESTER service could not be started.

      -   NET3060 The service did not respond to a control signal and was
          stopped with the DosKillProc function.

      IBM Communications Manager returns the following message on startup:

      -   ACS2390 ALERT: An unexpected OS/2 function call or 802.2 LAN Trans-
          port error has closed the logical LAN adapter.

      The above list of messages indicates the protocols and adapters may not
      be configured correctly for the LAN Distance product to support the
      LAN-based application.  See Using LAN Adapter & Protocol Support.


  66  LAN Distance Quick Start Guide









  o   SYMPTOM: YOU START IBM LAN REQUESTER AT THE LAN DISTANCE REMOTE BUT
      CANNOT LOG ON TO THE IBM LAN SERVER.  YOU RECEIVE ONE OF THE FOLLOWING
      MESSAGES:


      -   Domain Controller not Available.

      -   The Server is not responding.

      These error messages may indicate problems with the following:

          -   LAN protocols and adapters may not be configured correctly.  See
              Using LAN Adapter & Protocol Support for assistance with LAPS.

          -   Modems and ports may not be configured correctly.

          -   Bridge may not be configured correctly.

          -   LAN timers values may be too small.

  o   WCL0310: If the LAN Distance logical adapter network address of your LAN
      Distance Remote is not unique for every LAN-attached workstation and
      every LAN Distance Remote dialing into the LAN, you may have a network
      address duplication.  The more workstations attached to the LAN, the
      higher the possibility of a duplicate network address.

      If a duplicate network address condition develops, the LAN Distance
      Remote may receive the error message:

         WCL0310: Call to xxxxxxx has disconnected.

         Where xxxxxxx is the Phone Book entry name.

      The error will be logged to the Audit log at the LAN Distance Connection
      Server.  The LAN Distance Remote workstation user should contact the LAN
      Distance administrator to verify the cause.  To recover from this error
      condition, select a Network address that is unique.  Contact your LAN
      administrator for a unique number.

      The Help push button on the Network tab will give you further information
      on LAN Distance  logical adapter network addresses.


  o   MSG0002:If you try to log on to a LAN Distance workstation and receive a
      message such as:

         Msg0002: Your account is not active.

         Contact your Security administrator.

      You may have forgotten your User ID, your passphrase, or the other secu-
      rity restrictions applying to your access of the LAN Distance Connection
      Server.  You will need to contact your LAN Distance Security adminis-
      trator for assistance.


                                           Trouble Shooting Common Problems  67









  o   COMM695 and COMM593: IBM Communications Manager indicates that the 3270
      Controller is down or cannot be located.  Generally, this error message
      occurs if the bridge for the LAN Distance Connection Server has not been
      configured correctly.  The LAN Distance bridge must be configured If the
      3270 Controller is not located on the same LAN Segment Ring number as the
      LAN Distance Connection Server.  See Configure the Bridge Tab.


  USING OS2PING
  _____________

  To help you configure the LAN Distance bridge and understand more about your
  LAN topology, OS2PING is included in the \WAL subdirectory.  OS2PING is a
  useful tool for discovering the LAN Segment ring numbers, hop count, and
  ability to communicate with known workstations at specified LAN network
  address locations.  The 802.2 protocol is required to run OS2PING.  This pro-
  tocol is shipped with the LAN Distance product and can be configured using
  LAPS.


  You will find that this utility very helpful in the initial installation and
  configuration of the LAN Distance product or when bringing up new applica-
  tions.


  o   Once you install your LAN Distance Connection Server, it is helpful to
      use OS2PING to see if it is possible to "PING" the network resources that
      you will be trying to access from your remote workstations.  This will
      tell you if your Connection Server has access to LAN Resources.  If this
      is not possible then there is a problem with your Connection Server
      installation.


  o   Once you install your OS/2 Remote workstations and dial them into the
      Connection Server, it is helpful to use OS2PING to see if you can "PING"
      the network resources from the Remote.  If this is not possible then
      there is likely a problem with your ability to "Bridge" the remote onto
      the LAN.  It may be a "hop count" problem or some other problem with the
      Connection Server Bridge Configuration.  Remember, OS2PING requires the
      802.2 API on the remote.


  o   If you are able to ping the network resource but your application is not
      working, then the problem is likely with your application.

  To use OS2PING with the LAN Distance product, at the OS/2 command prompt
  enter:

       OS2PING -a=xxxxxxxxxxxx -r

       Where:
          xxxxxxxxxxxx is the destination (network) address of the Controller.
          -r is the command to display formatted routing information.




  68  LAN Distance Quick Start Guide









  This is an example of a ping from the LAN Distance Remote workstation to a
  Controller. The resulting routing information from OS2PING is:

          (002)  --- 1 ----> (cea) --- 7 --> (b22) --- 5 --> (c3a)
         (WAN1)  LD/Bridge  (LAN2)  Bridge  (LAN3)  Bridge  (LAN4)

  o   Each value in parentheses (cea) is a LAN Segment number for a specific
      LAN. Each number after the LAN Segment is the bridge number.

  o   In this example, the "ping" traveled from the LAN Distance Remote to the
      LAN Distance Connection Server (WAN1) across three bridges to LAN4.

  o   The LAN Distance connection is WAN1.  The default WAN Segment for the LAN
      Distance product is 002. The first bridge is the LAN Distance Connection
      Server with a default bridge number of 1.  The Controller is located on
      LAN4 and is always the last LAN Segment in the returned information.

  For more information on the OS/2 Ping command, refer to Appendix C of the LAN
  Distance Advanced Guide.  The OS2PING documentation is also available online
  by executing VIEW OS2PING at an OS/2 command prompt.



  USING LAN ADAPTER & PROTOCOL SUPPORT
  ____________________________________

  LAN Adapter And Protocol Support (LAPS) is an application in the LAN Distance
  product that allows you to configure the adapters and protocols necessary to
  run applications.  During the installation of the LAN Distance product and
  most other applications, the adapters and protocols are automatically config-
  ured for you.

  The LAN Distance product will automatically configure a LAN DISTANCE LOGICAL
  ADAPTER with the NetBIOS protocol.  If your workstation is LAN-attached, con-
  figured, and running applications with protocols such as 802.2 (for IBM Com-
  munications Manager), the LAN Distance installation will establish a shuttle
  function allowing these protocols to function on the LAN Distance Remote.

  Unless you are trouble-shooting a problem, adding special protocols, or
  adding non-IBM adapters, you will not need to configure protocols using LAPS.

  The LAN Distance product uses a "logical adapter".  Just as the IBM LAN
  Requester application requires a physical LAN adapter and the NetBIOS pro-
  tocol, the LAN Distance product also requires a logical adapter (called the
  LAN Distance logical adapter) and the NetBIOS protocol.  The LAN Distance
  product allows the remote workstation to be a virtual member of the LAN.  The
  logical adapter is a software version of the physical LAN adapter found in
  the IBM LAN Requester and other LAN products.

  The information below describes how to use LAPS and what information should
  appear in both the LAN Distance Remote and LAN Distance Connection Server
  LAPS windows and the resulting PROTOCOL.INI files.

  Steps for installing LAN applications, accessing, or re-installing LAPS.



                                           Trouble Shooting Common Problems  69









  When properly configured, the LAPS "Current Configuration" list box for the
  LAN Distance Remote should have the following information:

    :font facename=Courier size=10X10.
    +--------------------------------------+
    | LAN DISTANCE LOGICAL ADAPTER...      |
    |   0 - IBM OS/2 NETBIOS       <-------|--- REQUIRED BY LAN DISTANCE
    |   0 - IBM IEEE 802.2         <-------|--- OPTIONAL, NOTE #1
    |   0 - IBM NETWARE REQUESTER  <-------|--- OPTIONAL, NOTE #2
    |   0 - IBM TCP/IP             <-------|--- OPTIONAL, NOTE #3
    +--------------------------------------+

  :font facename=default size=0X0.

  NOTE #1: 802.2 protocol is optional and is needed only if you are running an
  802.2 application, such as IBM Communications Manager or OS2PING, on the
  remote workstation.


  NOTE #2: Netware Requester protocol is optional and is needed only if you are
  running the Novell Requester over the LAN Distance Remote to a LAN Distance
  Connection Server to a Novell Server.

  NOTE #3: TCP/IP protocol is optional and is needed only if you are running
  applications requiring TCP/IP.

  LAPS configuration for the LAN DISTANCE CONNECTION SERVER requires only the
  LAN adapter and NetBIOS for the Token-Ring LAN and the LAN Distance logical
  adapter and NetBIOS for the LAN Distance product.  All application protocols
  are configured at the LAN Distance Remote.

  When properly configured, the LAPS "Current Configuration" list box for the
  LAN Distance Connection Server, should have the following information:

    :font facename=Courier size=10X10.
    +-----------------------------------+
    | IBM TOKEN-RING NETWORK ADAPTERS   |
    |    0 - IBM NETBIOS      <---------|--- REQUIRED BY THE TOKEN-RING ADAPTER
    |    0 - XXXXXXXXXXXXXX   <---------|--- NOTE #1
    | LAN DISTANCE LOGICAL ADAPTER      |
    |    1 - IBM OS/2 NETBIOS <---------|--- REQUIRED BY LAN DISTANCE
    +-----------------------------------+

  :font facename=default size=0X0.

  NOTE #1:  If the server workstation is dedicated to the LAN Distance Con-
  nection Server product, then no other protocols are listed under the LAN Dis-
  tance logical adapter or the Token-Ring adapter.  If this workstation
  functions as a LAN Distance Connection Server and also runs as a LAN-attached
  workstation, either as a Server or End User workstation , there may be a need
  to include other protocols with the Token-Ring Network Adapter.





  70  LAN Distance Quick Start Guide









  For examples of a Connection Server and Remote PROTOCOL.INI files consult the
  product documentation.



  MPTS
  ____

  To use MPTS with the LAN Distance product, you must have MPTS Version 2.60.2
  or later.

  NOTE:  LAN Server 4.0 is shipped with MPTS Version 2.60.2.

  NetBIOS 3.0 interface (provided with MPTS) supports only four adapters.  If
  four NetBIOS logical adapters are configured before LAN Distance installation
  or configuration, LAN Distance will assign VLAN MAC (PDFH.NIF) the fifth
  NetBIOS logical adapter number.  Since this fifth adapter is not supported by
  MPTS, you must delete one of the previous NetBIOS logical adapter configura-
  tions, then configure VLAN MAC through MPTS configuration.

  The VLAN MAC must also be configured through MPTS configuration if NetBIOS is
  not configured before LAN Distance installation or during LAN Distance con-
  figuration.


  MODEM PIF FILE CORRECTIONS
  __________________________

  The following problems with Modem PIF files have been resolved with the LAN
  Systems Evaluation CD-ROM, but exist with the production level of the LAN
  Distance 1.11 code.


  MICROCOM MODEM: The following problems occasionally occur when using the
  Microcom modem with the LAN Distance product:


  o   After having successfully connected with the Microcom modem, further
      attempts to reconnect with the modem or to connect with another modem
      have failed.

  o   The Microcom modem will not initially connect with certain modems.

  The following are symptoms of the above problems:

  o   The modem appears "deaf" to dialing strings.
  o   The modem fails to go off hook.
  o   The modem DTR signal fails to turn on.

  You can receive a corrected Microcom PIF file to alleviate this problem by
  calling IBM Service and requesting the fix for APAR IC08292.


  SUPRAFAX MODEM: There is also a corrected Modem PIF File for the Suprafax
  Modem.  This can be obtained by calling IBM Service and requesting the fix
  for APAR IC08043.


                                           Trouble Shooting Common Problems  71











  Both of these APAR's have been integrated into the LAN Systems Evaluation
  CD-ROM and do not need to be ordered.





  NETBIOS OVER TCP/IP
  ___________________

  The LAN Distance product does not support NetBIOS over TCP/IP (device driver
  TCPBEUI.OS2).


  DESELECTING MANUAL BRIDGE FILTER
  ________________________________

  For LAN Distance connection servers, on page 2 of the Bridge tab in the Set-
  tings notebook, you cannot deselect a filter criteria to make it inactive
  with the mouse.  To deselect a filter criteria, select it with the mouse,
  then press the space bar.


  PCMCIA ADAPTER CHANGES
  ______________________

  If you made modifications to use PCMCIA adapters, then you should upgrade to
  LAN Distance version 1.11 instead of removing the existing LAN Distance code
  and installing version 1.11.

  If you must remove the LAN Distance code and then install version 1.11, you
  must UNDO your modifications to the appropriate .NIF files for the PCMCIA
  adapters before installing the LAN Distance product.  After installing the
  LAN Distance product, you must REDO the same modifications to these files.
  See the LAN Distance Remote Guide, Chapter 13, sections "Shuttling with
  PCMCIA Adapters" and "Fixing DEVICE= Statement Parameter Loss during
  Shuttle".


  COMMUNICATIONS MANAGER/2 V1.11
  ______________________________

  If you are installing or upgrading to Communications Manager/2 V1.11 please
  note the following:

  o   To use the "SNA Phone Connections" feature of CM/2 V1.11 on the same
      machine with "LAN Distance using PSTN", you must get a CM/2 fix through
      IBM Service and Support by referencing APAR JR08194.

  o   To use "LAN Distance using ISDN", follow these steps:

      1.  Backup NETWORK.INI by renaming \CMLIB\NETWORK.INI to
          \CMLIB\NETWORK.BAK.  This prevents you from using the "SNA Phone Con-
          nections" feature of CM/2 V1.11.

      2.  Reinstall the ISDN Coprocessor Support Program Version V1.2 software.


  72  LAN Distance Quick Start Guide









      3.  Reconfigure LAN Distance using ISDN.























































                                           Trouble Shooting Common Problems  73






DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3076: :font facename=Courier size=
10X10.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3087: :font facename=default size=
0X0.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3108: :font facename=Courier size=
10X10.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3119: :font facename=default size=
0X0.
DSMBEG323I STARTING PASS 2 OF 2.
DSMW32708E TEXT EXCEEDS RIGHT PAGE BOUNDARY ON PAGE 51.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3076: :font facename=Courier size=
10X10.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3087: :font facename=default size=
0X0.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3108: :font facename=Courier size=
10X10.
DSMSSU588W NO APF FOUND FOR 'FONT' TAG.
DSMMOM395I 'LDQUICK' LINE 3119: :font facename=default size=
0X0.





































