═══ 1. About This Book ═══ This book supports IBM Enhanced Remote Access Connection Server for OS/2 Warp Server. The book describes how to set up and use the connection server in your network environment. Throughout the book, IBM Enhanced Remote Access Connection Server for OS/2 Warp Server is described using different terms, such as LAN Distance Connection Server, connection server, LAN Distance, and so on. This book provides installation, setup, and management information for the connection server. The online book LAN Distance Remote Guide provides information about LAN Distance remote workstations. The LAN Distance Advanced Guide is an advanced configuration guide and supplements the information provided in the Remote Guide. For more details about remote workstations, use the LAN Distance Remote Guide instead. Note: Some product features are not supported, or not fully supported, for the MS Windows version. For more information, see information about the LAN Distance Remote Product for MS Windows in the LAN Distance Remote Guide online book. ═══ 1.1. Who Should Use This Book ═══ This book is intended for LAN Distance administrators who will install, set up and manage LAN Distance Connection Server and LAN Distance Remote workstations to provide remote access to LAN resources. This book assumes the LAN Distance administrator is familiar with networking concepts and terms, communications hardware, and with the network operating system and LAN applications used in their network. ═══ 1.2. How This Book Is Organized ═══ This book includes the following chapters and appendixes:  Introducing the Product highlights the features of the LAN Distance product and describes the remote access environments it enables.  Setting Up the Product in Your LAN Environment describes the workstations and resources in your LAN Distance wide area network and identifies some planning considerations. Key differences between the MS Windows and OS/2 versions of the LAN Distance Remote product are also listed.  Quick Start lists required tasks for setting up your LAN Distance Connection Server. It also describes required tasks for configuring a LAN Distance Remote using the Settings notebook instead of Basic Settings.  Installing the Product explains how to install a LAN Distance Connection Server and choose an installation method for your LAN Distance workstations.  Understanding the User Interface introduces you to the LAN Distance Workstations window and its objects and actions.  Setting Up Ports and Modems explains how to configure the LAN Distance product to use your modems and WAN adapters.  Setting Up the LAN Distance Bridge covers setting up the LAN Distance bridge component for Token-Ring and Ethernet LANs and explains the product's automatic and customized filtering options for improving performance of the LAN Distance connection.  Setting Up Point-to-Point Protocol (PPP) describes the tasks you must complete to set up point-to-point protocol (PPP) for LAN Distance.  Setting Up LAN Distance Security describes the security features of the LAN Distance product and explains how to customize a security policy for your LAN Distance system.  Setting Up to Run LAN Applications Remotely provides setup tips for running your LAN applications remotely and describes protocol support provided for OS/2.  Setting Up Some Popular LAN Applications describes setup steps and configuration changes recommended for running some LAN applications remotely.  Setting Up the Phone Book describes how to set up phone book entries for the workstations that you want to call.  Dialing and Running LAN Applications describes how to establish a LAN Distance connection and start your LAN applications. Special setup for LAN-to-LAN connections and dialing out using the Dial Request applet are also covered.  Answering Incoming Calls explains how to setup answer modes so your LAN Distance workstation can answer calls.  Troubleshooting Tips provides steps for correcting some common problems.  Using System Management Tools describes the tools you can use to manage your LAN Distance wide area network.  Detecting and Resolving Errors directs you to resources and procedures for resolving problems.  Supported Hardware lists the modems and adapters that you can use with the LAN Distance product. Special setup for Ethernet adapters is also provided.  Command Line Interface Reference is a guide to the LAN Distance command line interface. In addition to syntax information for LAN Distance commands, this appendix includes example batch procedures.  Using OS2PING for Troubleshooting and LAN Distance Bridge Configuration explains how to use OS2PING and LANPING to verify a communication path and select LAN Distance bridge configuration values.  Modifying Modem Strings in a LAN Distance PIF File explains how to create a new PIF file (modem type) by editing an existing PIF file, other modifications to PIF files are also described. Additionally, the Port/Modem utility, another option for creating modem types, is also documented.  Creating a Co-Processor Parameter File explains how to create a co-processor parameter file if you are setting up an ARTIC card that uses non-micro channel (AT bus) hardware.  Example System Configuration Files contains samples of LAN Distance configuration files and system configuration files.  Security Database Tools provides a discussion of security database tools.  Developing Security User Exits describes the development of user exits. ═══ 1.2.1. Highlighting Conventions ═══ Throughout this book, the following highlighting conventions are used: ┌────────────────────────────────────────────────────────────────────────┐ │ Table 1. Highlighting Conventions │ ├───────────────────────┬────────────────────────────────────────────────┤ │ HIGHLIGHTING │ USED TO IDENTIFY │ ├───────────────────────┼────────────────────────────────────────────────┤ │ BOLD │ Controls (when used in procedures), for │ │ │ example: │ │ │ │ │ │ o Menu bar choices │ │ │ o Radio buttons │ │ │ o Push buttons │ │ │ o List boxes │ │ │ o Check boxes │ │ │ o Entry fields │ │ │ o Read-only entry fields │ │ │ o Tab names │ ├───────────────────────┼────────────────────────────────────────────────┤ │ CAPITAL LETTERS │ o Commands │ │ │ o Directory names │ │ │ o File names │ ├───────────────────────┼────────────────────────────────────────────────┤ │ Italics │ o Book and diskette names │ │ │ o Variable names and values │ │ │ o Technical terms when introduced │ │ │ o Words of emphasis │ ├───────────────────────┼────────────────────────────────────────────────┤ │ "Monospace" │ o Coding examples │ │ │ o Special characters │ │ │ o Text reader must type │ │ │ o Text displayed on the computer screen │ └───────────────────────┴────────────────────────────────────────────────┘ ═══ 1.3. LAN Distance Library ═══ Documentation for the LAN Distance product includes books, online information, and product information supplied in README files. ═══ 1.3.1. Books ═══ If you are setting up LAN Distance Remotes, you will need the LAN Distance Remote Guide. ═══ 1.3.2. Online Information ═══ This book is designed to be used with the online information provided in the Helps, Task Index and the Where & How. Helps Online help is an important component of the LAN Distance product documentation. General help for windows and specific help for fields is available when you select the Help push button from any window. Task Index The online task index is a comprehensive index of LAN Distance tasks. To access the task index:  From the LAN Distance Workstations window, select Help from the menu bar and Help index from the pull-down menu.  From any window, select the Help push button, then select the Index push button. Where & How Online Information This online document identifies where you can complete configuration information tasks in the LAN Distance Settings notebook and describes how to modify your existing configuration through the Settings notebook. README Files The following README files are shipped with the LAN Distance product: README file This file contains updated technical information that you may need to configure and use the LAN Distance Connection Server product. To access the README file, before the product is installed, insert Diskette 1. From an OS/2 command prompt, type A:TYPE README | MORE, then press Enter. To print the README file type A:PRINT README, then press Enter. DSI_API.TXT The dialer services interface (DSI) is an application program interface (API) for the dialer services component of the LAN Distance product. README.X25 The LAN Distance product supports access to X.25 networks through asynchronous modems with X.25 Packet Assembler Disassembler (PAD) capabilities. The READMEX25 file contains information you need to configure and use X.25 PAD capabilities with the LAN Distance product. Note: After installation, these files are installed in the WAL subdirectory. ═══ 1.4. Related Publications ═══ The following books may provide information helpful to setting up this product or the applications you plan to use with this product:  Automated Installation for CID Enabled Extended Services, LAN Server V3.O and Network Transportation Services/2  FFST/2 Administration Guide  IBM LAN Distance Configuration and Customization Guide  IBM LAN Technical Reference  IBM Token-Ring Network Architecture Reference  Multi-Protocol Transport Services Configuration Guide  LAN Support Program User's Guide  OS/2 LAN Server Network Administrator Reference, Volumes 2 and 3  Realtime Interface Co-Processor OS/2 Support Version 1.03 User's Guide  Supplement to LAN Technical Reference  Supplement to LAN Technical Reference (T-R 16/4 Adapter II)  TCP/IP OS/2 User's Guide  TCP/IP Installation and Maintenance Guide The following Internic Standards and RFCs relate to point-to-point protocol (PPP):  STD0051 The Point-to-Point Protocol (PPP)-obsoletes RFC1549, RFC1661, and RFC1662  RFC1332 PPP IP Control Protocol (IPCP)  RFC1334 PPP Authentication Protocols (PAP and CHAP)  RFC1541 Dynamic Host Configuration Protocol (DHCP)  RFC1570 PPP Link Control Protocol (LCP) extensions ═══ 2. Introducing the Product ═══ This chapter introduces LAN Distance and explains the types of remote LAN access environments that are supported. Remote-to-LAN is probably the most common type of remote access. Stand-alone LAN Distance remotes and PPP clients establish a connection by dialing a LAN Distance Connection Server on a remote LAN. The LAN Distance connection allows a LAN Distance remote or PPP client to access LAN application servers, host gateways, printers and LAN workstations, just as though the LAN Distance Remote or PPP client was a local node on the LAN. The connection environments the LAN Distance product supports are explained in LAN Distance Environments. The following picture illustrates how you can set up LAN Distance Connection Servers and LAN Distance Remotes in your environment to provide remote LAN access. Remote LAN Access Environments for the LAN Distance Product ═══ 2.1. Supported Communications Connections ═══ The LAN Distance product supports asynchronous, synchronous, ISDN and X.25 communications connections for remote LAN access environments.  For asynchronous communications using your workstation's COM port, support is provided for many manufacturer's external modems, as well as internal modems. Additionally, several asynchronous adapters, including IBM's Dual Asynchronous and Wide Area Connector, are supported. See Supported Hardware for a list of the asynchronous WAN hardware the LAN Distance product supports.  Synchronous modems require the use of an adapter that supports synchronous communications. See Supported Hardware for a list of the synchronous WAN hardware (modems and adapters) supported. Several of the asynchronous modems listed in Modems also support synchronous communications as a configuration option. Setup considerations for synchronous modems are described in Using Synchronous Modems and Leased Lines.  ISDN basic rate and ISDN primary rate switched communications are supported using the ISDN adapters in Wide Area Network Adapters.  The LAN Distance product supports access to X.25 networks through asynchronous modems with X.25 Packet Assembler (PAD) capabilities. To access the READMEX25 file, see Online Information. ═══ 2.2. LAN Distance Environments ═══ The LAN Distance product supports three types of remote LAN access environments:  Remote-to-Remote  Remote-to-LAN  LAN-to-LAN ═══ 2.2.1. Remote-to-Remote ═══ Two LAN Distance Remotes can establish a LAN Distance connection as shown in Remote-to-Remote Environment to form a virtual LAN. The remote-to-remote environment is a simple, low-cost solution for stand-alone workstations that require direct access to resources on other stand-alone workstations. For example, the remote-to-remote environment can be used in a local office environment in lieu of expensive LAN cabling or by traveling employees who need access to their office workstations. Remote-to-Remote Environment ═══ 2.2.1.1. Hardware Considerations ═══ Both LAN Distance Remotes must use compatible communications hardware to establish a LAN Distance connection. For example, to establish an asynchronous connection, the LAN Distance Remotes must have a COM port and modem, or an adapter and modem combination that support and are set up for asynchronous communications. You can set up more than two LAN Distance Remotes to share resources in the remote-to-remote environment. Each OS/2 LAN Distance Remote supports two concurrent connections. MS Windows LAN Distance Remotes support one asynchronous connection. ═══ 2.2.1.2. Software Considerations ═══ With the appropriate software, stand-alone LAN Distance Remotes can use a LAN Distance connection to conference or to share data and local resources, such as printers. For example, using a peer networking product, such as IBM OS/2 LAN Server 3.0 peer services or LANtastic (for MS Windows workstations), LAN Distance Remotes can share access to files and local resources. Using a desktop conferencing product, such as OS/2 Person to Person/2, LAN Distance Remotes can conference electronically. Client/server applications can also be used in the remote-to-remote environment. For example, a LAN Server application such as Time and Place/2 or Lotus Notes can be used in the remote-to-remote environment by setting up one LAN Distance Remote as the server, and one as the client. ═══ 2.2.1.3. Setting Up the LAN Distance Connection Server as a Stand-Alone Workstation ═══ As shown in Stand-Alone Server in Remote-to-Remote Environment, the LAN Distance Connection Server product can be installed on a stand-alone workstation to support more than two concurrent LAN Distance connections. This set up is useful if a number of users on stand-alone workstations need to access resources on a single server. For example, install LAN Server on a stand-alone LAN Distance Remote that you want to use as the server. (No LAN hardware is required for the LAN Server). A LAN Distance Remote running OS/2 LAN Requester or a MS Windows LAN Distance Remote running DOS LAN Requester can dial the stand-alone LAN Server and access resources as though they were on a local LAN. Stand-Alone Server in Remote-to-Remote Environment ═══ 2.2.2. Remote-to-LAN ═══ A LAN Distance remote workstation or PPP client can establish a LAN Distance connection to a LAN Distance Connection Server on the LAN as shown in Remote-to-LAN Environment. The LAN Distance remote workstation or PPP client functions as a remote node on the LAN. The LAN Distance connection provides access to all LAN workstations and resources, allowing the LAN Distance remote workstation or PPP client to access resources as though it were physically connected to the LAN. The remote-to-LAN environment is a flexible solution for users requiring access to resources from remote locations, such as home or while traveling. Users can dial the LAN Distance Connection Server on their office LAN and run the same applications remotely that they use in the office. Remote-to-LAN Environment ═══ 2.2.2.1. Hardware Considerations ═══ The LAN Distance Connection Server must have a supported Token-Ring or Ethernet LAN adapter to provide remote access to the LAN. See Local Area Network Adapters for a list of supported LAN adapters. The LAN Distance Connection Server requires communications hardware for the type of communications connections (asynchronous, synchronous and ISDN) and the number of concurrent LAN Distance connections that you want to support. The LAN Distance Remote does not require LAN hardware to connect to a LAN Distance Connection Server and access LAN resources. LAN Distance Remotes do require communications hardware, such as a modem and COM port or an adapter to establish a connection with the LAN Distance Connection Server. ═══ 2.2.2.2. Software Considerations ═══ The LAN Distance Connection Server only requires OS/2 version 2.0 (or later), it does not require any communications software (e.g. Communications Manager or LAN Requester) to support a LAN Distance connection. Over the LAN Distance connection, LAN Distance Remotes can run LAN applications and networking software that use industry-standard NDIS-compliant protocols, such as NetBIOS, IEEE 802.2, IPX, and TCP/IP. PPP clients can run LAN applications and networking software that use TCP/IP. See Examples of Supported LAN Protocols and Applications. ═══ 2.2.3. LAN-to-LAN Environments ═══ You can establish a LAN Distance connection between two LAN Distance Connection Servers to form a casual bridge between two LANs as shown in LAN-to-LAN Environments. LAN workstations on LAN A can use the LAN Distance connection to access LAN resources on LAN B as though they were physically attached to LAN A. Similarly, LAN workstations on LAN B can access resources on LAN A. LAN-to-LAN Environments Evaluate the following planning and setup considerations for the LAN-to-LAN environment: ═══ 2.2.3.1. LAN Size ═══ The LAN-to-LAN environment is designed to allow a limited number of workstations on a LAN to communicate with a limited number of workstations on another LAN. Connecting LANs with a large number (20 +) of workstations is recommended only if the number of workstations that access the LAN Distance connection can be limited to a small number (1 - 20). See Filtering Strategies for the LAN-to-LAN Environment. ═══ 2.2.3.2. LAN Topology ═══ Consider the topology of the LANs you are connecting using the LAN Distance product:  Do not use the LAN Distance product to establish a LAN-to-LAN connection between two LANs if any type of connection or a bridge already exists between the two LANs.  If the two LANs are connected to other LANs, workstations on the other LANs could also access the LAN Distance connection. Customized filtering criteria can be used to limit access to only the LAN workstations that require access to the LAN Distance connection. See Customizing Filtering Criteria. ═══ 2.2.3.3. Maximum Number of LAN Workstations ═══ If several LAN workstations in your environment require simultaneous access to the LAN-to-LAN connection, the performance of the LAN-to-LAN connection will vary based on:  The type of communications connection, the connection speed, and the connection throughput  The workload of the LAN workstations using the connection For example, if you use a modem that supports a connection speed of 38400 bps, up to five LAN workstations with average usage requirements may expect average response times. But if you use a 64K ISDN D channel, up to 10 LAN workstations with average usage requirements may expect average response times. ═══ 2.2.3.4. Improving Performance Factors ═══ Performance factors--connection throughput, connection speed, data volume and response times-- for the LAN Distance connection can be improved using the customized filtering capabilities of the LAN Distance product. See Types of Filtering Supported for the LAN Distance Bridge. Automatic filtering cannot be used for LAN-to-LAN connections. ═══ 2.2.3.5. Setting Up LAN Workstations and LAN Distance Connection Servers ═══ If an OS/2 LAN workstation needs to establish a connection to a LAN Distance Connection Server or LAN Distance Remote on a separate LAN, set up the LAN workstation to use the LDMKCALL program, set up the dialing LAN Distance Connection Server to use the LDACCEPT program, and set up the answering LAN Distance Connection Server or LAN Distance Remote to answer calls. See Using the Dial Request Applet for LAN Dial Out. ═══ 2.2.3.6. Coordinating Security ═══ If security is enabled on the dialing and answering LAN Distance Connection Servers, coordinate the security setup (user IDs and passphrases) for the workstations participating in the LAN-to-LAN environment. See Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection. ═══ 2.3. Point-to-Point Protocol (PPP) ═══ Point-to-point protocol (PPP) is a protocol that is used throughout the networking industry as a standardized method for interconnecting a variety of hosts, bridges, and routers from one or more vendors. The key features of the LAN Distance PPP support are:  LAN Distance connection server dynamically accepts calls from PPP clients whose LAN applications use the TCP/IP protocol. This is in addition to accepting calls from LAN Distance remote clients.  LAN Distance connection server supports multiple sessions of up to 128 LAN Distance remote clients and PPP clients, in any combination. The maximum number of concurrent PPP connections is 64. The maximum number of concurrent LAN Distance remote clients is 128.  PPP supports password authentication protocol (PAP) and challenge-handshake authentication protocol (CHAP) using an integrated database.  PPP IP address administration can be done in a combination of three ways: - Client-specified - Listed on the LAN Distance connection server - Allocated by Dynamic Host Configuration Protocol (DHCP) services  Optionally allows the DHCP server to use the LAN Distance user ID to update the DNS server. ═══ 3. Setting Up the Product in Your LAN Environment ═══ This chapter describes set up considerations for the workstations and resources in your LAN Distance environment, and identifies some planning considerations for adding the LAN Distance product to your LAN environment. ═══ 3.1. What Is a LAN Distance Wide Area Network? ═══ Your LAN Distance wide area network (WAN) is comprised of LAN Distance workstations, PPP clients, LAN workstations, and LAN resources. The workstations and resources on the LAN can participate in the LAN Distance wide area network if they are attached to a LAN where the LAN Distance Connection Server makes them available to LAN Distance Remotes. For example, when the LAN Distance Remote shown in the shaded region of LAN Distance Wide Area Network dials into the LAN Distance Connection Server, this LAN Distance Remote and the LAN workstations and resources on the LAN Distance Connection Server's LAN become part of the LAN Distance wide-area network. As other LAN Distance Remotes shown in LAN Distance Wide Area Network dial into the LAN, they are also added to the LAN Distance wide area network. The different types of workstations and resources in a LAN Distance wide area network are described in the following topics. LAN Distance Wide Area Network ═══ 3.1.1. LAN Distance Connection Server ═══ The LAN Distance Connection Server dials and answers calls to establish connections, routes and filters data to bridge the LAN Distance remote workstations and PPP clients to the LAN, prevents unauthorized access to provide security for LAN resources, and performs other administrative functions for the LAN Distance wide area network.  The LAN Distance Connection Server package is installed on workstations running OS/2 version 2.0 (or later).  The LAN Distance Connection Server allows multiple remote workstations to dial in concurrently and access LAN resources. The number of remote workstations supported is determined by your workstation's processing power, its communications adapter(s), and the version of the LAN Distance Connection Server product.  Two versions of the IBM LAN Distance Connection Server product are available: the LAN Distance Connection Server 8-Port product supports up to eight concurrent connections, and the LAN Distance Connection Server product supports more than eight. ═══ 3.1.2. The LAN Distance Remote for OS/2 Product ═══  The OS/2 version of the LAN Distance Remote product is installed on stand-alone workstations running OS/2 version 2.0 (or later). Up to two concurrent LAN Distance connections are supported.  LAN applications and networking software that use industry-standard NDIS-compliant protocols, such as NetBIOS, IEEE 802.2, IPX, and TCP/IP are supported.  LAN Distance Remotes do not require LAN hardware to use a LAN Distance connection to access LAN resources. WAN communications hardware (such as a modem and COM port or an adapter) is required for the type of communications connection that you want to support.  If you want to use the same workstation on and off the LAN, the LAN Distance Remote must have a LAN adapter installed. Users can use the shuttle feature to switch between LAN-attached and stand-alone configurations. ═══ 3.1.3. The LAN Distance Remote for MS Windows Product ═══ The features described in The LAN Distance Remote for OS/2 Product are also supported for the MS Windows version of the LAN Distance Remote product. Some key differences between the MS Windows and OS/2 versions of the product are highlighted in the following list. Additional features that are not supported or not fully supported for LAN Distance Remote for MS Windows product are described in "The LAN Distance Remote Product for MS Windows" in LAN Distance Remote Guide.  The version of the LAN Distance Remote product for MS Windows is installed on stand-alone workstations running Microsoft Windows version 3.1 with DOS version 5.0 or later. The MS Windows LAN Distance Remote supports one LAN Distance connection.  Only one asynchronous COM port connection (COM1 - COM4) is supported for LAN Distance Remote MS Windows workstations. Multiport configuration and ARTIC multiport adapters are supported only for the LAN Distance Remote for OS/2 product.  The LAN Distance Remote for MS Windows product does not supply or install LAN networking software. (NetBIOS is installed and configured.) If you need to set up applications that require additional protocols, such as 802.2, you must separately install and configure these protocols. See Protocol Support Provided for OS/2 and MS Windows LAN Distance Remotes. ═══ 3.1.4. Point-to-Point Protocol (PPP) Clients ═══ The following information pertains to point-to-point protocol (PPP) clients:  PPP clients can run LAN applications and networking software that use TCP/IP.  PPP clients do not require LAN hardware to use a LAN Distance connection in order to access LAN resources. WAN communications hardware, such as a modem and COM port or an adapter, is required for the type of communications connection you want to support.  LAN Distance connection server supports the following PPP clients: - Microsoft Windows 95 Version 4.0 client - IBM OS/2 Internet Dialer - IBM 8235 DIALs Connect for Windows Version 4.1 - IBM 8235 DIALs for OS/2 Version 4.5.2 or IBM 8235 DIALs for OS/2 Version 4.03 client + patch You can get the patch from the world wide web (WWW) at the following URL. The patch is called "DIALs for OS/2 Version 4.03 patch 3" in the 8235 Remote Access Server (Version 4.0) section. http://www.networking.ibm.com/nes/nes8235.htm - Microsoft Windows NT Version 4.0 client  The following restrictions apply to PPP support: - Callback is not supported for PPP clients - LAN Distance connection server does not support the ability to use LAN Distance logical adapter network addresses with a PPP user account. For more information, see Security for PPP Clients. - You cannot change passphrases from the client. For more information, see Security for PPP Clients. - PPP clients cannot TCP/IP ping LAN Distance clients. LAN Distance clients cannot TCP/IP ping PPP clients. ═══ 3.1.5. LAN Workstations ═══ When a LAN Distance Remote establishes a connection to a LAN Distance Connection Server, all of the workstations and resources on the LAN Distance Connection Server's LAN become part of the LAN Distance wide area network. If you do not want to open up the workstations and resources on your LAN to remote access, you can set up filtering criteria at the LAN Distance Connection Server to control access to resources on the LAN. If your LAN Distance Remotes will access applications on LAN workstations, adjust the NetBIOS timers on the LAN workstation and, if necessary, modify its applications to support remote access. ═══ 3.1.6. LAN Resources ═══ Resources on a LAN, such as printers, file servers, and host controllers, can also be accessed by LAN Distance Remotes through the LAN Distance Connection Server on the LAN. There are no set up requirements for these LAN resources. ═══ 3.2. Planning Considerations for Setting Up the LAN Distance Products ═══ Evaluate these planning considerations when you introduce the LAN Distance product to your LAN environment:  Selecting the LAN workstation that you want to use as the LAN Distance Connection Server  Setting up filtering at the LAN Distance Connection Server  Setting up the protocols on the LAN Distance Remote that you need to run your LAN applications  Setting up your LAN applications for remote access  Setting up security at the LAN Distance Connection Server to control unauthorized remote access  Setting up standard naming conventions to avoid duplicate LAN Distance logical adapter network addresses  Setting up standard naming conventions to avoid duplicate NetBIOS names  Testing the LAN Distance product to verify that you can establish a LAN Distance WAN connection For information about security for point-to-point protocol (PPP) and creating userids, see Security for PPP Clients. For information about PPP and subnetting, see PPP Client IP Address Considerations. ═══ 3.2.1. Selecting the LAN Distance Connection Server Workstation ═══ To select the LAN workstation that you want to use as the LAN Distance Connection Server, evaluate the following set up considerations:  Use a supported LAN adapter  Select an OS/2 FIFO workstation  Evaluate memory and fixed disk requirements  Select a dedicated or nondedicated workstation ═══ 3.2.1.1. Use a Supported LAN Adapter ═══ The LAN adapter installed on the LAN Distance Connection Server must be supported by the LAN Distance product. See Local Area Network Adapters for a list of supported adapters. ═══ 3.2.1.2. Select an OS/2 FIFO Workstation ═══ The LAN Distance product supports workstations with FIFO and non-FIFO serial communications (COM) ports. Non-FIFO workstations generally do not support connection speeds greater than 9600 bps, regardless of the connection speed supported by the attached modem. For this reason, FIFO machines, which typically support higher connection speeds, are recommended for the LAN Distance Connection Server. Note: If you plan to install the LAN Distance Connection Server product on a non-FIFO OS/2 workstation, you can try to optimize the connection speed for your non-FIFO serial port. See Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports. ═══ 3.2.1.3. Evaluate Memory and Fixed Disk Requirements ═══ The LAN Distance Connection Server product requires 5.0 Mb of fixed-disk storage space. First Failure Support Technology/2 (700 Kb) and required LAN transports (2.2 Mb), if these products are not already installed. The amount of memory recommended for running the LAN Distance Connection Server product, OS/2, and one LAN application is 12.0 Mb. The requirements for your LAN Distance Connection Server may vary depending on your LAN applications, data and response time requirements, and your workstation's processor speed. ═══ 3.2.1.4. Select a Dedicated or Nondedicated Workstation ═══ The LAN Distance Connection Server can be set up on a dedicated workstation or on a nondedicated workstation that is running other LAN applications in addition to the LAN Distance product. To determine the best set up for your LAN Distance Connection Server, review the following considerations. ═══ 3.2.2. Filtering LAN Data Frames at the Connection Server Workstation ═══ Setting up the LAN Distance product on a dedicated workstation may make it easier to define LAN Distance filtering requirements for the following reasons:  Filtering criteria defined at the LAN Distance bridge apply not only to data frames sent to the LAN Distance Connection Server and the LAN Distance Remote workstation, but also to any LAN applications residing at the LAN Distance Connection Server.  If you set up the LAN Distance product on a workstation running other LAN applications, you must define filtering criteria so these LAN applications can communicate with the necessary applications and resources on the LAN. ═══ 3.2.2.1. Transparent Bridging on Ethernet LANs ═══ Setting up the LAN Distance Connection Server product on a dedicated workstation may improve the performance of the LAN Distance bridge for the following reasons.  On Ethernet LANs, the LAN Distance product uses transparent bridging to route data frames. Transparent bridging is CPU intensive because each data frame is processed at the LAN Distance bridge.  If the LAN Distance Connection Server is installed on a nondedicated workstation where the LAN Distance bridge has to compete with other CPU intensive activities, LAN data frames may not be processed as efficiently. ═══ 3.2.2.2. Setting Up Filtering at the LAN Distance Connection Server ═══ If filtering is not enabled at the LAN Distance bridge, the traffic generated by a busy LAN with large volumes of LAN traffic can easily flood the LAN Distance WAN connection, causing performance and connection problems. Filtering is required in most environments to maximize performance and connection reliability of the LAN Distance WAN connection. The LAN Distance Connection Server product supports automatic and customized filtering at the LAN Distance bridge. Automatic filtering is set up and ready to go when you install the LAN Distance Connection Server product. It can be used for most applications and LAN Distance environments. For more information about LAN Distance filtering capabilities, see Types of Filtering Supported for the LAN Distance Bridge. ═══ 3.2.3. Supported LAN Protocols and Applications ═══ The LAN Distance product supports multiple protocols and applications through the Network Driver Interface Specification (NDIS). Over a LAN Distance connection, LAN Distance Remotes can run LAN applications and networking software that use industry-standard NDIS-compliant protocols, such as NetBIOS, IEEE 802.2, IPX, and TCP/IP. Over a LAN Distance connection, PPP clients can run LAN applications and networking software that use TCP/IP. Many LAN applications, including client-server applications, use LAN protocols supported by the LAN Distance product. Some compatible LAN applications and communications products include Lotus Notes, LANtastic, OS/2 Communications Manager/2, AS/400, PC Support, and Personal Communications/3270 and 5250. Some popular network operating systems using LAN protocols supported by the LAN Distance product include OS/2 LAN Server, NetWare, Microsoft LAN Manager and Banyan VINES. For OS/2 and MS Windows LAN Distance Remotes, the LAN Distance product installs and configures the NetBIOS protocol. If your OS/2 or MS Windows applications require NDIS-compliant protocols other than NetBIOS, see Protocol Support Provided for OS/2 and MS Windows LAN Distance Remotes. ═══ 3.2.4. Setting Up LAN Applications for Remote Access ═══ Because data transfer rates over WAN connections are considerably slower than rates on a LAN, it may not be efficient to load applications or large data files over a LAN Distance WAN connection. For example, some applications may load as much as 5 Mb of code during start up. On a high-speed LAN, this can take from 5 to 10 seconds, but over a WAN connection, using an asynchronous modem running at 14400 bps, loading 5 Mb of code can take from 5 to 10 minutes. To maximize the performance of the LAN Distance WAN connection, follow these guidelines when setting up your LAN applications to support remote access:  Load applications from the LAN Distance Remote's hard disk and not from a LAN-attached application server across the LAN Distance WAN connection.  When running an application from a drive on an application server, other drives are normally allocated for shared data, templates and personal data. When starting and stopping an application loaded from the LAN Distance Remote's hard disk, these drives should be allocated and deallocated dynamically (NET USE).  Some applications including word processors, spreadsheets, and presentation applications can generate large data files. Files of 1 Mb, which are not uncommon can take 10 or more minutes to load over the WAN connection. Users should keep these application files as small as possible. If large data files are used, they should be copied once from the application server on the LAN, then modified locally on the LAN Distance Remote.  Many applications periodically save changes. Set up the applications on the LAN Distance Remote so that these frequent saves are executed locally.  Some applications, such as wordprocessors and spreadsheets, use macros to perform repetitive or complex tasks. Any macro files that are required by the application should be loaded locally from the LAN Distance Remote' hard disk and not remotely over the LAN Distance WAN connection.  Printing can also cause a number of problems because postscript files and print files with graphics can be quite large. A simple 1-page printout may require a large print file to be sent to the printer. If you transmit print files over the LAN Distance WAN connection, it may take considerable time to print a document.  It is not uncommon for applications to create temporary files and printer spool files when formatting a printout. Make certain that any temporary print files are created locally. ═══ 3.2.5. Setting Up Security at the LAN Distance Connection Server ═══ Adding remote access capabilities to your LAN exposes the LAN and its resources to unauthorized remote access. Setting up LAN Distance security at the LAN Distance Connection Server is recommended to help prevent unauthorized users from accessing your LAN. LAN Distance security is an optional feature for LAN Distance Connection Servers and operates independently from other security systems on your LAN. To set up LAN Distance security, see Setting Up LAN Distance Security. ═══ 3.2.6. Avoiding Duplicate Addresses ═══ LAN Distance logical adapter network addresses identify LAN Distance Remote and LAN Distance Connection Servers in your LAN Distance wide area network, and like LAN adapter addresses, LAN Distance logical adapter network addresses must be unique throughout your network. A LAN Distance logical adapter network address is either specified by you or automatically generated and assigned to the LAN Distance Logical Adapter. To avoid duplicate addresses, use a standardized naming convention to assign LAN Distance logical adapter network address to LAN Distance Remotes and LAN Distance Connection Servers. When assigning LAN Distance logical adapter network addresses, consider the following:  If a LAN Distance logical adapter network address is automatically generated during installation, it is not guaranteed to be unique within your network.  If you use a LAN Distance Remote as a stand-alone and a LAN workstation, use the LAN address as the LAN Distance logical adapter network address. Because both configurations cannot be active at the same time, this address is unique when the workstation is set up as a LAN workstation and when it is a stand-alone LAN Distance Remote. ═══ 3.2.7. Avoiding Duplicate Names for NetBIOS Applications ═══ When you add a LAN Distance connection to your LAN environment, it is possible to start a NetBIOS application on a LAN Distance Remote even if its NetBIOS name is not unique. This can occur if a NetBIOS application is started on the LAN Distance Remote before a connection to the LAN Distance Connection Server is established. LAN Distance Remote NetBIOS names are verified by the LAN Distance Connection Server when a connection is established. If duplicate NetBIOS names are found, the LAN Distance Connection Server will disconnect the connection. To avoid problems with duplicate NetBIOS addresses, use a standardized naming convention to centrally assign and record these names throughout your network. ═══ 3.2.7.1. Multiple NetBIOS Adapters ═══ NetBIOS 3.0 Interface supports only four adapters. If four NetBIOS logical adapters are configured before LAN Distance installation or configuration, LAN Distance assigns the fifth NetBIOS adapter number to the LAN Distance logical adapter. Since this fifth adapter is not supported by NetBIOS 3.0, using LAPS or MPTS, you must delete one of the previous NetBIOS logical adapter configurations and then configure NetBIOS to be used by the LAN Distance logical adapter. ═══ 3.2.8. Testing LAN Applications and LAN Distance Connections ═══ Test your LAN applications and LAN Distance WAN connections as you add LAN Distance Connection Server and LAN Distance Remote workstations to your LAN environment: 1. Make sure your LAN applications are operating correctly on the LAN before you attempt to set up and run the same applications over the LAN Distance connection. 2. Install and configure the LAN Distance Remote product on a stand-alone workstation. Set up a phone book entry on the LAN Distance Remote to call the LAN Distance Connection Server. 3. Install and configure the LAN Distance Connection Server product on a LAN workstation. Start an answer mode to answer calls from the LAN Distance Remote. 4. From the LAN Distance Remote, dial the LAN Distance Connection Server to establish a LAN Distance connection. 5. To test a LAN application, start the LAN application on the LAN Distance Remote, then complete any performance tuning needed to run the application over the LAN Distance connection. ═══ 4. Quick Start ═══ This chapter summarizes required tasks for setting up a LAN Distance Connection Server. Begin LAN Distance Connection Server set up by reviewing the required tasks listed in Setup Tasks for a LAN Distance Connection Server .  Required set up tasks for OS/2 LAN Distance Remotes are listed in "Quick Start for OS/2" in the LAN Distance Remote Guide.  Required set up tasks for MS Windows LAN Distance Remotes are listed in "Quick Start for MS Windows Workstations" in the LAN Distance Remote Guide. ═══ 4.1. Setup Tasks for a LAN Distance Connection Server ═══ Setup Checklist for a LAN Distance Connection Server is a guide for installing and setting up a LAN Distance Connection Server. Tasks are divided into required and optional categories and cross-referenced to topics in this book. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 2. Setup Checklist for a LAN Distance Connection Server │ ├───────────────────────────────────┬───────────────────────────────────┬──────┤ │ TASK │ GO TO... │ DONE │ │ │ │ │ │ │ │ (X) │ ├───────────────────────────────────┴───────────────────────────────────┴──────┤ │ REQUIRED SETUP TASKS │ ├───────────────────────────────────┬───────────────────────────────────┬──────┤ │ 1) Select a LAN workstation to │ Selecting the LAN Distance Con- │ │ │ use as the LAN Distance Con- │ nection Server Workstation │ │ │ nection Server. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 2) Install prerequisite hardware │ Hardware and Software Require- │ │ │ and software. │ ments for the LAN Distance Con- │ │ │ │ nection Server │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 3) Install the LAN Distance Con- │ Steps for Installing the LAN Dis- │ │ │ nection Server product. │ tance Connection Server Using │ │ │ │ Diskettes │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 4) Stop all applications, shut │ │ │ │ down and restart your work- │ │ │ │ station. Double-click on the LAN │ │ │ │ Distance icon to start the LAN │ │ │ │ Distance product. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 5) Open the Settings notebook to │ Opening an Action Window │ │ │ complete configuration tasks. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 6) For each COM port, ARTIC │ Setting Up a LAN Distance Port │ │ │ port, and Other type of adapter │ │ │ │ port that you want to use with │ │ │ │ the LAN Distance product, set up │ │ │ │ a LAN Distance port. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 7) For each internal or external │ Configuring a Modem Type and │ │ │ modem, set up a LAN Distance │ Assigning Ports to a Modem Type │ │ │ modem type. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 8) Assign each LAN Distance port │ Configuring a Modem Type and │ │ │ that you set up to a modem type. │ Assigning Ports to a Modem Type │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 9) If your LAN Distance Con- │ Understanding Ethernet Bridges │ │ │ nection Server is on an Ethernet │ │ │ │ LAN, select Ethernet as your LAN │ │ │ │ type. (Token-Ring is the default │ │ │ │ setting.) │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 10) Record (or change) the LAN │ Changing a LAN Distance Logical │ │ │ Distance logical adapter network │ Adapter Network Address │ │ │ address assigned during installa- │ │ │ │ tion. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 11) If the LAN Distance Con- │ Defining Configuration Values for │ │ │ nection Server is installed on a │ the LAN Distance Bridge │ │ │ Token-Ring LAN that is connected │ │ │ │ to other LAN segments, define a │ │ │ │ bridge number, LAN segment ring │ │ │ │ number, and WAN segment ring │ │ │ │ number for the LAN Distance │ │ │ │ bridge. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 12) Verify that automatic fil- │ Using the Automatic Filtering │ │ │ tering is enabled for the LAN │ Feature │ │ │ Distance bridge. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 13) Set up answer criteria to │ Auto Answer and Answer Modes │ │ │ answer calls at the LAN Distance │ │ │ │ Connection Server. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 14) Stop all applications, shut │ │ │ │ down and restart your workstation │ │ │ │ to make your configuration │ │ │ │ changes effective. │ │ │ ├───────────────────────────────────┴───────────────────────────────────┴──────┤ │ OPTIONAL TASKS │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 2. Setup Checklist for a LAN Distance Connection Server │ ├───────────────────────────────────┬───────────────────────────────────┬──────┤ │ TASK │ GO TO... │ DONE │ │ │ │ │ │ │ │ (X) │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ Specify a name for your work- │ Changing Your Workstation Name │ │ │ station to uniquely identify your │ │ │ │ workstation icon. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ Customize your answer setup to │ Customizing Your Answer Modes │ │ │ automatically start an answer │ │ │ │ mode or a LAN application. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ To control remote access to LAN │ Enabling LAN Distance Security │ │ │ resources, enable security at the │ and Setting Up Required Fea- │ │ │ LAN Distance Connection Server │ tures for a User Account │ │ │ and set up user accounts to │ │ │ │ require user log on. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ To customize security for all │ Defining Policy Options for Your │ │ │ user accounts, define LAN Dis- │ User Accounts │ │ │ tance security policy. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ Customize filtering criteria for │ Types of Filtering Supported for │ │ │ the LAN Distance bridge by │ the LAN Distance Bridge │ │ │ defining filtering criteria. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ To dial out to a LAN Distance │ Creating Phone Book Entries │ │ │ workstation, set up a phone book │ │ │ │ entry for each LAN Distance work- │ │ │ │ station that you want to dial. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ To accept dial requests from LAN │ Setting Up LAN Distance Con- │ │ │ workstations, set up LDACCEPTC on │ nection Servers to Establish a │ │ │ the LAN Distance Connection │ LAN-to-LAN Connection and and │ │ │ Server, and define filtering cri- │ Filtering Strategies for the │ │ │ teria for the LAN Distance │ LAN-to-LAN Environment │ │ │ bridge. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ To configure point-to-point │ Setting Up PPP │ │ │ protocol (PPP). │ │ │ └───────────────────────────────────┴───────────────────────────────────┴──────┘ ═══ 4.2. Setting Up a LAN Distance Remote Using the Settings Notebook ═══ The Settings notebook can be used to set up any type of communications connection supported by the LAN Distance product.  LAN Distance Remotes setting up synchronous modems and adapters, ARTIC adapters for multiport connections, and leased lines must use the Settings notebook.  For LAN Distance Remotes using asynchronous and ISDN connections, the Basic Settings path is the easiest way to complete configuration. See Basic Settings set up tasks listed in "Quick Start for OS/2" in the LAN Distance Remote Guide. Setup Checklist for LAN Distance Remote Installation and Settings Notebook Configuration summarizes the general tasks required to configure a LAN Distance Remote using the Setting notebook. Tasks are divided into required and optional categories and cross-referenced to topics in this book and the LAN Distance Remote Guide. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 3. Setup Checklist for LAN Distance Remote Installation and Settings │ │ Notebook Configuration │ ├───────────────────────────────────┬───────────────────────────────────┬──────┤ │ TASK │ GO TO... │ DONE │ │ │ │ │ │ │ │ (X) │ ├───────────────────────────────────┴───────────────────────────────────┴──────┤ │ REQUIRED TASKS │ ├───────────────────────────────────┬───────────────────────────────────┬──────┤ │ 1) Install prerequisite hardware │ "Hardware and Software Require- │ │ │ and software. │ ments", in the LAN Distance │ │ │ │ Remote Guide │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 2) Review any set up consider- │ Setting Up to Run LAN Applica- │ │ │ ations for installing the LAN │ tions Remotely and Setting Up │ │ │ applications that you want to run │ Some Popular LAN Applications │ │ │ remotely. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 3) Install the LAN applications │ Setting Up to Run LAN Applica- │ │ │ that you want to run remotely and │ tions Remotely and and Setting │ │ │ complete any application set up │ Up Some Popular LAN Applications │ │ │ tasks that are required prior to │ │ │ │ installing the LAN Distance │ │ │ │ product. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 4) Install the LAN Distance │ "Installing the LAN Distance │ │ │ Remote product. │ Product Using Diskettes", in the │ │ │ │ LAN Distance Remote Guide │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 5) Stop all applications, shut- │ "Installing the LAN Distance │ │ │ down and restart your work- │ Product Using Diskettes", in the │ │ │ station. Double-click on the LAN │ LAN Distance Remote Guide │ │ │ Distance icon to start the LAN │ │ │ │ Distance product. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 6) Open the Settings notebook to │ Opening an Action Window │ │ │ complete configuration tasks. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 7) For each COM port, ARTIC │ Setting Up a LAN Distance Port │ │ │ port, and Other type of adapter │ │ │ │ port that you want to use with │ │ │ │ the LAN Distance product, set up │ │ │ │ a LAN Distance port. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 8) For each internal or external │ Configuring a Modem Type and │ │ │ modem, set up a LAN Distance │ Assigning Ports to a Modem Type │ │ │ modem type. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 9) Assign each LAN Distance port │ Configuring a Modem Type and │ │ │ that you set up to a modem type. │ Assigning Ports to a Modem Type │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 10) If the LAN Distance Con- │ Understanding Ethernet Bridges │ │ │ nection Server that you will │ │ │ │ connect to is on an Ethernet LAN, │ │ │ │ select Ethernet as your LAN type. │ │ │ │ (Token-Ring is the default │ │ │ │ setting.) │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 11) Record (or change) the LAN │ Changing a LAN Distance Logical │ │ │ Distance logical adapter network │ Adapter Network Address │ │ │ address assigned during installa- │ │ │ │ tion. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 12) Set up phone book entries to │ Creating Phone Book Entries │ │ │ dial out from the LAN Distance │ │ │ │ Remote │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 13) Stop all applications, shut │ │ │ │ down, and restart your work- │ │ │ │ station to make configuration │ │ │ │ changes effective. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ 14) Complete any application set │ Setting Up Some Popular LAN │ │ │ up tasks required after │ Applications │ │ │ installing the LAN Distance │ │ │ │ product to run your applications │ │ │ │ remotely. │ │ │ ├───────────────────────────────────┴───────────────────────────────────┴──────┤ │ OPTIONAL TASKS │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 3. Setup Checklist for LAN Distance Remote Installation and Settings │ │ Notebook Configuration │ ├───────────────────────────────────┬───────────────────────────────────┬──────┤ │ TASK │ GO TO... │ DONE │ │ │ │ │ │ │ │ (X) │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ Specify a name for the LAN Dis- │ Changing Your Workstation Name │ │ │ tance Remote to uniquely identify │ │ │ │ the workstation icon. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ Use the shuttle feature to switch │ "Using the Shuttle Feature for │ │ │ the LAN Distance Remote's config- │ OS/2" and "Using the Shuttle │ │ │ uration from LAN-attached to │ Feature for MS Windows", in the │ │ │ remote and remote to │ LAN Distance Remote Guide │ │ │ LAN-attached. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ If the LAN Distance Remote will │ Customizing Your Answer Modes │ │ │ answer calls from LAN Distance │ │ │ │ Connection Servers or LAN Dis- │ │ │ │ tance Remotes, customize │ │ │ │ autoanswer criteria. │ │ │ ├───────────────────────────────────┼───────────────────────────────────┼──────┤ │ To control access to the │ Enabling LAN Distance Security │ │ │ resources on the LAN Distance │ and and Setting Up Required Fea- │ │ │ Remote, enable security and set │ tures for a User Account │ │ │ up user accounts. │ │ │ └───────────────────────────────────┴───────────────────────────────────┴──────┘ Note: If the shuttle function was enabled during installation, your workstation must be shuttled to a remote workstation to use the settings notebook for configuration. ═══ 5. Installing the Product ═══ This chapter describes the installation methods the LAN Distance product supports for LAN Distance Connection Servers and LAN Distance Remotes, including redirected drive installation.  For the LAN Distance Connection Server, it describes preinstallation tasks, lists diskette installation steps, and explains how to reinstall, upgrade, and remove the LAN Distance Connection Server product.  To install the LAN Distance Remote product using diskettes, see "Installing the LAN Distance Product Using Diskettes" in the LAN Distance Remote Guide. The LAN Distance Remote Guide also covers reinstall, remove, and upgrade topics for the LAN Distance Remote. ═══ 5.1. Hardware and Software Requirements for the LAN Distance Connection Server ═══ Before you install the LAN Distance Connection Server product, install prerequisite software and the WAN hardware you want to configure for the LAN Distance product.  IBM Warp Server Version 4.0 or later  Install the network operating system software and any LAN applications that you will run on the LAN Distance Connection Server.  The LAN Distance Connection Server product requires 5.0 Mb of fixed-disk storage space. Additional disk space is required to install FFST/2 (700 Kb) and required LAN transports (2.2 Mb), if these products are not already installed. The amount of memory recommended for running the LAN Distance Connection Server product, OS/2, and one LAN application is 12.0 Mb. The requirements for your LAN Distance Connection Server may vary depending on your LAN applications, data and response time requirements, and your workstation's processor speed.  Verify that the LAN adapter for the LAN Distance Connection Server is supported by the LAN Distance product. See Local Area Network Adapters. If you are using a supported Ethernet card, see the set up instructions in Installing LAN Adapter Drivers Through LAPS.  A modem and/or adapter for asynchronous, synchronous, or ISDN communications. See Supported Hardware for a list of supported modems and adapters. If you are using an adapter for asynchronous or ISDN communications, install and configure the adapter using the adapter software, according to the manufacturer's instructions.  Access to a switched or nonswitched (leased) telephone line to establish an asynchronous, synchronous, or ISDN connection. The following are additional planning considerations for setting up the LAN Distance Connection Server.  WAN adapters used by the LAN Distance Connection Server product cannot be used by other applications simultaneously.  If Communication Manager/2 is installed on your workstation and you plan to set up an ISDN connection, set up Communications Manager so it is not configured for ISDN. See Using the Communications Manager/2 3270 Emulation Feature.  If you are using IBM OS/2 Warp Server Version 4.0, verify that you are using Multi-Protocol Transport Services (MPTS) Version 5.11 or later. If you are using IBM OS/2 Warp Server Version 4 (SMP), verify that you are using MPTS Version 5.2 or later with SMP MPTS APAR IC15968.  If you are using a DHCP server to assign IP addresses to PPP clients and you would like the LAN Distance userid to be associated with the IP address, you must use a DHCP server version that contains the "DNS proxy A record update" feature. For IBM OS/2 Warp Server Version 4.0, APAR IC15366 is required. For IBM OS/2 Warp Version 4 SMP feature, APAR IC16980 is required.  If you plan to install the LAN Distance Connection Server product on a non-FIFO OS/2 workstation, you can try to optimize the connection speed for your non-FIFO serial port. See Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports. ═══ 5.2. Selecting an Install Method ═══ Use one of the following installation methods to install the LAN Distance product:  Install using the product diskettes.  Install from a redirected drive (attended installation).  Install from a redirected drive using a response file (unattended installation). Note: To install the LAN Distance Remote product on a workstation using a redirected installation method, the workstation must be physically connected to a LAN. ═══ 5.2.1. Installing with Product Diskettes ═══ Installing from diskette is a simple procedure. From the workstation you want to set up as a LAN Distance Connection Server or LAN Distance Remote, insert Diskette 1 and start the installation program. Windows prompting you to make selections and insert diskettes guide you through the installation program.  See Steps for Installing the LAN Distance Connection Server Using Diskettes.  Steps for installing the LAN Distance Remote product using the product diskettes are described in "Installing the LAN Distance Product Using Diskettes" in the LAN Distance Remote Guide. ═══ 5.2.2. Installing from a Redirected Drive Using Diskette Images ═══ Redirected installation requires installing the LAN Distance product(s) once on a code server. After the code server is set up, users can access diskette images on the code server from a workstation physically connected to the LAN. This type of redirected installation (attended) uses the same interface used when installing from diskette. While you avoid swapping diskettes, you still must supply answers to installation questions.  See Copying the Diskette Images to the Code Server.  See Steps to Install from a Redirected Drive Using Diskette Images. ═══ 5.2.3. Installing from a Redirected Drive Using a Response File ═══ You can use a response file to supply answers to installation questions. This type of redirected installation (unattended) requires installing the LAN Distance product(s) on a code server and preparing a response file for each unique LAN Distance workstation that you plan to install. After installation is started from the workstation, you are not required to respond to installation questions. The instructions for creating response files are described in Creating Response Files for LAN Distance Workstations.  See Copying the Diskette Images to the Code Server.  See Creating Response Files for LAN Distance Workstations. ═══ 5.3. Steps for Installing the LAN Distance Connection Server Using Diskettes ═══ To install the LAN Distance Connection Server product on a LAN workstation: 1. With Diskette 1 in the diskette drive, type A:INSTALL at an OS/2 command prompt, and press Enter to start the installation program. 2. When the IBM Logo window is displayed, select the OK push button to start installation. 3. From the Welcome window, you can select Quick Start for a summary of the information you need to install the LAN Distance product. Select the OK push button to display the Target Drive window. 4. From the Target Drive window, specify the drive where you want to install the LAN Distance Connection Server product. LAN Distance files are stored in the WAL directory on this drive. Note: If LAN networking software is not already installed on your workstation and you select a drive that is not the boot drive, a message window gives you the option of installing LAN networking software on the boot drive or the drive selected for LAN Distance installation. 5. In the succeeding windows, answer questions, and insert diskettes to complete LAN Distance Connection Server installation. Select the Help push button from any window if you need additional information to make selections or enter values. 6. The Installation Complete window is displayed when the installation has successfully completed. Select the OK push button to exit the install program. 7. Remove any diskettes from the diskette drive, stop all currently active applications, shutdown and restart your workstation. The LAN Distance icon is displayed on the OS/2 desktop. 8. After you install the LAN Distance Remote product, read through the README file. This file contains important information that you may need to configure and use the LAN Distance Connection Server product. To access the README file, insert Diskette 1. From an OS/2 command prompt, type A:TYPE README | MORE, then press Enter. To print the README file type A:PRINT README, then press Enter. Note: To use the LAN Distance Connection Server product, you must configure the LAN Distance Connection Server using the Settings Notebook. Required steps are listed in Setup Checklist for a LAN Distance Connection Server. ═══ 5.4. Installing the LAN Distance Product from a Redirected Drive ═══ This section describes preparing a code server to support redirected installation, tells you how to access diskette images from a redirected drive, and provides steps for creating and using a response file to install the LAN Distance product. ═══ 5.4.1. Copying the Diskette Images to the Code Server ═══ Select a workstation to use as the code server that has sufficient available hard-disk space, and that can be accessed from workstations installing the LAN Distance product from a redirected drive. To copy the diskette images for the LAN Distance Remote or LAN Distance Connection Server product to the code server, run the LDIMAGE utility: 1. Diskette 1 for the LAN Distance products contains the diskette images and the LDIMAGE utility. Insert Diskette 1 for the product you want to copy to the code server, go to an OS/2 command prompt, and type: A:LDIMAGE /T:target The target parameter is the fully-qualified path on the code server where you want the diskette images copied. For example, to store the diskette images in the IMAGES directory on the D drive, type: A:LDIMAGE \IMAGES 2. The LDIMAGE utility creates a new directory for every diskette image copied. The naming convention for these directories is: LOnnnRx for the LAN Distance Remote for OS/2 LOnnnEx for the LAN Distance Connection Server 8-Port LOnnnAx for the LAN Distance Connection Server x is the number of the diskette image, and nnn is a version number for the product. Using the example in step Copying the Diskette Images to the Code Server, if you copied the LAN Distance Remote product to the code server, the diskette images would be saved to these directories: d:\IMAGES\LOnnnR1 \LOnnnR2 3. Repeat step Copying the Diskette Images to the Code Server for each LAN Distance product that you want to install from a redirected drive. ═══ 5.4.2. Steps to Install from a Redirected Drive Using Diskette Images ═══ After you copy diskette images to the code server, use the diskette images to install the LAN Distance product on your workstation. 1. To verify the names of the diskette image directories, type DIR from the target path you specified in step Copying the Diskette Images to the Code Server. For the example described in step Copying the Diskette Images to the Code Server, you would type the following to display the directories created: DIR d:\IMAGES\ The installation program for the LAN Distance products is located in the first directory (R1, E1, or A1) displayed. 2. To start the installation program, specify the fully-qualified path to the diskette images on the server (including the directory name for the first diskette image). For the previous example, you would type the following from an OS/2 command prompt: d:\IMAGES\LOnnnR1\INSTALL Note: When installing a LAN Distance Remote workstation from a redirected drive using a response file, after restarting, the workstation continues to be configured as a LAN workstation. To use the workstation as a stand-alone LAN Distance workstation, use the shuttle feature to switch from a LAN workstation to a remote workstation configuration. See "Using the Shuttle Feature for OS/2" in the LAN Distance Remote Guide. ═══ 5.5. Creating Response Files for LAN Distance Workstations ═══ A response file is a text file containing required and optional keywords and their values. Two sample response files (LD_REM.RSP and LD_SVR.RSP) are supplied with the LAN Distance Connection Server product, see Sample LAN Distance Response Files. These files are stored on Diskette 1 in the LAN Distance Connection Server package. During installation these files are placed in the WAL directory. You can copy sample response files and modify keyword=value pairs to create response files for LAN Distance workstations. A separate response file is required for each LAN Distance workstation type. Descriptions for keywords are in Keywords for Creating LAN Distance Response Files. For general information regarding the structure, processing and design of response files, see Automated Installation for CID Enabled Extended Services, LAN Server V3.0 and Network Transportation Services/2. Sample LAN Distance Response Files LD_REM.RSP Target = D:\ WorkstationType = Remote ConnectionType = Async Modem = IBM7855.PIF Port = COM2 Phone = (512)477-9254 Address = 400012345678 LD_SVR.RSP Target = D:\ WorkstationType = Server ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 4. Keywords for Creating LAN Distance Response Files │ ├─────────────────────────┬────────────────────────────────────────────────────┤ │ KEYWORD │ DESCRIPTION │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ Target │ This keyword is optional for LAN Distance Remotes │ │ │ and LAN Distance Connection Servers. It defines │ │ │ the fully-qualified path where the diskette images │ │ │ are copied on the code server. │ │ │ │ │ │ If the target keyword is not defined, the target │ │ │ defaults to the boot drive. │ │ │ │ │ │ If the target keyword is defined in the response │ │ │ file, it overrides the target path you specify at │ │ │ the command line. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ WorkstationType= │ This keyword is optional. It identifies the work- │ │ Remote, Server │ station type. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ ConnectionType = │ This keyword is required for ISDN. It identifies │ │ ASYNC, ISDN │ the type of WAN hardware (ASYNC modem or ISDN │ │ │ adapter) used to establish a LAN Distance con- │ │ │ nection. ASYNC is the default value. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ Modem = PIF file name │ This keyword is required for LAN Distance Remotes │ │ │ if the connection type is ASYNC. PIF file names │ │ │ for asynchronous modems are listed in Modems. No │ │ │ default is provided for this keyword. If an │ │ │ invalid file name is provided, modem configuration │ │ │ is incomplete. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ Port = COMx │ This keyword is required for LAN Distance Remotes │ │ │ if the connection type is ASYNC. COMx identifies │ │ │ the serial (COM) port that the asynchronous modem │ │ │ is connected to. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ Phone = 555-555-5555 │ This keyword is not required for LAN Distance │ │ │ Remotes. It identifies the phone number of the │ │ │ LAN Distance Remote or LAN Distance Connection │ │ │ Server you want to connect to. Use decimal digits │ │ │ (50-character maximum) to define the phone number; │ │ │ use dashes, spaces, and commas to separate digits. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ LANType = TokenRing, │ This keyword is required for Ethernet. It identi- │ │ Ethernet │ fies the type of LAN that the LAN Distance Con- │ │ │ nection Server is connected to. Token-Ring is the │ │ │ default value. │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ Address= 400012345678 │ This keyword is optional. This unique address is │ │ │ a hexadecimal number in either Token-Ring or │ │ │ Ethernet format. A default value is generated if │ │ │ a value is not specified. │ └─────────────────────────┴────────────────────────────────────────────────────┘ ═══ 5.5.1. Steps to Install from a Redirected Drive Using a Response File ═══ Review the command syntax for LAN Distance response files that follows before you begin installation steps: 1. To start installation using a response file, type the following from an OS/2 command line. The parameters shown in bold type are required. d:\path\INSTALL /R:rspfile /T:target /G:group /L1:log d: This parameter is required. It identifies the redirected drive on the code server where the LAN Distance diskette images are stored. path This parameter is required. It defines the fully-qualified path to the directory on the code server that contains the first diskette image (R1, E1 or A1). rspfile This parameter is required. It is the name of the response file. It must be preceded by a fully-qualified path that includes either a local or redirected drive specification. target This parameter is optional. If you do not specify a target path (drive and/or directory) at the command line, or define a target path in the response file, the LAN Distance product is installed on the current boot drive. group This parameter is optional. It is the path to your group response file. log This parameter is optional. It identifies the file name and fully-qualified path where your installation error messages are written. If you do not specify a file name, error messages are written to the WALINST.LOG file. 2. Response file installation takes several minutes. When installation is complete, a command prompt is returned. If a command prompt is returned quickly, check the error log. 3. After stopping all active applications, shut down and restart the workstation to activate these changes. Note: For LAN Distance Remotes, after you restart the workstation, the workstation is automatically set up to operate as a stand-alone LAN Distance Remote. To use the workstation on the LAN, use the Shuttle feature to switch to from the remote to the LAN-attached configuration. See "Using the Shuttle Feature for OS/2" in the LAN Distance Remote Guide. ═══ 5.6. Accessing Installation Error Log Files ═══ Installation information is saved in the following two files located in the \OS2\INSTALL directory: WALINST.LOG Contains LAN Distance installation messages LAPSHIST.LOG Contains LAPS installation messages ═══ 5.7. Modifications Made to Your Configuration Files During Installation ═══ When you install the LAN Distance product, LAN Distance files are created and some changes are made to your existing configuration files. ═══ 5.7.1. The LAN Distance Directory ═══ During installation, the LAN Distance WAL directory, is created. The LAN Distance files shown in LAN Distance User Configuration Files are stored in the WAL directory. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 5. LAN Distance User Configuration Files │ ├─────────────────────────┬────────────────────────────────────────────────────┤ │ FILE NAME │ FILE DESCRIPTION │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ WCLLOCAL.INI │ Local configuration information for the LAN Dis- │ │ │ tance workstation │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ WCBUSRF.ISF │ Security information from the user account data- │ │ │ base │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ WCLDIAL.CXD │ Telephone numbers and connection information for │ │ │ phone book entries │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ WCLNET.INI │ Modem configuration information │ ├─────────────────────────┼────────────────────────────────────────────────────┤ │ WCLIPADR.INI │ List of available IP addresses for point-to-point │ │ │ protocol (PPP). The user creates the file using │ │ │ an ASCII editor after installation is complete. │ └─────────────────────────┴────────────────────────────────────────────────────┘ ═══ 5.7.2. System Configuration Files ═══ During installation, changes are also made to the CONFIG.SYS and PROTOCOL.INI configuration files for your workstation. Backups of these system configuration files are saved before the files are changed. Configuration Files Changed During Installation describes the changes to these files. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 6. Configuration Files Changed During Installation │ ├──────────────┬──────────────┬────────────────────────────────────────────────┤ │ FILE │ BACKUP │ CHANGES │ ├──────────────┼──────────────┼────────────────────────────────────────────────┤ │ CONFIG.SYS │ d:\CONFIG.WAL│ o The WAL directory is added to your path │ │ │ │ specifications for: │ │ │ │ - LIBPATH │ │ │ │ - DPATH │ │ │ │ - PATH │ │ │ │ o The LAN Distance helps are added to the │ │ │ │ HELP specification. │ │ │ │ o The specifications for the LAN Distance │ │ │ │ device drivers are added. │ │ │ │ o The device drivers for LAPS and NetBIOS │ │ │ │ are added. │ │ │ │ o If FFST/2 is installed during LAN Distance │ │ │ │ installation, appropriate statements for │ │ │ │ it are added. │ │ │ │ o Statements for the locked file device │ │ │ │ driver are added temporarily to the top of │ │ │ │ your CONFIG.SYS file. The statements are │ │ │ │ removed the next time you start your work- │ │ │ │ station. │ ├──────────────┼──────────────┼────────────────────────────────────────────────┤ │ IBMCOM\ │ d:\WAL\ │ o If NetBIOS is installed during LAN Dis- │ │ PROTOCOL.INI │ PROTOCOL.WAL │ tance installation, a section for │ │ │ │ NETBEUI_NIF is added. │ │ │ │ o Your NetBIOS timers are adjusted. See │ │ │ │ Adjusting NetBIOS Timers for for the new │ │ │ │ timer values. │ │ │ │ o The number of NetBIOS NCBs, names, and │ │ │ │ sessions are increased. │ │ │ │ o A section is added for VLAN_kernel. │ │ │ │ o A section for PDFH_NIF is added. │ └──────────────┴──────────────┴────────────────────────────────────────────────┘ ═══ 5.8. Interrupting the LAN Distance Installation Program ═══ Interrupting the LAN Distance installation program is not recommended. If you must interrupt installation, wait until the Target Drive window is displayed. At this point in the installation, no files have been installed or changed so you can install the LAN Distance product again without having to restore your workstation. If you interrupt installation after selecting the OK push button on the Target Drive window, some files are installed and some are changed. Depending on how much of the installation procedure has been performed, you may be able to use the LDREMOVE program to restore your workstation. See Removing the LAN Distance Connection Server Product. ═══ 5.9. Upgrading or Reinstalling the LAN Distance Connection Server Product ═══ You can upgrade from a previous release (or a beta release) of the LAN Distance Connection Server product or reinstall the LAN Distance Connection Server product on your workstation.  The steps for upgrading and reinstalling the LAN Distance Connection Server product are the same.  Reinstalling or upgrading the LAN Distance Connection Server product requires an additional 2.4 Mb of temporary disk space.  If you want to change your workstation type (LAN Distance Connection Server or LAN Distance Remote), use LDREMOVE to remove the LAN Distance Connection Server product, then install the LAN Distance Remote product.  When you reinstall or upgrade, your current LAN Distance files are reinstalled, with the exception of user configuration files. See the LAN Distance User Configuration Files table in The LAN Distance Directory. The configuration information in these files is not changed.  If you upgrade to version 1.1 of the LAN Distance Connection Server product, the automatic filtering feature is not enabled until you open and close the Settings notebook.  If you do not want to save the information in your user configuration files, use LDREMOVE to remove the LAN Distance product and then perform an initial install. To upgrade or reinstall the LAN Distance Connection Server product. 1. Insert Diskette 1 in the diskette drive, type A:INSTALL from an OS/2 command prompt, and press Enter. 2. When this message window shown in Message for Upgrade or Reinstallation is displayed, select the OK push button to continue. Message for Upgrade or Reinstallation 3. When the Reinstallation Complete window appears, select the OK push button. 4. To use the LAN Distance Connection Server product, shut down and restart your workstation. Your Settings notebook configuration information has not been changed and is active. Make any configuration changes through the Settings notebook. ═══ 5.10. Removing the LAN Distance Connection Server Product ═══ Run the LDREMOVE program to remove the LAN Distance Connection Server product if you want to:  Remove the LAN Distance Connection Server product.  Remove a partially removed or partially installed LAN Distance Connection Server product. If the LDREMOVE product was not used to remove the LAN Distance product, or you interrupted the LAN Distance Connection Server installation program, some LAN Distance files may not be removed, and your system configuration files may not be restored.  Prepare to change your LAN Distance Connection Server to a LAN Distance Remote. To use the LDREMOVE program to remove the LAN Distance Connection Server product: 1. From an OS/2 command line, type LDREMOVE. If the LDREMOVE program is not found, insert Diskette 1 in the diskette drive, type A:LDREMOVE, and press Enter. If the LDREMOVE program is found, the Remove LAN Distance window is displayed. Go to step Removing the LAN Distance Connection Server Product. If the LDREMOVE program is not found, the REXX program needed to run the LDREMOVE program may not be installed on your workstation, go to step Removing the LAN Distance Connection Server Product. 2. Try using the LDREM command, which does not require the REXX program. With Diskette 1 in the diskette drive, from an OS/2 command prompt, type a:LDREM a: (where a: is the diskette drive). 3. From the Remove LAN Distance window, specify whether you want to archive or delete LAN Distance configuration files. Remove LAN Distance Window  Select the Delete configuration files radio button to remove LAN Distance configuration files.  Select the Archive configuration files radio button to store a backup copy of your LAN Distance configuration files. The user configuration files listed in The LAN Distance Directory are stored in the WAL\BACKUP directory. User configuration files are not automatically restored when you install the LAN Distance Connection Server program again. To restore the information in these files, manually copy the files after you install the LAN Distance Connection Server product. The following files are also stored in the WAL\BACKUP directory when you archive configuration files. PROTOCOL.WAL Contains the PROTOCOL.INI file that was active before you typed LDREMOVE CONFIG.WAL Contains the CONFIG.SYS file that was active before you typed LDREMOVE 4. Select the Remove push button to start the removal process. 5. When the LAN Distance Remove Complete window appears stating that removal is complete, shut down and restart your workstation. ═══ 6. Understanding the User Interface ═══ The LAN Distance user interface is based on the object-action model of the Workplace Shell implemented in OS/2 version 2.0 and later, where an object is selected and then an action is selected to be applied to the object. Objects within the LAN Distance user interface are represented by icons and names. Your workstation is an example of a LAN Distance object. Objects are displayed as items in windows, list boxes, and containers. Actions are selected using pull-down menus, pop-up windows, and push buttons. ═══ 6.1. The LAN Distance Workstations Window ═══ The LAN Distance installation program adds the LAN Distance product icon, shown in The LAN Distance Product Icon, to your OS/2 Workplace Shell. You can move the icon anywhere in the Workplace Shell. The LAN Distance Product Icon To select the LAN Distance product icon and open your LAN Distance Workstations window: 1. Locate the LAN Distance product icon. 2. Double click on the icon with mouse button 1. The LAN Distance Workstations window displays as shown in The LAN Distance Workstations Window. It is where you work with the workstations in your LAN Distance wide area network. The LAN Distance Workstations Window To refresh or change the format of your LAN Distance Workstations window: 1. Open the LAN Distance Workstations window. and select the MyWorkstation icon. 2. Select View from the menu bar. 3. Select:  Icon, to view workstations in an icon format.  Details, to view workstations in a details format.  Refresh now, to update your LAN Distance Workstations window. In addition to refreshing the LAN Distance Remote workstations that you dialed, your workstation sends a broadcast message to locate LAN Distance Connection Servers. It might take several minutes for all of their responses to be received, depending on LAN traffic, bridge hops, and the number of LAN Distance Connection Servers that respond. The default name for your workstation icon is MyWorkstation. If you want to change your name to something more descriptive, see Changing Your Workstation Name. Use the menu bar at the top of the LAN Distance Workstations window to begin working with a LAN Distance workstation. LAN Distance Workstations Window, Menu Bar describes the actions that can be selected from the menu bar. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 7. LAN Distance Workstations Window, Menu Bar │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ ACTION │ CHOICE │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ SELECTED │ Choose service, management, and configuration action windows │ │ │ from the pull-down menu for the selected workstation. │ │ │ │ │ │ Open an action window for a workstation from the pull-down. │ │ │ For example, open MYWORKSTATION as Phone Book to dial to │ │ │ another workstation. See LAN Distance Connection Server │ │ │ Workstation Actions for information about all the action │ │ │ windows that can be selected from this pull-down menu. │ │ │ │ │ │ If you are not already logged on to a secure LAN Distance │ │ │ workstation, you are prompted to log on when you open an │ │ │ action window for the workstation. See User IDs and │ │ │ Passphrases for information about logging on. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ VIEW │ Select how LAN Distance objects are displayed in windows: │ │ │ as icons or in a details format. │ │ │ │ │ │ Also, refresh your LAN Distance Workstations window or │ │ │ change the order of the workstations displayed there. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ HELP │ Access online help for the LAN Distance Workstations window │ │ │ or view the task index. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 6.2. Opening an Action Window ═══ To open an action window for a LAN Distance workstation: 1. Open the LAN Distance Workstations window and select the MyWorkstation icon. 2. From the menu bar, select Selected and Open as. 3. Select an action window from the pull-down menu. The Open as pull-down menu is shown in Open as Pull-Down Menu. Open as Pull-Down Menu Perform many actions by selecting action windows from the Open as pull-down menu. On a secure LAN Distance workstation only those action windows that you are authorized to open are included in the pull-down menu. For example, if you are a LAN Distance administrator, the User Account Management notebook is not included in the pull-down menu because only security administrators can update security policies and the user account database. If LAN Distance security is not enabled on a workstation, the Open as pull-down menu includes only the action windows that a LAN Distance administrator is authorized to open. See Setting Up LAN Distance Security for information about LAN Distance security, user types, and logging on. ═══ 6.2.1. Notebooks ═══ Opening some action windows results in opening a notebook. Notebooks are divided into sections by tabs. To move through a notebook, select its tabs or turn its pages using the arrows at the bottom right corner of the notebook. Some notebooks have other notebooks nested within them. A tab section can contain more than one page. Make sure you proceed completely through all of the pages for a section when you access it. ═══ 6.2.2. Action Window ═══ LAN Distance Connection Server Workstation Actions describes all the action windows that can be included in the Open as pull-down. The user type required for each action window is also listed. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 8. LAN Distance Connection Server Workstation Actions │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ OPEN AS... │ ACTION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PHONE BOOK │ Establish connections to LANs and other workstations. │ │ │ │ │ │ The phone book is your dialing directory. It contains phone │ │ │ book entries for the information needed to establish con- │ │ │ nections. │ │ │ │ │ │ Double clicking with mouse button 1 on MYWORKSTATION also │ │ │ opens your Phone Book window. │ │ │ │ │ │ Required LAN Distance privilege: user │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ CALL AND PORT │ View and manage the calls established through the work- │ │ MANAGEMENT │ station. Also, stop and start your port managers. │ │ │ │ │ │ Required LAN Distance privilege: user │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ LOGGED-ON │ View the users that are logged on to the workstation. │ │ USERS │ │ │ │ This action window is available only on secure LAN Distance │ │ │ workstations. │ │ │ │ │ │ Required LAN Distance privilege: user │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PERSONAL │ Manage your personal account on the workstation. │ │ ACCOUNT │ │ │ INFORMATION │ View your passphrase status and, optionally, change your │ │ │ passphrase and your personal account description. │ │ │ │ │ │ This action window is available only on secure LAN Distance │ │ │ workstations. │ │ │ │ │ │ Required LAN Distance privilege: user │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ USER ACCOUNT │ Manage the workstation security policy and its user account │ │ MANAGEMENT │ database. │ │ │ │ │ │ Set up a user account database to designate which users are │ │ │ allowed to remotely access the workstation or LAN. │ │ │ │ │ │ This action window is available only on secure LAN Distance │ │ │ workstations. │ │ │ │ │ │ Required LAN Distance privilege: LAN Distance security │ │ │ administrator │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ SETTINGS │ Configure the LAN Distance product. │ │ │ │ │ │ The Settings notebook contains many pages. Five of its tabs │ │ │ lead to other notebooks: │ │ │ │ │ │ o Phone Book │ │ │ o Answer │ │ │ o Ports │ │ │ o Modems │ │ │ o Bridge │ │ │ │ │ │ Configuration changes you make in the Settings notebook or │ │ │ its imbedded notebooks are not saved until you close the │ │ │ Settings notebook. You can view and work with all of your │ │ │ changes while the notebook is open. When you close the Set- │ │ │ tings notebook, choose whether to accept or delete your │ │ │ changes. │ │ │ │ │ │ The Settings notebook can be opened by any user. On a │ │ │ secure LAN Distance workstation, the Settings notebook dis- │ │ │ plays only the tabs that are granted to the user who opens │ │ │ the notebook. For example, the notebook includes only the │ │ │ Information tab for a LAN Distance user. If a LAN Distance │ │ │ administrator opens the notebook, all of tabs, except Secu- │ │ │ rity are available. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 8. LAN Distance Connection Server Workstation Actions │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ OPEN AS... │ ACTION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ MESSAGE LOG │ View error and warning messages generated by the LAN Dis- │ │ │ tance product. │ │ │ │ │ │ Use the message log to investigate and correct LAN Distance │ │ │ configuration and connection problems. Contact your desig- │ │ │ nated support organization for additional help if you cannot │ │ │ resolve a problem with the LAN Distance product. │ │ │ │ │ │ Required LAN Distance privilege: user │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ ERROR LOG │ Access the OS/2 error log facility and view the errors │ │ │ logged there by the LAN Distance product. │ │ │ │ │ │ The information in the OS/2 error log is in hexadecimal │ │ │ format. It is intended to help your designated support │ │ │ organization resolve error situations. │ │ │ │ │ │ Required LAN Distance privilege: user │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ TRACKING │ Access information and tools for problem determination, │ │ │ including the audit log. Tools include trace, dump, and │ │ │ file retrieval facilities. │ │ │ │ │ │ On a secure LAN Distance workstation, the Tracking notebook │ │ │ displays only the tabs that are granted to the user who │ │ │ opens the notebook. For example, a LAN Distance user cannot │ │ │ access an audit log, so the Audit tab is not displayed for a │ │ │ LAN Distance user. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 6.3. Remotely Administering a LAN Distance Connection Server ═══ To manage a LAN Distance Connection Server from a remote location, select the LAN Distance Connection Server in your LAN Distance Workstations window. The following functions, however, are not available when you access a LAN Distance Connection Server remotely:  Phone Book  Message log  Error log Other restrictions on performing tasks remotely are:  The Security tab is not included in the Settings notebook for a remote LAN Distance Connection Server.  Only a LAN Distance administrator can open the Tracking notebook on a remote LAN Distance Connection Server. ═══ 6.4. Command Line Interface ═══ The LAN Distance product provides a command line interface as an alternative to using its graphical user interface. Type commands directly at the OS/2 command prompt or imbed them in command files to create batch procedures. Mix them with your network operating system and LAN application commands to create integrated procedures. For example, use LAN Distance commands to start and stop the LAN Distance product, log on, and dial. See Command Line Interface Reference for information about the LAN Distance command line interface. ═══ 6.5. Stopping the LAN Distance Product ═══ Before stopping the LAN Distance product on your workstation, hang up all your LAN Distance connections and close all your open notebooks. To stop the LAN Distance product, close the LAN Distance Workstations window. If you do not hang up your LAN Distance connections, the LAN Distance product hangs them up before stopping. Also, any open notebooks are closed and the changes are not saved. ═══ 6.6. Changing Your Workstation Name ═══ To change your LAN Distance workstation name from its default of MyWorkstation: 1. Open the LAN Distance Workstations window and select the MyWorkstation icon. 2. From the menu bar, select Selected, Open as, and Settings. 3. Select the Workstation tab. Use Settings Notebook, Workstation Tab as a guide for updating your LAN Distance workstation name. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 9. Settings Notebook, Workstation Tab │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ NAME OF THIS │ Specify your new LAN Distance workstation name. │ │ LAN DISTANCE │ │ │ WORKSTATION │ The icon for your workstation in the LAN Distance Work- │ │ │ stations window includes your workstation name. Your work- │ │ │ station name also identifies your workstation for call and │ │ │ port management when security is disabled. (If security is │ │ │ enabled, then your user ID identifies your workstation.) │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ DESCRIPTION │ Describe your workstation. │ │ OF THIS LAN │ │ │ DISTANCE │ Your workstation description is displayed when your LAN Dis- │ │ WORKSTATION │ tance Workstations window is viewed in details format. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 6.7. Connecting to a Non-LAN Distance Workstation ═══ Your LAN Distance workstation runs in 1 of 2 modes to allow it to connect to either LAN Distance or non-LAN Distance workstations. Note: A PPP client is considered to be a LAN Distance client. LAN Distance security functions are not available when your workstation is set up to connect to a non-LAN Distance workstation. To switch modes: 1. Open the Settings notebook and select the Workstation tab. 2. Select the Connect to a non-LAN Distance destination check box. 3. Restart the LAN Distance product to activate your new mode. ═══ 7. Setting Up Ports and Modems ═══ The LAN Distance product uses your WAN hardware (modems and WAN adapters) to establish wide area connections. Before you can dial out or answer calls to establish a LAN Distance connection, set up your LAN Distance ports. This chapter describes:  Setting up ports and modem types  Enabling ISDN ports  Customizing your modem configuration  Creating new modem types ═══ 7.1. Modems and WAN Adapters ═══ Install your modems and WAN adapters, according to the manufacturer instructions, before configuring your LAN Distance ports and modems. Supported Hardware lists the modems and adapters that the LAN Distance product supports. If your modem is not listed, you can try configuring your modem using a similar modem type, or modify the PIF file for a listed modem to meet the requirements of your unlisted modem. The LAN Distance Connection Server requires exclusive use of its WAN resources. When the LAN Distance product is running, other communications software can not use the modems, adapters, and ports configured for the LAN Distance product. The LAN Distance Connection Server supports up to 128 connections. Of these 128 connections, 64 can be PPP clients. In order to support more than 32 concurrent connections, a change must be made to config.sys. Each instance of DEVICE=x:\IBMCOM\MACS\MACFH.OS2 supports 16 connections. By default, there are two instances of this device driver loaded in the config.sys. To support more than 32 connections, additional instances of this device driver must be loaded. ═══ 7.2. Ports and Modem Types ═══ A LAN Distance port is the access point to your workstation for wide area connections. LAN Distance calls are dialed and answered through ports. One port is configured for each modem, internal or external, that you are setting up for the LAN Distance product. Use this procedure to set up a LAN Distance port and its asynchronous or synchronous modem: 1. Set up a LAN Distance port. Configure one LAN Distance port for every modem on your workstation. The LAN Distance product defines three types of ports:  Asynchronous COM ports with internal or external modems  ARTIC ports for asynchronous and synchronous external modems  Other for other types of asynchronous and synchronous WAN adapters 2. Configure a modem type. Set up at least one modem type for every type of modem you want to use with the LAN Distance product. Some examples of modem types are the IBM 7855 Modem, the Hayes Optima 14400 Modem, and the Codex 3260 Modem. 3. Assign your port to a modem type. The assignment of a port to a modem type provides the association between your ports and your modem. Assign each of your LAN Distance ports to a modem type. ═══ 7.2.1. Using Synchronous Modems and Leased Lines ═══ If you are using a synchronous modem or a leased line, you will need to assign one of the following generic modem types to your port. Synchronous Switched Connection Modem If you have a synchronous modem and a switched line, select this generic modem type regardless of the brand of modem you are using. For example, if you have an IBM 7855 modem that is configured for synchronous transmission mode, select this modem type instead of the IBM 7855 modem type. (The IBM 7855 modem type listed in the Available modem types list box is set up for asynchronous data transmission over a switched line.) Asynchronous Leased Line Modem If you have a leased line and are using an asynchronous modem, select this modem type regardless of the brand of modem you are using. For example, if a Hayes Optima modem is attached to your leased line, select this modem type instead of the Hayes Optima modem type. (The Hayes Optima modem type listed in the Available modem types list box is set up to use a switched telephone line.) Synchronous Leased Line Modem If you have a synchronous modem and a leased line, select this modem type regardless of the brand of modem you are using. For example, if you have an IBM 7855 modem attached to your leased line, select this modem type instead of the IBM 7855 modem type. (The IBM 7855 modem type listed in Available modem types is set up to use a switched connection.) ═══ 7.2.2. Starting and Stopping Your Modem Types ═══ All your modem types are automatically started when you start the LAN Distance product. After your modem types are started, you can dial and answer calls through the ports assigned to modem types. If you do not want your modem types started automatically, modify AUTOSTART parameter in the PIF file for the modem type. Modifying Modem Strings in a LAN Distance PIF File describes how to customize the configuration file for a modem type. All of the ports assigned to a modem type are started and stopped as a group. If you want to manage ports individually or define different subgroups, you can configure separate modem types. See Configuring a Modem Type and Assigning Ports to a Modem Type for information about setting up multiple modem types to manage your LAN Distance ports. For more information about managing your modem types, see Using System Management Tools. ═══ 7.2.3. Customizing Your Ports for Dialing and Answering ═══ You can configure phone book entries and answer modes so that certain ports are set up to either dial or answer calls. See Setting Up the Phone Book and Answering Incoming Calls for information about selecting ports for dialing and answering. ═══ 7.3. The Inactivity Timeout Feature ═══ This feature allows the administrator of a Connection Server to specify conditions for detecting a lack of activity over the various established connections and can force a disconnection of the link when that inactivity condition is present. ═══ 7.3.1. How Inactivity Timeout Works ═══ Every connection established by a machine where the inactivity timer is installed and operating is subjected to a "usage" test every minute. The test is somewhat like asking the question, "Over the past minute, have enough LAN frames passed across this link?" If the link fails the test enough times in succession without ever passing it, the link is broken. LAN Distance must be told two pieces of information by the Connection Server administrator:  How many minutes to tolerate inactivity on the link before forcing a disconnection  The minimum number of LAN frames that must cross the link (in either direction) within a one minute period for the link to be considered active. Inactivity Time Feature - Timers Page of Settings Notebook This information is provided to the Connection Server through values assigned to two new fields on the Timers page of the Settings notebook. The two fields are Inactivity timeout, which specifies the number of minutes of inactivity to tolerate before causing a line disconnect, and Inactivity threshold, which states the minimum number of frames that must cross an active link in a minute. The value of the Inactivity threshold field can be any number from 0 to 99999, but the test for sufficient usage of the link is skipped if the value is 0. Similarly, Inactivity timeout can have a value between 0 and 999, with 0 disabling the inactivity timeout feature. Each field is initially set to zero when the Connection Server is first installed. ═══ 7.3.2. Additional Information ═══ When disconnected, the remote workstation displays a WCL0310 message. In this version, no other indication is given to a user, and there is no warning that a disconnection is imminent. The values specified for Inactivity timeout and Inactivity threshold apply to all connections made to that Connection Server. They may not be customized or disabled for individual connections or ports. The value chosen for Inactivity threshold should be selected very carefully. The number of frames that cross the link during a passive connection where no real work is being performed can vary considerably from installation to installation. These values depend upon the type and configuration of the attached LAN. as well as the application being used on the remote workstation. The value chosen must be high enough so that a connection across an idle link is broken, but set low enough that low-intensity applications doing real work are not accidentally disconnected. Experimentation is required for each LAN environment where this feature is installed. A simple LAN Distance link, with the LAN parameters configured as recommended in the LAN Distances documentation, should see 4-5 frames cross each minute when no work is being done. This can be modified by the presence of LAN Requestor or Communications Manager. It is also necessary to experiment with the value of Inactivity threshold in the environment being used to determine an acceptable value. ═══ 7.4. Setting Up a LAN Distance Port ═══ To begin port set up: 1. Open the Settings notebook and select the Ports tab. The window shown in Settings Notebook, Ports Tab is displayed. Settings Notebook, Ports Tab 2. Select the Add push button. 3. Select the type of port you want to add. 4. Select OK. The ports you have already configured are displayed in the Configured ports list box. Select a push button to perform an action for a port. Your changes are saved when you close the Ports notebook. Shut down and restart your workstation to activate your changes. To add a port, select the Add push button. To delete a port, select the port you want to delete, then select the Delete push button. If you delete an active port, it remains active until you stop its modem type or you restart your workstation. If you delete a port that is the only port assigned to a modem type, the modem type is deleted also. Deleting a port also removes it from any phone book entry or answer mode to which it was assigned. Your phone book entries and answer modes are not disabled by removing the port; the LAN Distance product chooses any available, compatible port when dialing or answering calls. ═══ 7.4.1. Setting Up a COM Port ═══ Use Asynchronous COM Port as a guide for configuring an asynchronous COM port. Set up one LAN Distance port for every asynchronous modem attached to one of your COM ports. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 10. Asynchronous COM Port │ ├──────────────────┬────────────────┬──────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ COM PORT │ COM PORT │ Select the COM port for the LAN Distance │ │ │ │ port. │ │ │ │ │ │ │ │ All the COM ports installed on your │ │ │ │ workstation are included in this list │ │ │ │ box. Select a COM port that is not │ │ │ │ already in use by the LAN Distance │ │ │ │ product or another communications │ │ │ │ product. │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ COM PORT │ TRANSMIT FIFO │ Define the number of bytes that can be │ │ (Optional │ SIZE │ transmitted at one time using the asyn- │ │ fields) │ │ chronous FIFO support for your WAN │ │ │ │ adapter. │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ RECEIVE FIFO │ Define the number of bytes that trigger │ │ │ SIZE │ the asynchronous FIFO support for your │ │ │ │ WAN adapter. │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ IRQ │ Define the interrupt level for this │ │ │ │ port. Each COM port must be assigned a │ │ │ │ unique interrupt level. │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ BASE ADDRESS │ Define the memory address where the COM │ │ │ │ port is installed. │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ COM PORT │ LINE TYPE │ Select whether the port uses a switched │ │ │ │ or a leased line. │ │ │ Switched │ │ │ │ │ If you are setting up a COM port for a │ │ │ Nonswitched │ NULL modem, select SWITCHED. │ ├──────────────────┴────────────────┴──────────────────────────────────────────┤ │ NOTE: Default values for these optional fields are defined. Changing │ │ default values could cause your LAN Distance connections to fail. Leave the │ │ field blank to accept the default value. │ └──────────────────────────────────────────────────────────────────────────────┘ ═══ 7.5. Setting Up Supported ARTIC Adapters ═══ An ARTIC adapter is an IBM multiport adapter card for asynchronous and synchronous communications that supports up to eight ports. The LAN Distance product supports these ARTIC adapters:  IBM Realtime Interface Co-Processor Multiport for workstations with AT bus (non-micro channel) hardware. If you are using this ARTIC adapter, complete these tasks: - Creating a Co-Processor Parameter File - Steps for Setting Up an ARTIC Adapter - Steps for Setting Up an ARTIC Port  IBM Realtime Interface Co-processor PortMaster/A for micro channel workstations. If you are using this ARTIC adapter, complete these tasks: - Steps for Setting Up an ARTIC Adapter - Steps for Setting Up an ARTIC Port ═══ 7.5.1. Steps for Setting Up an ARTIC Adapter ═══ 1. Open the Settings notebook and select the Ports tab (Settings Notebook, Ports Tab). 2. From the Ports tab, select the Add push button. Settings Notebook, Ports Tab 3. From the window shown in Port Type/Adapter Type Window, select the ARTIC port type, then select the OK push button. Port Type/Adapter Type Window 4. The pop-up information window (Pop-Up Window for ARTIC Ports) is displayed if the statements required for ARTIC support are not in your CONFIG.SYS file. Select the OK push button to automatically add the following statements to your CONFIG.SYS file. device=[d:][\path\]ICARICIO.SYS run=[d:][\path\]ICARICCT.EXE -C32 Pop-Up Window for ARTIC Ports 5. The pop-up information window (ICAPARM.PRM Pop-Up Window) is displayed.  If you are setting up an IBM Realtime Interface Co-processor PortMaster/A adapter, you do not need to create the ICAPARM.PRM file.  If you are setting up an IBM Realtime Interface Co-Processor Multiport adapter, you must create an ICAPARM.PRM file as described in Creating a Co-Processor Parameter File before you complete Steps for Setting Up an ARTIC Port. Select the OK push button to continue. ICAPARM.PRM Pop-Up Window 6. Close the Settings notebook. Close the LAN Distance product and shut down and restart your workstation to save the changes made to your CONFIG.SYS file. ═══ 7.5.2. Steps for Setting Up an ARTIC Port ═══ Complete these steps for each port on your ARTIC adapter that you want to set up to use the LAN Distance product. 1. Open the Settings notebook and select the Ports tab to complete set up for your ARTIC ports. 2. From the Ports tab, select the Add push button to display the window shown in the following figure is displayed. 3. Select the ARTIC port type and select the OK push button. The ARTIC tab shown in ARTIC Tab, Page 1 of 2 is displayed. 4. From Page 1 of 2 of the ARTIC tab (ARTIC Tab, Page 1 of 2), make any changes to the default configuration values. For a description of the fields on these pages, select the Help push button. ARTIC Tab, Page 1 of 2 5. From Page 2 of 2 of the ARTIC tab, make any changes to default configuration values. For a description of the fields on these pages, select the Help push button. Select Close from the system menu icon to return to the Settings notebook. 6. Close the Settings notebook to save your configuration changes. Shut down and restart your workstation. Use Configuring an ARTIC Port as a guide for setting up one port for an ARTIC adapter. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 11. Configuring an ARTIC Port │ ├──────────────────┬────────────────┬──────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ ARTIC, PAGE 1 │ ARTIC CARD │ Select your ARTIC card number. │ │ │ NUMBER │ │ │ │ │ Use the value that was configured when │ │ │ │ you installed your ARTIC adapter. The │ │ │ │ ARTIC CARD TYPE field is updated after │ │ │ │ you make your selection here. │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ ARTIC CARD │ Select a port number for the port. │ │ │ PORT NUMBER │ │ │ │ │ Your port numbers are displayed here │ │ │ │ after you select your ARTIC CARD NUMBER. │ │ │ │ Select a unique value for every port you │ │ │ │ set up for this ARTIC adapter. │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ ARTIC, PAGE 1 │ MAXIMUM │ This value is used to allocate buffer │ │ (Optional │ RECEIVES │ space for receiving frames. │ │ fields) ├────────────────┼──────────────────────────────────────────┤ │ │ MAXIMUM TRANS- │ Define the maximum number of │ │ │ MITS │ TransmitChains that can be received from │ │ │ │ higher layer before acknowledgement is │ │ │ │ required. │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ ARTIC, PAGE 1 │ LINE TYPE │ Select whether the port uses a switched │ │ │ │ or a leased line. │ │ │ Switched │ │ │ │ │ │ │ │ Nonswitched │ │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ ARTIC, PAGE 2 │ LINE PROTOCOL │ Select whether this is an asynchronous │ │ │ │ or synchronous port. │ │ │ Asynchronous │ │ │ │ │ │ │ │ Synchronous │ │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ CLOCKING │ Select whether clocking signals are gen- │ │ │ │ erated by the adapter (internal) or the │ │ │ Internal │ modem (external). │ │ │ │ │ │ │ External │ This field applies only to synchronous │ │ │ │ connections. │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ LINE SPEED │ Specify the internal clocking line │ │ │ │ speed. │ │ │ │ │ │ │ │ This field applies only to internal │ │ │ │ clocking for a synchronous connection. │ ├──────────────────┴────────────────┴──────────────────────────────────────────┤ │ NOTE: Default values for these optional fields are defined. Changing │ │ default values could cause your LAN Distance connections to fail. Leave the │ │ field blank to accept the default value. │ └──────────────────────────────────────────────────────────────────────────────┘ ═══ 7.5.3. Setting Up Ports for Other Types of WAN Adapters ═══ Use this process to set up a LAN Distance port for:  IBM Wide Area Connector (WAC) Adapter  Multiport adapters other than the ARTIC adapter  Any other adapter not supported by the previous two port configuration procedures Ports for these adapters are configured through LAN Adapter Protocol Support (LAPS), shown in LAPS Configure Workstation Window. LAPS Configure Workstation Window Use Ports Notebook, Other Tab as a guide for setting up a port through LAPS. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 12. Ports Notebook, Other Tab │ ├──────────────────┬────────────────┬──────────────────────────────────────────┤ │ TAB OR WINDOW │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ OTHER │ PORT TITLE │ View your port title. │ │ │ │ │ │ │ │ Select the LAPS push button to proceed │ │ │ │ to the LAPS interface. │ ├──────────────────┼────────────────┼──────────────────────────────────────────┤ │ CONFIGURE WORK- │ NETWORK │ Select your WAN adapter. │ │ STATION WINDOW │ ADAPTERS │ │ │ │ │ Select the ADD push button to add your │ │ │ │ WAN adapter to the CURRENT CONFIGURATION │ │ │ │ list box. │ │ │ │ │ │ │ │ The LAPS interface is not typically used │ │ │ │ for configuring WAN adapters. Many of │ │ │ │ the fields and actions are for setting │ │ │ │ up LAN protocols and LAN adapters. │ │ │ │ Ignore these items when you configure │ │ │ │ your WAN adapter. │ │ ├────────────────┼──────────────────────────────────────────┤ │ │ CURRENT CON- │ Identify your ports. │ │ │ FIGURATION │ │ │ │ (Required for │ If you are setting up ports for a multi- │ │ │ a multiport │ port adapter, you must identify every │ │ │ adapter) │ port on your adapter. For each port: │ │ │ │ │ │ │ │ 1. Select your multiport adapter from │ │ │ │ the CURRENT CONFIGURATION list box. │ │ │ │ 2. Select the EDIT push button. │ │ │ │ 3. Specify values for: │ │ │ │ o Slot number of card number │ │ │ │ o Port number │ │ │ │ o Port name displayed in the PPAT │ │ │ │ table │ │ │ │ 4. Select OK. │ └──────────────────┴────────────────┴──────────────────────────────────────────┘ ═══ 7.5.4. Setting Up ISDN Ports ═══ The LAN Distance product and the IBM Communication Manager/2 product cannot use your ISDN adapters simultaneously. When you configure an ISDN port for the LAN Distance product, this port can be used only by the LAN Distance product. Configure your ISDN adapter and the telephone numbers for its channels outside the LAN Distance product before enabling your LAN Distance ISDN ports. To enable your ISDN ports: 1. Open the Settings notebook and select the Ports tab. 2. Check Enable ISDN ports. To change your ISDN configuration after enabling your LAN Distance ISDN ports: 1. Disable your LAN Distance ISDN ports. 2. Run your ISDN configuration program. 3. Re-enable your LAN Distance ISDN ports. ═══ 7.6. Setting Up for a WAC Adapter ═══ 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:  Enter the ROM address of the WAC Adapter recorded above.  For "Line Mode" enter 0 for Constant RTS.  For "MAC Type Description" enter HDLC.  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 synchronous leased line. However, you must carefully configure LAN Distance 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 Criteria 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: -- 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.  For "ANDIS PCM Support" enter 1 for YES.  For "Slot Number" enter the slot number in which the adapter is inserted.  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.  For "Link Connection type" enter 1 for switched or 0 for non-switched (leased line) connections.  For "Portname displayed in the PPAT table" enter a name to identify the adapter to the port connection manager.  Typically, you can use default values for the rest of the parameters. ═══ 7.7. Configuring a Modem Type and Assigning Ports to a Modem Type ═══ Set up at least one configuration for every unique modem type on your workstation. Associate your logical ports with your physical WAN hardware by assigning each port to a modem type. A modem type can have multiple ports assigned as long as the number of ports does not exceed the actual number of modems of that type installed on your workstation. Configuring the same modem type more than once gives you the flexibility to:  Control your ports individually.  Customize your modems differently.  Support different communication connections and line types with the same modem type. All the ports for a modem type are managed together. This means that they are started and stopped as a group. If you want to maintain individual control over your ports and they all use the same modem type, configure a separate modem type for each port. You can use the same modem type configuration as a model for each one. To customize the configuration of one of your modems without modifying the configuration for all the modems of that type, set up an additional modem type. You can base your customized configuration on the configuration of the original modem type. All of the modems for a modem type must use the same connection and line type. For example, if your workstation uses IBM 7855 modems to support both switched and leased lines, configure two IBM 7855 modem types: one to support the switched connection and the other to support the nonswitched connection. To begin modem type configuration: 1. Open the LAN Distance Workstations window and select MyWorkstation. 2. Select Selected from the menu bar. 3. Select Open as and Settings. 4. Select the Modems tab. The window shown in Settings Notebook, Modems Tab is displayed. Settings Notebook, Modems Tab The modem types already configured are displayed in the Modem type assignments list box. Select a push button to perform an action for a modem type. Your changes are saved when you close the Modems notebook. Restart the LAN Distance product to start your new modem type and its ports. Select Assign push button to set up a new modem type. Available Modem Types Window shows the window displayed when you assign a new modem type. When you configure a new modem type, you must specify one or more ports for it. To assign ports to a previously configured modem type, select the Change push button. If you delete an active modem type, its ports remain active until you stop the modem type or you restart the LAN Distance product. cannot be used to dial or answer calls until they are assigned to another modem type. Available Modem Types Window Use Settings Notebook, Modems Tab as a guide for configuring a modem type. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 13. Settings Notebook, Modems Tab │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ MODEMS │ AVAILABLE │ Select a modem type. │ │ │ MODEM TYPES │ │ │ │ │ If your modem is not listed in the AVAILABLE │ │ │ │ MODEM TYPES list box, see Using a Listed Modem │ │ │ │ Type to Configure Your Asynchronous Modem.. │ │ │ │ │ │ │ │ The modems types that support both asynchro- │ │ │ │ nous and synchronous connections are config- │ │ │ │ ured for an asynchronous connection, see Using │ │ │ │ Synchronous Modems and Leased Lines. │ │ │ │ │ │ │ │ Use the push buttons to add, change or delete │ │ │ │ ports for the modem type. The Ports window of │ │ │ │ the Modems notebook is displayed when you add │ │ │ │ a port. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CREATE NEW │ Set up a new modem type. │ │ │ ASYNCHRONOUS │ │ │ │ MODEM TYPE │ Select a modem type to use as a template for │ │ │ USING ABOVE AS │ creating a new modem type configuration for an │ │ │ MODEL │ unlisted modem. Try to select a modem type │ │ │ │ similar to your unlisted modem, or select a │ │ │ │ generic modem type. │ │ │ │ │ │ │ │ To customize the configuration values for your │ │ │ │ new modem type, see Modifying Modem Strings in │ │ │ │ a LAN Distance PIF File. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ NEW MODEM │ Specify a new modem title. │ │ │ TITLE │ │ │ │ │ If you are creating a new modem type, identify │ │ │ │ it uniquely with a new modem title. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ PORTS, │ SWITCHED │ Specify the phone number of the modem for the │ │ PAGE 1 │ │ port. │ │ │ PHONE NUMBER │ │ │ │ (Optional) │ The phone number identifies the specific modem │ │ │ │ that your port uses. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ NONSWITCHED │ Specify the name of the leased line for the │ │ │ │ port. │ │ │ PERMANENT CON- │ │ │ │ NECTION NAME │ The name identifies the leased line that your │ │ │ │ port uses. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ PORTS, │ AVAILABLE │ Select a port to assign to this modem type. │ │ PAGE 2 │ PORTS │ │ │ │ │ A list of previously configured ports is dis- │ │ │ │ played. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 7.8. What to Do If Your Modem Is Not Listed ═══ The Available modem types field, shown in the Available Modem Types Window table in Configuring a Modem Type and Assigning Ports to a Modem Type, lists the modems that the LAN Distance product is already set up to support. If your modem is not listed in Available modem types field, you can try to configure it using the following methods: 1. Select a listed modem type that will work for your modem. Complete the steps in Using a Listed Modem Type to Configure Your Asynchronous Modem. Try step What to Do If Your Modem Is Not Listed or step What to Do If Your Modem Is Not Listed only after you have tried using several of the listed modem types to configure your unlisted modem. 2. Use the graphical Port/Modem utility to create a new modem type. See Using the Port/Modem Utility. 3. Manually create a PIF file for your modem using the PIF file of a listed modem as a template. See Creating a New PIF File for a Modem Not in the List. Note: If you try all of these steps and are still unable to establish a LAN Distance connection, contact your designated support organization for assistance. ═══ 7.9. Using a Listed Modem Type to Configure Your Asynchronous Modem ═══ Repeat these steps until you find a listed modem type with configuration values that work for your modem, or until you have tried all the listed modem types. 1. If you have not already configured a port for your new modem type, see Setting Up a LAN Distance Port. 2. Open the Settings notebook and select the Modems tab. Select the Assign push button to begin configuring your modem type. 3. Try to select a similar modem type from Available modem types list box, using one or more of the following strategies: a) Select a modem type with the same manufacturer. b) If your modem is compatible with a listed modem type, select the compatible modem type. c) Select the Asynchronous Switched Connection Modem type. d) Select any other listed modem type. 4. Check Create new asynchronous modem type using above as model and specify a new name for your modem type in the New modem titlefield. 5. Select OK to continue. 6. Select the Add push button to assign ports to your new modem type. See Configuring a Modem Type and Assigning Ports to a Modem Type for more information. 7. Close the Settings notebook to save your new modem type configuration. 8. Restarting the LAN Distance product starts your new modem type and the ports assigned to it. To stop or start a modem type without stopping and restarting the LAN Distance product: a) Open the LAN Distance Workstations window. b) Select MyWorkstation. c) Select Selected from the menu bar. d) Select Open as and Call and port management. The Call and Port Management - Port View is displayed. e) Select View from the menu bar. f) Select Modem types to change your view to your modem types. g) Select your new Modem Type Name. h) Select Selected from the menu bar. i) Select an action:  Stop hard  Start 9. Your modem type is successfully configured if you can establish a connection, send and receive data, and disconnect the modem. If you cannot communicate using your new modem type, delete it through the Modems tab of the Settings notebook, and try another listed modem type. If you are not able to find a listed modem type that works for your modem type, try customizing a PIF file. See Creating a New PIF File for a Modem Not in the List for information about updating PIF files. Note: Software, modems and other hardware can also cause connection problems. Troubleshooting Tips for troubleshooting information. You can also use a null modem to test the connection and the modems as described in the following topic. ═══ 7.10. Setting Up a Null Modem to Test Your LAN Distance Connection ═══ You can set up a null modem cable to test the connection between two LAN Distance workstations before setting up a modem by setting up one workstation to answer calls and one workstation to dial out. Alternatively, if you experience problems with a connection after your modems are configured for the LAN Distance product, setting up a null modem cable is one way to determine if your modems are configured and functioning correctly. The line type (switched or nonswitched) setup for null modems is unique. Set up requirements are summarized in Line Type Configuration Settings for Null Modems. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 14. Line Type Configuration Settings for Null Modems │ ├───────────────────────────────────────┬──────────────────────────────────────┤ │ NULL MODEM CONFIGURATION SETTINGS │ SWITCHED OR NONSWITCHED │ ├───────────────────────────────────────┼──────────────────────────────────────┤ │ Ports │ Switched │ ├───────────────────────────────────────┼──────────────────────────────────────┤ │ Modems │ Nonswitched │ ├───────────────────────────────────────┼──────────────────────────────────────┤ │ Phone Book │ Nonswitched │ ├───────────────────────────────────────┼──────────────────────────────────────┤ │ Answer criteria │ Nonswitched │ └───────────────────────────────────────┴──────────────────────────────────────┘ Steps for setting up a null modem cable to test a connection between a LAN Distance Connection Server and a LAN Distance Remote are described in the following topics:  Setting Up a Null Modem to Answer Calls  Setting Up a Null Modem to Dial Out ═══ 7.10.1. Setting Up a Null Modem to Answer Calls ═══ Complete the following steps to set up a LAN Distance Connection Server to answer calls: 1. From the Settings notebook, select the Ports tab. 2. From the Ports tab, delete any ports from the Configured ports field that you plan to use for null modems. Select Add to begin port configuration. 3. From the Select an adapter type field, select the COM port adapter type. Select OK to continue port configuration. 4. From the COM port tab, select Switched for the Line type. Select Close from the system menu icon to return to the Ports tab in the Settings notebook. 5. Select the Modems tab. Delete any modem types from the Assignments for modem types field that you plan to use for null modems. Select Assign to begin modem configuration. 6. From the Available modem types field, select the Null Modem. Select OK to continue modem configuration. 7. From the Ports tab within Modems settings, select Add to assign a port to the Null Modem. 8. From the Null Modem - Settings window, verify that the Nonswitched radio button is selected. Specify a name in the Permanent connection name field. The name you specify for the LAN Distance Connection Server and LAN Distance Remote must match. Select OK to continue modem configuration. 9. From the Available ports field, select the COM port you configured in step 3. Select OK to return to the Ports tab. 10. Select Close from the system menu symbol to return to the Settings notebook. 11. Select the Answer tab. Select the Add push button to set up your LAN Distance Connection Server to answer calls. 12. From the Answer Mode Criteria - Settings window, select PSTN for the Network type and select Nonswitched for the Line type. Select OK to continue answer mode configuration. 13. From the Answer tab within Answer settings, type a name for the answer mode in the Answer mode name field. Check the Enable answer mode on startup field. 14. Select Close from the system menu symbol to return to the Settings notebook. 15. Close the Settings notebook. Shut down and restart your workstation to make these changes effective. ═══ 7.10.2. Setting Up a Null Modem to Dial Out ═══ Complete the following steps to set up a LAN Distance Remote or a LAN Distance Connection Server to dial out. 1. Complete steps 1 - 10 in Setting Up a Null Modem to Answer Calls. 2. Select the Phone Book tab in the Settings notebook. Select the Add push button to add a phone book entry for the Null Modem. 3. From the New Entry - Settings window, select PSTN for the Network type and select Nonswitched for the Line type. Select OK to continue phone book entry configuration. 4. From the Entry tab within Phone Book settings, type a name for the phone book entry in the Entry name field. 5. Select the Connect tab in Phone Book settings. Verify the information in the Modem and Leased line fields. 6. Select Close from the system menu symbol to return to the Phone Book tab in the Settings notebook. 7. Close the Settings notebook. Shut down and restart your workstation to make these changes effective. 8. Dial out from the LAN Distance Remote to the connection server to test your null modem connection. ═══ 8. Setting Up the LAN Distance Bridge ═══ This chapter explains the routing methods the LAN Distance bridge supports for Token-Ring and Ethernet LANs, describes how to set up the LAN Distance bridge for Token-Ring and Ethernet LANs, and explains the automatic and custom filtering capabilities of the LAN Distance bridge. ═══ 8.1. Overview of the LAN Distance Bridge ═══ The bridge component of the LAN Distance Connection Server product routes and filters data frames from the LAN segment to the WAN segment and from the WAN segment to the LAN segment. The LAN Distance bridge can be configured to route Token-Ring or Ethernet data frames.  If your LAN Distance Connection Server is installed on a Token-Ring LAN, see set up requirements described in Understanding Token-Ring Bridges.  If your LAN Distance Connection Server is installed on an Ethernet LAN, see set up requirements described in Understanding Ethernet Bridges.  PPP client frames are routed and not bridged. The LAN Distance Bridge ═══ 8.2. Understanding Token-Ring Bridges ═══ This section describes how Token-Ring LANs route data and tells you how to define LAN Distance bridge configuration values for Token-Ring LANs. ═══ 8.2.1. Source Routing Required for the LAN Distance Token-Ring Bridge ═══ Token-Ring bridges can support transparent or source routing of data frames. When the LAN Distance Connection Server is installed on a Token-Ring LAN, the LAN Distance bridge requires source routing information to route Token-Ring data frames on and off the LAN and WAN segments. Source routing information consists of a sequence of LAN segment numbers and bridge numbers stored in the routing information field of a Token-Ring data frame. When the LAN Distance Connection Server is installed on a Token-Ring LAN, a bridge number is assigned to the LAN Distance bridge and segment numbers are assigned to the LAN segment and the WAN segment. Complete these tasks to support Token-Ring source routing at the LAN Distance bridge:  Verify that the LAN Distance bridge is enabled. See Enabling and Disabling the LAN Distance Bridge.  Verify that automatic filtering is enabled at the LAN Distance bridge. See Using the Automatic Filtering Feature.  To configure the LAN Distance bridge to handle Token-Ring data frames, specify a LAN Distance bridge number, and segment numbers for the LAN and the LAN Distance WAN segment. See Defining LAN Distance Bridge Token-Ring Configuration Values.  The bridges and routers in your LAN environment must be configured to support source routing.  If you are running applications over a LAN Distance connection that allow you to configure a source routing option, such as Banyan VINES or NetWare, configure the application so its data frames contain source routing information. Note: The Token-Ring LAN adapter installed on the LAN Distance Connection Server must be supported by the LAN Distance product. See Local Area Network Adapters for a list of supported adapters. ═══ 8.3. Defining LAN Distance Bridge Token-Ring Configuration Values ═══ The LAN Distance bridge is identified by a bridge number, a LAN segment ring number, and a WAN segment ring number. These values must be customized for your network environment. See Defining Configuration Values for the LAN Distance Bridge. Note: For help configuring LAN Distance bridge configuration values, use the Bridge 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 WAL subdirectory for the CALLBRDG.RME file for a description of this utility. The OS2PING tool can also be used to define LAN Distance bridge configuration values, see Using OS2PING for Troubleshooting and LAN Distance Bridge Configuration. ═══ 8.3.1. Overview of Multisegmented Token-Ring LAN Environments ═══ Your Token-Ring LAN is one of three types:  Unsegmented  Segmented with one or more bridges  Segmented with several bridges and multiple paths to some destinations Your Token-Ring LAN environment is unsegmented if you have no bridges linking one LAN segment to another LAN segment. Your Token-Ring LAN environment is segmented if your LAN comprises more than one LAN segment, connected by bridges. Token-Ring LAN and LAN Distance Bridges Unsegmented LANs If your Token-Ring LAN is unsegmented, the LAN Distance Remote 1 in Token-Ring LAN and LAN Distance Bridges most closely resembles your environment. This workstation dials into LAN Distance Connection Server 1 to access LAN 1. This Token-Ring LAN has no other bridges; LAN resources are directly attached to the LAN. If your Token-Ring LAN is unsegmented, accept the LAN Distance default values for your LAN segment ring number, bridge number, and hop counts. Segmented LANs If your Token-Ring LAN is segmented with several bridges, the LAN Distance Remote 2 in Token-Ring LAN and LAN Distance Bridges most closely resembles your environment. This workstation dials into LAN Distance Connection Server 2 to access LAN 1. Modifying 3 bridge settings makes 2 of the bridges available to access LAN 2 and the 3270 Controller on LAN 2. When the LAN Distance bridge is configured with LAN segment ring number F03, the LAN Distance Connection Server matches the other bridges. When the LAN Distance bridge number is set to 3, the bridge number is unique for the LAN Distance product. When the hop counts are set to 2, the LAN Distance Remote can cross the LAN Distance and the F03 bridge. Segmented, multipath LANs If your LAN is segmented with several bridges and multiple paths, configure your LAN Distance bridge very carefully. In Token-Ring LAN and LAN Distance Bridges, 2 bridges have identical LAN segment ring numbers (F03/B02). To differentiate these bridges, each bridge must be assigned a unique bridge number. Also, LAN Distance Connection Server 2 must have a unique LAN Distance bridge number. If your Token-Ring LAN is segmented, but you do not want remote workstations to access resources outside your LAN segment, configure a unique LAN segment ring number for your LAN Distance bridge. This prevents other LAN segments from sending frames over your LAN Distance WAN connections and prevents remote workstations from communicating with any resources outside your LAN segment. You can also enhance the performance of your LAN Distance wide area network by placing your LAN Distance Connection Server on the LAN segment that contains the resources required by remote workstations and then configuring the LAN Distance bridge to access only resources on its own LAN segment. ═══ 8.3.2. Defining Configuration Values for the LAN Distance Bridge ═══ To begin configuring your LAN Distance bridge on a Token-Ring LAN, open the Settings notebook and select the Bridge tab. The first page of your LAN Distance bridge notebook, shown in Settings Notebook, Bridge Tab is displayed. Settings Notebook, Bridge Tab Use Settings Notebook, Bridge Tab as a guide for modifying your LAN Distance bridge configuration. Your changes are saved when you close the Bridge Settings notebook. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 15. Settings Notebook, Bridge Tab │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ BRIDGE, │ LOAD BRIDGE │ This field must be checked to allow LAN Dis- │ │ PAGE 1 │ SUPPORT │ tance Remotes to access LAN resources on │ │ │ │ Token-Ring and Ethernet LANs. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ENABLE AUTO- │ This field must be checked if you want the LAN │ │ │ MATIC FIL- │ Distance product to use automatic filtering. │ │ │ TERING │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ BRIDGE NUMBER │ Assign a number to the LAN Distance bridge. │ │ │ │ │ │ │ │ Your bridge number, LAN segment ring number, │ │ │ │ and WAN segment ring number combine to form a │ │ │ │ route designator for your LAN data frames. │ │ │ │ The route designator must be unique on your │ │ │ │ LAN Distance wide area network. One way to │ │ │ │ make sure it is unique is to assign different │ │ │ │ bridge numbers to each of the LAN Distance │ │ │ │ bridges in your system. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ MAXIMUM DATA │ Specify the largest data unit that can be │ │ │ UNIT SIZE │ transmitted by the LAN Distance bridge. │ │ │ │ │ │ │ │ If your LAN Distance bridge receives a data │ │ │ │ frame that exceeds this size, the frame is │ │ │ │ discarded. │ │ │ │ │ │ │ │ o A large data frame incurs less overhead │ │ │ │ for the amount of data being transmitted, │ │ │ │ so it might be transmitted faster than a │ │ │ │ set of smaller frames. │ │ │ │ o WAN transmission errors might occur on │ │ │ │ large data frames. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ BRIDGE, │ LAN SEGMENT │ Assign a ring number for the LAN Distance │ │ PAGE 2 │ RING NUMBER │ bridge LAN segment. │ │ │ │ │ │ │ │ This number is the ring number of the LAN │ │ │ │ segment on which your LAN Distance Connection │ │ │ │ Server resides. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ MAXIMUM NUMBER │ Specify the number of bridges a data frame can │ │ │ OF NETWORK │ cross. │ │ │ BRIDGE HOPS │ │ │ │ │ Restrict the number of network segments that a │ │ │ │ data frame can traverse before it reaches its │ │ │ │ destination. A network segment hop occurs at │ │ │ │ every bridge on your LAN, including the LAN │ │ │ │ Distance bridge. If the LAN Distance bridge │ │ │ │ detects that a frame has exceeded the config- │ │ │ │ ured hop count, it discards the frame. │ │ │ │ │ │ │ │ Set your hop count high enough for the data │ │ │ │ from your remote workstations to reach its │ │ │ │ destination. Your LAN and WAN hop counts │ │ │ │ should be the same. │ │ │ │ │ │ │ │ You can use hop counts to limit the trans- │ │ │ │ mission of LAN data frames to a certain │ │ │ │ geographic area. For example, setting your │ │ │ │ hop count to 1 allows only frames from LAN │ │ │ │ workstations on your LAN Distance Connection │ │ │ │ Server's LAN to be forwarded onto your wide │ │ │ │ area connections. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ACTIVE LAN │ View the active filtering criteria. │ │ │ FILTER │ │ │ │ │ One set of LAN segment filtering criteria can │ │ │ │ be active at a time. Activate a set of fil- │ │ │ │ tering criteria by selecting it in the LAN │ │ │ │ segment filter criteria list box. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ LAN SEGMENT │ Establish LAN segment filtering criteria. │ │ │ FILTER CRI- │ │ │ │ TERIA │ Use the push buttons to add, change, or delete │ │ │ │ filtering criteria. See Types of Filtering │ │ │ │ Supported for the LAN Distance Bridge. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 15. Settings Notebook, Bridge Tab │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ BRIDGE, │ WAN SEGMENT │ Assign a ring number for the LAN Distance │ │ PAGE 3 │ RING NUMBER │ bridge's WAN segment. │ │ │ │ │ │ │ │ Your WAN segment ring number must be different │ │ │ │ from your LAN segment ring number. Otherwise, │ │ │ │ your WAN segment ring number can be any value │ │ │ │ as long as it helps create a unique route des- │ │ │ │ ignator. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ MAXIMUM NUMBER │ Specify the number of bridges a data frame can │ │ │ OF NETWORK │ cross. │ │ │ BRIDGE HOPS │ │ │ │ │ Restrict the number of network segments that a │ │ │ │ data frame can cross before it reaches its │ │ │ │ destination. Your LAN and WAN hop counts │ │ │ │ should be the same. │ │ │ │ │ │ │ │ You can use hop counts to filter LAN traffic │ │ │ │ by limiting transmission of data to a certain │ │ │ │ geographic area. For example, prevent your │ │ │ │ remote users from accessing other workstations │ │ │ │ on your LAN by setting your hop count to 0. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ACTIVE WAN │ View the active filtering criteria. │ │ │ FILTER │ │ │ │ │ One set of LAN segment filtering criteria can │ │ │ │ be active at a time. Activate a set of fil- │ │ │ │ tering criteria by selecting it in the LAN │ │ │ │ SEGMENT FILTER CRITERIA list box. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ WAN SEGMENT │ Establish WAN segment filtering criteria. │ │ │ FILTER CRI- │ │ │ │ TERIA │ Use the push buttons to add, change, or delete │ │ │ │ filtering criteria. See Types of Filtering │ │ │ │ Supported for the LAN Distance Bridge. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 8.4. Understanding Ethernet Bridges ═══ Ethernet LANs support transparent routing of data frames. When the LAN Distance bridge is operating in an Ethernet environment, the LAN Distance bridge functions as a transparent bridge. Transparent bridges process each data frame, comparing the source and destination address for the data frame to the source and destination routing tables maintained at the LAN Distance bridge. Because each data frame is processed, transparent bridging is CPU intensive. Complete these steps to support Ethernet transparent routing at the LAN Distance bridge:  Verify that the LAN Distance bridge is enabled. See Enabling and Disabling the LAN Distance Bridge.  From the Address tab in the Setting notebook, select the Ethernet radio button from the LAN type field.  If you are setting up the LAN Distance Connection Server product on an Ethernet LAN, a dedicated workstation for the LAN Distance Connection Server is recommended. See Select a Dedicated or Nondedicated Workstation.  Verify that automatic filtering is enabled at the LAN Distance bridge. See Using the Automatic Filtering Feature.  When you install the LAN Distance Connection Server on a Ethernet LAN, source routing information, segment ring numbers and bridge numbers, are not required. Note: The Ethernet LAN adapter installed on the LAN Distance Connection Server must be supported by the LAN Distance product. See Local Area Network Adapters for a list of supported adapters. ═══ 8.5. Enabling and Disabling the LAN Distance Bridge ═══ The LAN Distance bridge function can be enabled and disabled from the Bridge tab in the Settings notebook. When you install the LAN Distance Connection Server, the Load bridge support field on the Bridge tab is enabled. To make this default setting active, simply open and close the Settings notebook. To disable the LAN Distance bridge on your LAN Distance Connection Server: 1. Open the Settings notebook and select the Bridge tab, shown in Defining Configuration Values for the LAN Distance Bridge. 2. From the Bridge tab, uncheck the Load bridge support check box. 3. To make this change take effect, close the LAN Distance product, shut down then restart your workstation. ═══ 8.6. Ethernet Bridge Configuration Considerations ═══ You do not need to configure an Ethernet Bridge if all your remote access clients are PPP clients. If you configure an Ethernet Bridge through the LAN Distance Settings notebook, Settings modifies PROTOCOL.INI as follows:  Replacing the Ethernet adapter in the Bindings statements for NetBEUI and TCPBEUI with the LAN Distance logical adapter.  Modifying and deleting statements in the NetBIOS section based on changes to the Bindings statements for NetBEUI and TCPBEUI. This reconfiguration may affect your LAN Server configuration. The following example demonstrates how your LAN Server configuration could be affected by the configuration of an Ethernet bridge. Your system was configured as follows prior to configuring the Ethernet bridge.  The MPTS adapters and protocols configuration panel displays the following: IBM LAN Adapter for Ethernet [IBMENI.OS2] ... 0 - IBM OS/2 NetBIOS 0 - IBM TCP/IP 2 - IBM OS/2 NetBIOS over TCP/IP LAN Distance Logical Adapter ... 1 - IBM TCP/IP 1 - IBM OS/2 NetBIOS  The networks section in the LAN Server configuration file, IBMLAN.INI, contains the following statements: net1 = NETBEUI$,0,LM10,34,70,14 net2 = NETBEUI$,1,LM10,34,70,14 net3 = TCPBEUI$,2,LM10,34,70,14 After configuring the Ethernet bridge, you system is configured as follows:  The MPTS adapters and protocols configuration panel displays the following: LAN Distance Logical Adapter ... 0 - IBM OS/2 NetBIOS 2 - IBM OS/2 NetBIOS over TCP/IP 1 - IBM TCP/IP IBM LAN Adapter for Ethernet [IBMENI.OS2] ... 0 - IBM TCP/IP 0 - [SR_BRIDGE] [BRIDGEFH] ... 1 - [SR_BRIDGE]  The networks section in the LAN Server configuration file, IBMLAN.INI, still contains the following statements: net1 = NETBEUI$,0,LM10,34,70,14 net2 = NETBEUI$,1,LM10,34,70,14 net3 = TCPBEUI$,2,LM10,34,70,14 With this configuration, you get the following error when you shutdown and reboot the system: NET3406: An error occurred while opening network device drive net2=NETBEUI$ NET3411: There was an error installing NETWKSTA.200. To fix your configuration, you must step through the "LAN Services Adapters" component configuration panels in the "OS/2 LAN Services Installation/Configuration" program in the "OS/2 LAN Services" folder. When you get to the "Adapter and Protocol Configuration" panel, add the IBM OS/2 NetBIOS and IBM OS/2 NetBIOS over TCP/IP back under the Ethernet adapter. If you do not make any changes in the protocol and adapters configuration panel, the program corrects the IBMLAN.INI file based on your current adapter and protocol configuration when you "Apply the changes". However, remote clients will not be able to access resources on your LAN for those networks that are removed. When you are done configuring LAN Services, your IBMLAN.INI file should remain the same. The MPTS adapters and protocols configuration panel displays the following: IBM LAN Adapter for Ethernet [IBMENI.OS2] ... 0 - IBM OS/2 NetBIOS 0 - IBM TCP/IP 2 - IBM OS/2 NetBIOS over TCP/IP 0 - [SR_BRIDGE] LAN Distance Logical Adapter ... 1 - IBM TCP/IP 1 - IBM OS/2 NetBIOS [BRIDGEFH] ... 1 - [SR_BRIDGE] ═══ 8.7. Types of Filtering Supported for the LAN Distance Bridge ═══ Filtering is an important performance feature of the LAN Distance product. The ability to filter data frames at the LAN Distance bridge prevents LAN data frames from saturating the slower LAN Distance WAN connection and degrading its performance. The LAN Distance product supports two types of filtering: automatic and customized. applications and LAN Distance environments. If you are setting up a LAN-to-LAN environment or using special applications, you can customize filtering criteria to meet your requirements. The following restrictions apply to the automatic filtering function:  Automatic filtering is not supported for a LAN Distance Remote set up as a stand-alone server, such as a LAN Server or a Database/2 Server. Disable automatic filtering if this restriction applies to your LAN Distance setup.  Automatic filtering is not supported for the LAN-to-LAN environment. If the answer mode for your port is set up for a LAN-to-LAN connection, automatic filtering will not work. To deactivate the LAN-to-LAN feature for an answer mode, simply uncheck the LAN-to-LAN connection check box. Step Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection in Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection tells how to access this check box.  When automatic filtering is enabled, NetBIOS broadcast datagrams are not forwarded to the LAN Distance Remotes. For example, a LAN Server/Requester command of "NET SEND * HELLO WORLD" is not forwarded by the LAN Distance bridge. ═══ 8.7.1. Using the Automatic Filtering Feature ═══ Automatic filtering is enabled on the LAN Distance Connection Server when you install the LAN Distance product. each LAN Distance Remote that dials in to a LAN Distance Connection Server. Automatic filtering is supported for the NDIS-compliant protocols supported by the LAN Distance product. ═══ 8.7.1.1. How Automatic Filtering Works ═══ Automatic filtering works by screening data frames based on protocol-specific criteria. Unique screening criteria is used for different protocol types. For example, a LAN Distance Remote running LAN Requester sends out data frames containing NetBIOS source names. The NetBIOS source name identifies the LAN Server receiving data frames. The automatic filtering function maintains a list of the NetBIOS source names received from the LAN Distance Remote and only forwards data frames from these NetBIOS source names. ═══ 8.7.1.2. Disabling Automatic Filtering ═══ When automatic filtering is enabled, it applies to all ports configured for the LAN Distance product. Automatic filtering is disabled when the Enable automatic filtering check box on page 1 of 3 of the Bridge notebook is not checked. Note: Automatic filtering is disabled for ports that have answer modes configured to accept LAN-to-LAN connections. ═══ 8.7.2. Customizing Filtering Criteria ═══ Customized filtering gives you the capability to define separate filtering criteria for the WAN and LAN segments of your LAN Distance wide area network. Data frames from the LAN and WAN segments are forwarded or rejected at the LAN Distance bridge based on the filtering criteria you define. This advanced filtering capability requires gathering information for the supported filtering types that you want to use. The custom filtering criteria that you define applies to all ports on the LAN Distance Connection Server, including the ports that you have set up for automatic filtering.  LAN segment filter criteria filters data frames sent to the WAN segment from workstations or resources on a LAN segment. Define LAN segment filter criteria on page 2 of 3 of the Bridge notebook.  WAN segment filter criteria filters data frames sent to the LAN from LAN Distance Remotes on your WAN segment. Define WAN segment filter criteria on page 3 of 3 of the Bridge notebook. ═══ 8.7.2.1. Defining Filter Criteria for a Filter Name ═══ Each set of WAN or LAN filter criteria that you define is identified by a filter name. More than one filter name can be created for your WAN and LAN segments, but only one filter name for the LAN segment and one filter name for the WAN segment can be active. You can define multiple filter types when you create a filter name, or you can create a filter name using only one filter type. The LAN Distance bridge supports the following filter types:  Source addresses  Range of source addresses  Bit mask destination address  Service Access Point (SAP)  NetBIOS names ═══ 8.7.2.2. Creating a Filter Name Using Only One Filter Type ═══ When you create a filter name using only one filter type, a logical OR is always applied to each of the criteria that you define for the filter type. This is true for the filter types that contain lists: source addresses, SAPs, and NetBIOS names. For example, if you define 4 source addresses for a filter name, data frames are forwarded by the LAN Distance bridge that match source address 1, OR source address 2, OR source address 3, OR source address 4. ═══ 8.7.2.3. Creating a Filter Name Using Multiple Filter Types ═══ If you define more than one type of filter criteria for a filter name, you can apply a logical OR or AND to the different filter types. ═══ 8.7.2.3.1. Applying Logical OR to Different Filter Types ═══ This is the default setting for this option. When the Apply logical OR to bridge filter criteria check box is selected, a logical OR is applied to the criteria defined between different filter types. For example, if you define an acceptable range of source addresses and 2 additional source addresses for a filter name, data frames are forwarded by the LAN Distance bridge that fall within the source address range OR that match source address 1 or source address 2. ═══ 8.7.2.3.2. Applying Logical AND to Different Filter Types ═══ When the Apply logical OR to bridge filter criteria check box is not checked, a logical AND is applied to criteria defined between different filter types. For example, if you define an acceptable range of source addresses and 5 NetBIOS names for a filter name, data frames are forwarded by the LAN Distance bridge that fall within the source address range AND that match at least 1 OR more of the 5 NetBIOS names. ═══ 8.8. Setting Up Filtering Criteria for the LAN and WAN Segments ═══ To begin setting up filtering criteria for either your LAN or WAN segment: 1. Select Settings and select the Bridge tab. 2. Go to Page 2 or Page 3 to set up filtering criteria for your LAN or WAN segment. The window for the LAN Segment page of the Bridge notebook is shown in Bridge Tab, Page 2 of 3. Bridge Tab, Page 2 of 3 Select a push button to perform an action for your filtering criteria. Your changes are saved when you close the Bridge notebook, and activated after you shut down and restart your workstation. Only one set of filtering criteria can be active at a time; however, you can combine different types of filtering criteria, such as SAPs and NetBIOS names, in one set. To activate a set of filtering criteria, select it from the filtering criteria list box for the LAN or WAN segment. Use Filtering Criteria as a guide for setting up your filtering criteria. This table applies to setting up filtering criteria for your LAN and WAN segments. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 16. Filtering Criteria │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ NAME │ FILTER NAME │ Specify a name for this set of filtering cri- │ │ │ │ teria. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ SAPS │ ACCEPT FRAMES │ Specify if and how source SAPs should be used │ │ │ FROM THE SPEC- │ for filtering LAN data. │ │ │ IFIED SAPS │ │ │ │ │ Configure your LAN Distance bridge to accept │ │ │ REJECT ALL │ or reject data frames from the SAPS specified │ │ │ FRAMES FROM │ in CURRENT SAP FILTERS. │ │ │ THE SPECIFIED │ │ │ │ SAPS │ For example, to disallow certain LAN protocols │ │ │ │ from participating in your LAN Distance wide │ │ │ NO SOURCE SAP │ area network, select the REJECT radio button │ │ │ FILTERING │ and specify those SAPs in your LAN segment │ │ │ │ filtering criteria. This prevents frames from │ │ │ │ those SAPs from being transmitted over your │ │ │ │ wide area connections. On the other hand, if │ │ │ │ you want to support only a certain set of LAN │ │ │ │ protocols remotely, select the ACCEPT radio │ │ │ │ button in the filtering criteria for your WAN │ │ │ │ segment and specify the LAN protocols whose │ │ │ │ frames you will accept. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CURRENT SAP │ Specify the names of the source SAPs to use │ │ │ FILTERS │ for filtering. │ │ │ │ │ │ │ │ Use the push buttons to add, change, or delete │ │ │ │ source SAPs for your filtering criteria. │ │ │ │ │ │ │ │ Source SAPs for some common LAN protocols are: │ │ │ │ │ │ │ │ SNA x'04', unless reconfigured │ │ │ │ TCP/IP x'AA' │ │ │ │ NETBIOS x'F0' │ │ │ │ NETWARE** x'E0' │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 16. Filtering Criteria │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ADDRESSES, │ ACCEPT FRAMES │ Specify if and how source LAN Distance logical │ │ PAGE 1 │ FROM THE SPEC- │ adapter network addresses should be used for │ │ │ IFIED SOURCE │ filtering LAN data. │ │ │ ADDRESSES │ │ │ │ │ Configure your LAN Distance bridge to accept │ │ │ REJECT ALL │ or reject data frames from the workstations │ │ │ FRAMES FROM │ with the LAN Distance logical adapter network │ │ │ THE SPECIFIED │ addresses specified in CURRENT ADDRESS │ │ │ SOURCE │ FILTERS. The LAN Distance bridge compares the │ │ │ ADDRESSES │ source address (SA) field of data frames to │ │ │ │ the LAN Distance logical adapter network │ │ │ NO SOURCE │ addresses in your filtering criteria. │ │ │ ADDRESS FIL- │ │ │ │ TERING │ For example, to allow only certain work- │ │ │ │ stations to access your LAN remotely, select │ │ │ │ the ACCEPT radio button in the filtering cri- │ │ │ │ teria for your WAN segment and list the LAN │ │ │ │ Distance logical adapter network addresses of │ │ │ │ the remote workstations. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CURRENT │ Specify the LAN Distance logical adapter │ │ │ ADDRESS │ network addresses of the source workstations │ │ │ FILTERS │ to use for filtering. │ │ │ │ │ │ │ │ Use the push buttons to add, change, or delete │ │ │ │ source workstations for your filtering cri- │ │ │ │ teria. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ADDRESSES, │ ACCEPT FRAMES │ Specify if and how a source LAN Distance │ │ PAGE 2 │ FROM THE │ logical adapter network address range should │ │ │ ADDRESSES │ be used for filtering LAN data. │ │ │ WITHIN THE │ │ │ │ SOURCE ADDRESS │ Configure your LAN Distance bridge to accept │ │ │ RANGE │ or reject data frames from the workstations │ │ │ │ with LAN Distance logical adapter network │ │ │ REJECT ALL │ addresses in the range specified in CURRENT │ │ │ FRAMES FROM │ ADDRESS FILTERS. │ │ │ THE ADDRESSES │ │ │ │ WITHIN THE │ │ │ │ SOURCE ADDRESS │ │ │ │ RANGE │ │ │ │ │ │ │ │ NO SOURCE │ │ │ │ ADDRESS RANGE │ │ │ │ FILTERING │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CURRENT │ Specify the source LAN Distance logical │ │ │ ADDRESS │ adapter network address range to use for fil- │ │ │ FILTERS │ tering. │ │ │ │ │ │ │ │ Use the push buttons to add, change, or delete │ │ │ │ a source address range for your filtering cri- │ │ │ │ teria. Specify the range by its lower and │ │ │ │ upper limits. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 16. Filtering Criteria │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ADDRESSES, │ FORWARD FRAMES │ Specify if and how a destination address bit │ │ PAGE 3 │ TO THE │ mask should be used for filtering LAN data. │ │ │ ADDRESSES │ │ │ │ WHICH MATCH │ Configure your LAN Distance bridge to accept │ │ │ THE BIT MASK │ or reject data frames whose destination │ │ │ │ address (DA) matches a bit mask specified in │ │ │ FILTER OUT ALL │ BIT MASK. Use bit masks to filter data by │ │ │ FRAMES TO THE │ functional addresses, especially those │ │ │ ADDRESSES │ addresses generated by specialized applica- │ │ │ WHICH MATCH │ tions. │ │ │ THE BIT MASK │ │ │ │ │ │ │ │ NO DESTINATION │ │ │ │ ADDRESS BIT │ │ │ │ MASK FILTERING │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ BIT MASK │ Specify a bit mask to use for filtering desti- │ │ │ │ nation addresses. │ │ │ │ │ │ │ │ Use bit masks for functional address fil- │ │ │ │ tering. The destination address (DA) field of │ │ │ │ data frames is compared to your bit mask. A │ │ │ │ match is found if any of the bits set to 1 in │ │ │ │ the bit mask are also set to 1 in your desti- │ │ │ │ nation address field. │ │ │ │ │ │ │ │ Bit masks for some common functional addresses │ │ │ │ are: │ │ │ │ │ │ │ │ NETBIOS x'C00000000080' │ │ │ │ LAN MANAGER* x'C00000002000' │ │ │ │ USER-DEFINED x'C00000080000' through │ │ │ │ x'C00040000000' │ │ │ │ │ │ │ │ Use the push buttons to add, change, or delete │ │ │ │ destination address bit masks for your fil- │ │ │ │ tering criteria. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ NETBIOS │ ACCEPT FRAMES │ Specify if and how NetBIOS names should be │ │ │ WITH THE SPEC- │ used for filtering LAN data. │ │ │ IFIED NETBIOS │ │ │ │ NAMES │ │ │ │ │ │ │ │ FILTER OUT ALL │ │ │ │ FRAMES WITH │ │ │ │ THE SPECIFIED │ │ │ │ NETBIOS NAMES │ │ │ │ │ │ │ │ NO NETBIOS │ │ │ │ NAME FILTERING │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CURRENT NAME │ Specify NetBIOS names to use for filtering. │ │ │ FILTERS │ │ │ │ │ An example of a NetBIOS name is one defined in │ │ │ │ an IBMLAN.INI file. │ │ │ │ │ │ │ │ Use the push buttons to add, change, or delete │ │ │ │ NetBIOS names in your filtering criteria. │ │ │ │ │ │ │ │ Filtering is performed on all NetBIOS names │ │ │ │ that match the name or portion of the NetBIOS │ │ │ │ name that is entered. │ │ │ │ │ │ │ │ To use wild card filtering, place the first │ │ │ │ characters of the NetBIOS name in the entry │ │ │ │ field. All trailing characters are omitted. │ │ │ │ For example, the value AUS, used as a fil- │ │ │ │ tering criteria, selects all names starting │ │ │ │ with AUS. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 8.9. Filtering Strategies for the LAN-to-LAN Environment ═══ Automatic filtering is not supported for the LAN-to-LAN environment shown in LAN-to-LAN Environments. The filtering requirements for your LAN-to-LAN environment depend on the number of workstations that require access to the LAN Distance WAN connection and overall performance requirements. Customize filtering criteria and define the LAN Distance bridge hop count to:  Limit access to the LAN Distance WAN connection to only those LAN workstations that require access.  Improve the performance of the LAN Distance WAN connection by limiting the volume of LAN traffic. In the following examples, filtering strategies are provided for four LAN-to-LAN setups. Select the example that is similar to your setup. As defined for these examples, a small LAN has 1 - 20 workstations, a medium LAN has 20 - 50 workstations, and a large LAN has 50+ workstations. ═══ 8.9.1. Example 1: Small LAN Connecting to Small LAN ═══ Because there are not a large number of workstations on either LAN that require access to the LAN Distance WAN connection, filtering may not be required to limit the volume of LAN traffic. When connecting a small number of workstations, performance requirements--the capacity (speed) of the connection and desired response times--are the primary consideration for defining filtering criteria. ═══ 8.9.2. Example 2: Small LAN Connecting to Medium LAN ═══ If all of the workstations on the medium LAN have access to the resources on the small LAN, the volume of LAN traffic could easily inundate the LAN Distance connection. Define filtering criteria at the LAN Distance Connection Server on the medium LAN. Limit access to the LAN Distance connection to only the workstations on the small LAN that require access to resources on the medium LAN. ═══ 8.9.3. Example 3: Small LAN Connecting to Large Enterprise LAN ═══ A large enterprise LAN typically has multiple LAN segments connected by permanent bridges. To restrict the volume of LAN traffic on the LAN Distance connection, limit the resources on the enterprise LAN that the workstations on the small LAN can access. From the LAN Distance Connection Server on the enterprise LAN, define filtering criteria and use the bridge hop count to limit access only to these resources. ═══ 8.9.4. Example 4: Medium LAN Connecting to a Medium LAN ═══ Connecting LANs with a large number of workstations is only recommended if the number of workstations that require access to the LAN Distance connection can be limited to a small number. Identify the workstations on both LANs that require access to the LAN Distance connection. At each of the LAN Distance Connection Servers, use filtering criteria and the LAN Distance bridge hop count to limit access to only those workstations that require access. ═══ 8.10. Using Bit-Inverted Addresses to Filter Traffic between Token-Ring and Ethernet LAN Segments ═══ Multisegmented LANs can contain both Token-Ring and Ethernet segments. Hardware bridges between Token-Ring and Ethernet LANs use bit-inversion to convert Token-Ring and Ethernet addresses. To filter traffic from a LAN type different than the LAN type on which the LAN Distance Connection Server is installed, specify the bit-inverted address for the LAN resource that you want to filter. For example, if the address for the Ethernet LAN workstation shown in Filtering Traffic from an Ethernet LAN is 123456789ABC, you would specify the bit-inverted address (482C6A1E593D) when defining filter criteria at the LAN Distance Connection Server. To bit-invert LAN addresses, see Using Bit-Inverted Addresses to Filter Traffic between Token-Ring and Ethernet LAN Segments. Filtering Traffic from an Ethernet LAN ═══ 8.10.1. How to Bit-Invert LAN Addresses ═══ The following example lists steps for bit-inverting LAN address 123456789ABC. 1. Separate the 12-character hexadecimal address into six 2-character sets. Example: 12 34 56 78 9A BC 2. Reverse the positions of the characters in each 2-character set. Example: 21 43 65 87 A9 CB 3. Then convert each character using the following table. ┌───────────┬───┬────┬───┬───┬───┬───┬────┬───┬───┬───┬───┬────┬───┬───┬───┬───┐ │ CHARACTER │ 0 │ 1 │ 2 │ 3 │ 4 │ 5 │ 6 │ 7 │ 8 │ 9 │ A │ B │ C │ D │ E │ F │ ├───────────┼───┼────┼───┼───┼───┼───┼────┼───┼───┼───┼───┼────┼───┼───┼───┼───┤ │ Conver- │ 0 │ 8 │ 4 │ C │ 2 │ A │ 6 │ E │ 1 │ 9 │ 5 │ D │ 3 │ B │ 7 │ F │ │ sion │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └───────────┴───┴────┴───┴───┴───┴───┴────┴───┴───┴───┴───┴────┴───┴───┴───┴───┘ Example: 482C6A1E593D ═══ 9. Setting Up Point-to-Point Protocol (PPP) ═══ There are several tasks you must do to configure the connection server to support PPP clients. These tasks include:  Reviewing IP address considerations for PPP clients  Configuring a TCP/IP protocol router. This includes: - Binding the IBM TCP/IP protocol to certain adapters - Setting TCP/IP configuration information.  Updating the \WAL\WCLLOCAL.INI file and adding PPP operating parameters.  Administering IP addresses for PPP connections. You can administer IP addresses in three ways: - Local IP address listing - DHCP server services - Client IP address configuration.  Creating userids for PPP clients. The setup tasks are described in the sections that follow. Information about creating userids for PPP clients is described in Security for PPP Clients. ═══ 9.1. PPP Client IP Address Considerations ═══ The LAN Distance connection server supports two ways of routing frames between the LAN and the WAN for PPP clients:  LAN and WAN are different networks TCP/IP has two interfaces configured, each with an IP address from a different subnet. PPP clients must be assigned an IP address from the same subnet that is assigned to the WAN interface.  LAN and WAN are the same network The TCP/IP proxy ARP feature allows two interfaces to be configured with IP addresses from the same network. For example, the LAN is using a Class B network number of 172.16.x.x, which does not understand subnets. The IP address 172.16.1.26 is assigned to the LAN interface and 172.16.2.8 is assigned to the WAN interface. Using a router subnet mask of 255.255.255.0 causes frames to be routed between the LAN and the WAN. When a PPP client connects and is assigned an IP address of 172.16.2.x, the LAN Distance connection server adds ARP and route entries, as required, for the proxy ARP configuration. The TCP/IP router responds to ARP requests from the LAN to a PPP client with its own hardware address. When the connection server receives a frame that is intended for the PPP client, the TCP/IP router forwards the frame to the correct client based on the ARP and Route table entries. Note: An alternative way to configure the two TCP/IP interfaces is to use two different subnet masks. For example, assume that all workstations on the LAN are using a subnet mask of 255.255.255.0. Use 255.255.255.0 for the LAN interface and 255.255.255.128 for the WAN interface. ═══ 9.2. Configuring a TCP/IP Protocol Router ═══ The LAN Distance connection server bridges all data frames from LAN Distance clients between the LAN and the WAN as described in the previous section. However, for PPP clients, data frames are sent to the TCP/IP stack bound to the LAN Distance logical adapter. Therefore, you must configure TCP/IP as a router between the LAN and the WAN. To configure TCP/IP for routing, you must first bind the IBM TCP/IP protocol to the:  LAN adapter  LAN Distance logical adapter After this is complete, you must set some TCP/IP configuration information for PPP. The steps to complete these tasks are described in the next two sections. Note: When the LAN Distance connection server is configured for transparent bridging and the TCP/IP router is configured, LAN Distance clients will not be able to TCP/IP ping the LAN or WAN TCP/IP interfaces on the connection server. ═══ 9.2.1. Binding the IBM TCP/IP Protocol to the LAN Adapters ═══ The first step in configuring TCP/IP for routing is to bind the IBM TCP/IP protocol to the:  LAN adapter  LAN Distance logical adapter Complete the following steps: 1. To bind the IBM TCP/IP protocol to the adapters, use the Adapters and Protocol Support application. You can start the application in one of three ways:  If LAN Server is installed, open the LAN Services File and Print folder. Double-click the OS/2 LAN Services Installation/Configuration icon. Select the Tailored pushbutton on the Easy or Tailored Installation/Configuration panel. Then select the Install or configure this workstation radio button on the Installation Tasks panel to continue to the Adapter and Protocol Configuration window.  Enter mpts from an OS/2 command prompt.  Open the OS/2 System folder. Open the System Setup folder. Double-click on the MPTS Adapters and Protocols icon. 2. If MPTS was started from an OS/2 command prompt or from the OS/2 System Folder, then when the Configure window is displayed, select the LAN adapters and protocols radio button. Click on the Configure push button. 3. Use the Adapter and Protocol Configuration window to bind the IBM TCP/IP protocol to the adapters. Note: LAN Distance assumes the LAN adapter that is used for routing is the first adapter that is the same LAN type as the connection server (Ethernet or Token Ring) and is configured for TCP/IP. In the Current Configuration list box, highlight the LAN adapter you will use for routing. Highlight the IBM TCP/IP protocol in the Protocols list box. Click on the Add push button directly under the Protocols list box. The window is redisplayed and shows IBM TCP/IP below the LAN adapter you selected. 4. In the Current Configuration list box, highlight the LAN Distance logical adapter. Highlight the IBM TCP/IP protocol in the Protocols list box. Click on the Add push button directly under the Protocols list box. The window is redisplayed and shows IBM TCP/IP below the LAN Distance logical adapter you selected. The following is a Token Ring example of how the Current Configuration list box might look after you bind the TCP/IP protocol to the two adapters. IBM Compatible Token-Ring Network Adapter (IBMTOK.OS2).......... 0 - IBM IEEE 802.2 0 - IBM TCP/IP LAN Distance Logical Adapter.......... 1 - IBM OS/2 NETBIOS 1 - IBM TCP/IP The following is an Ethernet example of how the Current Configuration list box might look after you bind the TCP/IP protocol to the two adapters. LAN Distance Logical Adapter.......... 1 - IBM OS/2 NETBIOS 1 - IBM TCP/IP SMC Ethernet MCA Adapter Family (SMC8000.OS2).......... 0 - [SR_BRIDGE] 0 - IBM TCP/IP [BRIDGEFH].......... 1 - [SR_BRIDGE] 5. Select the appropriate push buttons to close the Adapters and Protocol Support application. 6. The application updates the CONFIG.SYS file. You are asked to select the appropriate drives for the file and the Update CONFIG.SYS check box. 7. Select the appropriate push buttons to close the application. 8. After you close the application, you must set some TCP/IP configuration information. See Setting TCP/IP Configuration Information for PPP. ═══ 9.2.2. Setting TCP/IP Configuration Information for PPP ═══ After you bind the IBM TCP/IP protocol to the adapters, you must set TCP/IP configuration information for PPP. You must configure a LAN interface for the LAN adapter and a LAN interface for the LAN Distance logical adapter. The application you use depends on whether or not you have TCP/IP installed. 1. Follow the procedure that best describes your configuration:  If TCP/IP is not installed, use Multi-Protocol Transport Services (MPTS). You can access MPTS by entering mpts from an OS/2 command prompt or by double-clicking on the MPTS Adapters and Protocols icon in the System Setup folder.  If TCP/IP is installed, use the TCP/IP Configuration application. You can access the application by entering tcpcfg from an OS/2 command prompt or by double-clicking on the TCP/IP Configuration icon in the TCP/IP folder. 2. With either of the above configurations, you must configure an interface for the LAN adapter. Then, configure an interface for the LAN Distance logical adapter. Note: The IP addresses for the two interfaces cannot be assigned by DHCP if the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file is set to DHCP. 3. Next, create a default route. 4. Some networks require dynamic routing. If your network requires dynamic routing, then start ROUTED. TCP/IP must be installed in order to start ROUTED. 5. After you have completed these steps, close the application. 6. You must now shut down your OS/2 system and then restart it. ═══ 9.3. Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File ═══ When the LAN Distance connection server starts, it gets specific operating information from the \WAL\WCLLOCAL.INI file. You need to include operating parameters for point-to-point protocol (PPP) in this file. 1. Edit the \WAL\WCLLOCAL.INI file using an ASCII editor. 2. Update a PPP section to the file as follows. Additional information about the parameters follows the example. [PPP] ObtainIPaddr={LIST, DHCP, USERSPEC} pppSecurity={PAP, CHAP} DDNS={YES, NO} ClientsDomainNm=domain name DHCPMaxWait=seconds Where: ObtainIPaddr = indicates where PPP gets the IP addresses for a PPP session. LIST = Get IP addresses from the \WAL\WCLIPADR.INI file. DHCP = Get IP addresses from a DHCP server that is operating on the LAN. USERSPEC = The client workstation or workstations have configured their own IP addresses. You can use LIST, DHCP, and USERSPEC together. pppSecurity = indicates whether PPP uses PAP security or CHAP security for user authentication. PAP = Use PAP security for user authentication. CHAP = Use CHAP security for user authentication. You can use PAP and CHAP together. DDNS = indicates whether PPP will enable DDNS for PPP sessions. YES = PPP will enable DDNS. NO = PPP will not enable DDNS. You cannot use YES and NO together. ClientsDomainNm = indicates the domain name of the client. DHCPMaxWait = indicates the interval, in seconds, that the LAN Distance connection server waits for a response from any DHCP server. You can specify a value from 2-40 seconds. The following provides more information about the configuration parameters and options. ObtainIPaddr For the ObtainIPaddr parameter, you can use the LIST, DHCP, and USERSPEC options together. PPP tries to use the first option that is specified. If the option does not work, PPP tries to use the next specified option, and so on. If you do not explicitly specify an option, the default option is USERSPEC. The following are some examples showing how you can specify the three options: ObtainIPaddr=LIST ObtainIPaddr=LIST,DHCP,USERSPEC ObtainIPaddr=USERSPEC,DHCP ObtainIPaddr=DHCP pppSecurity For the pppSecurity parameter, you can use the PAP and CHAP options together, in any order. PPP tries to use the first option that is specified. If the option does not work, PPP tries to use the next specified option. If you do not explicitly specify an option, the default option is CHAP. The following are some examples showing how you can specify the two options: pppSecurity=PAP,CHAP pppSecurity=CHAP pppSecurity=CHAP,PAP For more information, see Creating Userids for PPP Clients. DDNS The DDNS parameter indicates whether the LAN Distance userid should be used as the host name that is associated with the IP address. The IP address is obtained from the DHCP server. You can specify either YES or NO, but not both. If you specify YES, the dynamic name server (DNS) is updated when an IP address is obtained. If you do not explicitly specify an option, the default option is NO. The DDNS parameter is only used when an IP address is obtained using DHCP. The following show how you can specify the two options: DDNS=YES DDNS=NO In order to specify YES, the DHCP server must support the fully qualified domain name as an option. The DNS must let someone other than the client update the fully qualified domain name to IP address mapping. LAN Distance uses the following options in the DHCP messages:  Option 81 - Fully qualified domain name option  Option 12 - Host name option  Option 15 - Domain name option ClientsDomainNm This parameter is used only when DDNS=YES. If you do not specify a value, the domain name is obtained from \MPTN\ETC\RESOLV2 on the Warp server. Otherwise, the value you specify is used as the domain name. You can specify the name as follows: ClientsDomainNm=domain-name DHCPMaxWait For the DHCPMaxWait parameter, you can specify a value from 2-40 seconds. If the LAN Distance connection server does not receive a response from the DHCP server in the number of seconds you specify, the connection server does not get an IP address from DHCP for that specific PPP session request. The LAN Distance connection server retries two times. The default timeout value is 3. You can specify the number of seconds as follows: DHCPMaxWait=5 DHCPMaxWait=20 If the ObtainIPaddr parameter specifies DHCP and DHCP is followed by either LIST or USERSPEC, the PPP client connecting to the Lan Distance Connection Server must be able to remain active during the time period that the connection server is waiting for a response from the DHCP server. Since the LAN Distance Connection Server will always retry two times, the client must be able to wait for the number of seconds specified by this parameter times two. Example: If the DHCPMaxWait parameter is set to 3, then the client must be able to wait for a connection response for at least 6 seconds. Some PPP clients will time out in as little as 8 seconds. ═══ 9.4. Administering IP Addresses for PPP Connections ═══ There are three ways you can administer IP addresses for point-to-point protocol (PPP) connections:  Local IP address listing  DHCP server services  Client IP address configuration The administration information is described in the following sections. ═══ 9.4.1. Using the Local IP Address Listing ═══ To administer the IP addresses for point-to-point protocol (PPP) connections, you can use the local IP address listing in the \WAL\WCLIPADR.INI file. The \WAL\WCLIPADR.INI file contains an ASCII text listing of the IP addresses that are reserved for the connection server to use for PPP connections. LAN Distance processes the listing as follows. When there is a request for an IP address, the IP address is assigned for the duration of the PPP connection. The IP address cannot be reused until the PPP connection ends. The \WAL\WCLIPADR.INI file is used for administering IP addresses if the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file specifies LIST. The ObtainIPaddr parameter allows the LIST option to be specified with the DHCP and USERSPEC options. PPP tries to use the first option that is specified. If the option does not work, PPP tries to use the second option, and so on. For more information about the ObtainIPaddr parameter, see Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File. To use the local IP address listing, do the following: 1. Edit or create the \WAL\WCLIPADR.INI file using an ASCII editor. 2. Add the following information to the file using the specified format: [IPADDRESSES] x.x.x.x y.y.y.y-z.z.z.z Where: x.x.x.x represents a single IP address that can be assigned for a PPP connection. y.y.y.y-z.z.z.z represents a range of IP addresses that can be assigned for a PPP connection. ═══ 9.4.2. Using DHCP Server Services ═══ You can use DHCP server services to administer the IP addresses for point-to-point protocol (PPP) connections. Using DHCP lets the LAN Distance connection server submit requests on behalf of a PPP client to a DHCP server. Client-generated DHCP requests over the PPP connection are not supported; only LAN Distance connection server requests are supported. LAN Distance obtains an IP address from a DHCP server and passes the address to the PPP client. LAN Distance maintains the lease for the IP address on behalf of the client. Note: If the LAN Distance connection server fails to renew the lease for an IP address, the client can no longer use the IP address. When the lease expires, the ARP table entries associated with the client's IP address are deleted from the connection server. Once the ARP table entries are deleted, the client can no longer use TCP/IP. The client does not receive notification that the IP address can no longer be used. The client must disconnect from the LAN Distance connection server and then reconnect in order to obtain a new IP address. A message is written to the LAN Distance connection server message log when this scenario occurs. Setting up DHCP services requires a good working knowledge of network management. If you do not feel comfortable using this option, see Using the Local IP Address Listing for an easier way to administer IP addresses. DHCP server services are used for administering IP addresses if the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file specifies DHCP. The ObtainIPaddr parameter allows the DHCP option to be specified with the LIST and USERSPEC options. PPP tries to use the first option that is specified. If the option does not work, PPP tries to use the second option, and so on. For more information about the ObtainIPaddr parameter, see Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File. ═══ 9.4.3. Using the Client IP Address Configuration ═══ A third method of administering IP addresses is to assign a unique IP address to each PPP client. This address is used with a PPP client dialer application. To use this method, each user must configure a unique IP address at the PPP client workstation. The client IP address configuration is used for administering IP addresses if the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file specifies USERSPEC. The ObtainIPaddr parameter allows the USERSPEC option to be specified with the LIST and DHCP options. PPP tries to use the first option that is specified. If the option does not work, PPP tries to use the second option, and so on. For more information about the ObtainIPaddr parameter, see Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File. Note: This method of administering IP addresses can be a difficult method to control. You could have problems whenever changes to the network are required or if users use duplicate IP addresses. ═══ 10. Setting Up LAN Distance Security ═══ Adding remote access capabilities to your LAN can make your LAN and its resources vulnerable to unauthorized remote access. The security features provided by the LAN Distance product control access to the LAN Distance Connection Server and help prevent LAN access by unauthorized users. This chapter describes LAN Distance security features, covers planning considerations, and provides steps for enabling security, logging on to a secure LAN Distance Connection Server, setting up user accounts, defining a security policy, and changing your passphrase.  All of the security features described in this chapter are optional and are supported for the LAN Distance Connection Server and the OS/2 LAN Distance Remote product. Because controlling access to LAN resources is so important, this chapter focuses on setting up security at a LAN Distance Connection Server.  The security features for PPP clients are described in Security for PPP Clients.  The security features supported for the MS Windows LAN Distance Remote are described in Security for MS Windows LAN Distance Remote Workstations. See Security Database Tools for additional tools that can be used for security administration on a LAN Distance Connection Server. ═══ 10.1. Understanding Required and Optional Security Features ═══ LAN Distance security supports a range of security features that allows you to set up as much, or as little, security as your environment requires. This section focuses on the LAN Distance security features required for each user account that you set up. Optional security features are not required for user accounts. See Setting Up Optional Features for a User Account for more information. ═══ 10.1.1. User IDs and Passphrases ═══ When a LAN Distance remote workstation dials a secure LAN Distance Connection Server, they are prompted for a user ID and passphrase. When a PPP client dials a secure LAN Distance connection server, the client must provide a user ID and passphrase as part of their dialer configuration. As the security administrator, you define a user ID for each authorized user; passphrases are optional. The user ID and passphrase the user specifies when logging on must match the user ID and passphrase you defined for that user account at your secure LAN Distance Connection Server. LAN Distance Remote Logon Window Note: A PPP client user cannot change the passphrase remotely. For more information about security features that you cannot use for PPP clients, see Security for PPP Clients. You can also require users to logon with a passphrase. Either the user or the security administrator can change the passphrase. If the user changes the passphrase and then forgets it, you cannot look up the passphrase. A user with security administrator privilege must specify a new passphrase for the forgetful user before they can log on. Warning: If you forget the passphrase for your personal security administrator account, you cannot log on to your secure LAN Distance Connection Server and access the user account database. If only one security administrator account is defined at this LAN Distance Connection Server, access to the user account database cannot be recovered. ═══ 10.1.2. User Privilege Types ═══ As the security administrator, you assign a user type for each user authorized to access your secure LAN Distance Connection Server. The tasks each user is allowed to perform will vary based on:  The user type you assign: user, system administrator, or security administrator.  The type of secure LAN Distance workstation the user logs on to.  Whether the user is logging on to a local or nonlocal workstation.  Whether the user is logged on from a PPP client. The following topics show the menu items different user types can access from the Open as pull-down menu when logging on to a secure LAN Distance Connection Server. In the following examples, the user and system administrator are logging on from a nonlocal workstation, and the security administrator is logging on at a local workstation. Note: In the following sections, the workstations in the examples are LAN Distance workstations, not PPP clients. ═══ 10.1.2.1. User ═══ When a user logs on to a nonlocal LAN Distance Connection Server, the menu items shown in User Logged on to a Secure LAN Distance Connection Server are displayed in the Open as pull-down menu. Users can:  View call activity for ports and view the modems currently in use at the LAN Distance Connection Server through call and port management.  View users logged on to the LAN Distance Connection Server.  Access their personal account information at the LAN Distance Connection Server and change their passphrases. User Logged on to a Secure LAN Distance Connection Server ═══ 10.1.2.2. System Administrator ═══ When a system administrator logs on to a nonlocal LAN Distance Connection Server, the menu items shown in System Administrator Logged on to a Secure LAN Distance Connection Server are displayed in the Open as pull-down menu. In addition to the user tasks listed above, a system administrator can:  Start and stop active calls for ports and modem types at the LAN Distance Connection Server through call and port management.  View and change configuration settings for the LAN Distance Connection Server through the Settings notebook.  Access the Tracking notebook tools to view statistics for system management and view error information for problem determination. Note: The system administrator cannot enable or disable security through the Settings notebook, and cannot access user accounts in the User Account Management notebook. System Administrator Logged on to a Secure LAN Distance Connection Server ═══ 10.1.2.3. Security Administrator ═══ When a security administrator logs on locally to a secure LAN Distance Connection Server, the menu items shown in Security Administrator Logged on to a Secure LAN Distance Connection Server are displayed in the Open as pull-down menu. In addition to the tasks that users and system administrators can perform, a security administrator can:  Select a phone book entry in the phone book to dial out and establish a connection. If the security administrator logs on to the LAN Distance Connection Server from a nonlocal workstation, the LAN Distance Connection Server phone book cannot be accessed.  Add and change user account information through the User Account Management notebook.  Enable and disable security for the LAN Distance Connection Server from the Security tab in the Settings notebook.  View any errors or messages logged for the LAN Distance Connection Server. If the security administrator logs on to the LAN Distance Connection Server from a nonlocal workstation, the security administrator does not have access to error and message logs at the LAN Distance Connection Server. Security Administrator Logged on to a Secure LAN Distance Connection Server ═══ 10.2. Planning Considerations for LAN Distance Security ═══ Review the planning considerations covered in this section before setting up security on a LAN Distance Connection Server or LAN Distance Remote. ═══ 10.2.1. Implementing Local Security on a LAN Distance Remote ═══ The primary purpose of LAN Distance security is to prevent unauthorized access to resources on your LAN. If a LAN Distance Remote in your environment is used as a stand-alone application or database server, you can set up local security to control access to resources at the LAN Distance Remote. The security features for the LAN Distance Remote are the same as those available on the LAN Distance Connection Server, and the steps for setting up security on the LAN Distance Remote are identical to those for the LAN Distance Connection Server. See Steps for Setting Up Security on a LAN Distance Workstation. ═══ 10.2.2. Security for MS Windows LAN Distance Remote Workstations ═══ Local security for a LAN Distance Remote is supported only for OS/2 LAN Distance Remotes. Security administrators can set up user IDs and passphrases at the LAN Distance Connection Server to validate access from a MS Windows LAN Distance Remote. MS Windows LAN Distance Remotes, like OS/2 LAN Distance Remotes, can dial into a secure LAN Distance Connection Server, access their personal account information and change their passphrases. ═══ 10.2.3. Creating User Accounts ═══ As the security administrator, you create user accounts for every user authorized to remotely access a secure LAN Distance Connection Server. User accounts contain required security features (user IDs and user types), plus any optional security features. The security administrator creates user accounts through the User Account Management notebook:  User accounts are stored in the user account database file (WCBUSRF.ISF) in the WAL directory.  Only users with a security administrator account can access the User Account Management notebook.  To control access to the User Account Management notebook a limited number of trusted security administrators should have a user account at a secure LAN Distance Connection Server.  After you create user accounts at the LAN Distance Connection Server, you can set up identical user accounts on another secure LAN Distance workstation simply by copying the WCBUSRF.ISF file to the WAL directory on that workstation.  Users logged on to a secure LAN Distance Connection Server can view general information about their user account and change their passphrase through the Personal Account Information notebook.  For information about security features that are not available for PPP clients, see Security for PPP Clients. ═══ 10.2.4. Protecting LAN Distance Passphrases ═══ In the LAN Distance user account database, passwords are saved in two forms:  One-way encrypted form, which is only used for LAN Distance clients  Data encryption standard (DES) form, which is only used for PPP clients. LAN Distance passphrases are one-way encrypted to form a password key. The password key is stored in its encrypted form in the user account database at the secure LAN Distance Connection Server. As added protection, the password key is encrypted with a secret session key before it is transmitted. To support PPP clients, the LAN Distance user account database also saves the passphrase using DES encryption. LAN Distance security adds another layer of security that supplements security provided by other systems on the LAN. Anyone monitoring your LAN Distance WAN connection cannot see the encrypted LAN Distance passphrase, but they can see passwords you use to log on to other systems that do not encrypt passwords. Passphrases should be unique across all of the secure systems that you log on to. For example, if you need to log on to other systems, such as a LAN Server or a 3270 host, make certain that the passphrase used to log on to the LAN Distance Connection Server and the passwords used for the LAN Server and the 3270 host sessions are different. You can set a minimum passphrase length to help make the LAN Distance passphrase unique. (See Description of Policy Options.) ═══ 10.2.5. Avoiding Multiple LAN Distance Logons ═══ When security is enabled at a LAN Distance Remote and at the LAN Distance Connection Server, the user at the LAN Distance Remote can avoid multiple logons if the same LAN Distance user ID and passphrase are defined at the secure LAN Distance workstations. For example, after the user logs on to their secure LAN Distance Remote and establishes a connection to the secure LAN Distance Connection Server, the user ID and passphrase used to log on to the LAN Distance Remote is used to automatically log on the user at the LAN Distance Connection Server. Note: Any additional logons required by secure systems on the LAN occur after the user establishes a connection to the LAN Distance Connection Server. ═══ 10.2.6. Physical Security for LAN Distance Workstations ═══ LAN Distance security can be effective only if your LAN Distance workstation is physically secure. When you enable security at a LAN Distance Connection Server or LAN Distance Remote user account information, such as user IDs and password keys (encrypted passphrase), is stored in the WCBUSRF.ISF file. To ensure that unauthorized users cannot access this file, physically secure your secure LAN Distance Connection Server and restrict access to a limited number trusted security administrators. ═══ 10.2.7. Encrypting LAN Data Sent over the LAN Distance Connection ═══ LAN Distance does not encrypt LAN data sent over the LAN Distance WAN connection. To encrypt LAN data sent over the LAN Distance connection, purchase special data encryption devices and employ them at both ends of the LAN Distance connection. ═══ 10.2.8. Using the LAN Distance Bridge Filtering Criteria to Restrict Access ═══ In addition to LAN Distance security, you can use custom filtering criteria to help prevent unauthorized access to LAN resources. For example, to restrict LAN access to a limited set of LAN Distance logical adapter network addresses, define these addresses through the Bridge tab in the Settings notebook. For steps, see Customizing Filtering Criteria. You can also use other custom filtering criteria--SAPs and NetBIOS names--to restrict access to LAN resources. ═══ 10.3. Security for PPP Clients ═══ The LAN Distance connection server supports password authentication protocol (PAP) and challenge-handshake authentication protocol (CHAP) that PPP clients can use. For information about specifying the PAP and CHAP options, see Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File. For PPP clients, you must create userids using this version of LAN Distance. For information about creating userids, see Creating Userids for PPP Clients. The following features are not supported for PPP clients:  PPP clients cannot perform security administration functions  PPP clients cannot change their own passphrases  The logical adapter network address and callback security features for user accounts are not supported for PPP clients  The maximum age and maximum logon attempts policy options are not enforced for PPP clients. ═══ 10.3.1. Creating Userids for PPP Clients ═══ If security is enabled on the connection server, you must create userids for any PPP clients. For previous versions of LAN Distance, the security database saves passwords in a one-way encrypted form. Because of this, the passwords for existing userids cannot be used to support password authentication protocol (PAP) or challenge-handshake authentication protocol (CHAP), which the connection server uses for passphrase authentication. For all current userids, you must either change the passphrase or create a new user account and passphrase. You can do this using the LAN Distance User Account Manager notebook or offline using the CMPRINT and CMMERGE tools. The database that this version of LAN Distance updates is compatible with the old servers. The passphrase considerations are:  The LAN Distance passphrases are case sensitive. If the PPP client does not support case sensitivity, define the initial passphrase in all uppercase.  The LAN Distance passphrase can be up to 32 characters. If the PPP client does not support long passphrases, create the initial passphrase using the limitations of the client. ═══ 10.4. Steps for Setting Up Security on a LAN Distance Workstation ═══ Follow these general steps to set up LAN Distance security at a LAN Distance Connection Server or OS/2 LAN Distance Remote. Each step is described in detail in sections that follow. 1. Enable security at the LAN Distance workstation. 2. Log on to your LAN Distance workstation using the default user account for the security administrator. 3. Set up a user account that contains required information (user ID and user type) for each user that needs to log on to your secure LAN Distance workstation. 4. Define any optional security features for user accounts. 5. Define security policy options for passphrases and user IDs that apply to all user accounts. ═══ 10.5. Enabling LAN Distance Security ═══ LAN Distance security must be enabled on a LAN Distance Connection Server or LAN Distance Remote before you can set up user accounts. Settings Notebook, Security Tab To enable Lan Distance security, 1. Select Settings from the Open as pull down menu. 2. From the Settings notebook select the Security tab. 3. From the Security tab page, (see Settings Notebook, Security Tab) select the Enable LAN Distance security checkbox. If the Enable LAN Distance security checkbox is not checked, LAN Distance security is disabled. 4. To activate security on your LAN Distance workstation, close the Settings notebook. Then stop and restart the LAN Distance product. ═══ 10.6. Enabling Third Party Authentication Protocol ═══ Third party authentication is used for remote dial-in only. The fields related to this checkbox are grayed out if LAN Distance security is disabled. To enable third party authentication, you must first enable LAN Distance security. 1. Select the Enable Third party authentication protocol checkbox to turn on third party authentication for the LAN Distance connection server only. 2. In the User exit name field, type the user exit DLL name. The maximum length for this field is 8 characters. Do not enter the DLL extension. 3. Select Disable remote LAN Distance authentication if you want to use only the third party authentication. Not selecting this checkbox allows you to use both the LAN Distance and the third party authentication. ═══ 10.7. Enabling Share Security Database ═══ To use a security database on a redirected LNA drive: 1. Select the Enable share security database checkbox. 2. Type the drive and path of the database in Location. The shared security database information, the user exit name, and remote authentication options are added automatically to the WCLLOCAL.INI file. Note: After security is enabled on your workstation, security at the local workstation must be disabled by a security administrator. ═══ 10.8. Logging On Initially to Your Secure LAN Distance Workstation ═══ After restarting the LAN Distance product, log on to your secure LAN Distance workstation using the default user account for the security administrator. 1. Select the icon for your secure LAN Distance workstation. From the Open as pull-down menu, select Logon. 2. From the LAN Distance Logon window (LAN Distance Logon Window), type the default userid (in upper- or lowercase) and the default password. Then select the OK button. If you installed Remote Access Services (PPP Server) while installing OS/2 Warp Server for e-business or if you installed Remote Access Services (PPP Server) from 'Selective Install for Networking' on the OS/2 Warp Server for e-business, the default security administrator userid and passphrase is the same as the userid and passphrase that you entered during installation. If you installed Remote Access Services (PPP Server) directly from the CID\SERVER\PPPSRV directory on the OS/2 Warp Server for e-business CD, the default security administrator userid is SECADMIN and its passphrase is SECADMIN (all in uppercase). PPP Server passphrases are case sensitive. The passphrase entered during installation will be in uppercase. Be sure to type the passphrase in uppercase the first time you logon to the PPP Server. LAN Distance Logon Window 3. From the pop-up message window, select the OK push button. 4. From the Change Passphrase window (Change Passphrase Window), type a new passphrase in the New Passphrase field. Note: Passphrases are case-sensitive. The default minimum length for passphrases is 8 characters. Type your new passphrase again in the Verify Passphrase field. Change Passphrase Window If you specify a valid passphrase, you are logged on as a security administrator. If you specify an invalid passphrase, the log on attempt will fail and you will be prompted to log on again. Warning: If you exceed the default maximum number of four unsuccessful logon attempts, you must refresh your security database file. You can use one of the following methods:  Remove LAN Distance from your system and then reinstall it. Enable security before you log on again.  Get the default security database file from the first Remote Access Services (PPP Server) diskette or diskette directory. Note: On the OS/2 Warp Server for e-business CD, the contents of the first diskette are located in \CID\SERVER\PPPSRV\LO510A1. Use PKUNZIP2.EXE to unzip the INITRS.ZIP file into a temporary directory. Copy the WCBUSRF.ISF into the WAL directory on your server. The default security ID is now SECADMIN and the passphrase is SECADMIN (all in uppercase). ═══ 10.9. Setting Up Required Features for a User Account ═══ As the security administrator for your secure LAN Distance workstation, you must add a user account for every user authorized to access your workstation remotely. Use the User Account Management notebook to set up these required security features for user accounts:  User ID  User Type ═══ 10.9.1. Adding a User ID and User Type ═══ 1. After you log on to the secure LAN Distance workstation as a security administrator, select User Account Management from the Open as pull-down menu. 2. From the User Account Management notebook (User Account Management Notebook), select the Add push button. User Account Management Notebook 3. From the Type tab (Type Tab, User Account Management Notebook), specify required information for the new user. Type Tab, User Account Management Notebook  In the User ID field, specify a user ID.  In the User type field, select a user type. For information about user types, see User Privilege Types.  In the Account status field, select the Active push button. Activating the user account allows the user to log on to your secure LAN Distance workstation. Deactivating a user account prevents the user from logging to the secure LAN Distance workstation and saves the information in the user's account. A user account is deactivated if the user exceeds the maximum number of unsuccessful logon attempts. ═══ 10.10. Setting Up Optional Features for a User Account ═══ Use the User Account Management notebook to set up these optional security features for user accounts:  Passphrases  Logon Time Intervals  Logical Adapter Network Addresses  Callback ═══ 10.10.1. Defining a Passphrase for a User Account ═══ As the security administrator, you can require a user to supply a passphrase when logging on to a secure LAN Distance workstation. Passphrases are described in User IDs and Passphrases, and considerations for using passphrases are described in Protecting LAN Distance Passphrases. From the Passphrase tab, the security administrator can:  Specify whether a passphrase is required to log on to a secure LAN Distance workstation  Define a passphrase for a user account.  Change a passphrase for a user account. To specify a passphrase for a user account: 1. From the User Account Management notebook, select the Passphrase tab (Passphrase Tab, User Account Management Notebook). 2. Select the Passphrase required check box. Passphrase Tab, User Account Management Notebook 3. Type the passphrase in the Passphrase field and the Passphrase for verification field. Note: Passphrases are case-sensitive. 4. To verify that the passphrase you specified is valid, select the Verify passphrase push button. ═══ 10.10.2. Defining Logon Time Intervals for a User Account ═══ A LAN Distance security administrator can specify the days of the week and the time of day that a user can log on to the LAN Distance Connection Server. If a user attempts to log on at a time that is not within the defined interval, the log on will fail. From the Interval tab, the security administrator can add, change, or delete a log on time interval for a user account: 1. From the User Account Management notebook, select the Interval tab (Interval Tab, User Account Management Notebook). The default logon time interval is from Sunday to Saturday and from 00:00 to 24:00, allowing the user to log on at any time. 2. To restrict the days or hours that a user is allowed to log on to the secure LAN Distance workstation, select the Change push button. Interval Tab, User Account Management Notebook 3. From the Change Logon Time Interval window (Change Logon Time Interval Window), select the days and the times when the user is allowed to log on. Select the OK push button. Change Logon Time Interval Window You can specify multiple log on intervals. If log on intervals overlap, the earliest time is used as the starting point and the latest time is used as the stopping point. Note: Changes made to the log on time interval are saved when you close the User Account Management notebook. ═══ 10.10.3. Defining Valid Logon Addresses for a User ═══ A security administrator can specify up to 8 LAN Distance logical adapter network addresses for a user account. Logon will fail if the user logs on from a LAN Distance workstation with a LAN Distance logical adapter network address not in the list. This feature allows the user to log on to the LAN Distance Connection Server from more than one workstation. For example, a user might log on from a portable workstation when traveling and from a home terminal when working at home. Note: This feature is not available for use with PPP clients. 1. From the User Account Management notebook, select the Addresses tab (Addresses Tab, User Account Management Notebook). Addresses Tab, User Account Management Notebook 2. Specify the LAN Distance logical adapter network addresses for the LAN Distance workstations the user can log on from. If no LAN Distance logical adapter network addresses are listed, the user can log on to the secure LAN Distance workstation from any LAN Distance workstation. ═══ 10.10.4. Setting Up Callback for a LAN Distance Remote ═══ For LAN Distance Remotes, the security administrator can set up the callback feature. Callback provides additional security and allows long distance costs to be charged to the LAN Distance Connection Server. Note: Callback is not available for use with PPP clients. If callback is enabled for a user account, the user is prompted to log on after dialing the LAN Distance Connection Server. The LAN Distance Connection Server then disconnects the call and calls the user back using a fixed or variable phone book entry. After a connection is established, the user is authenticated and automatically logged on to the LAN Distance Connection Server. To enable callback for a user account: 1. From the User Account Management notebook, select the Callback tab (Callback Tab, User Account Management Notebook). Callback Tab, User Account Management Notebook 2. Select the Callback check box. 3. Select the Fixed or Variable radio button to specify whether the callback telephone number for this user does not change (fixed) or does change (variable). 4. Type the name of the phone book entry that the secure LAN Distance workstation will use to call this user back. ═══ 10.11. Defining Policy Options for Your User Accounts ═══ The security administrator can define a security policy that applies to all user accounts. For example, the security administrator may want to define a policy for LAN Distance passphrases that is similar to other security systems on the LAN. ═══ 10.11.1. Description of Policy Options ═══ The security administrator can define a security policy using any of the following options. Minimum Passphrase Length A passphrase can contain 4 to 32 mixed-case characters (including blanks). This flexible format makes passphrases easier to define and offers improved security. The default is 8 characters. To ensure the LAN Distance passphrase is unique, the security administrator can set the minimum length greater than the maximum length defined for other systems on the LAN. Duplicate Passphrases Checked The security administrator can define the number of unique passphrase (0 to 8) that must be used before a passphrase can be reused. The default is 8 passphrases. If 0 is selected, no duplicate check is performed. Maximum Passphrase Age The security administrator can define the age limit (1 to 999 days) for a passphrase. Users must change their passphrases on or before the day this age limit is reached. The default is 30 days. Minimum Passphrase Age The security administrator can define the minimum number of days (0 to 999) that can pass before users can change their passphrases. The default is 0. If 0 is selected, users can change their passphrase at any time. Maximum Number of Logon Attempts for a User ID The security administrator can define the number of unsuccessful logon attempts (1 to 9) allowed. The default is 4, which means if a user fails to log on after 4 tries, their user account is deactivated. Only a security administrator can reactivate a deactive account. Note: Automatic logons are counted as a log on attempt. Set this value to a minimum value of 2 so an unsuccessful automatic logon does not prevent a user from accessing a secure LAN Distance workstation. For information about the policy options as they apply to PPP clients, see Security for PPP Clients. ═══ 10.11.2. Steps for Defining Policy Options ═══ Follow these steps to define a policy option for all user accounts in the User Account Management notebook for your secure LAN Distance workstation: 1. From the User Account Management notebook, select the Policy tab. The options you can define and their default values are described in Defining Policy Options for Your User Accounts. Policy Tab, User Account Management Notebook 2. Specify the values for the options you want to define. 3. Policy option changes effective when you close the User Account Management notebook, stop and restart the LAN Distance product. ═══ 10.12. Changing Your Passphrase ═══ Users logged on to a secure LAN Distance Connection Server can view general information about their user accounts, and change their passphrases through the Personal Account Information notebook. To change the passphrase for your user account: 1. Select the icon for the secure LAN Distance workstation from the LAN Distance Workstations window. 2. From the Open as pull-down menu, select the Personal Account Information menu item. From the General tab, you can view information about your user account and change the description for your user account in the User comment field. 3. Select the Passphrase tab (Passphrase Tab, Personal Account Information Notebook). Type your current passphrase in the Current passphrase field. Passphrase Tab, Personal Account Information Notebook 4. Type your new passphrase in the New passphrase field and the New passphrase for verification field. Note: Passphrases are case-sensitive. 5. To verify that the passphrase you specified is valid, select the Verify passphrase push button. ═══ 11. Setting Up to Run LAN Applications Remotely ═══ This chapter explains the protocol support provided by the LAN Distance product, describes how to set up LAN protocols in addition to NetBIOS, tells you how to verify or change a LAN Distance logical adapter network address, and provides guidelines for adjusting NetBIOS timers on LAN Distance workstations and LAN workstations. ═══ 11.1. Tips for Setting Up LAN Applications ═══  Before setting up your LAN applications to run over a LAN Distance connection, make sure that your LAN applications are functioning correctly in the LAN environment.  Install the LAN Distance Remote product after you install the LAN applications that you want to run over the LAN Distance connection.  You may need to modify the configuration for your LAN applications to run these applications over the slower LAN Distance WAN connection. Before installing your LAN applications on the LAN Distance Remotes, see Setting Up Some Popular LAN Applications. ═══ 11.2. Understanding the Protocol Support Provided by the LAN Distance Product ═══ LAN applications use many different protocols including NetBIOS in the OS/2 LAN Server environment, IPX/SPX in the NetWare environment, and NetBIOS for Microsoft LAN Manager. The LAN Distance product supports multiple protocols through the industry-standard Network Driver Interface Specification (NDIS). product utilizes the network driver architecture provided by NDIS to allow you to set up NDIS-compliant protocols to run over the LAN Distance Logical Adapter. LAN Distance Product Components ═══ 11.2.1. Examples of Supported LAN Protocols and Applications ═══ Over a LAN Distance connection, LAN Distance Remotes can run LAN applications and networking software that use NDIS-compliant protocols. protocols supported by the LAN Distance product and lists some popular LAN applications, communications software, and network operating systems that use these protocols. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 17. Supported LAN Protocols and Examples of LAN Applications │ ├────────────┬─────────────────────────────────────────────────────────────────┤ │ SUPPORTED │ LAN APPLICATIONS │ │ PROTOCOLS │ │ ├────────────┼────────────────────────────────┬────────────────────────────────┤ │ NETBIOS │ OS/2 LAN Server │ Microsoft LAN Manager │ │ │ OS/2 LAN Requester │ (NetBEUI) │ │ │ Person to Person/2 │ DOS LAN Requester │ │ │ LAN Peer Services │ Lotus Notes │ │ │ LANtastic │ cc:Mail** │ │ │ OS/2 Extended Services* │ Time and Place/2 │ │ │ (Database Manager) │ System Performance Monitor/2 │ │ │ DATABASE 2 for OS/2* │ │ │ │ │ │ │ │ │ │ ├────────────┼────────────────────────────────┼────────────────────────────────┤ │ IEEE 802.2 │ OS/2 Extended Services* │ DATABASE 2 for OS/2 │ │ SNA(1) │ (Communication Manager) │ Personal Communications/3270 │ │ │ Communications Manager/2 │ Personal Communications/5250 │ │ │ AS/400* PC Support │ IBM System Network Architecture│ │ │ │ (SNA) for OS/2 │ │ │ │ │ │ │ │ │ ├────────────┼────────────────────────────────┼────────────────────────────────┤ │ TCP/IP │ TCP/IP for OS/2 │ LAN NetView* for OS/2 │ │ │ TCP/IP for MS Windows │ │ │ │ │ │ │ │ │ │ ├────────────┼────────────────────────────────┼────────────────────────────────┤ │ IPX │ Novell NetWare Server │ Novell NetWare Requester │ │ │ │ │ │ │ │ │ ├────────────┴────────────────────────────────┴────────────────────────────────┤ │ NOTE: (1)The LAN Distance product supports remote access for SNA applica- │ │ tions, such as IBM Communications Manager/2 3270 Emulation and Personal │ │ Communications/3270, which run over 802.2. See set up steps for 802.2 │ │ applications in Setting Up Some Popular LAN Applications. │ └──────────────────────────────────────────────────────────────────────────────┘ ═══ 11.2.2. Protocol Support Provided for OS/2 and MS Windows LAN Distance Remotes ═══ NetBIOS is installed and configured for OS/2 and MS Windows LAN Distance Remotes. If the LAN applications that you want to run over the LAN Distance connection use the NetBIOS protocol, no additional protocol set up is required to run these applications remotely. ═══ 11.2.2.1. OS/2 LAN Distance Remotes ═══ For OS/2 LAN Distance Remotes, in addition to NetBIOS, the IEEE 802.2 protocol is installed when the LAN Distance Remote product is installed, but it is not configured. If you need the 802.2 protocol to run your LAN applications, configure the 802.2 protocol through the LAPS tab in the Settings notebook. See Configuring Additional LAN Protocols Required for Your OS/2 LAN Applications. If you need protocols in addition to NetBIOS and IEEE 802.2, after you separately install these protocols, you can configure these protocols to run over the LAN Distance Logical Adapter through the LAPS tab in the Settings notebook. ═══ 11.2.2.2. MS Windows LAN Distance Remotes ═══ The LAN Distance Remote for MS Windows installs NetBIOS and NetWare Requester support (ODI2NDI), but does not install the IEEE 802.2 LAN protocol. If you need 802.2 to run your MS Windows applications, install the LAN Support Program (LSP) before you install the LAN Distance product. See Setting Up a MS Windows Remote to Run 802.2 Applications. If you need to run MS Windows applications that require other protocols, these protocols are typically installed with the application, and require special configuration to work with the LAN Distance product. See Setting Up Some Popular LAN Applications. ═══ 11.3. Configuring Additional LAN Protocols Required for Your OS/2 LAN Applications ═══ If your OS/2 applications require NDIS-compliant protocols other than NetBIOS, first install the required protocols, then follow these steps in this section to configure the protocols through the LAPS tab in the Settings notebook. Note: Set up your LAN protocols at the workstation on which you run your LAN applications. For example, if your LAN Distance Remote runs the 3270 emulation feature of IBM Communications Manager/2 to access a host on a LAN, configure the IEEE 802.2 LAN protocol at your LAN Distance Remote. IEEE 802.2 does not need to be configured on the LAN Distance Connection Server that you dial for access to the LAN. 1. Open the Settings notebook and select the LAPS tab, then select the LAPS push button to open the LAPS Configure Workstation window. LAPS Configure Workstation Window 2. From the Current Configuration list box, select the LAN Distance Logical Adapter. 3. From the Protocols list box, select the LAN protocol used by your LAN application(s). 4. Select Add from the Protocols list box to add the protocol you selected to the protocols currently configured for the LAN Distance Logical Adapter. 5. Repeat steps 3 and 4 for each additional protocol you need to configure for the LAN Distance Logical Adapter. 6. Select OK to exit the Configure Workstation window and return to the LAPS tab in the Settings notebook. 7. From the LAPS tab, double-click on the system menu symbol in the upper left corner to close the Settings notebook and save protocol changes. 8. Shut down and restart your OS/2 workstation. ═══ 11.4. Setting Up a MS Windows Remote to Run 802.2 Applications ═══ If you plan to run MS Windows applications that require the 802.2 protocol, you can use the LAN Support Program (LSP) version 1.35 and later to install and configure the NDIS-compliant version of 802.2. ═══ 11.4.1. Determine the Appropriate Method for Installing LSP ═══ The easiest method is to install LSP before you install the LAN Distance Remote product. See Installing LSP Before You Install the LAN Distance Product. You can also install LSP after you install the LAN Distance product. Use this method (described in Installing LSP After the LAN Distance Remote Is Installed) only if the LAN Distance product is already installed and at least one of the following statements apply:  Your workstation does not have a LAN adapter and you have no adapter option diskette available. Note: Some versions of LSP may include an adapter option on the LSP diskette in the A:\DOS directory.  You cannot remove the LAN Distance Remote product before installing LSP.  You installed LSP without NDIS 802.2 support. ═══ 11.5. Installing LSP Before You Install the LAN Distance Product ═══ Follow these steps (based on LSP version 1.35) to install LSP before you install the LAN Distance Remote product: Note: If you want to use the LSP installation method described here, but the LAN Distance Remote product is already installed, use the LDREMOVE command to remove the LAN Distance Remote product. 1. Insert the LSP diskette in the diskette drive, type A:DXMAID, and press Enter to start the LSP installation program. 2. Press Enter at the IBM Logo panel and information panels to get to the Environment Information panel. 3. From the Environment Information panel, specify the following options for your workstation: Configuration for this computer? Yes Use existing configuration information? Yes Do you have adapter option diskettes? Yes Are you configuring for 2 adapters? No Do you need 802.2 interface support? Yes Press Enter. 4. When the Process Adapter Option Diskette panel is displayed, insert the adapter option diskette in the diskette drive, specify the path that contains the DOS NDIS files (for example, A:\DOS) and press Enter. An information panel is displayed when the software driver configuration is complete. 5. Remove the adapter option diskette from the diskette drive, insert the LSP diskette, and press Enter to continue LSP installation. 6. From the Selections for Adapter Window, select the appropriate adapter for your workstation so it is displayed in the Primary Adapter Window. If your workstation does not have a LAN adapter, select: IBM Token-Ring Network Adapters with NDIS support (IBMTOK.DOS). Note: If you do not have a LAN adapter, record your adapter selection to use when you edit the CONFIG.SYS file. 7. Press the Tab key to get to the Selections for Protocol Window. 8. From the Selections for Protocol Window, select: IBM DOS IEEE 802.2 Protocol for NDIS (DXME0MOD.SYS) This selection is displayed in the Protocol Window. 9. From the Selections for Protocol Window, select: IBM DOS NETBIOS (DXMT0MOD.SYS) This selection is displayed in the Protocol Window. 10. If you have a LAN adapter and want to ensure that your LAN applications (such as Personal Communications/3270** or AttachMate**) are running correctly before installing the LAN Distance product, press PF5. From the IBM DOS NETBIOS (DXMT0MOD.SYS) panel, change the value for the Extra SAPs and Extra stations fields to 5. Press PF4 to save your changes. 11. Press PF4 to begin LSP installation and follow instructions displayed on the screen. 12. If you do not have a LAN adapter on your workstation, change the CONFIG.SYS file to avoid an error message when you restart you workstation. Use an ASCII text editor to edit the CONFIG.SYS file, and remove the appropriate device driver statement according to the adapter you selected in the Selections for Adapter Window. For example, if you selected: IBM Token-Ring Network Adapters with NDIS support (IBMTOK.DOS) delete the following line in the CONFIG.SYS file: DEVICE=\LSP\IBMTOK.DOS ═══ 11.5.1. Adjusting NetBIOS Timers ═══ WAN connections do not support the high data transmission speeds supported for LAN connections. To accommodate slower speeds on the LAN Distance WAN connection, adjust the NetBIOS timers for all the workstations that participate in your LAN Distance wide area network.  LAN Distance Connection Servers  LAN Distance Remotes  OS/2 LAN Workstations ═══ 11.5.2. Adjusting NetBIOS Timers on LAN Distance Workstations ═══ NetBIOS timers are automatically increased when the LAN Distance product is installed to accommodate line speeds as slow as 9600 bps., and to minimize connection problems and unnecessary retransmission of data frames on the LAN Distance connection. If you experience connection problems, you may need to increase NetBIOS timers through the Timers tab in the Settings notebook. Use Guidelines for Changing NetBIOS Timers as a guide to changing NetBIOS timers. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 18. Guidelines for Changing NetBIOS Timers │ ├───────────────────┬──────────────────────────────────────────────────────────┤ │ NETBIOS TIMERS │ DESCRIPTION OF NETBIOS TIMERS │ ├───────────────────┼──────────────────────────────────────────────────────────┤ │ INACTIVITY TIMER │ THE VALUE FOR THIS TIMER DETERMINES HOW OFTEN NETBIOS │ │ - TI │ CHECKS AN INACTIVE LINK TO VERIFY THAT THE LINK IS STILL │ │ │ OPERATIONAL │ │ │ │ │ │ The NetBIOS default value for this timer is 30,000 │ │ │ milliseconds. │ │ │ │ │ │ Increase the setting for this timer if your line speed │ │ │ is slower than 9600 bps. │ │ │ │ │ │ The value for this timer should be set to maintain the │ │ │ following relationship to the other NetBIOS timers: │ │ │ │ │ │ Acknowledgment timer <= Response timer <= Inactivity time│ ├───────────────────┼──────────────────────────────────────────────────────────┤ │ RESPONSE TIMER - │ THE VALUE FOR THIS TIMER SPECIFIES THE DELAY THAT SHOULD │ │ T1 │ OCCUR BEFORE RETRANSMITTING AN UNACKNOWLEDGED FRAME │ │ │ │ │ │ The NetBIOS default value for this timer is 500 milli- │ │ │ seconds. The LAN Distance product increases its value │ │ │ to 10,000 milliseconds. │ │ │ │ │ │ Increase the setting for this timer if your line speed │ │ │ is slower than 9600 bps. │ │ │ │ │ │ As a rule, the response timer (T1) should be 2-5 times │ │ │ larger than the acknowledgement timer (T2). │ │ │ │ │ │ The value for this timer should be set to maintain the │ │ │ following relationship to the other NetBIOS timers: │ │ │ │ │ │ Acknowledgment timer <= Response timer <= Inactivity time│ ├───────────────────┼──────────────────────────────────────────────────────────┤ │ ACKNOWLEDGEMENT │ THE VALUE FOR THIS TIMER SPECIFIES THE DELAY THAT SHOULD │ │ TIMER - T2 │ OCCUR BEFORE ACKNOWLEDGING A RECEIVED FRAME WHEN THE │ │ │ NUMBER OF MAXIMUM FRAMES SENT IS LESS THAN THE CONFIG- │ │ │ URED MAXIMUM │ │ │ │ │ │ The NetBIOS default value for this timer is 200 milli- │ │ │ seconds. The LAN Distance product increases its setting │ │ │ to 2,000 milliseconds. │ │ │ │ │ │ Increase the setting for this timer if your line speed │ │ │ is slower than 9600 bps. │ │ │ │ │ │ The value for this timer should be set to maintain the │ │ │ following relationship to the other NetBIOS timers: │ │ │ │ │ │ Acknowledgment timer <= Response timer <= Inactivity time│ └───────────────────┴──────────────────────────────────────────────────────────┘ ═══ 11.5.3. Adjusting NetBIOS Timers for OS/2 LAN Workstations ═══ The NetBIOS timers on LAN workstations accessed by LAN Distance Remotes, such as an IBM Server domain controller, must be set to the LAN Distance default settings listed in Guidelines for Changing NetBIOS Timers table in Adjusting NetBIOS Timers on LAN Distance Workstation. To adjust NetBIOS timers on a LAN workstation, complete these steps: 1. From an OS/2 command prompt, go to the IBMCOM directory and type LAPS or MPTS to start the LAPS program. From the logo window, select the Configure push button. 2. From the Configuration pop-up window, select the Configure LAN transports radio button, then select the OK push button. 3. From the Current Configuration field in the Configure Workstations window, verify that the NetBIOS protocol is listed as one of the protocols configured for your LAN adapter. If NetBIOS is listed, go to step Adjusting NetBIOS Timers for OS/2 LAN Workstations. If NetBIOS is not listed, select NetBIOS from the Protocols field and select Add to add this protocol to your LAN adapter. 4. In the Current Configuration list box, select NetBIOS to highlight it in the list box. 5. Select the Edit push button. 6. Click on the scroll bars to locate the Ti, T1, and T2 timer fields. Use the table in Adjusting NetBIOS Timers on LAN Distance Workstations as a guide to set these timers to the LAN Distance defaults. ═══ 11.6. Changing a LAN Distance Logical Adapter Network Address ═══ When you install the LAN Distance Connection Server or LAN Distance Remote product, a LAN Distance logical adapter network address is assigned to your LAN Distance Logical Adapter. Your LAN Distance logical adapter network address must be unique among all the workstations and resources in your LAN Distance wide area network and it must adhere to the required address format for your LAN type. For Token-Ring LANs, the format is:  12-character hex value  Range = 400000000000 through 7FFFFFFFFFFF For Ethernet LANs, the format is:  12-character hex value in IEEE 802.3 Ethernet format  Range = 020000000000 through FEFFFFFFFFFF If you switch LAN types, the LAN Distance product automatically converts your LAN Distance logical adapter network address to the proper format for your current LAN type. To change or verify a LAN Distance logical adapter network address on a LAN Distance Connection Server or LAN Distance Remote, complete these steps: 1. Open the Settings notebook and select the Address tab. From page 1 of 2, you can change or verify your LAN Distance logical adapter network address. Address Tab, Page 1 of 2 Note: Most LAN Distance Remotes use only one or two protocols and require only one LAN Distance logical adapter network address. If you require more than five LAN protocols to run your LAN applications, configure an additional LAN Distance logical adapter network address on page 2 of 2. 2. Type a 12-character hexadecimal address in the LAN Distance logical adapter network address field to change this address. 3. Close the Settings notebook to save your changes. ═══ 12. Setting Up Some Popular LAN Applications ═══ This chapter describes how to set up your LAN Distance Remote and LAN Distance Connection Server workstations to support some popular network operating systems and LAN applications. ═══ 12.1. Using LAN Server and LAN Requester ═══ From your OS/2 or MS Windows LAN Distance Remote, you can use the LAN Requester product to access a LAN Server. You can also establish a LAN Distance connection between LAN Server workstations on separate LANs. These configurations are illustrated in LAN Requester and LAN Server Setup. LAN Requester and LAN Server Setup ═══ 12.1.1. Set Up Considerations ═══ Review the following set up considerations for using the LAN Requester and LAN Server products with the LAN Distance product.  The LAN Distance product supports version 1.12 and higher of the IBM LAN Server and LAN Requester products.  Install the LAN Server and Requester products before you install the LAN Distance product.  Install the LAN Distance Remote product on your stand-alone LAN Requester workstation to establish a connection to a LAN Server workstation.  As shown in Using LAN Server and LAN Requester, the LAN Distance Connection Server product can be installed on any LAN workstation. It does not need to be installed on your LAN Server to access resources at the LAN Server workstation.  If you are using LAN Server or LAN Requester 3.0, install Corrective Service Diskette (CSD) IPO7001 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 (International).  Recommended configuration changes for LAN Server and LAN Requester are described in Modifying LAN Server and Requester Configurations.  If you are running version 1.12 or 3.0 of DOS LAN Requester on a MS Windows LAN Distance Remote, you should install CSD IPO7003. See Using DOS LAN Requester.  If you are running DOS LAN Requester, complete the steps described in Changing DOS LAN Requester Performance Parameters. ═══ 12.1.2. Modifying LAN Server and Requester Configurations ═══ 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 on to a LAN Server. To avoid these problems, make the following modifications for:  every LAN Server that has resources you will access using the LAN Distance product.  every LAN Requester workstation using the LAN Distance product. ═══ 12.1.3. Modify NetBIOS Timers for LAN Server Workstations ═══ NetBIOS timers are automatically adjusted when the LAN Distance product is installed on a workstation. If the LAN Distance product is not installed on a LAN Server that you need to access, manually adjust the NetBIOS timers through LAPS. LAN Distance default settings for NetBIOS timers are listed in Adjusting NetBIOS Timers for OS/2 LAN Workstations. ═══ 12.1.3.1. Modify the LAN Server SRVHEURISTICS Parameter ═══ 1. Locate the SRVHEURISTICS parameter in the LAN Server IBMLAN.INI file. 2. Change bit 15 (marked by an ) 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, set the timeout value to infinite by setting bit 15 to 9. 1 (bit position counter->) 0123456789012345678 SRVHEURISTICS = 1111014111131102133  ═══ 12.1.3.2. Increase the LAN Server SESSTIMEOUT Parameter ═══ 1. Locate the SESSTIMEOUT parameter, in the LAN Server IBMLAN.INI file. 2. Increase this value from 45 to 300 seconds to help prevent a LAN server session from timing out. ═══ 12.1.3.3. Modify the LAN Requester WRKHEURISTICS Parameter ═══ 1. Locate the WRKHEURISTICS parameter in the LAN Requester IBMLAN.INI file. 2. Change bits 11, 12, and 13 (marked by an ) in the WRKHEURISTICS parameter to 0. 1 2 3 (bit position counter->) 0123456789012345678901234567890123 WRKHEURISTICS = 1111111121300011110001011120111221  ═══ 12.1.3.4. Increase the LAN Requester SESSTIMEOUT Parameter ═══ 1. Locate the SESSTIMEOUT parameter, in the LAN Server IBMLAN.INI file. 2. Increase this value from 45 to 300 seconds to help prevent a LAN server session from timing out. ═══ 12.1.4. Using DOS LAN Requester ═══ The LAN Distance product supports versions 1.12 and later of DOS LAN Requester. If you are using DOS LAN Requester 3.0 with the MS Windows LAN Distance Remote product, install Corrective Service Diskette (CSD) IPO7003. To obtain CSD IPO7003 for DOS LAN Requester, contact IBM Software Solutions at 1-800-992-4777 (United States), 1-800-465-2222 (Canada), or 1-800-426-1774 (International). If you cannot obtain CSD IPO7003, edit the DOSLAN.INI file found in the DOSLAN directory, and change the /NMS:0 parameter to /NMS:3. If this parameter does not exist, then add /NMS:3 to any of the existing parameter lines or a new line. ═══ 12.1.5. Changing DOS LAN Requester Performance Parameters ═══ Make the following additions and changes to performance parameters in the DOSLAN.INI file before starting DOS LAN Requester on the LAN Distance Remote: 1. From a DOS command prompt, go to the DOSLAN directory and locate the DOSLAN.INI file. 2. Use an ASCII editor to add the following statement to the DOSLAN.INI file: /NMS:3 /NVS:2 /API 3. Set the /NBS (network buffer size) parameter to match the value for the sizereqbuf parameter in the IBMLAN\IBMLAN.INI file on the IBM LAN Server. For example, if the value for the sizereqbuf in the IBMLAN.INI file is 4096, set the /NBS parameter in the DOSLAN.INI file to: /NBS:4K 4. Change the /BBS (big buffer size) parameter so it is 1K larger than the /NBS parameter specified in step Changing DOS LAN Requester Performance Parameters. 5. Change the fourth character in the /WKS (DLR heuristics) parameter to 0 and the last character to 1. /WKS:111021101021211   For more information about tuning DOS LAN Requester performance parameters, see IBM OS/2 LAN Server Network Administrator Reference Volume 2: Performance Tuning. ═══ 12.2. Microsoft LAN Manager ═══ If you are using Microsoft LAN Manager with LAN Distance, complete the setup and tuning steps in the following sections. ═══ 12.2.1. OS/2 - LAN Manager Requester ═══  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.  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 environment will give you slightly improved performance when you are directly attached to the LAN.  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  Edit your STARTUP.CMD: (Temporarily) remark out the starting of the LAN Manager Requester: REM NET START WORKSTATION REM NET LOGON ...  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 [workstation] section to look like the following: [workstation] ; 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 Administrator's Reference for a full description of these heuristics. 3. Edit/add the sesstimeout value in the [workstation] section as follows: [workstation] sesstimeout = 300  Install the LAN Distance Remote for OS/2 product and use the Basic Settings Option to configure your initial setup.  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 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.  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.  Complete steps further below under "LAN Manager Server".  "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.  TCP/IP NOTE: The LAN Manager TCP/IP protocol does not work with LAN Distance. ═══ 12.2.2. LAN Manager Server ═══ Complete the following tuning steps so that the LAN Manager server can work with the slower LAN Distance WAN connections:  Edit the LANMAN.INI file: 1. Edit the sesstimeout value in the [workstation] section as follows: [workstation] sesstimeout = 300 2. Add a srvheuristics parameter (or change the current one) in the [server] section: [server] ; 0 1 ; 01234567890123456789 srvheuristics = 11110151111211021331 If you already have a srvheuristics parameter, the only change necessary 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.  If you are running the NETBIOS protocol over a LAN Distance WAN connection, edit the PROTOCOL.INI file: The NETBIOS timer values must be relaxed to handle the slower WAN connection. Add or the change the following parameters in the NETBEUI_XIF section: [NETBEUI_XIF] TI = 60000 T1 = 10000 T2 = 2000 ═══ 12.3. Using the Communications Manager/2 3270 Emulation Feature ═══ A LAN Distance Remote can dial into a LAN and use the 3270 Emulation feature of IBM Communication Manager/2 to access a LAN-attached host controller as shown in Communication Manager/2 Set Up. Communication Manager/2 Set Up Review the following set up considerations for using Communications Manager/2 and its 3270 emulation feature.  The LAN Distance product supports versions 1.0 and 1.1 of the Communications Manager/2 product. Version 1.1 of the Communications Manager/2 product routes data frames using general broadcast instead of source routing frames (used in version 1.0 of the Communications Manager/2 product). If you are running version 1.1, verify that the hop count defined at the LAN Distance bridge is large enough to allow Communication Manager/2 general broadcast frames to reach the receiving workstation. See Example 2: Using OS2PING to Verify the LAN Distance Bridge Hop Count.  Install Communications Manager/2 before you install the LAN Distance product.  If you are running Communications Manager/2 with SNA, configure the 802.2 protocol when you install Communications Manager/2.  Configure the 802.2 LAN protocol on the LAN Distance Remote where the Communications Manager/2 product is installed. See Configuring Additional LAN Protocols Required for Your OS/2 LAN Applications.  Set the maximum number of network bridge hops at the LAN Distance bridge so the data frames sent from the LAN Distance Remote running 3270 emulation can be received at the 3745 controller. See Defining Configuration Values for the LAN Distance Bridge.  The LAN Distance product and Communications Manager/2 cannot simultaneously support ISDN. If you plan to run LAN Distance over an ISDN connection, you cannot simultaneously run Communications Manager/2 if it is configured for ISDN.  To use the CM/2 v1.11 PSTN "SNA Phone Connections" feature with LAN Distance PSTN support, apply a CM/2 file for APAR JR08194. This file can be obtained through IBM Service and Support by referencing this APAR number. ═══ 12.4. Using NetWare Server and NetWare Requester ═══ A LAN Distance Remote running the NetWare Requester product can remotely access a NetWare Server by dialing a LAN Distance Connection Server on the NetWare LAN. From your NetWare Requester workstation, you can use the LAN Distance product to establish a connection to a NetWare Server as shown in NetWare Requester and NetWare Server Set Up. NetWare Requester and NetWare Server Set Up The LAN Distance product supports the following versions of the NetWare products:  NetWare Requester for OS/2 versions 2.x, 3.1x, 4.0 (or later)  NetWare Server versions 2.x, 3.1x, 4.0 (or later) The LAN Distance product uses the IBM NetWare Requester Support protocol driver, ODI2NDI, to support the NetWare products. ODI2NDI can operate concurrently with the NetBIOS, IEEE 802.2, and TCP/IP LAN protocols over a single LAN Distance connection. ═══ 12.4.1. Setting Up a NetWare Server ═══ On a Token-Ring LAN, your LAN Distance Connection Server uses source-routing bridge software to support connections with LAN Distance Remotes. To run a NetWare Server with the LAN Distance product on a Token-Ring LAN, load the NetWare source-routing driver, ROUTE.NLM, on the NetWare Server. To load the NetWare source-routing driver, type LOAD ROUTE BOARD=x (x is the adapter number of the NetWare Server's LAN adapter). See your NetWare documentation for more information. You do not need to restart the NetWare Server to enable ROUTE.NLM. The ROUTE.NLM driver adds source routing information to all LAN data frames transmitted by the NetWare Server's LAN adapter. The ROUTE.NLM driver is required only for NetWare Servers that are accessed remotely. Note: No special setup is required to remotely access a NetWare Server that is on an Ethernet LAN. ═══ 12.4.2. Setting Up a NetWare Requester for OS/2 ═══ To set up your LAN Distance Remote to use the NetWare Requester for 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 NetWare installation, select the appropriate network interface card driver:  If your NetWare Server is on an Ethernet LAN, select the appropriate network interface card driver for the Ethernet adapter.  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 information required by the LAN Distance product. 3. Install the LAN Distance Remote product on your workstation. See "Installing the LAN Distance Product Using Diskettes" in the LAN Distance Remote Guide. 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. The Parameters for IBM NetWare Requester Support window (Parameters for IBM NetWare Requester Support) is displayed. Parameters for IBM NetWare Requester Support 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. 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, complete the steps in NetWare Connection ID Error Message (NWD0115 or REQ0815). for the version of NetWare Requester installed on your workstation. For a NetWare server to support clients using packet burst in a WAN environment, 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:  Burst retries could saturate WAN links due to low retry timeout values.  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. ═══ 12.5. NetWare Connection ID Error Message (NWD0115 or REQ0815). ═══ If you are running the NetWare Requester on your LAN Distance Remote, when you start your LAN Distance Remote workstation you will receive a NetWare error message indicating that the NetWare Requester cannot locate the NetWare Server. attempts to locate the NetWare Server on the LAN before a LAN Distance connection is established. The following recommendations are for running OS/2 NetWare Requester. Note that a few of the steps only apply to a token ring environment.  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.  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  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.  The OS/2 NetWare requester must have a fix for NWREQ.SYS. 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 can cause frames to be retransmitted several times causing slow performance 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 shutdown OS/2. This NetWare fix is available through IBM Support and Service by referencing APAR IC07834. ═══ 12.5.1. NetWare Requester for OS/2 Version 2.1 (or Later). ═══ If you are running NetWare Requester for OS/2 Version 2.1 (or later), error message REQ0815 displays when you start your LAN Distance Remote. To clear the error, press the Enter key. After you establish a connection to the LAN Distance Connection Server, the NetWare Requester will automatically locate the NetWare Server and operate normally. ═══ 12.5.2. NetWare Requester for OS/2 Versions Prior to 2.1 ═══ If you are running a version of the NetWare Requester released prior to version 2.1, in addition to receiving error message NWD0115, a delay of approximately 3-1/2 minutes occurs when you start the LAN Distance Remote. During the delay, only a blank OS/2 desktop is displayed. After the delay, error message SYS0059 is displayed. When you establish a connection to the LAN Distance Connection Server, the NetWare Requester can locate the NetWare Server and operate normally. If you want to avoid these error messages and the delay when starting your LAN Distance Remote, perform the following steps. 1. Use an ASCII 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, before logging on to the NetWare Server, complete step NetWare Requester for OS/2 Versions Prior to 2.1. ═══ 12.5.3. Setting Up NetWare Requester for MS Windows ═══ You can set up 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. 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. ═══ 12.5.4. Running NetWare Requester on a LAN Distance Remote ═══ Review the following considerations for running NetWare Requester on a LAN Distance Remote: ═══ 12.5.4.1. 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 from a local drive on the LAN Distance Remote, you avoid the delay involved in loading large files over the LAN Distance connection. ═══ 12.5.4.2. Verifying the MaxFrame Value Defined at the NetWare Server ═══ When NetWare Requester is installed on the LAN Distance Remote, the MaxFrame parameter in the [SOCKDD_MOD] 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 [SOCKDD_MOD] and [COMx] sections of the WAL\PROTOCOL.INI match. (COMx identifies the COM port you are using for LAN Distance; for example, COM1 or COM2.) ═══ 12.6. Using TCP/IP for OS/2 ═══ The LAN Distance product supports version 1.2.1 and later of the Using TCP/IP for OS/2 product. You can install TCP/IP on these types of workstations:  LAN-attached workstation that you are setting up as a LAN Distance Remote.  Stand-alone workstation that you are setting up as a LAN Distance Remote. ═══ 12.7. Setting Up TCP/IP on a LAN-Attached Workstation ═══ To set up TCP/IP on a LAN-attached workstation or on a stand-alone workstation that already has a LAN adapter installed: 1. Install and configure Using TCP/IP for OS/2 using the automated tool, ICAT, shown in TCP/IP Version 3.0. TCP/IP Version 3.0 2. From an OS/2 command line, use the COPY command to copy these files from \TCPIP\BIN to \IBMCOM\PROTOCOL. TCPIP.NIF INET.SYS IFNDIS.SYS 3. Shut down and restart your workstation. 4. Use LAPS to configure the TCP/IP protocol for your LAN adapter. From an OS/2 command line, go to the IBMCOM directory and type LAPS or MPTS to start the LAPS program. LAPS Logo Window 5. From the logo window (shown in LAPS Logo Window), select the Configure push button. From the Configure pop-up window, select the Configure LAN transports radio button, and the Continue push button to open the Configure Workstation window. 6. From the Configure Workstation window (shown in LAPS Configure Workstation Window), be sure the Current Configuration list box displays your LAN adapter. Otherwise, select your LAN adapter from the Network Adapters field, and select the Add push button to add it to the Current Configuration list box. LAPS Configure Workstation Window 7. From the Protocols list box, select the IBM TCP/IP protocol. Select the Add push button to add this protocol to your LAN adapter. 8. Select OK to exit the Configure Workstation window. 9. Select the Exit push button from the LAPS logo window to exit LAPS. 10. Shut down and restart your workstation before you complete step Setting Up TCP/IP on a LAN-Attached Workstation. 11. Install the LAN Distance product. 12. Shut down and restart your workstation. Note: You can use the shuttle feature to switch between the LAN-attached configuration and the standalone LAN Distance Remote configuration. See "Using the Shuttle Feature for OS/2" in the LAN Distance Remote Guide. ═══ 12.7.1. Setting Up TCP/IP on a Stand-Alone Workstation ═══ To set up TCP/IP on a stand-alone Remote that does not have a LAN adapter installed: 1. Install the LAN Distance product. 2. Shut down and restart your workstation. 3. Install and configure TCP/IP using the automated tool, ICAT, shown in TCP/IP Version 3.0 in Using TCP/IP for OS/2. 4. From an OS/2 command line, use the COPY command to copy these files from \TCPIP\BIN to \IBMCOM\PROTOCOL. TCPIP.NIF INET.SYS IFNDIS.SYS 5. Shut down and restart your workstation. 6. Add the TCP/IP protocol to the LAN Distance Logical Adapter. a) From the LAPS tab in the Settings notebook, select the LAPS push button to open the LAPS Configure Workstation window (shown in LAPS Configure Workstation Window). You can also access the LAPS program from an OS/2 command line. Go to the IBMCOM directory and type LAPS to start the LAPS program. b) Steps for adding TCP/IP to the LAN Distance Logical Adapter are listed in Setting Up TCP/IP on a LAN-Attached Workstation through Setting Up TCP/IP on a LAN-Attached Workstation. . LAPS Configure Workstation Window 7. After you shut down and restart you workstation, you can verify that TCP/IP is configured correctly. Go to the LAPS tab in the Settings notebook, and select the LAPS push button to open the LAPS Configure Workstation window. If TCP/IP is configured for the LAN Distance Logical Adapter, it is added to the LAN Distance Logical Adapter in the Current Configuration list box, as shown in LAPS Configure Workstation Window. LAPS Configure Workstation Window ═══ 12.8. Using TCP/IP for DOS ═══ Install TCP/IP for DOS on a MS Windows workstation before you install the LAN Distance Remote product. If you installed TCP/IP for DOS after you installed the LAN Distance Remote product, you must follow these steps for TCP/IP to work: 1. Use an ASCII editor to edit the CONFIG.SYS file, and be sure that the TCP/IP DEVICE= statement appears after the section of LAN Distance configuration statements. The following statement is an example TCP/IP DEVICE= statement: DEVICE=C:\TCPDOS\BIN\DOSTCP.SYS 2. Use an ASCII text editor and ensure that the TCP/IP section is copied from the \LSP\PROTOCOL.INI file to the C:\WAL\PROTOCOL.INI file, where C:\WAL is the correct drive and pathname of your WAL directory. Change the Bindings value to SOCKDD_MOD, as shown below: Bindings=SOCKDD_MOD 3. Use an ASCII text editor to add the following line to the AUTOEXEC.BAT file: CALL TCPSTART ═══ 12.9. Special Considerations for Running OS/2 802.2 Applications ═══ If you experience problems running 802.2 applications, such as IBM Communication Manager, you may need to increase 802.2 timers through LAPS: 1. Open the Settings notebook and select the LAPS tab, then select the LAPS push button to open the LAPS Configure Workstation window shown in LAPS Configure Workstation Window in Setting Up TCP/IP on a LAN-Attached Workstation. 2. From the Current Configuration list box, select the IBM IEEE 802.2 protocol. 3. Select the Edit push button to increase the Group 1 response timer - T1 and the Group 2 response timer - T2 for the IBM IEEE 802.2 protocol. 4. Select OK to exit the Configure Workstation window and return to the LAPS tab in the Settings notebook. 5. From the LAPS tab, double-click on the system menu symbol in the upper left corner to close the Settings notebook and save changes. 6. Shut down and restart your workstation. ═══ 12.10. Installing LSP After the LAN Distance Remote Is Installed ═══ This section describes how to install LAN Support Program (LSP) for 802.2 support after the LAN Distance Remote product is installed. Use this method to install LSP only if one of the following statements apply. If none of these statements apply, see Installing LSP Before You Install the LAN Distance Product.  Your workstation does not have a LAN adapter, AND you have no adapter option diskette available. Note: Some versions of LSP may include an adapter option on the LSP diskette.  You cannot remove the LAN Distance Remote product before installing LSP.  You installed LSP without NDIS 802.2 support. The following steps are based on LSP version 1.35: 1. Insert the LSP diskette in the diskette drive, type A:DXMAID, and press Enter to start the LSP installation program. 2. Press Enter to get past the IBM logo screen and Information panels to the Environment Information panel. 3. From the Environment Information panel, specify the following options for your workstation: Configuration for this computer? Yes Use existing configuration information? Yes Do you have adapter option diskettes? No Are you configuring for 2 adapters? No Do you need 802.2 interface support? Yes Press Enter. 4. From the Selections for Adapter Window, select: SOCKDD_MOD The selection is displayed in the Primary Adapter Window. 5. Press the Tab key to get to the Selections for Protocol Window. 6. From the Selections for Protocol Window, select: IBM DOS IEEE 802.2 Protocol for NDIS (DXME0MOD.SYS) This selection is displayed in the Protocol Window. 7. From the Selections for Protocol Window., ensure that the following protocol is not selected: IBM DOS NETBIOS (DXMT0MOD.SYS) This selection should not be displayed in the Protocol Window. 8. Press PF4 to begin LSP installation and follow any further instructions. 9. Use an ASCII text editor and remove the following statement from the AUTOEXEC.BAT file: \LSP\NETBIND 10. Use an ASCII text editor and make the following changes to the CONFIG.SYS file: a) Replace the following LSP protman device statement: DEVICE=\LSP\PROTMAN.DOC /I:\LSP with this LAN Distance protman device statement: DEVICE=C:\WAL\PROTMAN.DOS /I:C:\WAL where C:\WAL is the correct drive letter and path for the WAL directory in BOTH places in the statement. b) Ensure that the following device statements are in the CONFIG.SYS file in this order: DEVICE=C:\WAL\PROTMAN.DOS /I:C:\WAL DEVICE=\LSP\DXMA0MOD.SYS 001 DEVICE=C:\WAL\DXMJ0MOD.SYS DEVICE=\LSP\DXME0MOD.SYS 001 where C:\WAL is the correct drive letter and path for the WAL directory. c) The LSP install program may add a REM statement that instructs you to remove some DEVICE= statements. Remove only the REM statement. DO NOT remove any DEVICE= statements. 11. The LSP install program adds a section defining the 802.2 support to the \LSP\PROTOCOL.INI file. You must copy this section from the \LSP\PROTOCOL.INI file to the \WAL\PROTOCOL.INI file. Do not copy the entire PROTOCOL.INI file. Move only the following section defining the 802.2 support: [DXME0_xxx] DriverName = DXME0$ Bindings = VLANMAC_MOD where xxx is different, depending on which LSP version you are installing. Copy this section to the bottom of the \WAL\PROTOCOl.INI file. 12. Shut down and restart your workstation. 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. 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. ═══ 12.11. Using Banyan VINES ═══ The LAN Distance product supports VINES Revision 4.11(5), 5.5x (or later) VINES NDIS device drivers. Requester and Banyan VINES Server products are described in this section.  After installing the Banyan VINES Requester product, modify the CONFIG.SYS file.  Configure source routing for the Banyan VINES Requester product.  After installing the LAN Distance Remote product on the Banyan VINES Requester workstation, modify the PROTOCOL.INI file.  Configure source routing for the Banyan VINES Server. ═══ 12.11.1. Setting Up the Banyan VINES Requester ═══ 1. Install the Banyan VINES Requester product using the VCLIENT command, or manually install the product and copy the appropriate NDIS and VINES device drivers. Refer to the Banyan VINES manual (Managing VINES Workstations) for installation support. 2. When the Banyan VINES Requester product is installed, use an ASCII editor to add the following statement (if it does not already exist) to the end of the CONFIG.SYS file. DEVICE=x:\VINESDRIVERS\BN_NDIS\NDISBAN2.SYS x represents the drive where the Banyan VINES Requester product is installed. 3. To configure source routing on the Banyan VINES Requester, from an OS/2 command prompt, go to the VINES directory and type PCCONFIG. Select Network Card Settings. Make sure Enable EndNode Source Routine is set to Y. 4. Install the LAN Distance Remote product on the Banyan VINES Requester workstation.  Whether you use Basic Settings or the Settings notebook for configuration, complete step Setting Up the Banyan VINES Requester before shutting down your workstation.  Before you complete step Setting Up the Banyan VINES Requester, the LAN Distance Remote must be shuttled to the stand-alone configuration. - If you install the LAN Distance Remote product on a LAN-attached workstation, before installation is done, the Shuttle message window displays. Select Yes to shuttle your workstation to the stand-alone environment. - If you install the LAN Distance Remote product on a stand-alone workstation, the stand-alone configuration is active. 5. After LAN Distance Remote installation, but before you shut down and restart the workstation, use an ASCII editor to edit the IBMCOM\PROTOCOL.INI file. Add or modify the [VINES_nif] section of the PROTOCOL.INI file to match the following: [VINES_nif] DriverName = NDISBAN$ Bindings = PDFH_nif 6. Shut down and restart your workstation. 7. Start the LAN Distance Remote product. 8. To start the Banyan VINES Requester product, from an OS/2 command prompt, go to the VINES directory, and type BAN. ═══ 12.11.2. Configuring Source Routing for the Banyan VINES Server ═══ 1. From the Operator Menu, select System Maintenance. Then, select Configure/Diagnose Server. 2. Select Add Card/Change Card Configuration. 3. Make sure Enable End Node Source Routing is set to Y. ═══ 12.11.3. Additional Tips for Using Banyan VINES ═══  To update the VINES device drivers on the LAN Distance Remote, use the VINES command NEWREV instead of the VCLIENT command.  Install local copies of all your frequently used VINES utilities and place these files in your VINES (or appropriate) subdirectory. The following are some files recommended for copying: - LOGIN.EXE - LOGIN.MSB - LOGOUT.EXE - LOGOUT.MSB - INTLDATA.BIN  Load Banyan VINES with the "slr.nl" switch and execute login locally, for example: BAN /nl LOGIN The following Banyan fix is in the Banyan Maintenance release 5.54(5). If this release is not available, then contact your Banyan SE.  You must modify the Banyan VINES protocol drivers for Banyan VINES and LAN Distance to work together correctly: Adjustable metrics were added for the NDIS protocol. This required modification 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 [VINES_XIF] section: [VINES_XIF] DRIVERNAME=NDISBAN$ BINDINGS="SOCKDD_MOD" LANABASE=0 METRIC=90 ═══ 13. Setting Up the Phone Book ═══ The phone book is the directory of information the LAN Distance product needs to dial workstations. Create a phone book entry for every workstation you dial, including workstations you connect to over a leased line. A phone book entry is required to dial any remote location, even over a nonswitched line. Configure your LAN Distance ports and modems before setting up your phone book; some phone book entry fields require port information. See Setting Up Ports and Modems for information about LAN Distance ports. This chapter describes how to:  Set up phone book entries for asynchronous and synchronous connections using a switched line.  Set up phone book entries for asynchronous and synchronous connections using a leased line.  Set up phone book entries for ISDN switched connections.  Configure a phone book entry to automatically start your LAN applications or command files. ═══ 13.1. Creating Phone Book Entries ═══ To begin configuring a phone book entry, open the Settings notebook and select the Phone Book tab. The Phone Book tab is shown in Settings Notebook, Phone Book Tab. Settings Notebook, Phone Book Tab Select a push button to perform an action for a phone book entry. Your changes are saved when you close the Phone Book - Settings notebook. Entry Type Window - Settings describes the Entry Type Window - Settings that is displayed when you add a phone book entry. Use Asynchronous or Synchronous Switched Line Phone Book Entry, Asynchronous or Synchronous Leased Line Phone Book Entry, and ISDN Switched Line Phone Book Entry in Asynchronous and Synchronous (PSTN) Switched Line Connections as guides to setting up phone book entries for specific connection and line types. The Copy push button sets up a new phone book entry using information from an existing phone book entry. After naming your new phone book entry, close the Phone Book - Settings notebook to save it. Then, select the Change push button to customize your new phone book entry. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 19. Entry Type Window - Settings │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELD │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ NETWORK TYPE │ Select the connection type for the phone book entry : │ │ │ │ │ │ PSTN - Public Systems Telephone Network (asynchronous or │ │ │ synchronous) │ │ │ │ │ │ ISDN - Integrated Services Digital Network │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ LINE TYPE │ Select the line type for the phone book entry: │ │ │ │ │ │ Switched │ │ │ │ │ │ Nonswitched (leased or permanent connection) │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 13.1.1. Asynchronous and Synchronous (PSTN) Switched Line Connections ═══ Use Asynchronous or Synchronous Switched Line Phone Book Entry for setting up a phone book entry for an asynchronous or synchronous switched line connection. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 20. Asynchronous or Synchronous Switched Line Phone Book Entry │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ENTRY │ ENTRY NAME │ Specify a name for the phone book entry. │ │ │ │ │ │ │ │ The name of the phone book entry must be │ │ │ │ unique within the phone book. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DESCRIPTION │ Describe the phone book entry. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CALLBACK ENTRY │ Select whether the phone book entry can be │ │ │ │ used for callback. │ │ │ │ │ │ │ │ Only phone book entries that are marked as │ │ │ │ callback entries can be selected from the list │ │ │ │ box in the callback options for a user │ │ │ │ account. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ NUMBERS │ TELEPHONE │ View the telephone numbers for the phone book │ │ │ NUMBER │ entry. │ │ │ │ │ │ │ │ Each phone book entry contains a call list of │ │ │ │ one or more telephone numbers. When you dial │ │ │ │ the phone book entry, the numbers in the call │ │ │ │ list are dialed in the order specified, until │ │ │ │ a successful connection is established or the │ │ │ │ dial retry limit is reached. (See Customizing │ │ │ │ Your Dialing Setup for information about dial │ │ │ │ retry). │ │ │ │ │ │ │ │ Being able to configure multiple telephone │ │ │ │ numbers allows you to dial alternative numbers │ │ │ │ when the primary telephone number is busy or │ │ │ │ not answering. │ │ │ │ │ │ │ │ Select a push button to add, change, or delete │ │ │ │ telephone numbers in your call list. A window │ │ │ │ containing these fields is displayed when you │ │ │ │ add or change a telephone number: │ │ │ │ │ │ │ │ o TELEPHONE NUMBER TO BE DIALED │ │ │ │ o DIALING ORDER │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ TELEPHONE │ Specify the telephone number of the work- │ │ │ NUMBER TO BE │ station to be dialed. │ │ │ DIALED │ │ │ │ │ Specify the complete telephone number that is │ │ │ │ required to complete the call. For example, │ │ │ │ include the area code for long distance tele- │ │ │ │ phone numbers. │ │ │ │ │ │ │ │ If you always precede your telephone numbers │ │ │ │ with a particular dialing prefix (such as a │ │ │ │ '9') consider updating your modem dialing │ │ │ │ string. Phone book entries do not need to │ │ │ │ include the dialing prefix because all calls │ │ │ │ dialed through the modem will automatically │ │ │ │ have the dialing prefix added to them. See │ │ │ │ Modifying a Dial String for Outside Calls for │ │ │ │ information about modem dialing strings. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DIALING ORDER │ Select the telephone number position in the │ │ │ │ dialing order list. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 20. Asynchronous or Synchronous Switched Line Phone Book Entry │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ MODEM │ ASYNCHRONOUS │ For an asynchronous connection, select the │ │ │ │ modem class that best matches that of the │ │ │ MODEM CLASS │ dialed workstation modem. │ │ │ │ │ │ │ │ When you dial the phone book entry, an avail- │ │ │ │ able modem is selected whose class is closest │ │ │ │ to the selected modem class. If a close match │ │ │ │ is not found or the best modem is not avail- │ │ │ │ able, another modem is used. The call does │ │ │ │ not fail because the desired modem is not │ │ │ │ available. │ │ │ │ │ │ │ │ Modem class represents the fastest modulation │ │ │ │ standard supported by an asynchronous modem. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ SYNCHRONOUS │ For a synchronous connection, select the │ │ │ │ dialed workstation's modem encoding scheme. │ │ │ ENCODING │ │ │ │ SCHEME │ Two encoding schemes are supported: NRZ and │ │ │ │ NRZI. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ PORT │ PORT BY TELE- │ Select a port to use when dialing the phone │ │ │ PHONE NUMBER │ book entry. │ │ (Optional) │ │ │ │ │ │ If you do not select a port, an available port │ │ │ │ is selected for you when you dial the phone │ │ │ │ book entry. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ AUTOSTART │ AUTOSTART │ Start a LAN application automatically after a │ │ │ PROGRAM WHEN │ connection is successfully established using │ │ (Optional) │ CONNECTION │ the phone book entry. │ │ │ ESTABLISHED │ │ │ │ │ Use Phone Book Entry, Autostart Tab for │ │ │ │ setting up the Autostart feature. for setting │ │ │ │ up the Autostart feature. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 13.1.2. Asynchronous and Synchronous (PSTN) Leased Line Connections ═══ Use Asynchronous or Synchronous Leased Line Phone Book Entry for setting up a phone book entry for an asynchronous or synchronous leased line connection. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 21. Asynchronous or Synchronous Leased Line Phone Book Entry │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ENTRY │ ENTRY NAME │ Specify a name for the phone book entry. │ │ │ │ │ │ │ │ The name of the phone book entry must be │ │ │ │ unique within the phone book. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DESCRIPTION │ Describe the phone book entry. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ CONNECT │ MODEM │ Select the modem type associated with the │ │ │ │ leased line for the phone book entry. │ │ │ │ │ │ │ │ The modem types that are assigned leased lines │ │ │ │ are displayed in the list box. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ LEASED LINE │ Select the leased line to be used when dialing │ │ │ NAME │ the phone book entry. │ │ │ │ │ │ │ │ Your leased line names are displayed after you │ │ │ │ select your modem. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ENCODING │ For a synchronous connection, select the │ │ │ SCHEME │ dialed workstation modem encoding scheme. │ │ │ │ │ │ │ │ Two encoding schemes are supported: NRZ and │ │ │ │ NRZI. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ AUTOSTART │ AUTOSTART │ Start a LAN application automatically after a │ │ │ PROGRAM WHEN │ connection is successfully established using │ │ (Optional) │ CONNECTION │ the phone book entry. │ │ │ ESTABLISHED │ │ │ │ │ Use Phone Book Entry, Autostart Tab for │ │ │ │ setting up the Autostart feature. for setting │ │ │ │ up the Autostart feature. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 13.1.3. ISDN Switched Line Connections ═══ Use ISDN Switched Line Phone Book Entry for setting up a phone book entry for an ISDN switched line connection. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 22. ISDN Switched Line Phone Book Entry │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ENTRY │ ENTRY NAME │ Specify a name for the phone book entry. │ │ │ │ │ │ │ │ The name of the phone book entry must be │ │ │ │ unique within the phone book. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DESCRIPTION │ Describe the phone book entry. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CALLBACK ENTRY │ Select whether the phone book entry can be │ │ │ │ used for callback. │ │ │ │ │ │ │ │ Only phone book entries that are marked as │ │ │ │ callback entries can be selected from the list │ │ │ │ box in the callback options for a user │ │ │ │ account. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ NUMBERS │ TELEPHONE │ View the telephone numbers for the phone book │ │ │ NUMBER │ entry. │ │ │ │ │ │ │ │ Each phone book entry contains a call list of │ │ │ │ one or more telephone numbers. When you dial │ │ │ │ the phone book entry, the numbers in the call │ │ │ │ list are dialed in the order specified, until │ │ │ │ a successful connection is established or the │ │ │ │ dial retry limit is reached. (See Customizing │ │ │ │ Your Dialing Setup for information about dial │ │ │ │ retry). │ │ │ │ │ │ │ │ Being able to configure multiple telephone │ │ │ │ numbers enables you to dial alternative │ │ │ │ numbers when the primary telephone number is │ │ │ │ busy or not answering. │ │ │ │ │ │ │ │ Select a push button to add, change, or delete │ │ │ │ telephone numbers in the phone book entry. A │ │ │ │ window containing the following fields is dis- │ │ │ │ played when you add or change a telephone │ │ │ │ number. │ │ │ │ │ │ │ │ o TELEPHONE NUMBER TO BE DIALED │ │ │ │ o DIALING ORDER │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ TELEPHONE │ Specify the telephone number of the work- │ │ │ NUMBER TO BE │ station to be dialed. │ │ │ DIALED │ │ │ │ │ Specify the complete telephone number that is │ │ │ │ required to complete the call. For example, │ │ │ │ include the area code for long distance tele- │ │ │ │ phone numbers. │ │ │ │ │ │ │ │ If you always precede your telephone numbers │ │ │ │ with a particular dialing prefix (such as a │ │ │ │ '9') consider updating your modem dialing │ │ │ │ string. Phone book entries do not need to │ │ │ │ include the dialing prefix because all calls │ │ │ │ dialed through the modem will automatically │ │ │ │ have the dialing prefix added to them. See │ │ │ │ Modifying a Dial String for Outside Calls for │ │ │ │ information about modem dialing strings. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DIALING ORDER │ Select the telephone number position in the │ │ │ │ call list. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ NUMBER TYPE │ Select the telephone number type. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ NUMBERING PLAN │ Select the telephone number plan. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ DATA RATE │ 64 KBPS │ Select the appropriate rate for calls dialed │ │ │ 56 KBPS │ for the phone book entry. │ │ │ │ │ │ │ │ If you are not sure of the appropriate data │ │ │ │ rate, select 64 KBPS. Change it to 56 KBPS if │ │ │ │ you cannot dial this phone book entry success- │ │ │ │ fully. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 22. ISDN Switched Line Phone Book Entry │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ CALLER ID │ DO NOT SEND │ Select whether you want your telephone number │ │ │ TELEPHONE │ sent to the dialed workstation. │ │ (Optional) │ NUMBER │ │ │ │ SEND TELEPHONE │ Your local telephone number is your caller ID. │ │ │ NUMBER │ If you choose to send your caller ID, the │ │ │ │ local telephone number specified through the │ │ │ │ CHANNEL tab is sent to the dialed workstation. │ │ │ │ If no telephone number is configured there, │ │ │ │ the LAN Distance product chooses one of your │ │ │ │ local telephone numbers for dialing the call │ │ │ │ and sends that number. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ CHANNEL │ ANY TELEPHONE │ Use any local telephone number to dial the │ │ │ NUMBER │ phone book entry. │ │ (Optional) │ │ │ │ │ │ The LAN Distance product selects any available │ │ │ │ local telephone number (port) for you when you │ │ │ │ dial the phone book entry. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ SPECIFIC LOCAL │ Select the telephone number of a local channel │ │ │ TELEPHONE │ to be used when dialing the phone book entry. │ │ │ NUMBER │ │ │ │ │ │ │ │ LOCAL TELE- │ │ │ │ PHONE NUMBER │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ANY CHANNEL │ Use any available channel when dialing the │ │ │ │ phone book entry. │ │ │ │ │ │ │ │ Any available channel whose telephone number │ │ │ │ matches the LOCAL TELEPHONE NUMBER is used │ │ │ │ when you dial the phone book entry. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ SPECIFIC │ Specify a channel to use when dialing the │ │ │ CHANNEL │ phone book entry. │ │ │ │ │ │ │ CHANNEL NUMBER │ If you specify a LOCAL TELEPHONE NUMBER, then │ │ │ │ CHANNEL NUMBER must be configured for that │ │ │ │ telephone number. Otherwise, an error occurs │ │ │ │ when you dial the phone book entry. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ AUTOSTART │ AUTOSTART │ Start a LAN application automatically after a │ │ │ PROGRAM WHEN │ connection is successfully established using │ │ (Optional) │ CONNECTION │ the phone book entry. │ │ │ ESTABLISHED │ │ │ │ │ Use Phone Book Entry, Autostart Tab for │ │ │ │ setting up the Autostart feature. for setting │ │ │ │ up the Autostart feature. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 13.2. Automatically Starting a LAN Application ═══ Configure your phone book entry to automatically start a LAN application or command file on your workstation after you establish a LAN Distance connection. The tasks in this section apply to both LAN applications and command files. To configure autostart settings for an existing phone book entry: 1. Open the Settings notebook and select the Phone Book tab. 2. Select a phone book entry. 3. Select the Change push button. 4. Select the Autostart tab. Use Phone Book Entry, Autostart Tab as a guide for configuring your autostart settings. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 23. Phone Book Entry, Autostart Tab │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ AUTOSTART │ Start a LAN application automatically after a connection is │ │ PROGRAM WHEN │ established using the phone book entry. │ │ CONNECTION │ │ │ ESTABLISHED │ The LAN application is automatically started on the dialing │ │ │ workstation. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PROGRAM TITLE │ Specify the program name for the OS/2 Window List. │ │ │ │ │ │ This name is added to the OS/2 Window List after the LAN │ │ │ Distance product starts your LAN application. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PATH AND FILE │ Specify the fully-qualified name of your LAN application. │ │ NAME │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PARAMETERS │ Specify the input parameters to your LAN application. │ │ (Optional) │ │ │ │ If your LAN application enables input parameters, specify │ │ │ their values here. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PROGRAM TYPE │ Specify your LAN application program type. │ │ │ │ │ │ Choose a program type: │ │ │ │ │ │ o Default │ │ │ o CMD │ │ │ o Full-screen │ │ │ o PM │ │ │ o Windowed │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ INITIAL │ Specify the window size for your LAN application. │ │ WINDOW SIZE │ │ │ │ Choose a window size: │ │ │ │ │ │ o Normal │ │ │ o Maximized │ │ │ o Minimized │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ START IN │ Select whether your LAN application is to be started in the │ │ │ foreground or background. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 13.3. Customizing a Phone Book Entry for Calling Card Use ═══ Warning: Every time you dial out from your LAN Distance Remote workstation using a calling card, calling card information for that phone book entry is recorded in a LAN Distance file, and can be viewed by anyone who has access to your machine. You have the option of including calling card information when you define a telephone number for a LAN Distance Remote or LAN Distance Connection Server. This allows you to charge the cost for a long distance connection to your calling card. You can temporarily customize telephone numbers from the Phone Book, or you can add or change telephone numbers through the Settings notebook by making the appropriate selections from the Phone Book tab. See Creating Phone Book Entries. ═══ 13.3.1. Example: Adding Calling Card Information to a Telephone Number ═══ Adding Calling Card Information to a Phone Book Entry shows a telephone number that is set up to use a calling card number. In this example, the telephone number (4445551234) is preceded by a number that identifies the long distance carrier (102880) and a 0. After the telephone number is dialed, the modem pauses (,,) to wait for a gong tone before dialing the calling card number. The comma (,) dial modifier is used to instruct the modem to pause for 2 seconds. Use several commas for a longer delay. The comma is a dial modifier that is common to most modems. Any dial modifier defined for your modem can be entered in the Telephone number to be dialed field. For more information about dial modifiers, see your modem manual. Adding Calling Card Information to a Phone Book Entry ═══ 13.3.2. Maximum Number of Characters for a Telephone Number ═══ A LAN Distance telephone number field can contain a maximum of 50 characters. Your modem buffer may hold more or less than the maximum number of 50 characters. The dial prefix (ATDT) and suffix (\CR) transmitted with the telephone number reduces the buffer space for your modem by 5 characters. If the information for your calling card and telephone number exceeds the maximum number of 50 characters, you can customize the dial string in the PIF file for your modem type. For more information, see Modifying a Dial String for Outside Calls. ═══ 14. Dialing and Running LAN Applications ═══ This chapter describes how to establish LAN Distance connections and run LAN applications over the connections. This chapter applies only to LAN Distance Remotes and stand-alone LAN Distance Connection Servers. The following information is described in this chapter:  Establishing a LAN Distance connection  Running your LAN applications over a LAN Distance connection  Hanging up a LAN Distance connection  Customizing your dial setup ═══ 14.1. Establishing a LAN Distance Connection ═══ The actions you perform to establish a LAN Distance connection are much the same as those performed when placing a normal telephone call. These actions include the following: 1. Select a phone book entry and dial it. 2. Wait until the dialed workstation answers your call. 3. Exchange information, such as your user identification, with the dialed workstation. 4. After your connection is established, run your LAN applications over it. 5. End the call by hanging up. The concept of dialing and answering applies to connections made over switched and nonswitched lines (even though a telephone number is not required for nonswitched lines). To dial a LAN Distance workstation, first open the phone book using step Establishing a LAN Distance Connection or Establishing a LAN Distance Connection. Then complete step Establishing a LAN Distance Connection. 1. Open the LAN Distance Workstations window, and double-click on the MyWorkstation icon. 2. Open the LAN Distance Workstations window, and select the Phone Book from the Open as pull-down menu. 3. Select the phone book entry for the LAN Distance workstation that you want to call. The Phone Book window is shown in Phone Book Window. Note: If your country code is not US or Great Britain, tabs will not display in the Phone Book window. Phone Book Window Phone Book Entry Window Push Buttons describes the actions for the push buttons on the Phone Book window. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 24. Phone Book Entry Window Push Buttons │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ PUSH BUTTONS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ DIAL │ Select a phone book entry and push the DIAL push button to │ │ │ dial the phone book entry. │ │ │ │ │ │ Your phone book entry contains a call list of one or more │ │ │ telephone numbers. When you dial the phone book entry, the │ │ │ numbers in your call list are dialed in the order specified, │ │ │ until a successful connection is established or your dial │ │ │ retry limit is reached (see Customizing Your Dialing Setup). │ │ │ │ │ │ Having multiple telephone numbers for one phone book entry │ │ │ enables you to dial alternative numbers when you get busy │ │ │ signals. │ │ │ │ │ │ Logon is required when you dial a secure LAN Distance work- │ │ │ station (seeLogging On to a Secure LAN Distance │ │ │ Workstation). │ │ │ │ │ │ A secure LAN Distance workstation might perform callback │ │ │ when you place a call to it; callback is performed automat- │ │ │ ically (see Callback). │ │ │ │ │ │ The Phone Book Entry window is displayed for the duration of │ │ │ your call. Minimize the Phone Book Entry window if you do │ │ │ not want it displayed. Status indicates your call status, │ │ │ such as when it is in the process of connecting and when the │ │ │ connection is established. │ │ │ │ │ │ Use the Call and Port Management window to view and manage │ │ │ your calls (see Using System Management Tools). │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ ALTERNATE │ Change your call list temporarily. │ │ │ │ │ │ Update the call list to: │ │ │ │ │ │ o Dial a telephone number not included in the call list. │ │ │ o Specify a different dialing order. │ │ │ o Change telephone numbers. For example, you can add a │ │ │ calling card number to long distance telephone numbers. │ │ │ │ │ │ Use the push buttons to add, change, and delete telephone │ │ │ numbers in your call list. Reset ignores your changes. │ │ │ │ │ │ Changes to your call list are temporary; they are not dis- │ │ │ played the next time you open the phone book. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ HANG UP │ Hang up the call. │ │ │ │ │ │ Stop your LAN applications before hanging up a call. If │ │ │ they are still running when the call ends, they might detect │ │ │ connection errors and fail. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 14.2. Logging On to a Secure LAN Distance Workstation ═══ A user account must be set up for you on every secure LAN Distance workstation that you dial. When you dial a secure LAN Distance workstation, you are required to log on to it. When you log on, the LAN Distance product verifies your user ID and passphrase (if specified) with your user account on the secure LAN Distance workstation. If security is enabled on your workstation and the workstation you are dialing, two logons are required: one for your workstation and one for the dialed workstation. The second logon is attempted automatically for you when you dial. If your user ID and passphrase are the same for both workstations, the automatic logon succeeds. However, if your user IDs and passphrases are different, you are prompted to log on to the dialed workstation. You remain logged on to the secure LAN Distance workstation until:  You log off  The LAN Distance product is stopped on the secure LAN Distance workstation  Your connection to the secure LAN Distance workstation ends The Logon window displays as shown in Logon Window. Logon Window Use Logon as a guide for logging on to a secure LAN Distance workstation. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 25. Logon │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ USER ID │ Specify your user ID for the workstation │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PASSPHRASE │ Specify your passphrase. │ │ │ │ │ │ The LAN Distance product uses a passphrase, rather than a │ │ │ password, for user authentication. The passphrase allows │ │ │ imbedded spaces and mixed case characters so that you can │ │ │ create flexible and complex combinations. │ │ │ │ │ │ A passphrase is required for logon if one is defined in your │ │ │ user account on the secure LAN Distance workstation. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 14.3. Callback ═══ Your user account at a secure LAN Distance workstation can require that callback be performed for your calls. The procedure for callback is: 1. You dial and log on to the secure LAN Distance workstation. 2. The secure LAN Distance workstation hangs up. 3. The secure LAN Distance workstation calls you back. 4. Your workstation answers the callback call. 5. You are logged on automatically to the secure LAN Distance workstation again. Callback is performed only for calls originating from a LAN Distance Remote. Callback is performed to either a fixed or variable location. Fixed callback dials a pre-configured telephone number. Variable callback prompts you for a telephone number to dial. If your workstation is not already enabled to answer calls, auto answer is automatically activated so that you can receive the callback call. If auto answer cannot be activated, callback fails and your connection might not be established. ═══ 14.4. Starting and Running Your LAN Application ═══ When you run your LAN applications over LAN Distance connections, they operate as if they are being run over a LAN to other LAN workstations. You have a number of options for starting and running your LAN applications remotely:  Start your LAN application after you establish a LAN Distance connection.  Set up your phone book entry to automatically start your LAN application. See Automatically Starting a LAN Application for information about autostarting your LAN applications.  Create a command file that contains LAN Distance commands for dialing and application commands for running your LAN application. See Command Line Interface Reference for information about the LAN Distance command line interface. Note: The LAN Distance product performs no code page translation of the data it transmits over your wide area connections. Make sure your LAN applications handle any code page differences that might occur between workstations. ═══ 14.5. Ending a Call ═══ Your LAN Distance connection remains active until:  You hang up  The workstation you dialed hangs up  A connection problem occurs, such as a line failure  The LAN Distance product is stopped on your workstation or the dialed workstation To hang up a call, select Hang Up on the Phone Book window (see Phone Book Endtry Window Push Buttons in Establishing a LAN Distance Connection). You can also hang up a call through the Call and Port Management window (see Using System Management Tools). A pop-up message displays when your LAN Distance connection hangs up. If you do not want this notification, see Customizing Your Dialing Setup for instructions on disabling it. ═══ 14.6. Customizing Your Dialing Setup ═══ Configure your dial settings to enable and disable call event pop-up messages and to customize dial retry. To begin configuring your dial settings, open the Settings notebook and select the Dial tab. Use Settings Notebook, Dial Tab as a guide to customizing your dial settings. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 26. Settings Notebook, Dial Tab │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELD │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ INCOMING CALL │ Select whether a pop-up displays when an incoming call is │ │ │ received. │ │ │ │ │ │ This pop-up applies to only a LAN Distance Remote. It is │ │ │ part of your autoanswer setup. See Customizing Auto Answer │ │ │ Messages for a LAN Distance Remote for more information. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ UNEXPECTED │ Select whether a pop-up displays when a call that your work- │ │ DISCONNECT OF │ station has answered hangs up unexpectedly. │ │ INCOMING CALL │ │ │ │ This pop-up applies to only a LAN Distance Remote. It is │ │ │ part of your autoanswer setup. See Customizing Auto Answer │ │ │ Messages for a LAN Distance Remote for more information. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ UNEXPECTED │ Select whether a pop-up displays when a call that you dialed │ │ DISCONNECT OF │ hangs up unexpectedly. │ │ OUTGOING CALL │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ RETRY COUNT │ Specify the number of times your call list is retried. │ │ │ │ │ │ Use dial retry to give your calls additional chances to be │ │ │ answered. until a LAN Distance connection is successfully │ │ │ established or your dial retry limit is reached. Each tele- │ │ │ phone number in your call list is dialed once before │ │ │ starting the next dial retry. │ │ │ │ │ │ A value of 1 for RETRY COUNT means that your call list is │ │ │ dialed twice. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ RETRY │ Specify the number of seconds between dial retries. │ │ INTERVAL │ │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 14.7. Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection ═══ You can establish a LAN-to-LAN connection between a dialing LAN Distance Connection Server and an answering LAN Distance Connection Server on separate LANs. After the connection is established, LAN workstations on one LAN can access LAN workstations on the other LAN. See LAN-to-LAN Environments. Note: Do not use the LAN Distance product to establish a LAN-to-LAN connection between two LANs if any type of connection or a bridge already exists between the two LANs. To establish a LAN Distance connection between 2 LAN Distance Connection Servers: 1. Set up the filtering criteria required for your LAN-to-LAN environment, see the filtering considerations described in Improving Performance Factors. 2. The WAN segment ring number configured for the LAN Distance bridges on the 2 LANs you are connecting must match. (The LAN segment ring numbers must be different.) 3. Start the LAN Distance product on the dialing and answering LAN Distance Connection Servers. 4. From the dialing LAN Distance Connection Server, create a phone book entry to call the answering LAN Distance Connection Server. See Creating Phone Book Entries. 5. From the answering LAN Distance Connection Server, open the Settings notebook and select the Answer tab. 6. From the Answer mode list box on the Answer tab, select the answer mode needed to establish a connection with the dialing LAN Distance Connection Server. If an answer mode with the required criteria is not defined, create an answer mode by selecting the Add push button. With the required answer mode highlighted in the Answer mode list box, select the Change push button. Select the LAN-to-LAN connection check box for this answer mode to set up the answering LAN Distance Connection Server to receive calls from the dialing LAN Distance Connection Server. Note: Automatic filtering is disabled for ports that have answer modes configured to accept LAN-to-LAN connections. See Types of Filtering Supported for the LAN Distance Bridge. 7. Select the Start mode push button to activate this answer mode, or automatically start this answer mode by selecting Enable answer mode on startup. 8. From the dialing LAN Distance Connection Server, select the phone book entry created in step Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection to establish a LAN Distance connection with the answering LAN Distance Connection Server. ═══ 14.8. Using the Dial Request Applet for LAN Dial Out ═══ The dial request applet provided in the LAN Distance Connection Server product allows any OS/2 LAN workstation to request that a LAN Distance Connection Server establish a connection to an answering LAN Distance Connection Server or LAN Distance Remote. See LAN-to-LAN Environments. The dial request applet is made of 2 programs: LDMKCALL and LDACCEPT. To use the dial request applet to make a LAN-to-LAN connection:  Set up the LAN Distance Connection Servers to establish a LAN-to-LAN connection as described in Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection.  Set up LAN workstations to use LDMKCALL that require dial out capability.  Set up a dialing LAN Distance Connection Server to use LDACCEPT to receive call requests, and set up an answering LAN Distance Connection Server to answer calls. Note: The dial request applet uses NetBIOS. If your NetBIOS resources are not adequate, you can receive the following error message when you start LDMKCALL or LDACCEPT: Request resource(s) not available If you get this message, go to LAPS to increase one or more of these NetBIOS parameters: names, sessions, and commands (network control blocks). ═══ 14.8.1. Setting Up an OS/2 LAN Workstation ═══ To set up an OS/2 LAN workstation to dial out using the LDMKCALL program, complete these steps: 1. Install and configure the NetBIOS LAN protocol on the LAN workstation. NetBIOS can be configured through LAPS, which is provided with NTS/2 and MPTS. If you are running the LAN Requester product, NetBIOS is already configured. 2. Install the LDMKCALL program on your workstation. LDMKCALL is located in the WAL directory on the LAN Distance Connection Server.  Copy LDMKCALL.EXE from the WAL directory located on your LAN Distance Connection Server to a diskette by typing the following from an OS/2 command line. COPY LDMKCALL.EXE A:  From the LAN workstation, copy LDMKCALL.EXE from diskette to a drive and directory (path) location of your choice. The path you choose must be defined in the PATH statement in your CONFIG.SYS file. From an OS/2 command line, type: COPY a:LDMKCALL.EXE x:\ ═══ 14.8.2. Setting Up LAN Distance Connection Servers ═══ To set up the dialing LAN Distance Connection Server to use the LDACCEPT program, and set up the answering LAN Distance Connection Server to answer, complete the steps in Setting Up LAN Distance Connection Servers to Establish a LAN-to-LAN Connection. ═══ 14.8.3. Dialing Out from an OS/2 LAN Workstation ═══ Use the LDMKCALL program to make a call request to a LAN Distance Connection Server and to hang up a LAN Distance connection. ═══ 14.8.3.1. Dialing Out Using LDMKCALL and LDACCEPT ═══ To make a call request, complete these steps: 1. Set up the dialing LAN Distance Connection Server to dial and set up the answering LAN Distance Connection Server to answer. See the steps in Setting Up an OS/2 LAN Workstation and Setting Up LAN Distance Connection Servers. 2. If LAN Distance security is enabled on the answering LAN Distance Connection Server, it must also be enabled on the dialing LAN Distance Connection Server. See Enabling and Disabling the LAN Distance Bridge. If security is enabled on both LAN Distance Connection Servers, the user ID and passphrase used to logon to the dialing LAN Distance Connection Server must also be defined in the user account database at the answering LAN Distance Connection Server. See Creating User Accounts. 3. Start the LDACCEPT program on the dialing LAN Distance Connection Server by typing LDACCEPT at an OS/2 command prompt. The name of the NetBIOS session is displayed when the LDACCEPT program is started, for example LDLS400012345678. The LAN workstation uses the NetBIOS session name to send dial or hangup requests to the dialing LAN Distance Connection Server The dialing LAN Distance Connection Server is ready to accept call requests from LAN workstations. 4. From the LAN workstation, go to an OS/2 command prompt, and type: LDMKCALL /D:directoryname /S:netbiosname /N:phonenumber /A:adapter /D:directoryname This parameter is required. It is the name of the phone book entry at the dialing LAN Distance Connection Server that is used to establish the connection. /S:netbiosname This parameter is required. It is the applet's NetBIOS name that receives the call request. This NetBIOS name is displayed at the dialing LAN Distance Connection Server when the LDACCEPT applet is started. /N:phonenumber This parameter is optional. If a phone number is not supplied, the phone number in the phone book entry is used. If a phone number is provided, it overrides the phone number in the phone book entry. /A:adapter This parameter is optional. Specify the NetBIOS adapter number (0-15) to be used by the dial request applet. The NetBIOS adapter number defaults to 0. 5. The LDMKCALL program sends a dial or hang up request to the LAN Distance Connection Server that issues the LDIST DIAL or LDIST HANGUP command. The results of these commands are displayed following the LDMKCALL command. Refer to the Command Line Interface Reference for a description of the LDIST command. ═══ 14.8.3.2. Ending a Connection Using LDMKCALL ═══ You can end a connection started using the LDMKCALL program from any LAN Distance Connection Server or LAN workstation that has the LDMKCALL program installed. To end a connection, complete these steps: 1. From the LAN workstation, go to an OS/2 command prompt, and type: LDMKCALL HANGUP /D:directoryname /S:netbiosname /A:adapter /D:directoryname This parameter is required. It is the name of the phone book entry at the dialing LAN Distance Connection Server that is used to establish the connection. /S:netbiosname This parameter is required. It is the name of the LAN Distance Connection Server dial request applet used to establish the connection, for example LDLS400012345678. /A:adapter This parameter is optional. Specify the NetBIOS adapter number (0-15) to be used by the dial request applet. The NetBIOS adapter number defaults to 0. ═══ 15. Answering Incoming Calls ═══ Choose whether or not your workstation accepts incoming calls and, optionally, configure which LAN Distance ports are used to answer those calls. Your ports must be set up before your workstation can answer calls. See Setting Up Ports and Modems for information about LAN Distance ports. This chapter describes how to:  Enable and disable the autoanswer feature  Customize your answer criteria  Automatically start your LAN applications after a LAN Distance connection is established  Receive notification of incoming calls (LAN Distance Remote only) ═══ 15.1. Auto Answer and Answer Modes ═══ Autoanswer allows your workstation to answer incoming calls automatically. Calls are accepted or rejected without any active intervention by you. An answer mode is an answering state for a workstation and it is based on a set of answer criteria that determine which incoming calls are accepted. For example, your workstation can be configured to accept calls over only a specific leased line. Include the name of the leased line in the answer criteria for an answer mode and activate the answer mode to answer calls over only that leased line. Two answer modes are installed on your workstation:  PSTN_ALL_CALLS  ISDN_ALL_CALLS When they are activated, your workstation can accept all incoming calls for a connection type. Two additional answer modes, used only for callback, are installed on a LAN Distance Remote:  CALLBACK_PSTN  CALLBACK_ISDN These answer modes are used by the phone book to place the LAN Distance Remote in autoanswer mode if a LAN Distance Connection Server is configured to call the LAN Distance Remote back. To activate or deactivate autoanswer on your workstation: 1. Open the Settings notebook and select the Answer tab. 2. Select an Answer mode. 3. Select one of the radio buttons, as appropriate: Start mode Stop mode 4. Repeat these steps for every answer mode you want to activate or deactivate. Note: These steps activate autoanswer one time only. To activate the answer mode the next time you run the LAN Distance product, you must perform the same steps again. The Answer page of the Settings notebook displays as shown in Settings Notebook, Answer Tab. Settings Notebook, Answer Tab To automatically activate an answer mode every time you run the LAN Distance product: 1. Open the Answer tab of the Settings notebook. 2. Select answer mode you want to automatically activate. 3. Select the Change push button. 4. Check Enable answer mode on startup. 5. Repeat these steps for every answer mode you want to activate automatically. ═══ 15.2. Customizing Your Answer Modes ═══ The answer criteria for an answer mode determines which calls your workstation answers. To begin customizing an answer mode open the Settings notebook and select the Answer tab. Select a push button to perform an action for an answer mode. Your changes are saved when you close the Answer page of the Settings notebook. Entry Type Window - Settings describes the Entry Type Window - Settings that is displayed when you add an answer mode. Use Asynchronous or Synchronous (PSTN) Switched Line Connections, Asynchronous or Synchronous Leased Line Answer Modes, and ISDN Switched Line Answer Mode as guides to set up answer modes for specific connection and line types. Set up at least one answer mode for every WAN connection type over which your workstation accepts calls. Also, a separate answer mode is required for each leased line on your workstation. The Copy push button sets up a new answer mode using information from an existing answer mode. Name your new answer mode, close the Answer page of the Settings notebook to save it, and then select the Change push button to customize your new answer mode. If you delete an active answer mode, it remains active until you disable it or you stop the LAN Distance product. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 27. Entry Type Window - Settings │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELD │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ NETWORK TYPE │ Select the connection type for the answer mode: │ │ │ │ │ │ PSTN - Public Systems Telephone Network (asynchronous or │ │ │ synchronous) │ │ │ │ │ │ ISDN - Integrated Services Digital Network │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ LINE TYPE │ Select the line type for the answer mode: │ │ │ │ │ │ Switched │ │ │ │ │ │ Nonswitched (leased or permanent connection) │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 15.2.1. Asynchronous and Synchronous (PSTN) Switched Line Connections ═══ Use Asynchronous or Synchronous Switched Line Answer Modes as a guide for setting up an answer mode for an asynchronous or synchronous switched line connection. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 28. Asynchronous or Synchronous Switched Line Answer Modes │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ANSWER │ ANSWER MODE │ Specify a name for the answer mode. │ │ │ NAME │ │ │ │ │ The name of your answer mode must be unique on │ │ │ │ your workstation. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DESCRIPTION │ Describe the answer mode. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ENABLE ANSWER │ Select whether you want to automatically acti- │ │ │ MODE ON │ vate the answer mode every time you start the │ │ │ STARTUP │ LAN Distance product. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ PORT │ ALL PORTS │ Select whether you will accept calls on all or │ │ │ SPECIFIC PORTS │ specific ports. │ │ (Optional) ├────────────────┼────────────────────────────────────────────────┤ │ │ PORT LIST │ Select which ports are allowed to answer │ │ │ │ calls. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ AUTOSTART │ AUTOSTART │ Start a LAN application automatically after a │ │ │ PROGRAM WHEN │ connection is successfully established using │ │ (Optional) │ CONNECTION │ this answer mode. │ │ │ ESTABLISHED │ │ │ │ │ Use Autostart Tab, Answer Mode as a guide for │ │ │ │ setting up the Autostart as a guide for │ │ │ │ setting up the Autostart feature. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 15.2.2. Asynchronous and Synchronous (PSTN) Leased Line Connections ═══ Use Asynchronous or Synchronous Leased Line Answer Modes as a guide for setting up an answer mode for an asynchronous or synchronous leased line connection. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 29. Asynchronous or Synchronous Leased Line Answer Modes │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ANSWER │ ANSWER MODE │ Specify a name for the answer mode. │ │ │ NAME │ │ │ │ │ The name of your answer mode must be unique on │ │ │ │ your workstation. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DESCRIPTION │ Describe the answer mode. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ENABLE ANSWER │ Select whether you want to automatically acti- │ │ │ MODE ON │ vate the answer mode every time you start the │ │ │ STARTUP │ LAN Distance product. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ CONNECT │ MODEM │ Select the modem type for the leased line for │ │ │ │ the answer mode. │ │ │ │ │ │ │ │ The modem types that are assigned leased lines │ │ │ │ are displayed in the list box. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ LEASED LINE │ Specify the name of the leased line that can │ │ │ NAME │ accept incoming calls. │ │ │ │ │ │ │ │ Your leased line names are displayed after you │ │ │ │ select your modem. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ENCODING │ For a synchronous connection, select the │ │ │ SCHEME │ dialing workstation's modem encoding scheme. │ │ │ │ │ │ │ │ Two encoding schemes are supported: NRZ and │ │ │ │ NRZI. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ AUTOSTART │ AUTOSTART │ Start a LAN application automatically after a │ │ │ PROGRAM WHEN │ connection is successfully established using │ │ (Optional) │ CONNECTION │ this answer mode. │ │ │ ESTABLISHED │ │ │ │ │ Use Autostart Tab, Answer Mode as a guide for │ │ │ │ setting up the Autostart as a guide for │ │ │ │ setting up the Autostart feature. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 15.2.3. ISDN Switched Line Connections ═══ Use ISDN Switched Line Answer Mode as a guide for setting up an answer mode for an ISDN switched connection. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 30. ISDN Switched Line Answer Mode │ ├────────────┬────────────────┬────────────────────────────────────────────────┤ │ TAB │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ ANSWER │ ANSWER MODE │ Specify a name for the answer mode. │ │ │ NAME │ │ │ │ │ The name of your answer mode must be unique on │ │ │ │ your workstation. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ DESCRIPTION │ Describe the answer mode. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ ENABLE ANSWER │ Select whether you want to automatically acti- │ │ │ MODE ON │ vate the answer mode every time you start the │ │ │ STARTUP │ LAN Distance product. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ LOCAL │ ALL TELEPHONE │ Select whether any channel or specific chan- │ │ │ NUMBERS │ nels can answer calls. │ │ (Optional) │ SPECIFIC TELE- │ │ │ │ PHONE NUMBERS │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CURRENT LOCAL │ Select the telephone numbers of the channels │ │ │ TELEPHONE │ that can accept calls. │ │ │ NUMBERS │ │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ NUMBERS │ ACCEPT ALL │ Select whether and how to screen calls from │ │ │ CALLS │ specific telephone numbers. │ │ │ ACCEPT ONLY │ │ │ │ CALLS FROM │ │ │ │ SPECIFIC │ │ │ │ NUMBERS │ │ │ │ REJECT CALLS │ │ │ │ FROM SPECIFIC │ │ │ │ NUMBERS │ │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ CURRENT │ View the telephone numbers from which you │ │ │ CALLING NUMBER │ accept or reject calls. │ │ │ FILTERS │ │ │ │ │ Select a push button to add, change, or delete │ │ │ │ a telephone number in your filters. A window │ │ │ │ containing these fields is displayed when you │ │ │ │ add or change a telephone number: │ │ │ │ │ │ │ │ o Telephone number │ │ │ │ o Screening indicator │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ TELEPHONE │ Specify a telephone number from which you will │ │ │ NUMBER │ accept or reject calls. │ │ ├────────────────┼────────────────────────────────────────────────┤ │ │ SCREENING │ Select whether the telephone number is sup- │ │ │ INDICATOR │ plied by the network, the dialing workstation, │ │ │ │ or either. │ ├────────────┼────────────────┼────────────────────────────────────────────────┤ │ AUTOSTART │ AUTOSTART │ Start a LAN application automatically after a │ │ │ PROGRAM WHEN │ connection is successfully established using │ │ (Optional) │ CONNECTION │ this answer mode. │ │ │ ESTABLISHED │ │ │ │ │ Use Autostart Tab, Answer Mode as a guide for │ │ │ │ setting up the autostart as a guide for │ │ │ │ setting up the autostart feature. │ └────────────┴────────────────┴────────────────────────────────────────────────┘ ═══ 15.3. Starting Your LAN Application Automatically ═══ Configure your answer criteria to automatically start a LAN application or a command file on your workstation after you answer a call and establish a LAN Distance connection. The tasks in this section apply to LAN applications and command files. To configure autostart settings for an existing answer mode: 1. Open the Settings notebook, and select the Answer tab. 2. Select an answer mode. 3. Select the Change push button. 4. Select the Autostart tab. Use Autostart Tab, Answer Mode as a guide for configuring your autostart settings. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 31. Autostart Tab, Answer Mode │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ ENTRY FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ AUTOSTART │ Start a LAN application automatically after a connection is │ │ PROGRAM WHEN │ established using this answer mode. │ │ CONNECTION │ │ │ ESTABLISHED │ The LAN application is automatically started on the │ │ │ answering workstation. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PROGRAM TITLE │ Specify the program name for the OS/2 Window List. │ │ │ │ │ │ This name is added to the OS/2 window list after the LAN │ │ │ Distance product starts your LAN application. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PATH AND FILE │ Specify the fully-qualified name of your LAN application. │ │ NAME │ │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PARAMETERS │ Specify the input parameters to your LAN application. │ │ (Optional) │ │ │ │ If your LAN application allows input parameters, specify │ │ │ their values here. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ PROGRAM TYPE │ Specify your LAN application program type. │ │ │ │ │ │ Choose a program type: │ │ │ │ │ │ o Default │ │ │ o CMD │ │ │ o Full-screen │ │ │ o PM │ │ │ o Windowed │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ INITIAL │ Specify the window size for your LAN application. │ │ WINDOW SIZE │ │ │ │ Choose a window size: │ │ │ │ │ │ o Normal │ │ │ o Maximized │ │ │ o Minimized │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ START IN │ Select whether your LAN application is to be started in the │ │ │ foreground or background. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 15.4. Customizing Auto Answer Messages for a LAN Distance Remote ═══ Pop-up messages notify you when an incoming call ends unexpectedly, such as when your connection experiences a line failure. A pop-up message also displays when a call is received and accepted by your workstation. The pop-up message is displayed until you acknowledge them. If you do not want to be notified of these call events, disable the messages. To specify when you receive pop-up messages: 1. Select Settings and select the Dial tab. 2. Choose whether to display pop-up messages for: Incoming call Unexpected disconnect of incoming call ═══ 16. Troubleshooting Tips ═══ This chapter contains troubleshooting tips for these situations:  Error messages during LAN Distance Remote for MS Windows installation  Restoring a LAN Distance Connection Server if you interrupt installation  Message WCL0233 displays when you start the LAN Distance product  Message WCL0567  Message WCL0589 and WCL0219  Message VL10128 displays when you start the LAN Distance Connection Server  Virtual LAN kernel message displays  LAN Distance COM port flooded with LAN data  Problems establishing a LAN Distance connection  Problems running IBM LAN Server and Requester  IBM Communication Manager/2 3270 emulation error message displays  Unable to communicate with the Banyan VINES Server.  Avoiding the NetWare connection error on the NetWare Requester  Delay when starting up your LAN application ═══ 16.1. Error Messages During LAN Distance Remote for MS Windows Installation ═══ If the upper memory on your DOS workstation is not being utilized correctly, when you install the LAN Distance Remote for MS Windows product, you can receive error messages similar to these: Severe error writing to drive C: Application error A decompression error has occurred... If you receive such an error message, verify that the parameter values specified for the DEVICE=EMM386.SYS (or equivalent) statement in your CONFIG.SYS are correct, or comment out the EMM386 line in your CONFIG.SYS file. If you make changes to the CONFIG.SYS file, stop all applications, restart your workstation, then install the LAN Distance Remote for MS Windows product again. ═══ 16.2. Restoring Your Workstation If You Interrupt Installation ═══ If you interrupt installation, try using the LDREMOVE program to restore your workstation. Follow the steps in Removing the LAN Distance Connection Server Product. If the LDREMOVE (or LDREM) program is successful, your workstation is restored, and you can install the LAN Distance product after you shut down and restart your workstation. If the LDREMOVE program fails, follow these steps before you shut down and restart your workstation: 1. Remove the following statements from your CONFIG.SYS file: DEVICE=C:\OS2INSTALL\IBMLANLK.SYSRUN=C:\OS2\INSTALL\IBMLANLK.EXE C:\OS2\INSTALL\WALLOCK.LST 2. Run the LDREMOVE program. If LDREMOVE is successful, then your workstation is restored and you can install the LAN Distance product after you shut down and restart your workstation. ═══ 16.3. Avoiding Message WCL0233 When Restarting Your Workstation ═══ This message is displayed if 1) you have a workstation with non-FIFO COM ports and 2) the serial port speed for the COM port is set to 38400 bps or greater. Because workstations without FIFO buffering generally cannot support transmission speeds exceeding 9600 bps, the LAN Distance product automatically resets this value. To keep this message from displaying each time you start the LAN Distance product, change the value of the SerialPortSpeed parameter in the WCLNET.INI file to 9600 bps. (If you prefer, you can change this parameter in the PIF file for your modem). 1. Stop the LAN Distance product. 2. From an OS/2 command prompt, go to the WCLNET.INI file in the WAL directory. 3. In the WCLNET.INI file, locate the SerialPortSpeed parameter. Use an ASCII editor to change the SerialPortSpeed value to 9600 bps. 4. Close the WCLNET.INI file and save your changes. 5. Restart the LAN Distance product. Note: Some non-FIFO machines with faster processors (25 MHz and above) and modems (14400 bps or better) can support higher transmission speeds, see Performance Tuning for Non-FIFO Workstations. ═══ 16.4. Message WCL0567 ═══ This message indicates that the LAN Distance logical adapter (PDFH) is not correctly configured for use by Remote Access Services (PPP Server). Follow the steps below to verify that the LAN Distance logical adapter is correctly configured. 1. Use MPTS or the LAN Services Installation/Configuration program to view the protocols that are bound to the LAN Distance logical adapter. If neither "IBM OS/2 NetBIOS" nor "IBM OS/2 NetBIOS over TCPIP" are bound to the LAN Distance logical adapter, add one of them to the adapter. If the LAN Distance logical adapter is correctly configured, note the number of logical adapters that are configured and the logical adapter numbers that are assigned to the protocols that are bound to the LAN Distance logical adapter. 2. Use an editor to view the value that is assigned to the ADAPTER parameter in the SRDDEFS section in WCLLOCAL.INI. This value tells Remote Access Services (PPP Server) how many logical adapters it needs to initialize for use with "IBM OS/2 NetBIOS" or with "IBM OS/2 NetBIOS over TCPIP". The default value is 2. If you have assigned a logical adapter value greater than 1 to the "IBM OS/2 NetBIOS" or "IBM OS/2 NetBIOS over TCPIP" protocols that are bound to the LAN Distance logical adapter, then you can change the configuration in one of two ways: a) Use MPTS or the LAN Services Installation/Configuration program to reorder the logical number assignments such that the LAN Distance logical adapter protocols mentioned above have assignments of 0 or 1. b) Or, use the editor to increase the value for the ADAPTER parameter in the SRDDEFS section in WCLLOCAL.INI as appropriate. ═══ 16.5. Message WCL0589 ═══ These messages 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 Creating a New PIF File for a Modem Not in the List. ═══ 16.6. Message VL10128 at OS/2 System Start Up ═══ This message is displayed when you reboot your Connection Server and is saved in the \IBMLAN\LANTRAN.LOG file. It indicates that the MAC frame size configured for the Token-Ring adapter is smaller than the maximum data unit size (MAC frame size) configured for the LAN Distance Connection Server product.  If you are using an IBM Token-Ring 16/4 adapter, complete the steps listed in Increasing the Shared RAM Size on Token-Ring 16/4 Adapters.  If you are using an IBM Token-Ring /A adapter, complete the steps listed in Changing Parameters for Token-Ring/A Adapters. ═══ 16.6.1. Increasing the Shared RAM Size on Token-Ring 16/4 Adapters ═══ To support remote access, the Token-Ring LAN adapter on the LAN Distance Connection Server should have a shared RAM size of 16 KB. When you installed the adapter, its shared RAM size is defaulted to a value less than 16 KB.  For micro channel adapters, use the reference diskette for the Token-Ring adapter to change the shared RAM size to 16 KB.  For non-micro channel adapters, see your adapter documentation for instructions on setting the shared RAM size for your adapter to 16 KB. ═══ 16.6.2. Changing Parameters for Token-Ring/A Adapters ═══ Change the following parameters only if you are using a Token-Ring/A adapter on the LAN Distance Connection Server: 1. Open the Settings notebook and select the Bridge tab. 2. Change the value in the Maximum data unit size field to 1500. 3. Select the LAPS tab, then select the LAPS push button to open the LAPS Configure Workstation window. 4. From the Current Configuration list box, select your Token-Ring adapter, then select Edit. 5. Scroll to the Bridge transmit control RAM field, and change the value to 5296. Select the OK push button. 6. To save your configuration changes, exit LAPS, close the Settings notebook, then shut down and restart your workstation. ═══ 16.7. Virtual LAN Kernel Message ═══ The following message may be saved in the \IBMLAN\LANTRAN.LOG file when you restart your workstation after installing the the LAN Distance Connection Server product. This message does not indicate a problem. It is the result of the LAN Distance virtual LAN kernel device driver attempting to locate the FFST/2 device driver. The IBM Virtual LAN Kernel could not attach to the FFST/2 device driver EPWDD.SYS ═══ 16.8. LAN Distance Remote COM Port Flooded with LAN Data ═══ If the LAN Distance Remote COM port is flooded with LAN data, you may notice some or all of the following problems:  Inability to transfer data or slow data transfer  The receive data light for your LAN Distance Remote modem is constantly lit  The LAN Distance connection drops unexpectedly  Inability to log on to a LAN Distance Connection Server If you experience any of these problems, filtering may not be set up at the LAN Distance bridge or the Token-Ring route designator defined for the LAN Distance bridge may not be unique. See Types of Filtering Supported for the LAN Distance Bridge and Defining LAN Distance Bridge Token-Ring Configuration Values. ═══ 16.9. Problems Establishing a LAN Distance Connection ═══ You can experience problems establishing or maintaining a LAN Distance connection. The most common causes of connection problems are related to your LAN Distance configuration and your communications hardware setup. This section describes steps to correct connection problems caused by the following:  Answer mode not started at the LAN Distance Connection Server  Modem fails to initialize  Defective modem cable  Filtering is not enabled at the LAN Distance Connection Server  FIFO transmit size needs adjusting  Secure LAN Distance workstation does not call back  Duplicate LAN adapter address  Non-LAN-Distance destination mis-match  External modem configuration overriding LAN Distance modem settings  COM port speed needs adjusting ═══ 16.9.1. Answer Mode Not Started at the LAN Distance Connection Server ═══ If an answer mode is not started at the dialed LAN Distance workstation, one of the error messages is displayed. In this situation, LAN Distance appears to establish a connection, but then drops the connection. WCL0318W: The remote modem is not answering. The call cannot be connected. WCL0334W: The called workstation rejected the call. The call cannot be connected. WCL0336E: The called workstation did not respond to requests to exchange information with the LAN Distance product. WCL0340E: The called workstation is not responding. The call cannot be connected. To start an answer mode at a LAN Distance Connection Server, see Auto Answer and Answer Modes. ═══ 16.9.2. Modem Fails to Initialize ═══ If you dial out to establish a connection with a LAN Distance workstation and receive a message similar to one of the following, your modem may not be properly configured to use the LAN Distance product. Your modem may appear to establish a connection, but the "Connected" message is never displayed in the Status field of the phone book. WCL0221: LAN Distance could not initialize the modem. WCL0336E: The called workstation did not respond to requests to exchange information with the LAN Distance product. To check your modem configuration, try any of the following recommendations that apply to your modem setup. ═══ 16.9.2.1. Asynchronous Switched Modem ═══ If you are setting up the LAN Distance product to use an asynchronous switched modem, your modem is either listed or not listed in the Available modem types field.  If your modem is listed, verify that the modem type you selected matches your modem.  If your modem is not listed, verify that the modem you selected is "similar" to your modem. See Using a Listed Modem Type to Configure Your Asynchronous Modem. Note: You can use the Port/Modem utility to select and test the connection between a similar modem and a COM port. See Using the Port/Modem Utility. ═══ 16.9.2.2. Synchronous Modem, Null Modem or Leased Line ═══ If you are setting up the LAN Distance product to use a synchronous modem, a null modem, or a leased line, select the appropriate generic modem type from the Available modem types list box. See Using Synchronous Modems and Leased Lines. ═══ 16.9.2.3. Custom PIF File ═══ If you created a custom PIF file using a similar modem as a template and continue to experience connection problems, check the following configuration values in the PIF file you created. Note: You can also use the Port/Modem utility to test the PIF file you created. See Using the Port/Modem Utility. DTE Rate The initialization string for your modem must set the DTE rate to "fixed". This is the speed at which data is passed between the serial port and the modem. AutoBaudDetect The Default keyword in the AutoBaudDetect section of the PIF file should be set to "off". DSR (Data Set Ready) Signal The initialization string for your modem must set the modem DSR signal to go from on to off when a connection ends. (For most modems, the correct command is &S1.) Use your modem manual to verify the correct command for your modem. CD (Carrier Detect) The initialization string for your modem must be set so the modem tracks the status of the carrier detect signal. (For most modems, this command is &C1.) Use your modem manual to verify the correct command for your modem. Some modem manuals refer to the CD as the DCD or RLSD. Flow Control The LAN Distance product requires hardware (RTS/CTS) flow control. Verify that the initialization parameters for your modem use RTS/CTS line signals for flow control, and do not use XON, XOFF characters for flow control. ═══ 16.9.2.4. IBM 7855 Modem ═══ External configuration is required to use the IBM7855 modem with the LAN Distance product. See External Settings for the IBM7855 Modem. ═══ 16.9.3. Defective Modem Cable ═══ If the following message is displayed when you try to establish a connection to a LAN Distance Remote or LAN Distance Connection Server, the workstation you dialed may have a defective modem cable. Some modems are more sensitive to cable wiring than others. Test the modem cable on the dialed workstation using another asynchronous software product. OS/2 version 2.1 users can access the PM Terminal product in the Productivity folder on the WorkPlace Shell. Or switch the modem cable attached to the dialed workstation with a cable that you know is functioning. WCL0336E: The called workstation did not respond to requests to exchange information with the LAN Distance product. ═══ 16.9.4. Filtering Is Not Enabled at the LAN Distance Connection Server ═══ If filtering is disabled at the LAN Distance Connection Server, the LAN Distance connection can quickly become flooded with LAN data frames. You may notice the following symptoms:  Inability to transfer data or slow data transfer rate  The receive data light on your modem is constantly lit  The LAN Distance connection drops unexpectedly  Inability to log on to a LAN Distance Connection Server To enable filtering for the LAN Distance Connection Server, see Customizing Filtering Criteria. ═══ 16.9.5. FIFO Transmit Size Needs Adjusting ═══ If your modem does not support the default FIFO transmit size (14) used by the LAN Distance product, you can experience time-outs, random disconnects, and slow response times when running LAN applications over a LAN Distance connection. Most modems will accept the default value. For some modems, including the Hayes Optima 9600 and the Hayes Ultra 9600, you may need to lower the LAN Distance FIFO transmit size to 7 (or the recommended value) if you experience these problems. The recommend value for the parameter is n-1, where n is the size of the FIFO buffer for your modem. To change the FIFO transmit size for your modem: 1. Open the Settings notebook and select the Ports tab. 2. From the Configured ports field, select your COM port, then select the Change push button. 3. From the COM port tab, specify a number in the Transmit FIFO size (0-16) field to replace the default. 4. Close the COM port tab and close the Ports tab. 5. Close the Settings notebook. 6. Stop the LAN Distance product and shut down and restart your workstation so this change can take effect. ═══ 16.9.6. Secure LAN Distance Workstation Does Not Call Back ═══ If you dial a secure LAN Distance workstation and a "Waiting for Callback" message is displayed indefinitely in the Status field of the Phone Book, the secure LAN Distance workstation may fail to respond for one of these reasons:  The secure LAN Distance workstation is turned off, or the LAN Distance product is not started. Verify that the secure LAN Distance workstation is turned on and the LAN Distance product is started.  The phone book entry the secure LAN Distance workstation uses to call back the dialing workstation is incorrect. Check the phone book entry name and the information defined for the phone book entry. ═══ 16.9.7. Using Duplicate LAN Adapter Address ═══ If a connection to a LAN Distance Connection Server is established temporarily, then the following message is displayed. WCL0310W: The call to 'EntryName' has disconnected. This message may be displayed because your LAN Distance logical adapter network address not unique. Consult your LAN administrator to find out if your LAN Distance logical adapter network address is assigned to a resource on the LAN. To specify a new LAN Distance logical adapter network address, complete these steps: 1. Open the Settings notebook and select the Address tab. 2. Specify a new address in the LAN Distance logical adapter network address field. 3. Close the Settings notebook, then shut down and restart your workstation so your new address is active. ═══ 16.9.8. WCL0336E Message for Non-LAN Distance Destination Mismatch ═══ The Connect to a non-LAN Distance destination field must be the same (enabled or disabled) on the dialing and answering workstations to establish a connection. If this selection is different, one of the following error messages is displayed. WCL0336E: The called workstation did not respond to requests to exchange information with the LAN Distance product. WCL0310W: The call to 'EntryName' has disconnected. In general, the Connect to a non-LAN Distance destination option should not be selected. If neither workstation has LAN Distance security enabled, you can select the Connect to a non-LAN Distance destination field to improve performance of the LAN Distance connection. To verify or change the setting for Connect to a non-LAN Distance destination: 1. Open the Settings notebook and select the Workstation tab. 2. Change the Connect to a non-LAN Distance destination. 3. Close the Settings notebook. 4. Close the LAN Distance Workstations and shut down and restart your workstation to make this change effective. ═══ 16.9.9. External Modem Configuration Overriding LAN Distance Modem Settings ═══ If you have problems using your modem with the LAN Distance product, the external configuration settings for your modem may be overriding some of the configuration settings (AT commands) required by the LAN Distance product. Use your modem manual to assure the external settings of your modem do not override the required settings for the LAN Distance product described in Creating a New PIF File for a Modem Not in the List. Most modems can be configured to work with the LAN Distance product simply by selecting the supported modem (PIF file) from the Available modem types list box. However, some modems such as the IBM 7855 modem, require external configuration to work with the LAN Distance product. See Modems Requiring External Configuration. ═══ 16.9.10. Serial (COM) Port Speed Needs Adjusting ═══ If the value for the SerialPortSpeed parameter in the WCLNET.INI file is too large, you can experience trouble establishing and maintaining a LAN Distance connection. Errors indicating that your FIFO or non-FIFO serial port speed is too large include WCL0221, WCL0336, and spontaneous disconnects. If you experience these errors, reduce the value of the SerialPortSpeed parameter in the WCLNET.INI file: 1. Stop the LAN Distance product. 2. Open the WCLNET.INI file in the WAL directory and locate the SerialPortSpeed value. 3. Using any text editor, try reducing this value as follows:  38400 to 19200  19200 to 14400(**)  14400 to 9600 4. Close the WCLNET.INI file and save your changes. Note: If you later change port and modem assignments through the Settings notebook, the WCLNET.INI file is recreated and changes made to the SerialPortSpeed parameter are not saved. 5. Start the LAN Distance product. ═══ 16.10. Problems Using Point-to-Point Protocol ═══ If you are using point-to-point protocol (PPP), you might have problems with the following:  Establishing a PPP connection  Using the password authentication protocol (PAP) or the challenge-handshake authentication protocol (CHAP)  Resolving the IP address for a PPP connection The following sections provide information about how you can correct these problems. ═══ 16.10.1. Problems Establishing a PPP Connection ═══ If you are unable to establish a point-to-point protocol (PPP) connection, check the following:  Check the settings notebook and make sure auto startup for the connection server services is set.  Check the port/modem status. From the LAN Distance - Workstation window, choose Selected, Open as, and call and port management. ═══ 16.10.2. Problems Using PAP or CHAP Authentication ═══ If you are having problems using either the password authentication protocol (PAP) or the challenge-handshake authentication protocol (CHAP), check the following:  Check that the Security Enabled setting is properly configured in the settings notebook  Ensure that the correct authentication setting is specified in the \WAL\WCLLOCAL.INI file. In the file, the PPPsecurity parameter can be set to PAP, CHAP, or both. For more information, see Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File. ═══ 16.10.3. Problems Resolving IP Addresses for PPP Connections ═══ If you are having problems resolving IP addresses for a PPP connection, check the following:  Ensure that the correct IP address options are specified in the \WAL\WCLLOCAL.INI file. In the file, you can set the ObtainIPaddr parameter to LIST, DHCP, and USERSPEC. For more information, see Specifying PPP Parameters in the \WAL\WCLLOCAL.INI File.  If you specify the USERSPEC option for the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file, check the IP address configuration on the client workstation.  If you specify the LIST option for the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file, check that the \WAL\WCLIPADR.INI file has a sufficient number of addresses to equal the number of PPP connections. For more information, see Using the Local IP Address Listing.  If you specify the DHCP option for the ObtainIPaddr parameter in the \WAL\WCLLOCAL.INI file, check that a DHCP server is available on the network and that the server is configured correctly. ═══ 16.11. Problems Running DOS LAN Requester ═══ The following problems can occur when using the IBM LAN Server and Requester products with the LAN Distance product.  DOS LAN Requester cannot start  Inability to log on to the LAN Server Domain Controller Before trying any of the solutions described here, verify that your LAN Server and LAN Requester workstations are set up correctly. See Using LAN Server and LAN Requester. ═══ 16.11.1. DOS LAN Requester Cannot Start ═══ If you start DOS LAN Requester after you start MS Windows, you will receive the following message: Cannot start because of a program conflict To resolve this error, start DOS LAN Requester before you start MS Windows by typing NET START from a DOS command line. If you want to autostart DOS LAN Requester, add the NET START statement to the AUTOEXEC.BAT file. ═══ 16.11.2. Inability to Log On to the LAN Server Domain Controller ═══ If you are running version 2.0 or 3.0 of the DOS LAN Requester product on a MS Windows LAN Distance Remote, you may experience problems logging on to the LAN Server Domain Controller. The DOS LAN Requester code incorrectly defaults the mailslot number to 0 instead of 3. To avoid logon problems, install CSD IPO7003 for the DOS LAN Requester product. This CSD correctly defaults the mailslot number to 3. If you do not have access to this CSD, make the following change to the /NMS (mailslot number) parameter: 1. From the MS Windows RUN command line, open the DOSLAN directory and locate the DOSLAN.INI file. 2. Use an ASCII editor to change the value for /NMS:0 to /NMS:3. ═══ 16.12. Problems Running IBM LAN Server and Requester ═══ The following problems can occur when using the IBM LAN Server and Requester.  Logon problems  Large file copy problems  Insufficient NetBIOS resources ═══ 16.12.1. Logon Problems with IBM LAN Server 2.0 ═══ If you install the LAN Server 2.0 product after installing the LAN Distance product, you may experience problems when you try to log on to the LAN Server from the LAN Distance Remote running LAN Requester. The following messages indicate a compatibility problem between the NetBIOS driver shipped with the LAN Distance product and the NetBIOS driver shipped with LAN Server 2.0. LAN Requester failing to start. or Failed logon attempt. If you enter NET ERROR at the OS/2 command prompt, the following messages are displayed: NET3106: An unexpected NCB was received. NET3140: The service has stopped due to repeated consecutive occurrence of an NCB error. To resolve this error, make the NetBIOS driver required by the LAN Server 2.0 product the active NetBIOS driver. 1. From an OS/2 command prompt, type: cd \IBMCOM\PROTOCOL 2. Make the NetBIOS driver used by IBM LAN Server 2.0 active by typing the following command: COPY A:\NETBIOS.LS2 NETBIOS.OS2 3. Shut down and restart your LAN Distance workstation. ═══ 16.12.2. Inability to Log On to the LAN Server ═══ If you can establish a connection from the LAN Distance Remote to the LAN Distance Connection Server, but cannot log on to the LAN Server using LAN Requester, one of the following messages is displayed: Domain Controller not Available. or The Server is not responding. If you receive one of these messages, complete the following steps, then try logging on to the LAN Server: 1. Complete the steps for setting up LAN Requester and LAN Server described in Modifying LAN Server and Requester Configurations. 2. Verify and adjust the LAN Distance bridge hop count. LAN Requester data frames may not be able to reach the LAN Server because the hop count at intervening bridges is not large enough. See Understanding Token-Ring Bridges and Example 2: Using OS2PING to Verify the LAN Distance Bridge Hop Count. 3. Verify that the LAN Distance bridge configuration values (bridge number, LAN segment ring number, and WAN segment ring number) are configured correctly at the LAN Distance Connection Server. See Settings Notebook, Bridge Tab. 4. Verify that filtering is enabled on the LAN Distance Connection Server. See Types of Filtering Supported for the LAN Distance Bridge. 5. Adjust serial (COM) port speed for your modem. See Serial (COM) Port Speed Needs Adjusting. 6. Adjust the FIFO transmit buffer size for your modem, see FIFO Transmit Size Needs Adjusting. ═══ 16.12.3. Insufficient NetBIOS Resources ═══ When running IBM LAN Server 4.0 with IBM LAN Distance Advanced Server you may experience problems with insufficient NetBIOS resources. Two possible symptoms indicate this problem:  When starting LAN Distance error message WCL554 appears stating that the LAN Distance product requires more NetBIOS resources than are available.  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 [Network] section, reduce the number of NCBs. See example below: ║ V NETx=NETBEUI$, 0, LM10, yyy , 175, zzz to ║ V NETx=NETBEUI$, 0, LM10, yyy , 125, zzz 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.  Edit the \WAL\WCLLOCAL.INI file with any ASCII editor.  Under [SRDDEFS] 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.  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 Distance product will attempt to take when it is started. [SRDDEFS] [SRDDEFS] maxconversations = 10 maxconversations = 10 adapter = 2 adapter = 2 sessions = 32 to sessions = 16 commands = 90 commands = 48 datagram = 6 datagram = 6 ═══ 16.12.4. Large File Copy Problems ═══ When copying files larger than 2 KB or using XCOPY to copy multiple files, the file(s) may not be copied, or may not be copied completely. You may receive one of the following messages. NET3193: A virtual circuit error occurred on the session to STLCORE. The NCB command and return code are the data. NET3190: Netwksta Internal Error has occurred. 1. Complete the steps for setting up LAN Requester and LAN Server described in Modifying LAN Server and Requester Configurations. 2. Adjust the serial (COM) port speed for your modem. See Serial (COM) Port Speed Needs Adjusting. 3. Adjust the FIFO transmit buffer size for your modem, see FIFO Transmit Size Needs Adjusting. ═══ 16.12.5. File Copy Problems on TCPIP Network ═══ You will not be able to copy large files from a file server after you have made a successful point-to-point (PPP) connection if you have not correctly configured the TCPIP maximum transmission unit (MTU) value for your network environment. Symptoms include the following:  You are able to edit and copy very small files on the file server from your PPP client.  When you try to copy larger files on the file server from your PPP client, the OS/2 session where the copy command was issued appears to hang.  After your copy command appears to hang, other TCPIP commands, such as PING, do not work in other OS/2 sessions on the PPP client.  IP traces show that the file server received the commands, but does not respond back. Check the documentation for your adapter on the PPP Server and verify that the MTU values currently configured on both the PPP Server and the PPP client are not greater than the MTU value specified in your documentation. The following table lists the MTU values for common communiciations adapters. ┌────────────────────────────────────────────────────────────────────────┐ │ Table 32. Common Communications Adapters MTU Values │ ├────────────────────────────┬───────────────────────────────────────────┤ │ MAXIMUM TRANSMISSION UNIT │ ADAPTER │ ├────────────────────────────┼───────────────────────────────────────────┤ │ 1500 │ Default │ ├────────────────────────────┼───────────────────────────────────────────┤ │ 1462 │ PCNet │ ├────────────────────────────┼───────────────────────────────────────────┤ │ 1492 │ Ethernet on an IEEE 802.3 network │ ├────────────────────────────┼───────────────────────────────────────────┤ │ 4400 │ Token-Ring 16/4 Adapter/A card on a 16 MB │ │ │ token-ring network │ ├────────────────────────────┼───────────────────────────────────────────┤ │ 576 │ X.25 coprocessor │ └────────────────────────────┴───────────────────────────────────────────┘ ═══ 16.13. IBM Communications Manager 3270 Emulation Error Message ═══ If your LAN Distance Remote is running the 3270 emulation feature of IBM Communications Manager/2 to access a host on a LAN, and you receive one of the following messages, LAPS is configured incorrectly. To configure LAPS, see Setting Up to Run LAN Applications Remotely. ACS 2390 ALERT: An unexpected OS/2 function call or 802.2 LAN Transport error has closed the logical LAN adapter Set up considerations for using the 3270 emulation feature of Communications Manager/2 are described in Using the Communications Manager/2 3270 Emulation Feature. ═══ 16.14. Banyan VINES Requester Error Message ═══ If source routing is not configured for the Banyan VINES Requester and Server, the following message is received when the BAN/nl command is issued from the Banyan VINES Requester. BAN: Unable to establish communications to the VINES Server. See your system administrator. To configure source routing for the Banyan VINES Requester, see Setting Up the Banyan VINES Requester. To configure source routing for the Banyan VINES Server, see Configuring Source Routing for the Banyan VINES Server. ═══ 16.15. Avoiding the NetWare Connection Error on the NetWare Requester ═══ The following message can occur when you restart the LAN Distance Remote after the NetWare Requester product is installed on the LAN Distance Remote. This message occurs because the NetWare Requester is trying to locate the NetWare Server before a LAN Distance connection is established. NWD0115: Error getting connection ID (0X880F) To avoid this error message when you start your workstation: 1. Use an ASCII 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 Avoiding the NetWare Connection Error on the NetWare Requester before logging on to the NetWare Server. ═══ 16.16. Delay When Starting Up Your LAN Application ═══ Certain applications are optimized for the LAN Distance connections. Client-server applications, such as IBM Communications Manager/2, that are installed on the LAN Distance Remote and pass data to the LAN are ideal for use with the LAN Distance product. Applications loaded on an application server, such as word processors, spreadsheets, and databases, and started remotely from a LAN Distance Remote, transmit executable files over the LAN Distance WAN connection, causing a start up delay. For example, a 1 Mb file can easily take 10 minutes to load over a LAN Distance WAN connection at speeds of 14400 bps. For more information, see Setting Up LAN Applications for Remote Access. If you experience a lengthy delay when you start up a LAN application from an application server on the LAN, try the following solutions:  Move the application to the LAN Distance Remote and use the LAN Distance connection to pass the data from the application to the LAN. For example, install the word processing application on the LAN Distance Remote and access the document files from the LAN.  Move part of the application to the LAN Distance Remote and use the LAN Distance connection to access the remainder of the application. For example with NetWare, you can copy the LOGON.EXE file to the LAN Distance Remote, significantly shortening the logon process.  While working with client-server applications remotely, you can simultaneously use a remote control application over the LAN Distance connection to access large, non-client-server applications on the LAN. ═══ 16.17. Microcom Modem ═══ The following problems occasionally occur when using the Microcom modem with the LAN Distance product:  After having successfully connected with the Microcom modem, further attempts to reconnect with the modem or to connect with another modem have failed.  The Microcom modem will not initially connect with certain modems. The following are symptoms of the above problems:  The modem appears "deaf" to dialing strings.  The modem fails to go off hook.  The modem DTR signal fails to turn on. Using other PIF files, specifically MICROPRT.PIF, will alleviate the problems in a few cases. ═══ 17. Using System Management Tools ═══ This chapter describes how to use the following LAN Distance system management tools to manage any LAN Distance workstation that you have the authority to access. Use these tools to monitor use of ports and modems; view LAN Distance bridge statistics; and gather audit statistics related to security, calls, and links. Call and Port Management Manages communication resources for a workstation. Using call and port management, you can monitor port use and, if necessary, disconnect a call through a port. You also can monitor, start, and stop modem types. For more information, see Call and Port Management. Tracking Notebook Gathers management data for a selected workstation. Using the tools in the Tracking notebook, you can collect LAN Distance workstation configuration and statistical information regarding security, calls, and links. For more information, see Using the System Management Tools in the Tracking Notebook. SNMP for LAN Distance Bridge Management Gathers LAN Distance bridge configuration and statistical information to use for performance tuning. For more information, see Managing the LAN Distance Bridge Using the TCP/IP SNMP Tool. ═══ 17.1. Call and Port Management ═══ Call and port management provides information about ports and modem types. Port A physical device that enables connections for a workstation. Modem type A manager that logically groups the operation of ports for a workstation. You can use call and port management when:  Your LAN Distance Remote starts a connection with another LAN Distance workstation, but cannot complete the connection. Use call and port management to disconnect the call.  Your LAN Distance Connection Server must be shut down for maintenance. Use call and port management to stop modem types and disconnect any LAN Distance Remotes after they complete their necessary communications. (This is known as a "soft stop".)  An authorized user accesses your LAN Distance Connection Server. Use call and port management to stop the related modem type and immediately disconnect the user. (This is known as a "hard stop".) Call and port management windows display information about ports and modem types for LAN Distance workstations. You can select and manage a specific port or modem type. Call and Port Management Views for Port and Modem Types shows how call and port management windows can be used to manage ports and modem types. Like other LAN Distance product functions, call and port management is object-oriented. You can perform call and port management for any LAN Distance workstation that you can select and access in the LAN Distance Workstations window. In Call and Port Management Views for Port and Modem Types, a Call and Port Management - Port View is displayed for the LAN Distance Remote while a Call and Port Management - Modem Type View is displayed for the LAN Distance Connection Server. You can display either view for a selected LAN Distance workstation. Call and Port Management Views for Port and Modem Types ═══ 17.1.1. Viewing Call Activity for a Port ═══ Call and port management displays information about the ports used by a LAN Distance workstation. Use this information to make management decisions regarding the use of port resources. For example, if you end a call, but the port does not appear to disconnect, you can verify the status of the port. Based upon this information, you can decide whether to disconnect the port. Call and port management provides the following information:  Call direction  Local phone number  Status or availability  User ID  Modem type  Connection type  Connection speed  Entry name  Workstation name To display port information: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. Call and Port Management - Port View Window The Call and Port Management - Port View window displays information regarding each port used by a LAN Distance workstation. The Call and Port Management - Port View is 1 of 2 main views for call and port management. (The Call and Port Management - Modem Type View displays information about modem types, which manage the ports. See Viewing Call Activity for a Modem Type.) Port information includes: Call Direction A call can have 1 of 5 directions: Note: Port icons only display connection arrows when a call session is active. Active permanent connection The call is active for a permanent or leased line connection. Inactive permanent connection No call is active for a permanent or leased line connection. Inactive port No call is active for the port. Incoming call The call is coming into the port from another location. When an incoming call is disconnected and you dial the previous caller, the port displays an incoming call. Outgoing call The call is going out from the port to another location. Local Phone Number Displays the local phone number used for the port. If you do not configure a phone number, "Unspecified" is displayed. Status Displays the status of a call for the port. The status can be: Available The port is available for use. Connected The call is physically established and can incur phone charges. Connecting The port is establishing a connection. Disconnecting The call is ending. If the call remains in a disconnecting status for a long time, the call has not properly disconnected. Unavailable The port is unavailable for use. For example, a port can be unavailable when its modem type is stopped. User ID Displays the logon ID of the LAN Distance user when security is enabled and a connection is established. Modem Type Name Displays the name of the modem type used for a port. For example, an asynchronous leased line can be named ASYNCLL. Modem Type Status Displays the status of the modem type used for a port. Started The modem type is started and available for use. Starting The modem type is currently starting. Stopped The modem type is stopped. Stopping The modem type is currently stopping. Connection Type Displays the connection type used for a call. The connection type can be: Integrated Services Digital Network Although ISDN is not a modem, a connection type can manage ISDN ports. Public Switched Telephone Network After the call is connected, the true connection type can be asynchronous or synchronous. Connection Speed Displays the speed of the connection for active calls. Entry Name Indicates the name used in the phone book for the answer criteria or an outgoing call when calls are active. Workstation Name Displays the name of the called workstation when calls are active. ═══ 17.1.2. Viewing Connection Details for a Port ═══ If you need information about how a port is being used, call and port management provides actual port connection details. For example, to verify the charges that are incurred for a call, you can use the Connection Details window. The Connection Details window can display the call start time of the connection. To display port connection details: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. 3. Select a port, and then Open as Connection details. The Connection Details window is displayed. Connection Details Window The Connection Details window displays information about the connection established by a port. Connection details include: Start time Displays the time the call was established for the port. Start date Displays the date the call was established for the port. Remote number Displays the telephone number of the workstation you called. The remote number of an incoming call is displayed only for an ISDN configured call. Mode Displays the mode of a port. Depending on the modem type that controls the port, the field displays: Non-switched The port connection uses a physical link that does not require dialing. The port has either a PSTN or ISDN modem type. Permanent The port connection uses a leased line, such as a null modem cable. The port has a ISDN modem type. Switched The port connection uses a telephone network. The port has either a PSTN or ISDN modem type. DSR (Data Set Ready) Signal Indicates whether the modem signal is ready to receive information. The field displays: 0 A signal is not present. 1 A signal is present. Note: If the port is not connected or uses ISDN, the field is blank. CD (Carrier Detect) Signal Indicates whether the modem detects a carrier signal. The field displays: 0 A signal is not present. 1 A signal is present. Note: If the port is not connected, the field is blank. Port name Displays the alias assigned to the port. If the port uses ISDN, an alias is not displayed. ═══ 17.1.3. Disconnecting a Call ═══ When you need to disconnect a port from a connection, you can use call and port management. For example, if a port has a physical connection but does not respond, you can disconnect the port and try to reconnect. Disconnecting a port can help you manage your port resources. For example, you can disconnect a call if a call is stuck or an unauthorized user accesses the LAN Distance Connection Server. Warning: When you disconnect a call, any active processing related to the call stops, and related data can be lost. To disconnect a call: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. 3. Select a port for which you want to disconnect a call, then select Selected, and Hangup. The port is disconnected. ═══ 17.1.4. Viewing Call Activity for a Modem Type ═══ Call and port management displays information about the modem types that manage LAN Distance workstation ports. You can use this information to manage modem types. For example, to see the ports managed by a modem type for a LAN Distance Remote, use the Call and Port Management - Modem Type View window. Call and port management provides the following information about modem types:  Mode type name  Status  Connection type  Number of defined ports To display modem type information: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. 3. Select View, then Modem types. The Call and Port Management - Modem Type View window (Call and Port Management - Modem Type View Window) is displayed. . Call and Port Management - Modem Type View Window The Call and Port Management - Modem Type View provides information about modem types. The Call and Port Management - Modem Type View is 1 of 2 main views for call and port management. (The Call and Port Management - Port View displays information about all the ports on a LAN Distance workstation. See Viewing Call Activity for a Port) Modem type information includes: Name Displays the name of the modem type used for a port. For example, an asynchronous leased line can be named ASYNCLL. Status Displays the status for the modem type. The status can be: Started The modem type is started and available for use. Starting The modem type is currently starting. Stopped The modem type is stopped. Stopping The modem type is currently stopping. Connection Type Displays the connection type this modem uses. The connection type can be: Integrated Services Digital Network Although ISDN communication does not require a modem, a LAN Distance modem type can manage ISDN ports. Public Switched Telephone Network After the call is connected, the true connection type can be asynchronous or synchronous. Ports Defined Displays the number of ports defined for a modem type. The number varies according to the kind of modem type used: ISDN Number of B channels PSTN Number of ports ═══ 17.1.5. Viewing the Ports Managed by a Modem Type ═══ Call and port management provides detailed information about the ports managed by a modem type. You can use this information to make management decisions regarding the use of a specific port or set of ports. For example, if a security breach occurs and requires you to disconnect all incoming calls for a specified modem type, use the Modem Type Details window. To display detailed information about a modem type: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. 3. Select View, then select Modem types. The Call and Port Management - Modem Type View window is displayed. 4. Select a modem type, then Selected, and Open as Modem Type details. The Modem Type Details window (Modem Type Details Window) is displayed. Modem Type Details Window The Modem Type Details window displays the individual ports for the selected modem type. Ports displayed in the Modem Type Details window are logically grouped according to their modem type. Call Direction A call can have 1 of 5 directions: Note: Port icons only display connection arrows when a call session is active. Active permanent connection The call is active for a permanent (leased-line) connection. Inactive permanent connection No call is active for a permanent (leased-line) connection. Inactive port No call is active for the port. Incoming call The call is coming into the port from another location. When an incoming call is disconnected and you dial the previous caller, the port displays an incoming call. Outgoing call The call is going out from the port to another location. Local Phone Number Displays the local phone number used for the port. If you do not configure a phone number, "Unspecified" is displayed. Status Displays the status of a call for the port. The status can be: Available The port is available for use. Connected The call is physically established and can incur phone charges. Connecting The port is establishing a connection. Disconnecting The call is ending. If the call remains in a disconnecting status for a long time, the call has not properly disconnected. Unavailable The port is unavailable for use. For example, a port can be unavailable when its modem type is stopped. User ID Displays the logon ID of the LAN Distance user when security is enabled and a connection is established. Connection Type Displays the connection type used for this port. The connection type can be: Integrated Services Digital Network Although ISDN is not a modem, a connection type can manage ISDN ports. Public Switched Telephone Network After the call is connected, the true connection type can be asynchronous or synchronous. Connection Speed Displays the speed of the connection for active calls. Entry Name Indicates the name used in the phone book for the answer criteria or an outgoing call when calls are active. Workstation Name Displays the name of the called workstation when calls are active. ═══ 17.1.6. Stopping a Modem Type ═══ Call and port management lets you stop a modem type and stop all of its port connections. For example, before you bring down a LAN Distance Connection Server for maintenance, you can stop the related modem types. This ensures that all active port connections are disabled before shutdown. Warning: If you stop a modem type, any call connection using that modem type are ended. Because stopping a modem type ends connections, you can stop a modem type in 1 of 2 ways: soft or hard.  A soft stop stops a modem type after all current connections complete. A soft stop can be used to bring down a LAN Distance Connection Server for maintenance and avoid interrupting current calls.  A hard stop immediately ends a connection for a modem type. A hard stop can be used to quickly bring down a LAN Distance Connection Server or disconnect active calls in an emergency. To stop a modem type: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. 3. Select View, then Modem types. The Call and Port Management - Modem Type View window (Call and Port Management - Modem Type View Window) is displayed. 4. Select a modem type, then select Selected. 5. You can stop a modem type in 1 of 2 ways:  To stop a modem type after all currently processing activities complete, select Stop soft.  To stop a modem type immediately, regardless of outstanding calls, processing calls, or answering calls, select Stop hard. The modem type is stopped. ═══ 17.1.7. Starting a Modem Type ═══ Call and port management lets you start modem types that have been stopped. To start a modem type: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be managed, then Selected, Open as, and Call and port management. The Call and Port Management - Port View window (Call and Port Management - Port View Window) is displayed. 3. Select View, then Modem types. The Call and Port Management - Modem Type View window (Call and Port Management - Modem Type View Window) is displayed. 4. Select a modem type, then Selected and Start. The modem type is started. ═══ 17.2. Using the System Management Tools in the Tracking Notebook ═══ The Tracking notebook lets you monitor several different aspects of a LAN Distance workstation. Like other LAN Distance product functions, the Tracking notebook is object-oriented. You can use tracking management for any workstation that you can select and access in the LAN Distance Workstations window. The ability to use tracking functions depends on your user type and the location of the LAN Distance workstation that you intend to manage. Your user type can be: Administrator A user who can perform advanced LAN Distance management functions. User A user who can perform basic LAN Distance functions. You can manage the LAN Distance workstation from 2 locations: Locally Managing locally occurs when you are using the managed LAN Distance workstation. For example, you can locally manage the LAN Distance Remote that you are using at your desk. Remotely Managing remotely occurs when you are not sitting at the managed LAN Distance workstation. For example, you can remotely manage a LAN Distance Connection Server in another building using the LAN Distance Remote at your desk. The Tracking notebook consists of many tabs, which display according to user type and location of the target workstation. The functions available in the Tracking notebook are:  General  Trace  Dump  Audit  Retrieve This section describes audit and retrieve, which are instrumental tools for system management. General, trace, and dump are used for problem determination. For more information about problem determination, see Detecting and Resolving Errors. ═══ 17.2.1. Using the Auditing Tool ═══ Audit is an administrative tool that captures statistical information about:  Security - logon errors and security violations - changes to user account, personal account, or security policy  Calls - call origin - start time - stop time  Links - bytes passed - bytes retransmitted This information is logged to the audit file. You can create a program to automatically extract information from the audit file to create reports, such as weekly usage of LAN Distance by each user. The audit file can be accessed locally or remotely using the Retrieve tool. See Using the Retrieve Tool. With security enabled, only users designated as administrators are authorized to use audit or retrieve its output. With security disabled, any user can use audit or access its output. An additional feature of audit is the ability to automatically start a user-supplied program when the audit file is full, or at a scheduled time or interval. The audit features are available from the 3 pages of the Audit tab of the Tracking notebook. To open the Audit tab: 1. Open the LAN Distance Workstations window. 2. Select the icon of the workstation to be audited, then Selected, Open as, and Tracking. The Audit tab (Tracking Notebook, Audit Tab) is displayed. Tracking Notebook, Audit Tab To audit your workstation: 1. In the Current settings group box, select the statistics to audit for this workstation. If you locally change the current audit statistics settings and close the Tracking notebook, you must start and stop the LAN Distance product before your changes take effect. 2. Select the right arrow at the bottom of the window to go to page 2 (Audit Tab, Page 2 of 3). 3. In the Filename of Audit file on xx field, enter the name for the audit file, or use the default file name, WCLAUDIT.001. The xx displays the Workstation name for the target workstation. 4. In the Maximum file size (in Kbytes) field, enter a maximum file size, or use the default file size of 64. 5. In the File format group box, select either ASCII or Binary as the file format. 6. Select the right arrow at the bottom of the window to see page 3 (Audit Tab, Page 3 of 3). 7. Optional - In the Report program field, enter the name of the user-supplied report program to be called when the program scheduling conditions you specify in step Using the Auditing Tool are met. 8. To create a new file or overwrite the existing file when the audit file exceeds its maximum size, select one of the following radio buttons from the When Audit file is full group box: New file Creates a new audit file Wrap Overwrites the existing audit file 9. Optional - To run a user-supplied report program, select the Run program check box. 10. Optional - To disable program scheduling, select Do not schedule in the Program scheduling group box. 11. To specify when a user-supplied program runs, select one of the following radio buttons: Daily Runs the report program on a daily basis Weekly Runs the report program on a weekly basis Monthly Runs the report program on a monthly basis 12. To finish creating an audit file, select the Apply push button. The audit file is created on the target workstation when the first audit event occurs. If the target workstation is remotely managed, use the Retrieve tab to access the audit file. For more information, see Using the Retrieve Tool. Audit Tab, Page 2 of 3 Audit Tab, Page 3 of 3 ═══ 17.2.1.1. Selecting the Statistics to Audit ═══ Three different categories of statistics are available for auditing: security statistics, call statistics, and link statistics. You can select more than 1 category from the Audit tab in the Tracking notebook. Note: Security statistics is a valid selection even if the workstation is configured with security disabled. No statistics are logged while security is disabled, but when security is enabled statistics are logged without further changes to the audit selection. Select any combination of statistics you wish to enable in the Current Settings group box: Security statistics Reports user ID and user account information Calls statistics Reports call session information Link statistics Reports call connection information Note: When you locally change the current audit statistics settings and close the Tracking notebook, you must start and stop the LAN Distance product before changes take effect. ═══ 17.2.1.2. Security Statistics ═══ Security statistics are logged only if security is enabled. However, Security statistics is a valid selection regardless of how security is configured. Security statistics include the following events: Session Duration/User ID Logon and Logoff time and user ID are logged as entries. Logon Errors Logon errors include:  Invalid passphrase  Expired passphrase  New passphrase duplication  Invalid user ID  Inactive account  Logon limit exceeded  Invalid logon time  Invalid MAC address  User cancelled logon  No response from user  Unsolicited SRD link drop User Account Database Changes When an addition, change, or deletion is made to the user account or security policy, an entry is made noting either the success or failure of the action and the user ID attempting the action. Security Status When security is disabled, an entry is made noting either the success or failure of the action and the user ID attempting the action. The following example shows part of a security audit file. This entry describes how the SECADMIN user made a logon attempt to a LAN Distance Connection Server. This entry shows a date, time, LAN adapter address (MAC), and user ID. Security audit: 000168FE Date: 1993/08/10 Time: 21:03:22 Logon MAC address: 40003D1B754D User ID: SECADMIN ((null)) Call ID: 16401318 ═══ 17.2.1.3. Call Statistics ═══ Call statistics are captured at the beginning and end of a call. Call statistics include: Call origin This is the ID of the user who originated the call. Call start This is the date and time the call was placed. Call stop This is the date and time the call was concluded. Call statistics Either active or inactive The following example shows part of a call statistics audit. This entry describes how the SECADMIN user at the COLBYREMOTE workstation started an incoming call session. This entry shows:  Date  Time  Session ID  Connection instance  Connection type  Workstation name  User ID  LAN adapter address (MAC)  and other information Call audit: Call started Date: 1993/08/10 Time: 21:03:32 Duration: 0 seconds Return code: 0000 Entry: PSTN_ALL_CALLS Call ID: 16401318 Link instance: B20FDC78 Call type: Incoming Link type: Incoming Workstation: COLBYREMOTE User: SECADMIN MAC Address: 4000276D25F6 Number of calls: 1 Callback directory name: Callback variable number: ═══ 17.2.1.4. Link Statistics ═══ Link statistics are captured at the time the link is terminated. Link statistics include: Total bytes received Total number of bytes received during a call session Total frames received Total number of frames received during a call session Total bytes transmitted Number of bytes sent during a call session Total frames transmitted Total number of frames sent during a call session The following example shows part of a link statistics audit. This entry describes how the B20FDC78 call ID issued a disconnect request to a LAN Distance Connection Server. This entry shows:  Audit event  Date  Time  Call ID  Instance type  Modem type  Local number Link statistic: B20FD830 Audit event: Link stopping Date: 1993/08/10 Time: 21:06:00Duration: 177 seconds Return code:0000 Entry: Link ID: B20FDC78 Instance type: Incoming - Disconnect request issued PCM: ROLM244PC (VSERIES) Local number: 80972 ═══ 17.2.2. Specifying the Audit File and Its Characteristics ═══ Several controls over the audit file are available:  Name of the file  Maximum size of the file  Format of the file  Audit information can be saved to a single file that wraps when the Maximum file size is reached, or another file can be created to hold additional audit information when the Maximum file size is reached. ═══ 17.2.2.1. Audit File Default Path ═══ The default path for the audit file is \WAL. You have the option of specifying a path other than the default in the Filename of Audit file on this workstation field. The file name is specified in the same field, located on Audit Tab, Page 2 of 3 in the Tracking notebook. The default file name is WCLAUDIT.001. This file is stored on the target workstation. To define a unique file name, specify a file name from 1 to 8 characters in length. For the 3-character file extension, you can either:  Leave the numeric file extension blank so it can be sequentially numbered from 001.  Specify the numeric extension (001 to 999) that you want sequential numbering to start with. For example, if you entered STATSFIL.017, the next audit file created will be named STATSFIL.018. ═══ 17.2.2.2. Deciding on the Format of the File ═══ The most compact form for a file is binary format. A binary format can be used as input to some user-supplied parsers that format and display the contents. The file can also be created in a more readable ASCII format. Both formats can be used by a user-supplied program for displaying or reporting purposes. Note: After the file is created in either of the 2 formats, audit cannot convert from one format to the other. If you change the format, you should also change the file name or extension, or both. ═══ 17.2.2.3. Specifying the Maximum Size of the Audit File ═══ The size of the file is specified on the Audit Tab, Page 2 of 3, in the Tracking notebook. The size of the file must be from 1 to 5000 KB specified in increments of 1 kilobytes (KB or 1024 bytes). For example, if you specify 100, the file size will be 100,000 KB. The default size is 64 KB. Because the size of the audit file can reach only 5000 KB, specify whether audit information should be saved to a new file or overwrite the information in the current file. Specify this option in the When Audit file is full group box on the Audit Tab, Page 3 of 3 in the Tracking notebook. New file Select this radio button to create a new audit file when the audit file exceeds its maximum size limit. For more information about how files are automatically named see Audit File Default Path. Wrap Select this radio button to wrap new information and overwrite the existing audit file when it exceeds its size limit. These selections take effect as soon as you select Apply push button. In addition, you can specify that a user-supplied program start as soon as the maximum size limit is reached by the audit file. Use this option with either the New file or Wrap options. For more information, see Automatically Starting a User-Supplied Program. ═══ 17.2.2.4. Accessing the Audit File ═══ If you are at the workstation, you can access an ASCII audit file with any text editor. If you are remote, you can access the audit file by using the Retrieve tool. For more information, see Using the Retrieve Tool. Note: The first 10 bytes of every audit file provide the file control information and are always in binary format. ═══ 17.2.3. Automatically Starting a User-Supplied Program ═══ The ability to trigger a specified program to automatically generate audit reports provides you with some flexibility in working with the audit file. You can designate that a specified program automatically start based on a schedule defined by you and/or when the audit file reaches the value defined for the Maximum file size field. ═══ 17.2.3.1. Why Would You Want to Do This ═══ A frequent reason for automatically starting a user-supplied program is to create a custom report that extracts only the information you require in a format that suits your individual purpose. A user-supplied program can start as soon as the audit file reaches the size you specified, or whenever you schedule the program to start. Some additional reasons to start a user-supplied program include archiving the audit file(s) to another system or notifying a user that the audit file is full. ═══ 17.2.3.2. Specifying Which Program to Start ═══ Specify the name of the user-supplied program to start automatically on the Audit Tab, Page 3 of 3, in the Tracking notebook. This must be a fully qualified file name that includes the path. For example: C:\ADMNPRGS\USERPROG.EXE Or, the program must be in a path specified in the PATH= statement of the CONFIG.SYS file. This program can be an executable file or a REXX program. ═══ 17.2.3.3. How to Schedule the Program ═══ Specify when the user-supplied program should start by making 1 of the following selections:  Select the Run program option on the Audit Tab, Page 3 of 3, so the user-supplied program starts when the value in Maximum file size is reached.  Schedule the program to run periodically by specifying a time to run the program on the Audit Tab, Page 3 of 3. Note: The program time selections are not mutually exclusive. Daily Select the hour of the day to start the program. Weekly Select the day of the week to start the program. Audit starts the program as soon after midnight as possible of the scheduled day. Monthly Select which day of the month you want the program to start. Audit starts the program as soon after midnight as possible of the specified day of the month. If you select the 31st of the month, audit starts the program on the last day of the month. When the LAN Distance program is running, it starts the user-supplied program within a minute after the specified time. This occurs even if the user-supplied program had just run due to reaching the Maximum file size value. If the LAN Distance program is not running when the scheduled time occurs, then the user-supplied program starts as soon as the LAN Distance program is starting. Note: While a user-supplied program can be run with either the wrap or new file option, the wrap option is not recommended because with this option the audit file contents can change at any time. This could result in program or data errors. When the user-supplied program starts, the LAN Distance Remote program passes the following information as command line parameters: File name Name of the audit file. For more information about how an audit file is named, see Audit File Default Path. File size Double word maximum size of the file in ASCII (actual size may be less) Indicators Two 1-byte indicators (in ASCII, for example "AN") Format 'A' - ASCII 'B' - binary File full option 'N' - new file 'W' - wrap ═══ 17.2.4. Using the Retrieve Tool ═══ Use the retrieve tool to obtain the following files from a LAN Distance workstation that you are not using:  General information  Trace  Dump  Audit Log  Error Log  Message Log Note: When you remotely configure the Settings notebook or retrieve the audit file, your files can be detected by different types of media monitoring. Passphrases or other sensitive information in these files are accessible to other users. For example, if you had the following statements in your CONFIG.SYS file: SET HOSTNAME=USERID SET TELNET.PASSPHRASE.ID=PASSPHRASE Other users may be able to see your user ID and passphrase while retrieving general information file. To retrieve information remotely: 1. Open the LAN Distance Workstations window. 2. Select the icon of the LAN Distance Connection Server from which the files are to be retrieved, then Selected, Open as, and Tracking. 3. Select the Retrieve tab (Tracking Notebook, Retrieve Tab). 4. In the File to retrieve from xx list box, select the file that you want to retrieve from the target workstation. The xx displays the name of the target workstation. 5. In the Filename to use on this workstation field, enter the name you want the file to have at the local workstation that is to receive the file. The default path is \WAL. 6. To finish retrieving the file, select the Retrieve push button. The retrieved file is stored at the local workstation. Tracking Notebook, Retrieve Tab ═══ 17.2.4.1. Deciding Which File to Retrieve ═══ Use the File to retrieve from xx list box to select a file that the Retrieve tool can access: Trace-output file This is the file name you specified when you copied a trace file from the Trace tab in the Tracking notebook. For more information, see Tracing for OS/2 Workstations. Audit-output file This is the file name you specified on page 2 of the Audit tab in the Tracking notebook. For more information, see Using the Auditing Tool. Dump-output file This is the file name you specified when you performed a dump from the Dump tab in the Tracking notebook. For more information, see Dumping Information to a File. General information-output file This is the name of the file you specified on the General tab when you captured a workstation file. For more information, see Capturing Workstation Configuration Information. Message log File name is WAL\WCL.DAT on the LAN Distance Connection Server. This appears as message log in the list. For more information, see Viewing Error Messages. Error log File name is \OS2\SYSTEM\LOG001.DAT on the LAN Distance Connection Server. This appears as error log in the list. Note: Use the default file name for the error log, so that the Retrieve tool can use this information. For more information, see Viewing the Error Log. ═══ 17.2.4.2. Naming the Retrieved Information ═══ Use the Filename to use on this workstation field to specify the file name that the retrieved file receives when it is stored on the LAN Distance workstation that you are using. The default directory is WAL. If you do not specify a file name, a default file name is provided. The default file name is displayed after you select a file to retrieve. The format of the file name depends on the file system of the workstation where the file is to be stored. A maximum of 256 characters can be used if the file system used on the workstation where the file to be stored is the OS/2 HPFS (high performance file system). But if that workstation's file system is FAT (file allocation table), the maximum file name length is 8 characters with a 3-character extension. If a file with that name already exists on the local workstation, a warning is displayed, asking for confirmation to overwrite the file. ═══ 17.2.4.3. Starting the Retrieve Process ═══ Select the Retrieve push button to begin the retrieval process. No retrieval occurs until this push button is selected. A notification is displayed of either the success or failure of the retrieval. ═══ 17.3. Managing the LAN Distance Bridge Using the TCP/IP SNMP Tool ═══ Simple Network Management Protocol (SNMP) is a network management tool for TCP/IP networks. For SNMP support, the LAN Distance product requires that OS/2 TCP/IP 1.2.1 or later be installed on your LAN Distance Connection Server. You can set up the LAN Distance Connection Server to use SNMP to gather bridge routing information, which can be used for performance tuning. Use the SNMP product in the LAN Distance environment to:  View LAN Distance bridge statistics for base (dot1Base) and source (dot1dSr) bridge functions. These functions are defined in Network Working Group Request for Comments (RFC) 1236 and listed in Using SNMP to Manage the LAN Distance Bridge .  View LAN Distance bridge statistics from an SNMP client workstation on the LAN. If you want to use SNMP on a client workstation, complete step Setting Up a LAN Distance Connection Server to U se SNMP in Setting Up a LAN Distance Connection Server to Use SNMP for the client workstation. To support SNMP, the LAN Distance Connection Server installs an SNMP bridge subagent that interfaces with the SNMP agent provided in the TCP/IP for OS/2 product. ═══ 17.3.1. Setting Up a LAN Distance Connection Server to Use SNMP ═══ To set up a LAN Distance Connection Server to use SNMP, complete the following steps: 1. Install OS/2 TCP/IP version 1.2.1 or later. 2. Configure the SNMP agent for OS/2 TCP/IP SNMP. See TCP/IP Version 1.2.1 Installation and Maintenance Guide. 3. Install the LAN Distance Connection Server product. The SNMP bridge subagent (RLSNMP.EXE) and a text file (RLMIB.TBL) containing definitions for the variables managed by the SNMP bridge subagent are installed in the WAL directory. 4. Append the RLMIB.TBL text file to the MIB2.TBL text file in the TCPIP\ETC directory. This allows the SNMP agent to resolve the LAN Distance SNMP bridge subagent variables and handle requests for the LAN Distance bridge. 5. Shut down and restart the LAN Distance Connection Server to make effective changes to the SNMP bridge subagent files. ═══ 17.3.2. Using SNMP to Manage the LAN Distance Bridge ═══ To use SNMP to manage the LAN Distance bridge, complete these steps from the LAN Distance Connection Server: 1. Start the TCP/IP for OS/2 SNMP program to start the SNMP agent (SNMPD.EXE). For information on starting the SNMP program, see TCP/IP Version 1.2.1 for OS/2 User's Guide, and the TCP/IP Version 1.2.1 Installation and Maintenance Guide. 2. Start the LAN Distance subagent (RLSNMP.EXE) from an OS/2 command prompt by typing: RLSNMP Specify the host and community names defined for the SNMP program. For more information about using the SNMP program, see the TCP/IP Version 1.2.1 for OS/2 User's Guide, and the TCP/IP Version 1.2.1 Installation and Maintenance Guide. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 33. Supported SNMP Variables for the LAN Distance Bridge │ ├──────────────────────────────────────────────────────────────────────────────┤ │ SUPPORTED SNMP BRIDGE VARIABLES │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBaseBridgeAddress │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.1.0 │ ├──────────────────────────────────────────────────────────────────────────────┤ │ display │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBaseNumPorts │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.2.0 │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBaseType │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.3.0 │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBasePort │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.4.1.1. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBasePortIfIndex │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.4.1.2. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBasePortCircuit │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.4.1.3. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ object │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBasePortDelayExceededDiscards │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.4.1.4. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dBasePortMtuExceededDiscards │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.1.4.1.5. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPort │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.1. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortHopCount │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.2. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortLocalSeg │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.3. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortBridgeNum │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.4. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortTargetSeg │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.5. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 33. Supported SNMP Variables for the LAN Distance Bridge │ ├──────────────────────────────────────────────────────────────────────────────┤ │ SUPPORTED SNMP BRIDGE VARIABLES │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortLargestFrame │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.6. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortSteSpanMode │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.7. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ number │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortSpecInFrames │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.8. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortSpecOutFrames │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.9. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortApeInFrames │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.10. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortApeOutFrames │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.11. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortSteInFrames │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.12. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortSteOutFrames │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.13. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortSegMismatchDisc │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.14. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortDupSegDisc │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.15. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ ├──────────────────────────────────────────────────────────────────────────────┤ │ dot1dSrPortHopCtExcDisc │ ├──────────────────────────────────────────────────────────────────────────────┤ │ 1.3.6.1.2.1.17.3.1.1.16. │ ├──────────────────────────────────────────────────────────────────────────────┤ │ counter │ └──────────────────────────────────────────────────────────────────────────────┘ ═══ 18. Detecting and Resolving Errors ═══ If a problem occurs using the LAN Distance product, problem determination information is available to help you diagnose and solve the problem. Use Tracking to either display problem determination information or collect it in a file.  All of the tracking features described in this chapter are supported for the LAN Distance Connection Server and the OS/2 LAN Distance Remote product.  The tracking features supported for the MS Windows LAN Distance Remote are described in Tracing for MS Windows Remotes and Viewing the Error Log for MS Windows Workstations. This chapter describes how to:  Capture workstation configuration information  Trace  Collect dump information The Tracking notebook has two tabs that are not described in this chapter. Audit is a system management tool; see Using the Auditing Tool. Retrieve functions obtain general, trace, dump, and audit information from remote workstations. See Using the Retrieve Tool. ═══ 18.1. Capturing Workstation Configuration Information ═══ Select the General tab to gather LAN Distance system configuration information for a select workstation. Use this information during LAN Distance problem determination. General information is stored in the general file, named by you. You can access the general file for your workstation or a remote LAN Distance Connection Server. For information about retrieving a general file from a remote LAN Distance workstation, see Using the Retrieve Tool. To capture general information for a LAN Distance workstation: 1. Open the LAN Distance Workstations window and select the MyWorkstation icon for the workstation you want to capture system configuration information for. 2. From the menu bar, select Selected, Open as, and Tracking. 3. Select the General tab. The General window displays as shown in Tracking Notebook, General Tab. Tracking Notebook, General Tab Use General Window as a guide to capturing general information. Target workstation is the workstation you are capturing general information for. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 34. General Window │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ NAME │ View the name of the target workstation. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ VERSION │ View the version number of the LAN Distance product │ │ │ installed on the target workstation. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ DATE │ View the date when the information on the General window was │ │ │ initially displayed. │ │ │ │ │ │ This date changes when you select the REFRESH push button or │ │ │ close and reopen the Tracking notebook. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ TIME │ View the time when the information on the General window was │ │ │ initially displayed. │ │ │ │ │ │ This time changes when you select the REFRESH push button or │ │ │ close and reopen the Tracking notebook. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ WORKSTATION │ View the LAN Distance workstations to which the user at the │ │ AND USER ID │ target workstation is logged on. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ MAC ADDRESSES │ VIEW THE MAC ADDRESSES THAT ARE AVAILABLE FOR THE TARGET │ │ │ WORKSTATION. │ │ │ │ │ │ The MAC addresses originate from the workstation's │ │ │ PROTOCOL.INI file. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ FILENAME OF │ SPECIFY THE NAME OF THE FILE TO WHICH YOU ARE CAPTURING │ │ GENERAL FILE │ WORKSTATION INFORMATION. │ │ ON XX │ │ │ │ If you are capturing information for your workstation, XX is │ │ │ "this workstation" If you are capturing information for a │ │ │ remote LAN Distance Connection Server, XX is the name of the │ │ │ LAN Distance Connection Server. │ │ │ │ │ │ The general file is created on the target workstation. If │ │ │ you captured information for a remote LAN Distance Con- │ │ │ nection Server, use the RETRIEVE tab in the Tracking note- │ │ │ book to access the general file (see Using the Retrieve │ │ │ Tool). │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ CAPTURE │ Select the CAPTURE push button to begin capturing informa- │ │ │ tion. │ └───────────────┴──────────────────────────────────────────────────────────────┘ The General file contains information from many sources. The following information is displayed in the General window: CONFIG.SYS file PROTOCOL.INI file NETWORK.INI file WCLLOCAL.INI file WCLNET.INI file LANTRAN.LOG file WCLDIAL.CXD file In addition, the general file contains information about configured ports and ARTIC adapters (if applicable). ═══ 18.2. Tracing for OS/2 Workstations ═══ Select the Trace tab to collect data about internal LAN Distance events. Collect trace information to assist your designated support organization with problem determination. To collect Trace information for a LAN Distance workstation: 1. Open the LAN Distance Workstations window and select the MyWorkstation icon for the workstation you are collecting trace information for. 2. From the menu bar, select Selected, Open as, and Tracking. 3. Select the Trace tab. The Trace window displays as shown in Tracking Notebook, Trace Tab. Tracking Notebook, Trace Tab Use Trace Window as a guide to capturing trace information. The target workstation is the workstation you are capturing trace information for. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 35. Trace Window │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ TRACEPOINT │ View the status of the trace points that are defined. │ │ NAME AND │ │ │ STATUS │ The STATUS for a trace point can be: │ │ │ │ │ │ ON The trace point is active. │ │ │ BLANK The trace point is inactive. │ │ │ │ │ │ To enable tracing, select one or more trace points: │ │ │ │ │ │ o Double-click on a trace point to toggle it between ON │ │ │ and OFF │ │ │ o Select a trace point and then select the START push │ │ │ button. (The STOP push button deactivates a trace │ │ │ point.) │ │ │ │ │ │ NOTE: You can select several trace points and select the │ │ │ START push button to activate many trace points at once. │ │ │ │ │ │ Select the STOP ALL push button to stop all trace points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ BUFFER SIZE │ Specify the size of your trace buffer. │ │ (*64 K) │ │ │ │ BUFFER SIZE(*64 K) ranges from 1 to 16, where each is a unit │ │ │ of 64 Kb. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ RECORD TRUN- │ Specify the maximum length for your trace records. │ │ CATION │ │ │ │ If a trace record exceeds the maximum length specified, it │ │ │ is truncated. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ WRAP COUNT │ Specify a wrap count for the trace buffer. │ │ │ │ │ │ The trace buffer wraps when it is full and the oldest data │ │ │ in the buffer is overwritten. To minimize the amount of │ │ │ wrapping that occurs, increase BUFFER SIZE or decrease │ │ │ RECORD TRUNCATION. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ FILENAME OF │ Specify the name of the file to which trace information is │ │ TRACE FILE ON │ copied. │ │ XX │ │ │ │ If you are capturing information for your workstation, xx is │ │ │ THIS WORKSTATION. If you are capturing information for a │ │ │ remote LAN Distance Connection Server workstation, xx is the │ │ │ REMOTE WORKSTATION NAME. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ COPY │ Select the COPY push button to copy your trace information │ │ │ to your file. │ │ │ │ │ │ If a trace point is ON, you cannot copy information for any │ │ │ trace point. The trace file is created on the target work- │ │ │ station. If you are copying information for a remote LAN │ │ │ Distance Connection Server, use the RETRIEVE tab in the │ │ │ tracking notebook to access the trace file (see Using the │ │ │ Retrieve Tool).). │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ START │ Select the START push button to activate the selected trace │ │ │ points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ STOP │ Select the STOP push button to disable the selected trace │ │ │ points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ STOP ALL │ Select the STOP ALL push button to disable all trace points. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 18.3. Tracing for MS Windows Remotes ═══ Open the Tracking window to collect data about internal LAN Distance events. Collect trace information to assist your designated support organization with problem determination. To collect Trace information for a MS Windows LAN Distance workstation, open the Tracking window: 1. From the LAN Distance Workstations window, select the MyWorkstation icon for the workstation you are collecting trace information for. 2. From the LAN Distance group window, double-click on the Tracking icon. The Tracking window displays as shown in Tracking Window for MS Windows. Tracking Window for MS Windows Use Tracking Window as a guide to capturing trace information. The target workstation is the workstation you are capturing trace information for. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 36. Tracking Window │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ TRACE POINTS │ View the status of the trace points that are defined. │ │ AND STATUS │ │ │ │ The STATUS for a trace point can be: │ │ │ │ │ │ ON The trace point is active. │ │ │ BLANK The trace point is inactive. │ │ │ │ │ │ To enable tracing, select one or more trace points: │ │ │ │ │ │ o Double-click on a trace point to toggle it between ON │ │ │ and OFF │ │ │ o Select a trace point and then select the START push │ │ │ button. (The STOP push button deactivates a trace │ │ │ point.) │ │ │ │ │ │ NOTE: You can select several trace points and select the │ │ │ START push button to activate many trace points at once. │ │ │ │ │ │ Select the STOP ALL push button to stop all trace points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ FILE WRAP SIZE│ Specify the size of your trace file. │ │ (*1k) │ │ │ │ FILE WRAP SIZE(*1k) ranges from 1 to 810, where each is a │ │ │ unit of 1 Kb. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ RECORD TRUN- │ Specify the maximum length for your trace records. │ │ CATION │ │ │ │ If a trace record exceeds the maximum length specified, it │ │ │ is truncated. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ WRAP COUNT │ Specify a wrap count for the trace file. │ │ │ │ │ │ The trace file wraps when it is full and the oldest data in │ │ │ the file is overwritten. To minimize the amount of wrapping │ │ │ that occurs, increase FILE WRAP SIZE or decrease RECORD │ │ │ TRUNCATION. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ TRACE │ Specify the name of the file to which trace information is │ │ FILENAME │ copied. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ START │ Select the START push button to activate the selected trace │ │ │ points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ STOP │ Select the STOP push button to disable the selected trace │ │ │ points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ START ALL │ Select the START ALL push button to activate all trace │ │ │ points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ STOP ALL │ Select the STOP ALL push button to disable all trace points. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ VIEW │ Select the VIEW push button to view the collected tracing │ │ │ information. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 18.4. Dumping Information to a File ═══ The Dump tab contains all of the control information for capturing Dump data to a file. You can select a dump point and a file name, capturing all of the dump information into that file. Collect dump information to send to your designated support organization. The dump information is stored in the dump file, which is named by an authorized user. The dump file can be accessed locally or remotely. For more information about retrieving a dump file from a remotely managed LAN Distance workstation, see Using the Retrieve Tool. To capture dump information about a LAN Distance workstation: 1. Open the LAN Distance Workstations window and select the MyWorkstation icon for the workstation you are collecting dump information for. 2. From the menu bar, select Selected, Open as, and Tracking. 3. Select the Dump tab (Tracking Notebook, Dump Tab) 4. In the Dump points field, select a dump point for which you want to capture information. 5. In the Filename of Dump file on xx field, enter the file name where you want to capture the workstation information. The xx displays this workstation or the remote workstation name depending on the location of the target workstation. 6. To store the dump information to the file specified in Filename of Dump file on xx, select the Dump push button. The dump file is created on the target workstation. If the target workstation is remotely managed, use the Retrieve tab to access the dump file. For more information about Retrieve, see Using the Retrieve Tool. Tracking Notebook, Dump Tab ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 37. Dump Window │ ├───────────────┬──────────────────────────────────────────────────────────────┤ │ FIELDS │ ACTIONS & INFORMATION │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ DUMP POINTS │ Specify the Dump points to use. │ │ │ │ │ │ The DUMP POINTS field displays all of the defined dump │ │ │ points. Next to each dump point in the list is a corre- │ │ │ sponding product name. You can activate one dump point at a │ │ │ time. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ FILENAME OF │ Specify the name of the file to which Dump information is │ │ DUMP FILE ON │ copied. │ │ XX │ │ │ │ In the FILENAME OF DUMP FILE ON XX field, enter the name of │ │ │ the file into which you want the dump data to be captured. │ │ │ The xx displays THIS WORKSTATION or the REMOTE WORKSTATION │ │ │ NAME depending on the location of the target workstation. │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ DUMP │ Select the Dump push button to capture the information to │ │ │ the file name that you specified in the FILENAME OF DUMP │ │ │ FILE ON XX field. │ │ │ │ │ │ Capturing the dump information stores this file at the │ │ │ target workstation. For more information about remotely │ │ │ retrieving tracking information from a target workstation, │ │ │ see Using the Retrieve Tool. │ └───────────────┴──────────────────────────────────────────────────────────────┘ ═══ 18.5. Viewing Error Messages ═══ The message log receives and displays error and warning indications for the LAN Distance product. Use the message log to monitor the performance of a LAN Distance workstation. The message log file can be accessed using FFST/2's message log facility, MSGLOGF.EXE. To invoke MSGLOGF.EXE: 1. Open the LAN Distance Workstations window, select the MyWorkstation icon. 2. From the menu bar, select Selected, Open as, and Message log. Note: 1. You can also access the message log by entering MSGLOGF WCL.DAT on an OS/2 command line from the \WAL directory. 2. When no message log (WCL.DAT) exists, an error message is displayed. ═══ 18.6. Error Reports ═══ LAN Distance administrators also can use error reports for LAN Distance Connection Servers that are active. Error reports inform the LAN Distance administrator that a problem that exists on a LAN Distance Connection Server. Unlike error messages, error reports automatically display error information about a LAN Distance Connection Server to all users with administrator privileges who are logged on to the LAN Distance Connection Server using the LAN Distance product. Error reports appear as pop-up windows and are logged in the LAN Distance administrator's message log. ═══ 18.6.1. Using Pop-Up Windows ═══ Pop-up windows can contain warnings, error indications, and informational messages. When a pop-up window is displayed, select a push button to acknowledge the message, and possibly indicate an action you can take. If you want pop-up windows to be displayed: 1. Select the Workstation tab in the Settings notebook. 2. Select Display LAN Distance messages. Note: Do not select pop-up window message display for an unattended LAN Distance Remote. When a message requires a user response, an unattended LAN Distance Connection Server could interrupt the function of a LAN Distance Remote. ═══ 18.7. Viewing the Error Log ═══ The error log receives and displays indications of errors that occur during a LAN Distance workstation's operation. These errors are unique to LAN Distance and can be used by designated support organization to fix a LAN Distance product problem. The error log includes error-specific data that can be used to isolate and identify the exact nature of the problem. To view the error log: 1. From the LAN Distance Workstations window, select the MyWorkstation icon. 2. From the menu bar, select Selected, Open as, and Error log. Note: You can also view the error log by entering SYSLOG on an OS/2 command line. ═══ 18.8. Viewing the Error Log for MS Windows Workstations ═══ The error log receives and displays indications of errors that occur during a LAN Distance workstation's operation. These errors are unique to LAN Distance and can be used by designated support organization to fix a LAN Distance product problem. The error log includes error-specific data that can be used to isolate and identify the exact nature of the problem. To view the error log: 1. Open the Tracking window as described in Tracing for MS Windows Remotes. 2. Select the View push button to view any errors logged by LAN Distance. Note: You do not have to activate any trace points to have LAN Distance errors logged in the trace file. ═══ 18.9. Viewing Alerts ═══ Alerts are pre-defined, expedited messages on the LAN, reporting an event that requires operator intervention or attention. Alerts can be sent to a central LAN management point. The LAN Distance product uses alerts to report various types of communications errors for ISDN, asynchronous, and synchronous connections. Every alert generated by the LAN Distance product is copied to a dump file, and is logged separately from error logs. You can view alerts through FFST/2's dump formatter. To use the dump formatter, enter EPWDF on an OS/2 command line. You can specify configuration information to control the way that alerts are displayed by the dump formatter. For more information about routing alerts and the dump formatter, refer to the FFST/2 Administrative Guide. The LAN Distance product also generates internal alerts called error reports. Error reports allow a LAN Distance Connection Server to report an error to the LAN Distance administrator regardless of where the administrator is logged on. For more information about error reports, see Error Reports. ═══ 19. Supported Hardware ═══ This appendix lists the hardware supported by this release of the LAN Distance product. See the README file for a list of any modems, WAN adapters, and LAN adapters that were added after this book was published. Changes or additions made to the list of supported hardware after the product shipped are documented in the MODEMS.TXT and the ADAPTERS.TXT files which are available from these sources:  CompuServe users can access the IBM PSPAPROD forum and access these files in the LAN Distance product's library section.  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). ═══ 19.1. Modems ═══ Modems used by the LAN Distance product must be homologated in the country of use. The LAN Distance product does not provide DTE support for country-specific homologation requirements. The minimum baud rate of a modem used by LAN Distance is 9600. Modems Supported by the LAN Distance Product lists the LAN Distance generic modems, IBM modems, and other manufacturer's modems listed for the LAN Distance product when this book was published. Note: Two dialog descriptor files (.DDF) are included to support leased line enhancements for the ASYNCLL.PIF and SYNCLL.PIF files. These two files, NODIALOG.DDF and NODIAL2.DDF are designed to replace files of the same name. These files must be used if the ASYNCLL.PIF or SYNCLL.PIF files included in this package are used. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 38. Modems Supported by the LAN Distance Product │ ├────────────────────────────────────────────────────┬─────────────────────────┤ │ MODEMS │ PIF FILE NAME │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ LAN DISTANCE GENERIC MODEMS │ │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Any Modem Not In This List │ NOTLIST.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Asynchronous Switched Connection Modem │ ASYNCSW.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Asynchronous Leased Line Modem │ ASYNCLL.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Generic Mwave Modem │ MWAVE.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Null Modem │ NULMODEM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Synchronous Switched Connection Modem │ SYNCSW.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Synchronous Leased Line Modem │ SYNCLL.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Switched 56 V.35 Modem │ SWITCH56.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ SYNCHRONOUS MODEMS (SWITCHED 56) │ │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Northern Telecom Meridian Datapath V.35 Modem │ MERIDIAN.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola UDS** DSU170 V.35 Synchronous Modem │ UDSDU170.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ DIGITAL SWITCHING ADAPTER │ │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM MWave Windsurfer 14400 Modem │ WINDSURF.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ PCMCIA MODEMS │ │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Apex PCMCIA** Fax/Modem IBP - 1414 │ APEXPCM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ AT&T KeepInTouch PCMCIA Modem │ ATTPCMC.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Banksia PCMCIA Data/Fax Modem │ BANKSIAP.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ BocaModem 14.4bps V.32bis PCMCIA Modem │ BOCAPCM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes Optima 144 PCMCIA Modem │ OPTIMAP.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM PCMCIA Data/Fax Modem │ IBMPCMCI.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM Microelectronics 14.4/14.4 Data/Fax Modem │ IBMTORON.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Megahertz** C5144 Data/Fax Modem │ MHC5144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Megahertz XJ1144FM PCMCIA Data/Fax Modem │ MH144PCM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Megahertz XJ196FM PCMCIA Data/Fax Modem │ MH96PCM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola CELLect 14.4 PCMCIA Modem │ MOTOCELL.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ INTERNAL MODEMS │ │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Apex Freedom 14/96 Data/Fax Laptop Modem │ APEX1496.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ BocaModem 14.4 V.32bis Internal Modem │ BOCA144I.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Data Race** RediCard** Internal Modem │ DRREDIMI.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Data Race Thinkpad Internal Modem │ DRTURBO.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM ASYNC/SDLC V.32 Modem/A │ IBMV32A.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM High Speed Internal Data/Fax Modem │ IBMHSINT.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM PS/2 14.4 Data/Fax Modem Adapter/A │ IBM144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Infotel 1414VOE V.32bis/V.32 FAX Modem │ INFOTL14.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Intel SatisFAXtion Modem/400e │ INTFAX4E.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Practical Peripherals FX PS/2 Internal Modem │ PPFXPS2.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Practical Peripherals PM 14400FX Internal Modem │ PPPM144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ZOOM EVFPV32bis Internal Modem │ ZMPV32BI.PIF │ └────────────────────────────────────────────────────┴─────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 38. Modems Supported by the LAN Distance Product │ ├────────────────────────────────────────────────────┬─────────────────────────┤ │ MODEMS │ PIF FILE NAME │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ZOOM EVFXV32 Internal Modem │ ZMFXV32I.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ EXTERNAL MODEMS │ │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Angia 14.4 Data/Fax Modem │ ANGIA144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Apex Freedom 14/96 Dat/Fax Laptop Modem │ APEX1496.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ AT&T Comsphere 3820 │ ATT3820.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ AT&T DataPort │ ATTDP.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Banksia MyFastModem 28800 │ MYFMODEM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Banksia MyModem 14400 │ MYMODEM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ BocaModem 14.4 V.32bis External Modem │ BOCA144E.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ BocaModem 14.4 V.32bis Internal Modem │ BOCA144I.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ BocaModem V.FAST Externa. Modem │ BOCAFAST.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Complete PC 14400 TurboModem │ COMPLETE.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Creatix LX 144 VF High Speed Modem │ LC144VF.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Digicom Eagle Plus V.32 │ EAGLEP.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ GVC FM-144V External Fax Modem │ GVCFM144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ GVC SM-96 External Modem │ GVCSM96.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Haeussler Dat/Fax Modem H-144 │ HAEUSS.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes ACCURA** 144 + FAX144 Modem │ ACCURA14.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes ACCURA 288 V.FC + FAX Modem │ ACCURA28.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes ACCURA 96 + FAX96 Modem │ ACCURA96.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes Optima 14400 Modem │ OPTIMA14.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes Optima 9600 Modem │ OPTIMA96.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes Optima 28800 Modem │ OPTIMA28.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes Ultra** 14400 Modem │ ULTRA144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Hayes Ultra 9600 Modem │ ULTRA96.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM 7851 14.4Kbps Data/Fax Modem │ IBM7851.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM 7855 Modem (stand-alone and rack-mount models) │ IBM7855.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ IBM Mwave Waverunner Digital Modem │ WAVERUNR.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Intel** 14.4EX Modem │ INT144EX.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Intel PCFM7600 14.4/14.4 External Modem │ INPCFM76.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Intel SatisFAXtion** Modem/400 │ INTFAX4.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Macronix Fax/Modem │ MACRONIX.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Microcom** DeskPorte FAST** Modem │ MICVFAST.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Microcom HDFast Modem │ HDFAST.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Microcom High Density 4232bis Modem │ MICROHDM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Microcom MicroPorte** 4232bis Portable Modem │ MICROPRT.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Microcom QX/4232bis** Modem │ MICROCOM.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola Codex 3220 Plus │ CODX3220.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola Codex 3260 Modem │ CODX3260.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola Codex 3261 Fast │ CODX326X.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola UDS FasTalk 32bx** Modem │ FASTALK.PIF │ └────────────────────────────────────────────────────┴─────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 38. Modems Supported by the LAN Distance Product │ ├────────────────────────────────────────────────────┬─────────────────────────┤ │ MODEMS │ PIF FILE NAME │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Motorola UDS V.3229 Modem │ UDSV3229.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Multitech** 1432 Modem │ MT1432.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Multitech 1432MU Modem │ MT1432MU.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Multitech 932 Modem │ MT932.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ NEC 19632E Intelligent Modem │ NEC19632.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Practical Peripherals FXMT Modem │ PPFXMT.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Practical Peripherals FXSA Modem │ PPFXSA.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Practical Peripherals PM 14400FX PKT Modem │ PPPM144P.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Racal-Datacom** ALM3223 Modem │ ALM3223.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Racal-Datacom ALM3226 V.32bis Modem │ ALM3226.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Rolm** 244PC Telephone │ ROLM244.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ SupraFAX** V.32bis Modem │ SUPRAFAX.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Telebit** T1600 Modem │ TBT1600.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Telebit T2500 Modem │ TBT2500.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Telebit T3000 Modem │ TBT3000.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Telebit Trailblazer** Plus Modem │ TELEBIT.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Telebit WorldBlazer Modem │ WLDBLAZE.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics Courier Dual Standard V.FC │ USRCDS28.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics Courier HST DS** │ USRHSTDS.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics Courier HST DS 28800 │ USRCOU28.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics Sportster 14400** Modem │ USRSPORT.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics Sportster 28800 Modem │ USRSP288.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics WorldPort 14400** Modem │ USRWPORT.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ USRobotics WorldPort 9600 Modem │ USRWPRT9.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ViVa 14.4/FAX Modem │ VIVA144.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ Zenith Data Systems 2000 Laptop Modem │ ZEN2000.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ZOOM EVFPV32bis Modem │ ZMFPV32B.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ZOOM EVFXV32 Modem │ ZMFXV32.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ZOOM V.32bis High Speed External Modem │ ZOOMV32B.PIF │ ├────────────────────────────────────────────────────┼─────────────────────────┤ │ ZyXEL U-1496 Modem │ ZYXEL.PIF │ └────────────────────────────────────────────────────┴─────────────────────────┘ ═══ 19.2. Null Modem Cables ═══ If your workstation uses a null modem, make sure the cable is wired as: (FG) 1----------------------1 (FG) Pin 1 straight through (TD) 2----------------------3 (RD) Pin 2 and 3 are crossed (RD) 3----------------------2 (TD) (RTS) 4----------------------5 (CTS) Pin 4 and 5 are crossed (CTS) 5----------------------4 (RTS) (SG) 7----------------------7 (SG) Pin 7 straight through (DSR) +--6 6---+ (DSR) Pin 6 and 8 together to | | Pin 20 of the other side (CD) +--8----------------------20 | (DTR) | (DTR) 20-----------------------8---+ (CD) ═══ 19.3. Wide Area Network Adapters ═══ A list of Wide Area Network adapters supported by the LAN Distance product are available from the World Wide Web at: http:\\www.austin.ibm.com\pspinfo\ldwan.htm ═══ 19.4. Local Area Network Adapters ═══ A list of Local Area Network adapters supported by the LAN Distance product are available from the World Wide Web at: http:\\www.austin.ibm.com\pspinfo\ldlan.htm ═══ 19.5. Setting Up LAN Adapters to Use the LAN Distance Product ═══ The LAN adapters supported by the LAN Distance product are listed in Local Area Network Adapters Supported by the LAN Distance Product. Before you can set up your supported LAN adapter to use the LAN Distance product, its adapter driver(s) must be installed through LAPS after you install the LAN Distance Connection Server product.  If the workstation on the LAN that you plan to use as the LAN Distance Connection Server already has a LAN adapter configured, the adapter driver(s) for the LAN adapter are already installed. Complete the steps listed in Setting Up a LAN Adapter Through the Settings Notebook.  If the LAN workstation that you plan to use as the LAN Distance Connection Server does not yet have a supported LAN adapter configured, the adapter drivers for the LAN adapter are not installed. Complete steps in Installing LAN Adapter Drivers Through LAPS, before completing steps listed in Setting Up a LAN Adapter Through the Settings Notebook. ═══ 19.6. Setting Up a LAN Adapter Through the Settings Notebook ═══ If your supported LAN adapter is already configured for your LAN, complete these steps to set up your adapter after installing the LAN Distance Connection Server product: 1. Open the Settings notebook and select the Address/LAN tab. 2. From the Adapter for bridging list, use the scroll bars to select your LAN adapter. Note: If your LAN adapter is not displayed, close the Settings notebook and do not save your configuration changes. You must complete steps listed in Installing LAN Adapter Drivers Through LAPS before you can set up your LAN adapter through the Settings notebook. 3. Close the Address/LAN tab. From the Settings notebook, complete any additional configuration required for your LAN Distance Connection Server, then close the Settings notebook. 4. Stop the LAN Distance Connection Server product, shut down and restart your workstation. ═══ 19.6.1. Installing LAN Adapter Drivers Through LAPS ═══ To install the required adapter drivers for your LAN adapter, you need the option diskette for your adapter. You may also need to refer to the adapter documentation that describes how to install your LAN adapter drivers through LAPS. After you install the LAN Distance Connection Server product, complete these steps to install the LAN adapter drivers for your LAN adapter: 1. From an OS/2 command prompt, go to the IBMCOM directory, and type LAPS or MPTS to start the LAPS program. 2. Insert the adapter option diskette in the diskette drive. 3. From the logo window (LAPS Logo Window), select the Install push button to copy the files needed to support your LAN adapter. LAPS Logo Window 4. From the Install Additional Network Drivers pop-up window (Install Additional Network Drivers), type the fully qualified path (drive and directory) to your LAN adapter drivers. Select the OK push button to return to the LAPS Logo window, and then select the Exit push button to save your changes and exit LAPS. 5. If the LAN adapter driver you first installed is not on the list of supported adapters but is plug-compatable with a supported adapter, you need to add the name of the Network Information File (NIF) to the LAN Distance configuration. To add the NIF file name: a) Edit the \WAL\WCLLOCAL.INI file. b) Locate the [TOKENRINGMACS] and [ETHERNETMACS] sections in the INI file. c) Add the name of your drivers NIF file to the appropriate Token-Ring or Ethernet section. For example, if the adapter you just added is an Ethernet driver and the NIF file for the driver is named ENETXMP.NIF, add the NIF file name to the [ETHERNETMACS] section. d) Save the updated \WAL\WCLLOCAL.INI file. Install Additional Network Drivers 6. Start the LAN Distance product and then complete the steps listed in Setting Up a LAN Adapter Through the Settings Notebook. ═══ 19.6.2. Modifying Parameters for a LAN Adapter Through LAPS ═══ If your LAN adapter supports configuration through LAPS, you can modify configuration parameters such as interrupts, base address and shared RAM, through LAPS. For additional information, refer to your adapter documentation. 1. Start the LAPS program and select Configure from the LAPS logo window to open the Configure Workstation window. 2. From the Configure Workstation window (Configure Workstation Window), select your LAN adapter from the Current Configuration list box. Configure Workstation Window 3. Select the Edit push button to modify the parameters for your LAN adapter (Parameters for IBM LAN Adapter for LAN). When you have completed modifying the parameters, select the OK push button to save your changes and return to the Configure Workstation window. Parameters for IBM LAN Adapter for LAN (IBMENI.OS2) 4. From the Configure Workstation window, select OK and exit LAPS. ═══ 19.7. Performance Tuning for Non-FIFO Workstations ═══ The OS/2 LAN Distance products supports FIFO and non-FIFO serial communications (COM) ports. If you install the LAN Distance product on a workstation that does not have FIFO buffering, you may receive message WCL0223 when you start your workstation. ═══ 19.7.1. Determining If Your Workstation Is Non-FIFO ═══ To see if you have a FIFO or non-FIFO workstation, complete these steps: 1. At the OS/2 command prompt, enter: MODE COM1 2. If the system response is BUFFER = N/A, you have a non-FIFO machine. 3. If the system response is BUFFER = AUTO or anything other than BUFFER = N/A, then you have a FIFO workstation. ═══ 19.7.2. Performance Tuning Steps for Non-FIFO Workstations ═══ Non-FIFO workstations generally do not support connection speeds greater than 9600 bps, regardless of the connection speed supported by the attached modem. You can try to increase your LAN Distance connection speed by completing the steps that follow if 1) your non-FIFO workstation has a processing speed of 25 Mhz or greater and 2) the modem attached to the COM port supports transmission speeds greater than 9600 bps. 1. Stop the LAN Distance product. 2. Open the WCLNET.INI file in the WAL directory and locate the SerialPortSpeed value. 3. Using any text editor, try increasing this value as follows:  9600 to 14400(**)  14400 to 19200  19200 to 38400 4. Close the WCLNET.INI file and save your changes. Note: If you later change port and modem assignments through the Settings notebook, the WCLNET.INI file is recreated and changes made to the SerialPortSpeed parameter are not saved. 5. Start the LAN Distance product. If you can establish a LAN Distance connection and access LAN resources, you have successfully increased the connection speed for your non-FIFO COM port. Errors indicating that the serial port speed value is too large include messages WCL0221, WCL0336, and spontaneous disconnects. If you experience these errors, reduce the value of the SerialPortSpeed in the WCLNET.INI file to 9600. ═══ 19.8. Modems Requiring External Configuration ═══ The LAN Distance product supplies .PIF files for each of the modems supported by the LAN Distance product. The .PIF file for your modem is configured when you select your supported modem from the Available modem types list box on the Modems tab in the Settings notebook. Most modems can be configured to work with the LAN Distance product simply by selecting the supported modem from the Available modem types list box. However some modems, such as the IBM 7855 modem, also require external configuration, as described in the following topic. ═══ 19.8.1. External Configuration for the IBM 7855 Modem ═══ After you configure the IBM7855 modem through the Settings notebook, external configuration is required to use the IBM7855 modem with the LAN Distance product. Configure the IBM7855 modem through the front panel of the modem, or use an application such as the IBM7855 configuration tool. You can obtain the IBM7855 tool from these sources:  CompuServe users can access the IBM PSPAPROD forum, go to the library section for the LAN Distance product, and download the IBM7855 tool and user documentation.  Users with access to IBMLink through OS2BBS can access the IBM7855 tool and user documentation from the REMOTE section of the OS/2 Software Library (3), OS/2 Selective Fixes (1). External Settings for the IBM7855 Modem describes the options you must set for the front panel controls to externally configure your modem the LAN Distance product. For reference, the extended AT commands for these options are also provided. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 39. External Settings for the IBM7855 Modem │ ├───────────────────┬───────────────────────────────────────┬──────────────────┤ │ FRONT PANEL │ SELECTED OPTION DESCRIPTION │ AT COMMANDS │ │ CONTROL │ │ │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Operating Mode │ Idle and connect async │ &M │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Command Set │ AT commands │ %L │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Network │ &L │ Public Switched │ │ │ │ Network (PSTN) │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ PSN Speed │ 12000 bps │ &AP │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ RLSD Control │ RLSD is ON only during a connection │ &C │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ RFS Control │ RFS follows V.25bis rules │ &R │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ DSR Control │ DSR follows DTR │ &S │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ DTR Control │ DTR drop ends PSN connection │ &D │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ ECL Start │ Accept ECL link request │ /N │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Compression │ Data compression enabled │ %C │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ DTE Interface │ Speed buffering disabled │ /M │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ DTE Flow Control │ DTE uses RTS flow control │ /Q │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Modem Flow │ Modem uses RFS flow control │ /R │ │ Control │ │ │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Call Progress │ Enable BUSY and DIALTONE detect │ X │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Handshake Timer │ 60 seconds │ S7 │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Character Format │ 8N1 │ &B │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Message │ Messages enabled │ Q │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Result Codes │ Messages are verbose │ V │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Character Echo │ Async character echo enabled │ E │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ ECL clocked size │ 64 │ /A │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Autoanswer │ 2 rings │ SO │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Retrain Control │ Short retrains │ %E │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Fall Back │ Fall back 1 rate │ %F │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Fall Forward │ Fall forward disabled │ %G │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Speaker Volume │ Loud volume │ L │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Speaker Control │ Speaker ON until carrier detect │ M │ ├───────────────────┼───────────────────────────────────────┼──────────────────┤ │ Message Display │ Compact messages │ %V │ └───────────────────┴───────────────────────────────────────┴──────────────────┘ ═══ 20. Command Line Interface Reference ═══ This appendix describes the commands you enter at the OS/2 command prompt to perform LAN Distance functions. ═══ 20.1. Getting Help ═══ At the OS/2 command prompt, enter LDIST HELP for help with the syntax of LDIST commands. ═══ 20.2. Command Syntax ═══ The commands in this appendix are described with syntax diagrams. The following will help you use the syntax diagrams to enter commands:  Read the syntax diagram from left to right and top to bottom.  The command name and required parameters are displayed on the baseline: >>──COMMAND NAME──required parameter──><  Optional parameters are displayed below the baseline: >>──COMMAND NAME──┬────────────────────┬──>< └─optional parameter─┘  When you can choose from two or more parameters, the values are displayed in a vertical stack. When a parameter is required, one value in the stack is displayed on the baseline: >>──COMMAND NAME──┬─required choice 1─┬──>< └─required choice 2─┘ When a parameter is optional, the entire stack of values is displayed below the baseline: >>──COMMAND NAME──┬───────────────────┬──>< ├─optional choice 1─┤ └─optional choice 2─┘ ═══ 20.3. Command Conventions ═══ This appendix uses the following conventions to describe commands in the syntax diagrams and examples. UPPERCASE Uppercase bold letters indicate commands and keyword parameters. You can enter command and keyword parameters in uppercase (LDIST DIAL), lowercase (ldist dial), or mixed-case letters. italics Lowercase italics indicate variable parameters that you must replace with a value. For example, replace userid with your user ID. /PARAMETER: variable When a parameter has two parts, a parameter name and a variable, use a colon (:) to separate the parameter name from the variable. When your variable parameters include spaces, place double quotation marks before and after the string of characters. For example, enter /PASSPHRASE:"The rain in Spain". ═══ 20.4. Creating Command Files ═══ Create a command (.CMD) file with LAN Distance commands to simplify routine dialing tasks. The following sample REXX command file uses LDIST commands to dial a workstation. If the connection to the workstation is successful, the command file then uses IBM LAN Requester commands to log on and access file resources. Sample REXX Procedure for Dialing /****************************************************************************/ /* This program will start the LAN Distance product, dial a phone book */ /* entry called MYSRVR, log onto the LAN Distance Connection Server */ /* (providing a passphrase), log the user onto the LAN server, and access */ /* two network drives. Optionally, if the user starts this program */ /* specifying a /p (or /P) parameter, the user will be prompted for the */ /* phone number, user ID, and passphrase to be used for this execution */ /* of the program. Also, help is provided if ? is specified when starting */ /****************************************************************************/ arg provide 'echo off' if provide = '?' then do say 'This program will start LAN Distance, dial a number from your' say 'phone book, log your ID onto the LAN Distance server, log an ID onto' say 'the LAN server, and attach network drives. If you wish to provide' say 'a number to dial, and a user ID/passphrase at the time you execute' say 'this program, start this program using the /p option. (i.e. DIALSRV /p)' say ' ' say ' ' say 'To execute the program now, with prompts for number to call, user ID' say 'and passphrase, enter the letter p now. To end the program now, just' say 'press Enter...' pull gonogo if gonogo <> 'P' then signal END_NOW provide = '/P' end /***************************************************************************/ /* First, start LAN Distance */ /***************************************************************************/ say 'Starting LAN Distance...' 'ldstart' /***************************************************************************/ /* Next, call the Phonebook entry named MYSRVR, and log on user REMOTE1, */ /* providing the passphrase, which in this case is 'password'. */ /***************************************************************************/ if provide = ' ' then do say 'Calling the LAN Distance Connection Server...' 'ldist dial /D:MYSRVR /U:REMOTE1 /P:password' end /**************************************************************************/ /* If running in 'Prompt' mode, get required number, User ID and password */ /**************************************************************************/ if provide = '/P' then do say 'Enter the number you want to dial:' pull newnum say ' ' say ' ' say 'Enter your User ID for signing onto the LAN Distance server:' pull userid say ' ' say ' ' say 'Enter your passphrase, if this User ID requires a passphrase:' say '(Remember, your passphrase is case sensitive.)' parse pull password say 'Calling the LAN Distance Connection Server...' 'ldist dial /D:"DIAL LOCATION" /N:'||newnum' /U:'||userid' /P:'||password end /***************************************************************************/ /* Now, log onto the LAN server domain TESTDOM, as user BJONES */ /***************************************************************************/ 'logon bjones /D:testdom' /***************************************************************************/ /* And attach a couple of aliases as drives M: and X: Of course, these */ /* drives can be changed to whatever the user wishes to access during the */ /* execution of this program, or can be deleted or replaced with other */ /* operations the user wishes to perform. */ /***************************************************************************/ 'net use m: testfile' 'net use x: tools' /***************************************************************************/ /* End of procedure */ /***************************************************************************/ END_NOW: 'echo on' say ' ' say ' ' say ' ' say 'Finished!' exit This sample REXX command file releases use of the file resources, and stops the LAN Distance connection. Sample REXX Procedure to Hang Up /***************************************************************************/ /* This program will reverse the process initiated by DIALSRV.CMD. That */ /* is, it will drop the network drives M: and X: (which were attached */ /* during DIALSRV), and log the user off the LAN server. It will then */ /* (optionally) stop LAN Distance, hanging up all active calls. */ /* Help is provided if ? is the load-time option. */ /***************************************************************************/ arg provide 'echo off' if provide = '?' then do say 'This program will drop the connection to the network drives M: and X:' say 'which were attached by the program DIALSRV. Then this program will ' say 'log the user off from the LAN Server, then (optionally) will stop ' say 'LAN Distance, hanging up the active call to the LAN Distance Connection' say 'server.' say ' ' say ' ' say 'To execute this program now, enter the letter p. To exit this ' say 'program now, just press Enter...' pull gonogo if gonogo <> 'P' then signal END_NOW provide = '/P' end /***************************************************************************/ /* First, drop use of the network drives M: and X: */ /***************************************************************************/ say 'Dropping use of network drives...' 'net use m: /d' 'net use x: /d' /***************************************************************************/ /* Next, log the user off from the LAN Server. */ /***************************************************************************/ say 'Logging off from LAN Server...' 'logoff' /**************************************************************************/ /* If running in 'Prompt' mode, see if they want to stop LAN Distance. */ /**************************************************************************/ if provide = '/P' then do say ' ' say ' ' say 'Do you want to hang up your calls and stop LAN Distance? (Y/N)' pull stopit if stopit <> 'Y' then signal END_NOW end /***************************************************************************/ /* Stop the LAN Distance product, which will also hang up all active calls.*/ /***************************************************************************/ say 'Stopping LAN Distance...' 'ldist stop /Y' /***************************************************************************/ /* End of procedure */ /***************************************************************************/ END_NOW: 'echo on' say ' ' say ' ' say ' ' say 'Finished!' exit For more information on REXX, see the OS/2 REXX Reference and the OS/2 REXX User's Guide. ═══ 20.4.1. Using Return Codes with Commands ═══ Successful LAN Distance commands return a value of 0; unsuccessful commands return non-zero values. Check the return code from a command to determine if your command procedure should continue or exit. ═══ 20.5. LDSTART ═══ LDSTART Purpose Starts LAN Distance services and (optionally) opens the LAN Distance Workstations window. Examples This example starts the LAN Distance product. LDSTART This command will start the LAN Distance product and open the LAN Distance Workstations window. LDSTART START /UI Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDSTART──┬───────────┬──>< │ │ └─START /UI─┘ │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters When you use the LDSTART command without parameters, the LAN Distance product is started but the LAN Distance Workstations window is not opened. You can use the following parameter with this command: START /UI Specifies that the LAN Distance Workstations window should be opened. Issuing the LDSTART START /UI command is equivalent to opening the LAN Distance icon on the desktop. Remarks Use the LDSTART command to start LAN Distance when you want to use LAN Distance functions by entering commands rather than through the user interface. The LDSTART command:  Starts basic services in the LAN Distance product so that your workstation can communicate with other LAN Distance workstations.  Starts any modem types configured as AUTOSTART = YES in the WCLNET.INI file. These modem types are ready to place outgoing calls and receive calls.  Starts autoanswer for any answer modes that are configured as Enable answer mode on startup. This means that your LAN Distance workstation is ready to receive incoming calls. Note: If you will use the product through the LDIST command interface, and you are not going to open the LAN Distance Workstations window, you must issue the LDSTART command before issuing LDIST commands. ═══ 20.6. LDIST START ═══ LDIST START Purpose Starts a modem type or starts autoanswer. Examples The following command starts autoanswer for an answer mode. named PSTN_ALL_CALLS: LDIST START /A:PSTN_ALL_CALLS Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDIST START──┬─/A:answermode─┬──>< │ │ └─/M:modemtype──┘ │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters You must specify a parameter with LDIST START: /A:answermode Specifies the name of the answer mode to be started. answer mode names are case-sensitive. /M:modemtype Specifies the name of the modem type to be started. Remarks Use this command to start autoanswer or to start a modem type after the LAN Distance product has been started. ═══ 20.7. LDIST STOP ═══ LDIST STOP Purpose Stops a modem type, autoanswer, or the LAN Distance product. Examples The following command will stop a modem type named "HAYES_MODEMS". No new connections will be made for this modem type, but any current connections will remain active until the users disconnect them. LDIST STOP /M:HAYES_MODEMS The following command will stop the modem type named "HAYES_MODEMS", and immediately stop any active connections for the modem type. LDIST STOP /M:HAYES_MODEMS /IMMEDIATE The following command will stop the LAN Distance product (including any active connections). You will not be prompted with a pop-up message to confirm the stop. LDIST STOP /IMMEDIATE /Y Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDIST STOP──┬───────────────┬──┬────────────┬──┬────┬──>< │ │ ├─/A:answermode─┤ └─/IMMEDIATE─┘ └─/Y─┘ │ │ └─/M:modemtype──┘ │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ If you issue the LDIST STOP command without parameters, the LAN Distance product is stopped. If you issue the LDIST STOP command with a parameter of answermode or a modemtype, only the item specified is stopped. You can use the following parameters with this command: Parameters /A:answermode Specifies the name of the answer mode to be stopped. No new incoming calls for answermode will be accepted. answer mode names are case-sensitive. /M:modemtype Specifies the name of the modem type to be stopped. No new calls will be accepted for modemtype. If calls are active for modemtype, and you do not use the IMMEDIATE option, the LDIST STOP command will not complete until the calls are stopped. /I(MMEDIATE) Specifies whether connections should be stopped immediately. If the IMMEDIATE option is specified on a LDISTSTOP command, all LAN Distance services (including active connections) will be stopped immediately. If the IMMEDIATE option is specified for autoanswer, autoanswer will be stopped and all incoming calls associated with the answer mode will be immediately disconnected. If the IMMEDIATE option is specified for a modem type, the modem type will be stopped (no longer available for making calls), and any active calls for the modem type will be immediately disconnected. If the IMMEDIATE option is not specified, connections will remain active until users end them. For example, if a LDIST STOP /A: is issued, no new incoming calls will be allowed, but active connections associated with the answer mode will remain active until ended by users. The LDIST STOP command will not complete until the calls are stopped. /Y(ES) Bypasses the confirmation pop-up message. This option is available when you are stopping the LAN Distance product. If you use this keyword parameter, you will not get a pop-up message to confirm the stop. If you do not supply this parameter, a pop-up message will prompt you to confirm that you want to stop the LAN Distance product. Remarks If the LDIST STOP command is issued, any open LAN Distance windows will be closed and the LAN Distance product will be stopped. ═══ 20.8. LDIST LOGON ═══ LDIST LOGON Purpose Obtains access to a LAN Distance workstation. Examples The following example shows the commands necessary to dial out of a secure LAN Distance workstation. The workstation could be a secure LAN Distance Remote or a secure LAN Distance Connection Server. LDIST LOGON /S:MyWorkstation /U:MyUserId /P:MyPassphrase LDIST DIAL /D:RemoteServer Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDIST LOGON──/S:server──┬───────────┬──opt./P:passphrase──>< │ │ └─/U:userid─┘ │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters You must use the following parameters with this command: /S:server The name of the secure LAN Distance Connection Server or LAN Distance Remote that you are logging on to. /U:userid Your user ID. If you do not supply this parameter, a pop-up window will prompt you for the information. /P:passphrase Your passphrase. If you do not supply this parameter, a pop-up window will prompt you for the information. Passphrases are case-sensitive. Remarks Use the LDIST LOGON command to obtain access to a machine before dialing out with the LDIST DIAL command. Log on only to workstations that are enabled for LAN Distance security. Specifying a user ID and passphrase with the LDIST LOGON command is not required. If you enter LDIST LOGON, the LAN Distance Logon window is displayed. Note: The keyboard lights for the Caps Lock, Scroll Lock and Num Lock may fail to light up if you use one of these keys to enter user ID and passphrase information in the LAN Distance Logon window. This problem is only temporary. When the LAN Distance Logon window is closed, these lights will function normally. ═══ 20.9. LDIST LOGOFF ═══ LDIST LOGOFF Purpose Logs off a LAN Distance workstation. Examples The following example shows the command for logging off a workstation named "MyWorkstation". LDIST LOGOFF /S:MyWorkstation Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDIST LOGOFF──/S:server──>< │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters You must use the following parameter with this command. /S:server The name of the secure LAN Distance Connection Server or LAN Distance Remote that you are logging off. Remarks If you are logging off a workstation with open windows, the windows will be closed. If you log off a secure workstation that you have dialed, the connection to that workstation remains active. ═══ 20.10. LDIST DIAL ═══ LDIST DIAL Purpose Dials a LAN Distance workstation and (optionally) automatically logs on to that workstation. Examples The following example demonstrates making a call from the command line for phone book entry "Remote Server". LDIST DIAL /D:"Remote Server" /U:UserId /P:"The rain in Spain" The status displayed will look similar to the following example, depending on your modem type and the redial and callback configuration. ATDT555-5555 RING RING CONNECT ECL/9600 Waiting for callback The request has completed successfully. You may notice a delay between receiving the modem's CONNECT message and the completion message, while the LAN Distance product exchanges information with the workstation you are dialing. Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDIST DIAL──/D:direntry──┬───────────┬──opt./U:userid──> │ │ └─/N:number─┘ │ │ │ │ >──┬───────────────┬──>< │ │ └─/P:passphrase─┘ │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters You must use the following parameters with this command. /D:direntry Name of the phone book entry. This is the name of a phone book entry that was configured in the Phone Book - Settings notebook. Phone book entry names are case-sensitive. /N:number This is an optional telephone number to override the telephone number configured in direntry. If direntry has more than one number configured (for redial), this number will override the first configured number. This number is not permanently stored in the configuration for direntry. /U:userid User ID for automatic logon to the secure LAN Distance workstation that is being dialed. /P:passphrase Passphrase for automatic logon to the secure LAN Distance workstation that is being dialed. Passphrases are case-sensitive. Remarks If a user ID and passphrase are given, the LAN Distance product will automatically log on after a connection is established. If a user ID and passphrase are not supplied and the LAN Distance workstation you are dialing is secure, a pop-up window will prompt you for logon information. As the connection is being made, modem status is displayed. If the connection cannot be made and you configured for automatic redial, redial status is displayed. Also, callback status is displayed if your workstation must be called back. The connection can be disconnected with the LDIST HANGUP command or through the LAN Distance Phone Book window. ═══ 20.11. LDIST HANGUP ═══ LDIST HANGUP Purpose Hangs up an active outgoing connection. Examples The following command will hang up an active connection with phone book entry "Remote Server". LDIST HANGUP /D:"Remote Server" Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDIST HANGUP──/D:direntry──>< │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters You must use the following parameter with this command. /D:direntry Name of the phone book entry. Phone book entry names are case-sensitive. Remarks You can use this command whether the connection was made with the LDIST DIAL command or through the Phone Book window. ═══ 20.12. LDSHUTTL ═══ LDSHUTTL Purpose Allows a LAN Distance Remote to function as LAN or stand-alone workstation. Use this command to move a workstation between a LAN environment and a stand-alone environment. Examples This command will shuttle your workstation to function on a LAN. LDSHUTTL LAN Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDSHUTTL──┬────────┬──>< │ │ ├─LAN────┤ │ │ └─REMOTE─┘ │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Parameters You can use the following parameters with this command. If a parameter is not specified, a pop-up window will prompt you for the environment to shuttle to. REMOTE Specifies that the workstation should be switched to function in a stand-alone environment. LAN Specifies that the workstation should be switched to function in a LAN environment. Remarks Two configurations are maintained for the workstation, one that sends LAN protocol data over a LAN adapter, and one that sends LAN protocol data over your WAN hardware. The shuttle function switches the workstation to use the appropriate configuration for the environment specified. After you enter the LDSHUTTL command, you must shutdown and restart your workstation. The LAN Distance product operates only when your workstation is in a stand-alone environment. ═══ 20.13. LDREMOVE ═══ LDREMOVE Purpose Removes the LAN Distance product from your workstation. Examples This command will remove the LAN Distance product from your workstation. LDREMOVE Syntax ┌──────────────────────────────────────────────────────────────────────────────┐ │ │ │ >>──LDREMOVE──>< │ │ │ └──────────────────────────────────────────────────────────────────────────────┘ Remarks When you enter this command, a window will display to confirm that you want to remove the product from your workstation. If you have erased the LAN Distance files from your workstation, you can still use the LDREMOVE command to remove LAN Distance configuration information from your workstation. To do this, insert the Diskette 1 in the diskette drive, and type LDREMOVE. ═══ 21. Using OS2PING for Troubleshooting and LAN Distance Bridge Configuration ═══ OS2PING is a multipurpose tool designed for Token-Ring LAN configuration and problem determination. OS2PING is provided with the LAN Distance product so you can use it for troubleshooting and LAN Distance bridge configuration tasks:  Verify that a communications path exists between 2 workstations in your LAN Distance wide area network.  Verify that the hop count defined at the LAN Distance bridge is large enough to allow data from the sending workstation to reach the receiving workstation.  Gather routing information to configure the LAN Distance bridge on a Token-Ring LAN in a multisegmented network environment. MSWIN MS Windows LAN Distance Remotes can use LANPING, the DOS version of OS2PING. See Using the LANPING Tool for MS Windows. ═══ 21.1. Using the OS2PING Tool ═══  The OS2PING tool is installed in the WAL directory when the LAN Distance product is installed. You can run OS2PING from a LAN Distance Remote or LAN Distance Connection Server.  OS2PING requires the IEEE 802.2 LAN protocol. Add the 802.2 LAN protocol to the protocols configured for the LAN Distance Logical Adapter. See Configuring Additional LAN Protocols Required for Your OS/2 LAN Applications.  Online help for the OS2PING tool is provided in the OS2PING.INF file. To view help information, from an OS/2 command line, type: VIEW OS2PING.INF  The syntax for the OS2PING command is shown below. In place of the -a parameter, specify the Token-Ring or Ethernet address of the destination workstation. The -r parameter is the option to return and display routing information. OS2PING -a=1234567890ABC -r  The bridge or router hardware between different LANs (Token-Ring and Ethernet) can bit-inverse LAN addresses. This is a consideration when using OS2PING across different LAN types. Follow these guidelines: - If the destination address is on a Token-Ring LAN, use the Token-Ring address, regardless of the LAN type (Token-Ring or Ethernet) used by the LAN Distance product. - If the destination address is on a Ethernet LAN, bit inverse the Ethernet address, regardless of the LAN type (Token-Ring or Ethernet) used by the LAN Distance product. Note: For information about bit-inversing LAN addresses, see Using Bit-Inverted Addresses to Filter Traffic between Token-Ring and Ethernet LAN Segments. ═══ 21.2. Using the LANPING Tool for MS Windows ═══ MS Windows LAN Distance Remotes can use LANPING as OS2PING is used: to verify a physical connection, check the hop count defined for the LAN Distance bridge, and gather information for LAN Distance bridge configuration.  LANPING is installed when the MS Windows LAN Distance Remote product is installed. LANPING is located in the WAL directory. You can run LANPING from a MS Windows LAN Distance Remote workstation.  LANPING requires the IEEE 802.2 LAN protocol. Use LSP to install the 802.2 protocol. See Determine the Appropriate Method for Installing LSP.  The syntax for the LANPING command is shown below. Specify this command from the MS Windows Run Command Line or from a DOS command prompt. In place of the -a parameter, specify the Token-Ring or Ethernet address of the destination. The -r parameter is the option to return and display routing information. LANPING -a=1234567890ABC -r ═══ 21.3. Example 1: Using OS2PING to Verify a Communications Connection ═══ If you experience problems establishing a connection to a LAN Distance workstation, or to another workstation (or resource) in your network, use the OS2PING tool to verify that a your workstation's address can communicate with a destination workstation's address. Multisegmented Token-Ring LAN Environment In the following example, the LAN Distance Remote shown in Multisegmented Token-Ring LAN Environment is using OS2PING to verify 1) the communications path from LAN Distance Remote to the LAN Distance Connection Server on LAN segment CEA and 2) the communications path to the LAN Server Domain Controller on LAN CEA. To verify that a communications path exists between the LAN Distance Remote and the LAN Distance Connection Server on LAN segment CEA: 1. Establish a LAN Distance connection from the LAN Distance Remote to the LAN Distance Connection Server on segment CEA. 2. To verify that the LAN Distance Remote can communicate with the LAN Distance Connection Server, run OS2PING from the LAN Distance Remote using the LAN Distance logical adapter network address of the LAN Distance Connection Server (400012345678). From an OS/2 command prompt, type OS2PING -a=400012345678 -r, then press Enter. 3. If OS2PING returns routing information, as shown in OS2PING Token-Ring Routing Information, the LAN Distance Remote and LAN Distance Connection Server can communicate over the LAN Distance connection. If the No Responses Received Message is displayed, one of the following problems can exist:  An incorrect LAN Distance logical adapter network address was specified for the LAN Distance Connection Server.  The LAN Distance Remote or LAN Distance Connection Server is not correctly configured. To verify that a communication path exists between the LAN Distance Remote and the LAN Server Domain Controller on LAN CEA: 1. Establish a LAN Distance connection from the LAN Distance Remote to the LAN Distance Connection Server on LAN segment CEA. 2. To verify that the LAN Distance Remote can communicate with the LAN Server Domain Controller on LAN segment CEA, run OS2PING from the LAN Distance Remote using the LAN network address of the LAN Server Domain Controller (400087654321). From an OS/2 command prompt, type OS2PING -a=400087654321 -r, then press Enter. 3. If a communications path exists between the LAN Distance Remote and the LAN Server Domain Controller, OS2PING returns routing information. If multiple paths between workstations exist, more than one line of routing information is displayed as shown in the example in OS2PING Token-Ring Routing Information. Note: If your destination address is an Ethernet address, routing information is not displayed because transparent bridging is used by Ethernet LANs. OS2PING Token-Ring Routing Information OS2PING: First response received OS2PING: ADDR=xxxxxxxxxxxx Route was: (002) 1 --> (cea) 7 --> (b22) 5 --> (c3a) OS2PING: Later response(s) : OS2PING: ADDR=xxxxxxxxxxxx Route was: (002) 1 --> (cea) 7 --> (b22) 5 --> (c3a) OS2PING: ADDR=xxxxxxxxxxxx Route was: (002) 1 --> (cea) 7 --> (4ab) 2 --> (c21) 3 --> (b31) 5-->(c3a) If a physical connection does not exist, or an incorrect address was used, OS2PING returns the "No responses received message" See Resolving the `No Responses Received' Message.. ═══ 21.4. Example 2: Using OS2PING to Verify the LAN Distance Bridge Hop Count ═══ If you experience problems establishing a LAN Distance connection, use the OS2PING tool to verify that the hop count defined for the LAN Distance bridge is large enough to allow data frames from the sending workstation to reach the receiving workstation. In the following example, the LAN Distance Remote shown is using OS2PING to count the number of bridges between the LAN Distance Remote on WAN segment 002 and the LAN Server on LAN segment C3A. 1. Establish a LAN Distance connection from the LAN Distance Remote to the LAN Distance Connection Server on LAN segment CEA. 2. Run OS2PING using the LAN network address of the LAN Server on C3A to count the number of bridges between the LAN Distance Remote and the LAN Server (400012345ABC). 3. From an OS/2 command line, type OS2PING -a=400012345ABC -r, then press Enter. 4. OS2PING displays routing information for the path between the LAN Distance Remote and the LAN Server on LAN segment C3A. OS2PINGToken - RingRoutingInformation (002) 1 --> (CEA) 7 --> (B22) 5 --> (C3A) (WAN-1) LD Bridge (LAN-2) Bridge (LAN-3) Bridge (LAN-4) The routing information displayed in OS2PING Token-Ring Routing Information indicates:  Three bridges were crossed from the LAN Distance Remote on segment 002 to the LAN Server on segment C3A. (One LAN Distance bridge and 2 Token-Ring bridges.)  For this example, the hop count defined for the LAN Distance bridge should be equal to or greater than 3. ═══ 21.5. Example 3: Using OS2PING to Define LAN Distance Bridge Configuration Values ═══ This example uses the routing information from Example 2 to show how to interpret OS2PING routing information, and use this routing information to configure the LAN Distance bridge. ═══ 21.5.1. Interpreting OS2PING Routing Information ═══ The routing information displayed in OS2PING Token-Ring Routing Information indicates:  The values in parentheses are segment ring numbers. 002 is the WAN segment ring number and CEA, B22, and C3A are the LAN segment ring numbers.  The LAN Distance bridge is number 1, and the other Token-Ring LAN bridges are numbered 7 and 5.  Three bridges (one LAN Distance bridge and 2 Token-Ring bridges) were crossed from the LAN Distance Remote on WAN segment 002 to the LAN Server on LAN segment C3A.  LAN Distance Connection Server segment ring number is CEA. OS2PING Token-Ring Routing Information (002) 1 --> (CEA) 7 --> (B22) 5 --> (C3A) (WAN-1) LD Bridge (LAN-2) Bridge (LAN-3) Bridge (LAN-4) ═══ 21.5.2. Defining Configuration Values for the LAN Distance Bridge ═══ The routing information from Example 1: Using OS2PING to Verify a Communications Connection is used as an example to define the LAN Distance bridge configuration values shown in LAN Distance Bridge Configuration Example. Bridge configuration values are entered on pages 1, 2, and 3 of the Bridge tab in the Settings notebook. See Setting Up the LAN Distance Bridge. Remember these requirements for LAN Distance bridge configuration values:  In a multisegmented LAN environment, the LAN Distance bridge number, LAN segment ring number, and WAN segment ring number must combine to form a unique route designator.  The hop count defined for the LAN Distance bridge should be equal to or greater than the number of bridges (including the LAN Distance bridge) between the sending and receiving workstations.  Your LAN Distance LAN segment ring number must match the number defined for your LAN segment at other bridges in your LAN environment.  Your LAN Distance WAN segment ring number must be unique. ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 40. LAN Distance Bridge Configuration Example │ ├────────────┬───────┬─────────────────────────────────────────────────────────┤ │ FIELD │ VALUE │ EXPLANATION │ ├────────────┼───────┼─────────────────────────────────────────────────────────┤ │ Bridge │ 1 │ OS2PING returned routing information, so the default │ │ number │ │ LAN Distance bridge number of 1 can be used. │ ├────────────┼───────┼─────────────────────────────────────────────────────────┤ │ LAN │ CEA │ This is the segment number for the LAN that the LAN │ │ segment │ │ Distance Connection Server is connected to. │ │ ring │ │ │ │ number │ │ │ ├────────────┼───────┼─────────────────────────────────────────────────────────┤ │ Maximum │ 3 │ The network bridge hop number defined for the LAN │ │ number of │ │ segment (page 2 of 2) should match the network bridge │ │ network │ │ hop number defined for the WAN segment (page 3 of 3). │ │ bridge │ │ │ │ hops │ │ Calculate the minimum value for the hop count by adding │ │ │ │ the LAN Distance bridge and the 2 Token-Ring bridges │ │ │ │ between the LAN Distance Remote on segment 002 and the │ │ │ │ LAN Server on segment cea. │ ├────────────┼───────┼─────────────────────────────────────────────────────────┤ │ WAN │ 002 │ OS2PING returned routing information, so the default │ │ segment │ │ WAN segment ring number of 2 can be used. │ │ ring │ │ │ │ number │ │ The WAN segment ring number must be different than the │ │ │ │ LAN segment ring number. │ ├────────────┼───────┼─────────────────────────────────────────────────────────┤ │ Maximum │ 3 │ The network bridge hop number defined for the WAN │ │ number of │ │ segment (page 3 of 3) should match the network bridge │ │ network │ │ hop number defined for the LAN segment (page 2 of 2). │ │ bridge │ │ │ │ hops │ │ Calculate the minimum value for the hop count by adding │ │ │ │ the LAN Distance bridge and the 2 Token-Ring bridges │ │ │ │ between the LAN Distance Remote on segment 002 and the │ │ │ │ LAN Server on segment CEA. │ └────────────┴───────┴─────────────────────────────────────────────────────────┘ ═══ 21.5.3. Resolving the `No Responses Received' Message. ═══ If OS2PING is unable to find the destination address you specify, the following message is returned: OS2PING: No responses received during 10 second wait. This message can be displayed for any of the following reasons:  The default -wait parameter (10 seconds) does not allow enough time for a response to be returned.  An incorrect address was specified for the destination workstation.  A workstation on the LAN may not be correctly attached to the LAN or correctly configured for LAN communications.  The hop counts defined for the LAN Distance bridge or other hardware bridges are not large enough to allow data from the sending workstation to reach the receiving workstation.  The segment numbers for your LAN Distance bridge are not configured correctly. The following troubleshooting steps address these problems. If you receive the No Responses Received Message, try using these steps to test your communications connections. 1. The -wait parameter specifies the amount of time (in seconds) to wait for a response. Increase the -wait parameter (the default is 10 seconds). In this example, the -wait parameter is increased to 30 seconds. OS2PING -a=1234567890ABC -r -w=30 2. To verify that the LAN Distance Connection Server is properly attached to the LAN, from the LAN Distance Connection Server run OS2PING using the address of LAN workstation on the LAN Distance Connection Server's LAN segment. If routing information is returned, the LAN Distance Connection Server is properly attached and configured for LAN communications. 3. To verify the address for the destination LAN workstation on the LAN, from the LAN Distance Connection Server run OS2PING using the destination address of the LAN workstation. If routing information is returned, you know 1) that you are using the correct destination address and 2) that the LAN Distance Connection Server can communicate with the destination LAN workstation. 4. To verify the LAN Distance WAN connection between a LAN Distance Remote and a LAN Distance Connection Server, from the LAN Distance Remote run OS2PING using the LAN Distance logical adapter network address of the LAN Distance Connection Server. If routing information is returned, the 2 workstations can communicate over the LAN Distance WAN connection. 5. To check the hop counts between a LAN Distance Remote and a destination workstation on the LAN, from the LAN Distance Remote run OS2PING using the address of a workstation on each LAN segment between the LAN Distance WAN segment and the destination workstation's LAN segment. For example, if the destination workstation is on LAN-4, from the LAN Distance Remote, run OS2PING using the destination address of a workstation on LAN-1, LAN-2, and LAN-3. If routing information is returned for all of the LANs except for LAN-3, try increasing the hop count for bridge between LAN-2 and LAN-3. 6. To ensure that the segment numbers for your LAN Distance bridge are configured correctly, review the information in Defining Configuration Values for the LAN Distance Bridge. ═══ 22. Modifying Modem Strings in a LAN Distance PIF File ═══ Product information files (PIFs) contain the configuration values and modem string information needed to initialize a modem. Each modem type supported by the LAN Distance product has its own PIF file (stored in the WAL directory). A sample PIF file for the IBM7855 modem is provided in this appendix. The following tasks are described in this chapter:  Use the graphical Port/Modem utility to create a modem type for a modem not listed in the Available modem types list box. See Using the Port/Modem Utility.  Manually create a new PIF file for a modem type not listed in the Available modem types list box. See Creating a New PIF File for a Modem Not in the List.  Use the graphical Port/Modem utility to customize an asynchronous modem's dial string for calling card user. See Modifying a Dial String for Outside Calls.  Manually customize an asynchronous modem's dial string for calling card use by editing the PIF file. See Modifying a Dial String for Outside Calls.  Use the graphical Port/Modem utility to modify the serial port speed for your asynchronous modem. See Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports.  Manually modify the serial port speed for asynchronous modems. See Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports. Note: To modify configuration values and modem strings in a LAN Distance PIF file, you need technical knowledge of modems and experience in configuring communications software. The instruction manual for your modem contains important information about AT command set modem commands, dial modifiers, and default configuration values for your modem. You will need to refer to your modem user documentation to complete the tasks described in this chapter. ═══ 22.1. Using the Port/Modem Utility ═══ Use the Port/Modem utility to create a new modem type to configure your unlisted modem if:  You are unable to configure your unlisted modem using a listed modem as described in What to Do If Your Modem Is Not Listed.  You cannot establish a connection using the PIF file you created in Creating a New PIF File for a Modem Not in the List. After you create a new modem type for your unlisted modem, you can use the Port/Modem utility to configure your new modem type and test the new modem type to see if it will work with the LAN Distance product. ═══ 22.1.1. Starting the Port/Modem Utility ═══ To start the Port/Modem utility, type CFMODEM from an OS/2 command prompt. Port/Modem Utility Notebook ═══ 22.1.2. Creating a New Modem Type for a COM Port ═══ Follow these steps to create a new modem type for your unlisted modem using the Port/Modem utility: 1. Start the Port/Modem utility. From the Port/Modem utility notebook (shown below), select the Strings tab. 2. From the Strings tab, select the Select modem type push button. Port/Modem Notebook, Available Modem Types Window Select a similar modem type from the Available modem types list box (Port/Modem Notebook, Available Modem Types Window) to use as a model for creating your new modem type. To select a similar modem type, use the following guidelines:  Select a modem type from the same manufacturer.  If your modem is compatible with a listed modem type, select the compatible modem.  Select the Asynchronous Switched Connection Modem type.  Select any of the other modem types listed. 3. Select the Create a new asynchronous modem type using the selected modem type as a model check box. 4. Specify a title for the new modem type in the modem type field. A title is required to identify your new modem type among the many modem types listed in the Available modem types field. Select the OK push button. The title of the modem type you are creating is displayed in the Modem title field on the Strings tab (Port/Modem Notebook, Strings Tab). Port/Modem Notebook, Strings Tab 5. Create an initialization string for your new modem type, select the Build string push button. The Port/Modem Build String window (Port/Modem Notebook, Build Strings Window) is displayed. Port/Modem Notebook, Build Strings Window 6. Use the documentation for your unlisted modem to answer questions 1 through 19 on the Build Strings window. Answers to these questions are unique to your modem and are used to build the initialization string for your modem (shown on Page 1 of 2 of the Strings tab). When you have answered all the questions, select the OK push button. 7. From the Strings tab, select the Save push button to save the initialization string (Initialization 1 and Initialization 2) created for your new modem type. Note: Optional configuration values for fine tuning your modem are available on Page 2 of 2 of the Strings tab. ═══ 22.1.3. Configuring a New Modem Type ═══ Follow these steps to configure the new modem type: 1. Select the Ports tab (Port/Modem Utility Notebook, Ports Tab) to define required COM port parameters and assign a COM port to your modem type. Port/Modem Utility Notebook, Ports Tab From the COM port field, select the COM port (COM1, COM2...) that your modem is connected to. From the Line type field, select the Switched radio button. (Use this default setting for switched and nonswitched telephone lines) 2. Select the Save push button to save the configuration settings for your COM port. 3. Select the Assign tab and select the Assign push button to display the Port/Modems Assignments window (Port/Modem Assignments Window). 4. From the Available modem types list box, select the modem type you created. From the Unassigned configured ports list box, select your COM port. Port/Modem Assignments Window Select the Link push button to link your COM port and modem type selections. Selecting the Link push button displays the Phone number window. This gives you the option of specifying a telephone number or a permanent connection name. 5. Select Exit from the Port/Modem Assignments window, to return to the Assign tab. The COM port and modem type you linked are displayed in the list box (Port/Modem Notebook, Assign Tab). Port/Modem Notebook, Assign Tab ═══ 22.1.4. Testing the New Modem Type ═══ Follow these steps to test the new modem type: 1. From the Assign tab (Port/Modem Notebook), select the Test string push button to test the initialization string for your new modem type. If you receive a message stating that the maximum speed for your port has been updated, this indicates that your new modem type can use the initialization string you created. It also indicates that you should be able to dial out and establish a LAN Distance connection using your modem. If you receive a message stating that there is an error with the initialization string you created, return to the Port/Modem Build Strings window to verify the answers supplied to questions 1 through 19. Use your modem manual to verify your answers. Then rebuild and retest your initialization string. Note: If you are unable use the modem type created using the Port/Modem utility to establish a LAN Distance connection, and you tried creating a new PIF file for your modem type, contact your designated support organization for assistance. ═══ 22.2. Creating a New PIF File for a Modem Not in the List ═══ If you are unable to establish a LAN Distance connection with your unlisted modem using a listed modem type as described in What to Do If Your Modem Is Not Listed, you can:  Create a new modem type using the graphical Port/Modem utility. See Using the Port/Modem Utility.  Manually create a new modem type by creating a new PIF file. Complete the steps listed in this section. Follow these steps to create a PIF file: Select a PIF File to Use as a Template 1. Open the Settings notebook, select the Modems tab and select the Assign push button. 2. From the Available modem types field, scroll through the list to identify a modem similar to yours. 3. Try the following strategies, as listed, to select a comparable modem type from the Available modem types field: a) Select a modem made by the same manufacturer. b) If your modem is compatible with a supported modem type, select the compatible modem type. c) Select the Asynchronous Switched Connection Modem type. d) Select any remaining listed modem type. Record the name of the modem type you identify as similar to your modem. 4. In Modems Supported by the LAN Distance Product in Modems, find the PIF file name that matches the modem type you recorded in step Creating a New PIF File for a Modem Not in the List. 5. Make a copy of that PIF file to use as a template.  From an OS/2 command prompt, type CD WAL to go to the WAL directory.  Type COPY oldfile.PIF newfile.PIF. Oldfile is the name of the PIF file identified in step Creating a New PIF File for a Modem Not in the List and newfile is the new name of your new PIF file. Modify the Template PIF File for Your Modem Use any ASCII text editor to modify the template PIF file. This example uses the OS/2 system editor. 6. To modify the template PIF file to create a PIF file for your modem:  From an OS/2 command prompt, type CD WAL to go to the WAL directory.  From the WAL directory, type E newfile.PIF and press Enter. Newfile is the new name of your new PIF file. 7. In your template PIF file, modify the following parameters. The values listed here are taken from the example PIF file for the IBM 7855 Modem, provided later in this section. PIF = IBM7855.PIF This parameter contains the name of the file you are using as a template. Choose an 8-character file name that is specific to your modem, and use PIF as the file extension, for example PDQMODEM.PIF. Title = "IBM 7855 Modem" Choose a title description that is specific to your modem and will be easy for you to recognize in a list of other modems. You can enter up to 60 characters, for example "PDQ Giga Bit Screamer". The opening and closing quote marks are required. If you have already specified a title description, you do not need to change it. [SerialPortSpeed] The default value for the serial port speed specifies the speed at which data is passed between the serial port and the modem. It is also called the modem-to-computer or DTE line speed. Use your modem manual to determine the speed to specify when the modem is using internal data buffering. The left and right brackets are required. [Initialization1] [Initialization2:] 8. In the template PIF file, you may need to change the default initialization string to meet the configuration requirements described in steps a through g. The commands for these configuration requirements can vary from modem to modem, consult your modem manual for the correct commands for your modem. AT command set commands are entered on the Default = lines of the [Initialization1] and [Initialization2] section of the PIF file. Use LAN Distance required characters to represent the following characters in the initialization string. Characters LAN Distance Required Characters carriage return character \CR line feed character \LF backslash character \\ Change your template PIF file as follows: a) DTR (Data Terminal Ready) The DTR signal indicates to the modem when the computer is ready to send and receive information. Different modem commands cause the modem to interpret the DTR signal in various ways. Select the modem command that configures the modem to hang up and enter the command state if the DTR signal turns off. The modem should not respond to incoming calls when the DTR signal is low. Do not configure the DTR command so the modem resets when an on-to-off transition occurs. (For most modems, the correct command is &D2). b) CD (Carrier Detect) The CD signal tracks the presence or absence of the carrier signal from the modem on the other end of the line. Some modem manuals refer to the CD as the DCD or RLSD. Modems can be configured to interpret the CD in several ways. Select the CD modem command that causes the modem to track the status of the carrier detect signal. (For most modems, this command is &C1.) c) DSR (Data Set Ready) The DSR is a signal the modem sends to the computer to indicate that the modem is ready to start a dialog. Configure the DSR for your modem to go from on to off when a connection ends. (For most modems, the correct command is &S1.) d) RTS/CTS Several types of flow control are supported for most modems. RTS and CTS signals support bidirectional hardware flow control. (Some modem manuals refer to CTS as RFS.) Configure your modem so it supports RTS/CTS flow control. The AT modem command for this feature varies from modem to modem. e) Data Buffering Data buffering prevents loss of data during transmission. It is essential for all communications in which the modem-to-computer (DTE) speed is faster than the modem-to-modem (DCE) speed. Select the data buffering AT command to enable data buffering for your modem. The AT modem command for this feature varies from modem to modem. f) Automatic Answer Set up the modem to automatically answer a call on the second ring. For most modems, this command is S0=n, where n specifies the number of rings before the modem automatically answers the call. Set n to 2. g) Character Echo The character echo feature can be configured to display or not display commands received by the modem when it is in the command state. Select the modem command that enables character echo. (For most modems, this command is E1.) h) 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.) 9. Save your new PIF file in the \WAL directory. Configure Your Modem Using the PIF File You Created 10. Start the LAN Distance product. 11. Open the Settings notebook. 12. If you already have a port configured, continue with step Creating a New PIF File for a Modem Not in the List. If you do not have a port configured, configure one: a) Select the Ports tab, then select the Add push button. b) Select a port then select OK. c) Select the COM port you will assign to the modem. d) Select Switched for Line type. e) Close the COM port window. You now have a port configured. 13. Select the Modems tab. Delete any modem type assigned to your configured port. This only deletes the association between a modem type and a configured port. It does not delete either the modem type or the port configuration. The deletion is necessary in order to pick up the changes made to the PIF file. 14. Select the Assign push button. 15. From the Available modem types field, select the modem type you created for your modem then select OK. The modem type you created will have the name you entered in the Title keyword during step Creating a New PIF File for a Modem Not in the List. 16. From the Ports tab within Modem settings, select Add to continue modem configuration. 17. Select Switched for the type of telephone line. You may also specify an optional Phone Number for the modem. Select OK. 18. From the Available ports field, select the configured port that you want to assign to the modem type. Select OK. 19. Close the Ports tab. 20. Close the Settings notebook and select Yes to save changes. 21. If you made changes to the Ports tab, stop all applications, shut down and restart your workstation. If you only made changes to the Modems tab, stop and restart the LAN Distance product. 22. Establishing a LAN Distance Connection describes how to establish a connection. 23. If you cannot communicate using your modem, retry the steps described in the Select a PIF File to Use as a Template procedure and the Modify the Template PIF File for Your Modem procedure, (steps Creating a New PIF File for a Modem Not in the List through Creating a New PIF File for a Modem Not in the List). Note: If you are unable use the PIF file to establish a LAN Distance connection, and you have tried creating a new modem type using the Port/Modem utility, contact your designated support organization for assistance. ═══ 22.3. Customizing the Dial String for Asynchronous Modems ═══ You may want to modify the modem string to automatically access an outside line or use your calling card each time you dial out through that modem type. When you change the dial string in the PIF file, remember that the dial string is changed for each call placed through any modem managed by this modem type. Choose one of the following methods to customize the dial string for your modem type:  Use the graphical Port/Modem utility to customize the dial string for your modem. Edit the Dial Prefix and Dial Suffix fields on pages 1 and 2 of the Strings tab. See Using the Port/Modem Utility.  Manually customize the dial string in the PIF file by completing the steps listed in this section. To manually customize the dial string in the PIF file for a modem, complete these steps: Modifying the Dial String for an Asynchronous Modem 1. Match a PIF file name to your modem type using Modems Supported by the LAN Distance Product in the Supported Hardware. 2. PIF files contain values required to use your modem with the LAN Distance product. Make a backup copy of the file you are modifying so you always have a copy of your modem's original PIF file.  From an OS/2 command prompt, type CD\ WAL to go to the WAL directory.  From the WAL directory, type COPY filename.PIF filename.BAK. Filename is the name of the PIF file identified in step Customizing the Dial String for Asynchronous Modems. 3. Use any ASCII text editor, such as the OS/2 system editor, to modify your modem's dial string.  From an OS/2 command prompt, type CD\ WAL to go to the WAL directory.  From the WAL directory, type E filename.PIF Filename is the name you gave the copy of your modem's PIF file. 4. Modify the dial string for your dialing requirements. In the PIF file for your modem type, locate the DialPrefix and DialSuffix. The dial string for your modem is made up of the DialPrefix and DialSuffix sections in a PIF file as shown in the following example. [DialPrefix] Display = D12 Type = String StrLength = 255 Default = "ATDT" Optional = NO Help = H12 [DialSuffix] Display = D13 Type = String StrLength = 255 Default = "\CR" Optional = NO Help = H13 When you modify the DialPrefix and DialSuffix in your modem's PIF file: a) See your modem user manual to determine the dial modifiers to use to modify the dial string for your modem. b) Add numbers and dial modifiers at the end of the Default = "ATDT" command in the DialPrefix section at the beginning of the Default = "\CR" command in the DialSuffix section, depending on the telephone requirements. c) When you modify the dial string, represent the following characters using LAN Distance required characters: Characters LAN Distance Required Characters carriage return character \CR line feed character \LF backslash character \\ d) The modem responds to the commands in the DialPrefix before the telephone number is dialed, and to the commands in the DialSuffix after the telephone number is dialed. Example 1: Customizing the Dial String to Make Outside Calls To dial "9" and wait for a second dial tone, add "9W" to the end of the default DialPrefix string. The "W" dial modifier instructs the modem to wait for a second dial tone before proceeding. Modifying a Dial String for Outside Calls [DialPrefix] Display = D12 Type = String StrLength = 255 Default = "ATDT9W" Optional = NO Help = H12 Example 2: Customizing the Dial String for Calling Card Use When using a calling card to make a long distance call, the telephone number is usually preceded by a number identifying the long distance carrier and a 0. Add these numbers to the end of the default DialPrefix string. Once the telephone number is dialed, the modem must pause to wait for a gong tone, and then dial the calling card number. The comma (,) dial modifier instructs the modem to pause for 2 seconds. Several commas can be used for a longer delay. The commas and the calling card number are added to the beginning of the default DialSuffix string. Modifying a Dial String for Calling Card Use [DialPrefix] Display = D12 Type = String StrLength = 255 Default = "ATDT102880" Optional = NO Help = H12 [DialSuffix] Display = D13 Type = String StrLength = 255 Default = ",,51282300001234\CR" Optional = NO Help = H13 In Modifying a Dial String for Calling Card Use, when a call is made the modem dials the long distance carrier identifier (10288), 0, and then the telephone number specified in the phone book. After dialing the telephone number, the modem pauses for 4 seconds (2 commas) and then dials the calling card number (51282300001234). Warning: If a LAN Distance Connection Server dials out through a modem type customized with a calling card number, this number can be accessed by LAN Distance Remotes that dial the LAN Distance Connection Server through call and port management. If a LAN Distance Remote dials out through a modem type customized with a calling card number, this number can be accessed only from the dialing LAN Distance Remote. 5. When you finish modifying the dial string, save your PIF file in the WAL directory. Configure Your Modem Using the Modified PIF File 6. Start the LAN Distance product if it is not started. 7. Open the Settings notebook. 8. If you already have a port configured, continue with step Customizing the Dial String for Asynchronous Modems. If you do not have a port configured, configure one: a) Select the Ports tab, then select the Add push button. b) Select a port then select OK. c) Select the COM port you will assign to the modem. d) Select Switched for Line type. e) Close the COM port window. You now have a port configured. 9. Select the Modems tab. Delete any modem type assigned to your configured port. Note: This only deletes the association between a modem type and a configured port. It does not delete either the modem type or the port configuration. The deletion is necessary in order to pick up the changes made to the PIF file. 10. Select the Assign push button. 11. From the Available modem types field, select the modem type for your modem then select OK. 12. From the Ports tab within Modem settings, select the Add push button to continue modem configuration. 13. Select Switched for the type of telephone line. You can also specify an optional Phone Number for the modem. Select OK. 14. From the Available ports field, select the configured port that you want to assign to the modem type. Select OK. 15. Close the Ports tab. 16. Close the Settings notebook and select Yes to save changes. 17. If you made changes to the Ports tab, stop all applications, shut down and restart your workstation. If you only made changes to the Modems tab, stop and restart the LAN Distance product. 18. Establishing a LAN Distance Connection describes how to establish a connection. 19. If you cannot communicate using your modem or the dial string is not passing the values you have configured, check the previous steps. ═══ 22.4. Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports ═══ Because OS/2 non-FIFO workstations generally do not support connection speeds greater than 9600 bps, the LAN Distance product sets the serial port speed for non-FIFO modems to 9600 bps. You can try to optimize your serial port speed if 1) your OS/2 non-FIFO workstation has a processing speed of 25 Mhz or greater or 2) the modem attached to the COM port supports transmission speeds greater than 9600 bps. Note: You may also need to change the serial port speed for a FIFO serial port if you receive errors WCL0221, WCL0336, or experience spontaneous disconnects. Choose one of the following methods to modify the serial port speed:  Using the graphical Port/Modem utility, you can change the serial port speed for your modem by editing the SerialPortSpeed parameter on Page 2 of 2 of the Strings tab. See Using the Port/Modem Utility.  Manually change the serial port speed in the PIF file by completing the steps listed in this section. To manually change the default serial port speed in your PIF file, complete these steps: 1. Follow the steps in Modifying a Dial String for Outside Calls, except, substitute step Customizing the Dial String for Asynchronous Mod Modems with step Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports. 2. Specify a new value for the Default keyword (see step Modifying the Speed for FIFO and non-FIFO Serial (COM) Ports) in the SerialPortSpeed section of the PIF file to increase the serial port speed for your modem. SerialPortSpeed Section in a PIF File [SerialPortSpeed] Display = D4 Type = Decimal Default = 19200 Range = 1200-115200 Optional = NO Help = H4 3. Try incrementing this value as follows:  9600 to 14400(**)  14400 to 19200  19200 to 38400 ═══ 22.5. Example LAN Distance PIF File for the IBM 7855 Modem ═══ PIF files contain multiple sections and list keyword=value pairs within each section. Sample PIF File for the IBM 7855 Modem is the PIF file for the IBM 7855 modem. When you create a PIF file for your modem, you must change certain configuration values in the PIF file you are using as a template. Values you may need to change appear in bold type in Sample PIF File for the IBM 7855 Modem. Using the Port/Modem utility, you can change the configuration values for your modem type by editing the fields on pages 1 and 2 of the Strings tab. See Using the Port/Modem Utility. Sample PIF File for the IBM 7855 Modem [IBM7855] DLL = WCLVPCM Entry = StartVPCM Autostart = YES PIF = IBM7855.PIF Title = "IBM 7855 Modem" [Strings] D1 = "Synchronicity" D2 = "Modem Class" D3 = "Auto Baud Detect" D4 = "Serial Port Speed" D5 = "Flow Control" D10 = "First Initialization String" D11 = "Second Initialization String" D12 = "Dial Prefix String" D13 = "Dial Suffix String" D14 = "Success Response String" D15 = "Failure Response String" D16 = "Connection Prefix String" D17 = "Connection Suffix String" D18 = "Escape String" D19 = "Hangup String" D20 = "Ring Back String" D21 = "Busy String" D22 = "No Carrier String" D23 = "No Dialtone String" D24 = "No Answer String" D25 = "Voice String" D26 = "Ring String" H2 = "Select the fastest modulation standard that the modem supports." H3 = "If Auto Baud Detect is on, then the Port Manager will automatically change the serial port speed to match the speed at which the modems connect. If Auto Baud Detect is off, then the serial port speed will remain fixed." H4 = "Enter the speed at which the computer will communicate with the modem. This speed may change if Auto Baud Detect is on." H5 = "Select the type of flow control that is used to limit the flow of data between the computer and the modem." H10 = "This is the first initialization string that is sent to the modem." H11 = "This is the second initialization string that is sent to the modem." H12 = "This is the first part of the string that commands the modem to dial a phone number. The dial prefix string is followed by a phone number and the dial suffix string." H13 = "This string finishes the dial command sent to the modem." H14 = "The modem returns this response string if a command is successful." H15 = "The modem returns this response string if a command is unsuccessful." H16 = "This is the beginning of a connection response string returned by the modem when a connection is successful." H17 = "This is the end of the connection response string returned by the modem." H18 = "This is the escape sequence that is sent to modem to bring the modem back to the command state." H19 = "This string commands the modem to hang up the phone." H20 = "The modem returns this response string when it detects that the phone is ringing at the remote end." H21 = "The modem returns this response string if the phone is busy at the remote end." H22 = "The modem returns this response string if the switched connection is achieved, but no carrier signal is detected." H23 = "The modem returns this response string if there is no dial tone on the telephone line." H24 = "The modem returns this response string if the remote end did not answer the call." H25 = "The modem returns this response string if the switched connection is achieved, but a person answered the call." H26 = "The modem returns this response string if an incoming call is being received." M1 = "Unspecified" M2 = "V.22 1200 bps" M3 = "V.22bis 2400 bps" M4 = "V.32 9600 bps" M5 = "V.32bis 14400 bps" M6 = "Proprietary" ON = "On" OFF = "Off" F1 = "None" F2 = "RTS/CTS" F3 = "XON/XOFF" [DialogType] Type = String Default = "ATCMD.DDF" Editable = NO Paneled = NO [Synchronicity] Display = D1 Default = "Asynchronous" Editable = NO [ModemClass] Display = D2 Type = String Default = "V.32" Set = M1, M2, M3, M4, M5, M6 SetValues = "Unspecified","V.22","V.22bis""V.32","V.32bis","Proprietary" Optional = NO Help = H2 [AutoBaudDetect] Display = D3 Type = String Default = "Off" Set = ON, OFF SetValues = "On","Off" Optional = NO Help = H3 [SerialPortSpeed] Display = D4 Type = Decimal Default = 19200 Range = 1200-115200 Optional = NO Help = H4 [FlowControl] Display = D5 Type = String Default = "RTS/CTS" Set = F1, F2, F3 Setvalues = "None","RTS/CTS","XON/XOFF" Optional = NO Help = H5 [Initialization1] Display = D10 Type = String StrLength = 255 Default = "ATI3\CR" Optional = NO Help = H10 [Initialization2] Display = D11 Type = String StrLength = 255 Default= "ATE1Q0V1X4S7=60S0=2\\R2.\\Q2\\X0.\\\N3\ \V1&D2&S1&R0&C1&IO\CR" Optional = NO Help = H11 [DialPrefix] Display = D12 Type = String StrLength = 255 Default = "ATDT" Optional = NO Help = H12 [DialSuffix] Display = D13 Type = String StrLength = 255 Default = "\CR" Optional = NO Help = H13 [Success] Display = D14 Type = String StrLength = 255 Default = "OK\CR\LF" Optional = NO Help = H14 [Failure] Display = D15 Type = String StrLength = 255 Default = "ERROR\CR\LF" Optional = NO Help = H15 [ConnectPrefix] Display = D16 Type = String StrLength = 255 Default = "CONNECT" Optional = NO Help = H16 [ConnectSuffix] Display = D17 Type = String StrLength = 255 Default = "\CR\LF" Optional = NO Help = H17 [Escape] Display = D18 Type = String StrLength = 255 Default = "+++" Optional = NO Help = H18 [Hangup] Display = D19 Type = String StrLength = 255 Default = "ATH\CR" Optional = NO Help = H19 [RingBack] Display = D20 Type = String StrLength = 255 Default = "RING\CR\LF" Optional = NO Help = H20 [Busy] Display = D21 Type = String StrLength = 255 Default = "BUSY\CR\LF" Optional = NO Help = H21 [NoCarrier] Display = D22 Type = String StrLength = 255 Default = "NO CARRIER\CR\LF" Optional = NO Help = H22 [NoDialtone] Display = D23 Type = String StrLength = 255 Default = "NO DIALTONE\CR\LF" Optional = NO Help = H23 [NoAnswer] Display = D24 Type = String StrLength = 255 Default = "NO ANSWER\CR\LF" Optional = NO Help = H24 [Voice] Display = D25 Type = String StrLength = 255 Default = "VOICE\CR\LF" Optional = NO Help = H25 [Ring] Display = D26 Type = String StrLength = 255 Default = "RING\CR\LF" Optional = NO Help = H26 ═══ 23. Creating a Co-Processor Parameter File ═══ To set up your IBM Realtime Interface Co-Processor Multiport Adapter to use the LAN Distance product, follow the instructions described in this section, then complete the steps in Steps for Setting Up an ARTIC Adapter and Steps for Setting Up an ARTIC Port. The co-processor parameter file is an ASCII text file that defines values for parameters used to configure your ARTIC co-processor adapter(s) that use AT bus hardware. This file is used by the OS/2 device driver (ICARICIO.SYS) to initialize the co-processor adapter. ═══ 23.1. Instructions for Creating the Co-Processor Parameter File ═══ Use any ASCII text editor to create the co-processor file for your IBM Realtime Interface Co-Processor Multiport Adapter.  Name the co-processor file ICAPARM.PRM.  Save the ICAPARM.PRM file to the root directory of your boot drive.  For each co-processor adapter installed on your workstation, you must include one line (record) of values to define the required parameters. Example Co-Processor Parameter File shows a co-processor parameter file with two records defined for a workstation with two co-processor adapters. The record for each co-processor adapter must: - Begin with a "#" character and end with a ";" character, except the last record, which must end with a "$" character. Records that do not begin with a "#" character are treated as comments. - Contain fields (02A0, 0, 6C, etc.) expressed in hexadecimal values using upper- or lowercase characters. - Use a space or comma to separate each field. - Be listed in the correct order. The record order in the ICAPARM.PRM file is associated with the logical card number for the co-processor adapter. In Example Co-Processor Parameter File, the first record (# 02A0...) is associated with logical co-processor adapter 0, and the second record (# 0AA0...) is associated with logical co-processor adapter 1. Example Co-Processor Parameter File # 02A0 0 6C 10 10 10 10 0F E010 ; First co-processor adapter # 0AA0 0 6D 10 10 10 10 0F E010 $ Last co-processor adapter | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Compare degate 1 and 0 | | | | | | | Compare degate 2 | | | | | | MAXTIME | | | | | MAXQUEUE | | | | MAXPRI | | | MAXTASK | | Page value | Megabyte value Co-processor adapter I/O address ═══ 23.2. Descriptions of Parameters for the Co-Processor File ═══ The parameters that you must include in the record for your co-processor adapter are described in this section. For more information about the parameters in this file, refer to The Realtime Interface Co-Processor OS/2 Support 1.03 User's Guide(order number - S04G1029). ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 41. Descriptions of Parameters for the Co-Processor File │ ├───────────────────────────────┬──────────────────────────────────────────────┤ │ PARAMETER CHARACTERISTICS │ DEFINITION │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ CO-PROCESSOR ADAPTER BASE I/O │ This value is set by the switches on the │ │ ADDRESS │ Interface Co-Processor Multiport Adapter, │ │ │ Model 2. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Hex Value (Word) │ Physical Co-Processor Adapter Number │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ 02A0h │ Co-Processor Adapter 0 │ │ 06A0h │ Co-Processor Adapter 1 │ │ 0AA0h │ Co-Processor Adapter 2 │ │ 0EA0h │ Co-Processor Adapter 3 │ │ 12A0h │ Co-Processor Adapter 4 │ │ 16A0h │ Co-Processor Adapter 5 │ │ 1AA0h │ Co-Processor Adapter 6 │ │ 1EA0h │ Co-Processor Adapter 7 │ │ 22A0h │ Co-Processor Adapter 8 │ │ 26A0h │ Co-Processor Adapter 9 │ │ 2AA0h │ Co-Processor Adapter 10 │ │ 2EA0h │ Co-Processor Adapter 11 │ │ 32A0h │ Co-Processor Adapter 12 │ │ 36A0h │ Co-Processor Adapter 13 │ │ 3AA0h │ Co-Processor Adapter 14 │ │ 3EA0h │ Co-Processor Adapter 15 │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ MEGABYTE VALUE │ The megabyte value indicates which megabyte │ │ │ of system unit storage is used for the co- │ │ │ processor adapter's window. A megabyte │ │ │ value of 0 indicates that the window is │ │ │ located in the first megabyte of system unit │ │ │ storage. A value of 1 indicates that the │ │ │ window is located in the second megabyte of │ │ │ system unit storage. │ │ │ │ │ │ See the description of the Page Value param- │ │ │ eter regarding placement of the window. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 00h - 0Fh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ PAGE VALUE │ The page value is an offset (in increments │ │ │ of 8 KB) within the megabyte specified by │ │ │ the megabyte value. This value indicates │ │ │ the location of the co-processor adapter's │ │ │ shared storage window within the specified │ │ │ megabyte. A page value of 0 indicates the │ │ │ window is located at the beginning of the │ │ │ megabyte specified by the megabyte value. │ │ │ When assigning the location of the co- │ │ │ processor, the adapter's shared storage │ │ │ window should not overlap the window of │ │ │ another co-processor adapter. In addition, │ │ │ regions are 128 KB wide and are defined by │ │ │ the type of memory devices that reside in │ │ │ those regions. If a co-processor adapter is │ │ │ configured as an 8-bit device, it cannot │ │ │ reside in the same 128 KB region as an 8-bit │ │ │ device. Conversely, if a co-processor │ │ │ adapter is configured as a 16-bit device, it │ │ │ cannot reside in the same 128 KB region as │ │ │ an 8-bit device. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 00h - 7Fh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ MAXTASK │ This is the highest task number that can be │ │ │ loaded on a given co-processor adapter. │ │ │ Task 0 is reserved for the Realtime Control │ │ │ Microcode. This value should be selected │ │ │ carefully to avoid reserving unnecessary │ │ │ space in the Realtime Control Microcode's │ │ │ data area. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 00h - F8h │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Recommended Hex Value │ 10 │ └───────────────────────────────┴──────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 41. Descriptions of Parameters for the Co-Processor File │ ├───────────────────────────────┬──────────────────────────────────────────────┤ │ PARAMETER CHARACTERISTICS │ DEFINITION │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ MAXPRI │ This is the highest priority level that may │ │ │ be assigned to a task loaded on this co- │ │ │ processor adapter. This value should be │ │ │ selected carefully to avoid reserving unnec- │ │ │ essary space in the Realtime Control Micro- │ │ │ code's data area. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 01h - FFh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Recommended Hex Value │ 10 │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ MAXQUEUE │ This is the highest queue number available │ │ │ for application tasks executing on the co- │ │ │ processor adapter. This value should be │ │ │ selected carefully to avoid reserving unnec- │ │ │ essary space in the Realtime Control Micro- │ │ │ code's data area. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 00h - FEh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Recommended Hex Value │ 10 │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ MAXTIME │ This is the highest timer number reserved │ │ │ for application tasks executing on the given │ │ │ co-processor adapter. This value should be │ │ │ selected carefully to avoid reserving unnec- │ │ │ essary space in the Realtime Control Micro- │ │ │ code's data area. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 00h - FEh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Recommended Hex Value │ 10 │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ COMPARE DEGATE 2 │ When this address, in conjunction with │ │ │ Compare Degate 1 and 0, is accessed by the │ │ │ system unit, the co-processor adapter's │ │ │ shared storage window automatically degates │ │ │ from the system unit memory bus. If the │ │ │ system unit architecture only supports 1 │ │ │ megabyte of memory, this parameter is │ │ │ limited to 00h - 0Fh. 00h - FFh is valid │ │ │ only in a system designed for 16 megabytes │ │ │ of memory. This field should have a value │ │ │ of 0 to disable the feature. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Byte) │ 00h - FFh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Your System Unit │ Recommended Hex Value - Compare Degate 2 │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ IBM 5531, 7531, or 7532 Indust│i0F │ │ Computer; PC XT; PC AT; PS/2 │ │ │ Model 25 or 30; IBM 5531, 7531│ │ │ and 7532 Industrial Computer │ │ │ │ │ │ IBM 7552 Industrial Computer │ 0C │ │ │ │ │ IBM 7541, 7542, 7561, 7562 and│ Any Value │ │ 7568 Industrial Computer; PS/2│ │ │ Model 50, 50Z, 55, 60, 70, or │0 │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ COMPARE DEGATE 1 AND 0 │ When this address, in conjunction with │ │ │ Compare Degate 2, is accessed by the system │ │ │ unit, the co-processor adapter automatically │ │ │ degates its shared storage window from the │ │ │ system unit bus. (See the description for │ │ │ Compare Degate 2.) To disable this feature, │ │ │ the field has a value of 0. │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Range (Word) │ 0000h - FFFFh │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ Your System Unit │ Recommended Hex Value - Compare Degate 1 and │ │ │ 0 │ └───────────────────────────────┴──────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Table 41. Descriptions of Parameters for the Co-Processor File │ ├───────────────────────────────┬──────────────────────────────────────────────┤ │ PARAMETER CHARACTERISTICS │ DEFINITION │ ├───────────────────────────────┼──────────────────────────────────────────────┤ │ IBM 5531, 7531, or 7532 Indust│iE010 │ │ Computer; PC XT; PC AT; PS/2 │ │ │ Model 25 or 30; IBM 5531, 7531│ │ │ and 7532 Industrial Computer │ │ │ │ │ │ IBM 7552 Industrial Computer │ 0000 │ │ │ │ │ IBM 7541, 7542, 7561, 7562 and│ Any Value │ │ 7568 Industrial Computer; PS/2│ │ │ Model 50, 50Z, 55, 60, 70, or │0 │ └───────────────────────────────┴──────────────────────────────────────────────┘ ═══ 24. Example System Configuration Files ═══ This appendix contains configuration file samples for a LAN Distance Connection Server, an OS/2 LAN Distance Remote, and a MS Windows LAN Distance Remote. ═══ 24.1. Example PROTOCOL.INI for a LAN Distance Connection Server ═══ [PROT_MAN] DRIVERNAME = PROTMAN$ [VLAN_KERNEL] DRIVERNAME = VLANKNL$ CFGTYPE = "Locked" MODE = "LEARN_WFLOWS" LANTYPE = "802.5" MAXADDRESSES = 3500 [sr_bridge] DriverName = BRIDGE$ Bridgenum = 15 Maxframe = 2052 Spanningtree = NO CfgType = "Locked" Bindings = IBMTOK_nifB,BRIDGEFH Ringnum = 0xA52,0x222 Maxhopcount = 6,3 Filtercriteria = Criteria_ Prionbindings = IBMTOK_nif,PDFH_nif [BRIDGEFH] DriverName = LANFH$01 CfgType = "Locked" [ARTIC0000] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 0 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0000" [ARTIC0001] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 1 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0001" [ARTIC0002] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 2 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0002" [ARTIC0003] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 3 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0003" [ARTIC0004] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 4 Value Changed RICTASKNO = 5 Value Changed RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0004" [ARTIC0005] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 5 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0005" [ARTIC0006] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 6 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0006" [ARTIC0007] DriverName = WCLARMC$ CFGTYPE = "LOCKED" RICCARDTYPE = 3 RICMICROCODE = "C:\ICA\ICARCM.COM" RICMACCODE = "C:\IBMCOM\WCLARTSK.EXE" RICCARDNO = 0 RICPORTNO = 7 RICTASKNO = 255 RICPORTTYPE = 0 LINEPROTOCOL = 1 NRZI = 1 RTS = 0 RTSDROPDELAY = 0 CLOCKING = 1 LINESPEED = "9600" MAXFRAMESIZE = 2088 MAXTRANSMITS = 6 MAXRECEIVES = 6 OUTBOARDDLC = 0 PCMSUPPORT = 1 CONNTYPE = 1 PORTNAME = "ARTIC0007" [IBMLXCFG] NETBEUI_nif = netbeui.nif PDFH_nif = PDFH.NIF IBMTOK_nif = IBMTOK.NIF [NETBEUI_nif] DriverName = netbeui$ Bindings = PDFH_nif,IBMTOK_nif ETHERAND_TYPE = IBM Corporation" USEADDRREV = "YES" OS2TRACEMASK = 0xFFFF SESSIONS = 64 NCBS = 100 NAMES = 40 SELECTORS = 5 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 60000 T1 = 10000 T2 = 2000 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 1500 NETBIOSRETRIES = 8 NAMECACHE = 0 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 2 PACKETS = 350 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 10 [PDFH_nif] DriverName = PDFH$ NETADDRESS = "t4000412E068A" [IBMTOK_nif] DriverName = IBMTOK$ ADAPTER = "PRIMARY" MAXTRANSMITS = 6 RECVBUFS = 2 RECVBUFSIZE = 256 XMITBUFS = 1 ENABLEBRIDGE [Criteria_] VALID_SADDRS = t10005A8B1278,t10005AAC3CD8,t400015000082 ═══ 24.1.1. Example WCLNET.INI for a LAN Distance Connection Server ═══ [DONOTREMOVE] KEYWORD = VALUE [REMOTELAN01] DLL = WCLVPCM ENTRY = StartVPCM AUTOSTART = YES PIF = OPTIMA14.PIF TITLE = Hayes Optima 14400 Modem PCMNAME = OPTIMA14 [OPTIMA14] DialogType = "ATCMD.DDF" PortName = "ARTIC0000","ARTIC0001","ARTIC0002","ARTIC0003","ARTIC0004", "ARTIC0005","ARTIC0006","ARTIC0007" PermConnection = "NO","NO","NO","NO","NO","NO","NO","NO" PhoneNumber = "5-0209","5-0210","5-0211","5-0212","5-0213","5-0214", "5-0215", "5-0216" Synchronicity = "Asynchronous" ModemClass = "V.32bis" AutoBaudDetect = "Off" SerialPortSpeed = 38400 FlowControl = "RTS/CTS" Initialization1 = "ATI0\CR" Initialization2 = "ATE1Q0V1M1N1W2X4Y0&C1&D2&K3&Q5&R0&S1&T5S7=60S0=2S37=0\CR" DialPrefix = "ATDT" DialSuffix = "\CR" Success = "OK\CR\LF" Failure = "ERROR\CR\LF" ConnectPrefix = "CONNECT" ConnectSuffix = "\CR\LF" Escape = "+++" Hangup = "ATH\CR" RingBack = "RING\CR\LF" Busy = "BUSY\CR\LF" NoCarrier = "NO CARRIER\CR\LF" NoDialtone = "NO DIALTONE\CR\LF" NoAnswer = "NO ANSWER\CR\LF" Voice = "VOICE\CR\LF" Ring = "RING\CR\LF" ═══ 24.1.2. Example CONFIG.SYS for a LAN Distance Connection Server ═══ IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4 PROTSHELL=C:\OS2\PMSHELL.EXE SET USER_INI=C:\OS2\OS2.INI SET SYSTEM_INI=C:\OS2\OS2SYS.INI SET OS2_SHELL=C:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE SET COMSPEC=C:\OS2\CMD.EXE LIBPATH=C:\IBMCOM\DLL;C:\IBMLAN\NETLIB;C:\MUGLIB\DLL;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL; C:\ICA;C:\WAL\DLL; SET PATH=C:\IBMLAN\NETPROG;C:\MUGLIB;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\; C:\OS2\MDOS;C:\OS2\APPS;C:\ICA;C:\WAL; SET DPATH=C:\IBMCOM;C:\IBMLAN\NETPROG;C:\IBMLAN;C:\MUGLIB;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2; C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\ICA;C:\WAL; SET PROMPT=$i[$p] SETHELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;C:\WAL; SET GLOSSARY=C:\OS2\HELP\GLOSS; SET IPF_KEYS=SBCS PRIORITY_DISK_IO=YES FILES=20 DEVICE=C:\IBMCOM\LANMSGDD.OS2/I:C:\IBMCOM DEVICE=C:\IBMCOM\PROTMAN.OS2I:C:\IBMCOM DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2 DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2 DEVICE=C:\OS2\TESTCFG.SYS DEVICE=C:\OS2\DOS.SYS DEVICE=C:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=1024,LW,AC MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=C:\OS2\SYSTEM. 2048 2048 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512; BASEDEV=PRINT02.SYS BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2SCSI.ADD /LED BASEDEV=OS2DASD.DMD SET BOOKSHELF=C:\IBMLAN\BOOK;C:\OS2\BOOK; SET EPMPATH=C:\OS2\APPS; REM DEVICE=C:\OS2\APPS\SASYNCDB.SYS PROTECTONLY=NO SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS FCBS=16,8 RMSIZE=640 DEVICE=C:\ OS2\MDOS\VEMM.SYS DOS=LOW,NOUMB DEVICE=C:\OS2\MDOSV\DPX.SYS DEVICE=C:\OS2\MDOSV\XMS.SYS /UMB DEVICE=C:\OS2\MDOS\VDPMI.SYS DEVICE=C:\OS2\MDOS\VCDROM.SYS DEVICE=C:\OS2\MDOS\VWIN.SYS DEVICE=C:\OS2\PCMCIA.SYS DEVICE=C:\OS2\MDOS\VPCMCIA.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS DEVICE=C:\OS2\COM.SYS DEVICE=C:\OS2\MDOS\VCOM.SYS CODEPAGE=437,850 DEVINFO=KBD,US,C:OS2\KEYBOARD.DCP BASEDEV=XGA.SYS DEVICE=C:\OS2\XGARING0.SYS DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_XGA SET VIO_XGA=DEVICE(BVHVGA,BVHXGA) DEVICE=C:\ OS2\MDOS\VVGA.SYS DEVICE=C:\OS2\MDOS\VXGA.SYS ********************************************************** ***Add if NetBIOS not already added ********************************************************** DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200 IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 / I:C:\IBMLAN /N DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2 RUN=C:\OS2\EPW.EXE ************************************************************** *** ARTIC installation ************************************************************** DEVICE=C:\ICA\ICARICIO.SYS RUN=C:\ICA\ICARICCT.EXE -32 RUN=C:\ IBMLAN\NETPROG\LSDAEMON.EXE RUN=C:\OS2\SYSTEM\LOGDAEM.EXE RUN=C:\OS2\EPWROUT.EXE 1 DEVICE=C:\OS2\LOG.SYS **************************************************** *** Add for LAN Distance **************************************************** DEVICE=C:\WAL\WCLVPCM.OS2 DEVICE=C:\IBMCOM\MEMMAN.OS2 DEVICE=C:\IBMCOM\VLAN.OS2 RUN=C:\IBMCOM\VLANINIT.EXE DEVICE=C:\IBMCOM\MACS\PDFH.OS2 DEVICE=C:\IBMCOM\MACS\MACFH.OS2RUN=C:\IBMCOM\WCLLDRIC.EXE RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=C:\IBMCOM\LANMSGEX.EXE DEVICE=C:\IBMCOM\MACS\BRIDGEFH.OS2 DEVICE=C:\IBMCOM\PROTOCOL\BRIDGE.OS2 DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 DEVICE=C:\IBMCOM\MACS\WCLARMAC.OS2 ═══ 24.2. OS/2 LAN Distance Remote Configuration Files ═══ ═══ 24.2.1. Example PROTOCOL.INI for a LAN Distance Remote ═══ [PROT_MAN] DriverName = PROTMAN$ [VLAN_KERNEL] DRIVERNAME = VLANKNL$ CFGTYPE = "Locked" MODE = "LEARN_WFLOWS" LANTYPE = "802.5" MAXADDRESSES = 512 [COM1] DRIVERNAME = WCLCPMC$ CFGTYPE = "LOCKED" PCMSUPPORT = "YES" MACTYPE = "802.5" CONN_TYPE = "SWITCHED" PORTNAME = "COM1" [IBMLXCFG] LANDD_nif = LANDD.NIF NETBEUI_nif = NETBEUI.NIF ODI2NDI_nif = ODI2NDI.NIF TCPIP_nif = TCPIP.NIF PDFH_nif = PDFH.NIF [LANDD_nif] DriverName = LANDD$ Bindings = PDFH_nif ETHERAND_TYPE = "I" SYSTEM_KEY = 0x0 OPEN_OPTIONS = 0x2000 TRACE = 0x0 LINKS = 8 MAX_SAPS = 3 MAX_G_SAPS = 0 USERS = 3 TI_TICK_G1 = 255 T1_TICK_G1 = 15 T2_TICK_G1 = 3 TI_TICK_G2 = 255 T1_TICK_G2 = 25 T2_TICK_G2 = 10 IPACKETS = 250 UIPACKETS = 100 MAXTRANSMITS = 6 MINTRANSMITS = 2 TCBS = 64 GDTS = 30 ELEMENTS = 800 [NETBEUI_nif] DriverName = netbeui$ Bindings = PDFH_nif ETHERAND_TYPE = IBM Corporation" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 70 NCBS = 125 NAMES = 51 SELECTORS = 5 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 512 TI = 60000 T1 = 10000 T2 = 2000 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 500 NETBIOSRETRIES = 8 NAMECACHE = 0 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 2 PACKETS = 350 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 5 [ODI2NDI_nif] DriverName = odi2ndi$ Bindings = PDFH_nif NETADDRESS = "T4000000000AA" TOKEN-RING = "yes" TOKEN-RING_SNAP = "no" ETHERNET_802.3 = "no" ETHERNET_802.2 = "no" ETHERNET_II = "no" ETHERNET_SNAP = "no" TRACE = 0x0 [TCPIP_nif] DriverName = TCPIP$ Bindings = PDFH_nif [PDFH_nif] DriverName = PDFH$ NETADDRESS = "4000000000AA" ═══ 24.2.2. Example WCLNET.INI for a LAN Distance Remote ═══ [DONOTREMOVE] KEYWORD = VALUE [REMOTELAN01] DLL = WCLVPCM Entry = StartVPCM Autostart = YES PIF = OPTIMA14.PIF Title = "Hayes Optima 14400 Modem" PCMNAME = OPTIMA14 [OPTIMA14] PortName = COM1 PermConnection = No PhoneNumber = "Unspecified" DialogType = "ATCMD.DDF" Synchronicity = "Asynchronous" ModemClass = "V.32bis" AutoBaudDetect = "Off" SerialPortSpeed = 38400 FlowControl = "RTS/CTS" Initialization1 = "ATI0\" Initialization2 ="ATE1Q0V1M1N1S95=40X4Y0&C1&D2&K3&Q5&R0&S1&T5S7=60S0=2S37=0\CR" DialPrefix = "ATDT" DialSuffix = "\CR" [OPTIMA14], continued Success = "OK\CR\LF" Failure = "ERROR\CR\LF" ConnectPrefix = "CONNECT" ConnectSuffix = "\CR\LF" Escape = "+++" Hangup = "ATH\CR" RingBack = "RING\CR\LF" Busy = "BUSY\CR\LF" NoCarrier = "NO CARRIER\CR\LF" NoDialtone = "NO DIALTONE\CR\LF" NoAnswer = "NO ANSWER\CR\LF" Voice = "VOICE\CR\LF" Ring = "RING\CR\LF" ═══ 24.2.3. Example CONFIG.SYS for a LAN Distance Remote ═══ IFS=D:\OS2\HPFS.IFS /CACHE:64 /CRECL:4 DEVICE=D:\IBMCOM\LANMSGDD.OS2DEVICE=D:\IBMCOM\PROTMAN.OS2DEVICE=D:\IBMCOM\PROTOCOL\LANDD.OS2 DEVICE=D:\IBMCOM\PROTOCOL\LANDLLDD.OS2 DEVICE=E:\CMLIB\R0CSDD.SYS DEVICE=D:\IBMCOM\PROTOCOL\LANPDD.OS2 DEVICE=D:\IBMCOM\PROTOCOL\LANVDD.OS2 PROTSHELL=D:\OS2\PMSHELL.EXE SET USER_INI=D:\OS2\OS2.INI SET SYSTEM_INI=D:\OS2\OS2SYS.INI SET OS2_SHELL=D:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS SET RESTARTOBJECTS=NO SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE SET COMSPEC=D:\OS2\CMD.EXE LIBPATH=D:\IBMCOM\DLL;D:\MUGLIB\DLL;D:\IBMLAN\NETLIB;.;D:\OS2\DLL;D:\OS2\ MDOS;D:\;D:\OS2\APPS\DLL;E:NOTES;E:\NETWARE;E:\TCPIP\DLL; E:\CMLIB\DLL;Y:\;E:\WAL\DLL; SET PATH=D:\IBMLAN\NETPROG;D:\MUGLIB;D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\ WINOS2;D:\OS2\INSTALL;D:\;D:\OS2\MDOS;D:\OS2\APPS;E:\NOTES;L:\OS2; P:\OS2;E:\NETWARE;E:\TCPIP\BIN;D:\IBMCOM;E:\CMLIB;E:\WAL; SET DPATH=D:\IBMCOM;D:\IBMLAN\NETPROG;D:\IBMLAN;D:\MUGLIB;D:\OS2;D:\OS2\SYSTEM; D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;D:\;D:\OS2\BITMAP;D:\OS2\MDOS; D:\OS2\APPS;E:\NETWARE;E:\CMLIB;E:\WAL; SET PROMPT=$i[$p] HELP\TUTORIAL;E:\TCPIP\HELP;E:\CMLIB;E:\WAL; SET GLOSSARY=D:\OS2\HELP\GLOSS; SET IPF_KEYS=SBCS PRIORITY_DISK_IO=YES FILES=20 TRACEBUF=63 DEVICE=D:\OS2\TESTCFG.SYS DEVICE=D:\OS2\DOS.SYS DEVICE=D:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=2048,LW,AC:D MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=D:\OS2\SYSTEM 2048 2048 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512; BASEDEV=PRINT02.SYS BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2SCSI.ADD /LED BASEDEV=OS2DASD.DMD SET BOOKSHELF=D:\IBMLAN\BOOK;D:\OS2\BOOK;E:\CMLIB\BOOK; SET EPMPATH=D:\OS2\APPS; REM DEVICE=D:\OS2\APPS\SASYNCDB.SYS PROTECTONLY=NO SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS FCBS=16,8 RMSIZE=640 DEVICE=D:\OS2\MDOS\VEMM.SYS DOS=LOW,NOUMB DEVICE=D:\OS2\MDOS\VDPX.SYS DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB DEVICE=D:\OS2\MDOS\VDPMI.SYS DEVICE=D:\OS2\MDOS\VCDROM.SYS DEVICE=D:\OS2\MDOS\VWIN.SYS REM DEVICE=D:\OS2\PCMCIA.SYS REM DEVICE=D:\OS2\MDOS\VPCMCIA.SYS DEVICE=D:\OS2\MDOS\MOUSE.SYS DEVICE=D:\OS2\POINTDD.SYS DEVICE=D:\OS2\MOUSE.SYS DEVICE=D:\OS2\COM.SYS DEVICE=D:\OS2\VCOM.SYS CODEPAGE=437,850 DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP DEVINFO=SCR,VGA,D:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_VGA SET VIO_VGA=DEVICE(BVHVGA) DEVICE=D:\OS2\MDOS\VVGA.SYS DEVICE=D:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=D:\IBMLAN\NETPROG\RDRHELP.200 *************************************************************** ***REM--- NetWare Requester statements BEGIN --- *************************************************************** DEVICE=E:\NETWARE\LSL.SYS RUN=E:\NETWARE\DDAEMON.EXE DEVICE = D:\IBMCOM\PROTOCOL\ODI2NDI.OS2 REM DEVICE=E:\NETWARE\TOKEN.SYS DEVICE=E:\NETWARE\ROUTE.SYS DEVICE=E:\NETWARE\IPX.SYS REM DEVICE=E:\NETWARE\SPX.SYS REM RUN=E:\NETWARE\SPDAEMON.EXE REM DEVICE=E:\NETWARE\NMPIPE.SYS REM DEVICE=E:\NETWARE\NPSERVER.SYS REM RUN=E:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME DEVICE=E:\NETWARE\NWREQ.SYS IFS=E:\NETWARE\NWIFS.IFS ****************************************************************** ***REM --- Comment the next line out if running Tbird ***REM --- Then execute DETACH ***REM --- After Connection has established with the Tbird Server ****************************************************************** E:\NETWARE\NWDAEMON.EXE REM RUN=E:\NETWARE\NWDAEMON.EXE REM DEVICE=E:\NETWARE\NETBIOS.SYS REM RUN=E:\NETWARE\NBDAEMON.EXE DEVICE=E:\NETWARE\VIPX.SYS DEVICE=E:\NETWARE\VSHELL.SYS ******************************************************************* ***REM --- NetWare Requester statements END --- ******************************************************************* IFS=D:\IBMLAN\NETPROG\NETWKSTA.200/I:D:\IBMLAN /N DEVICE=D:\IBMCOM\PROTOCOL\NETBIOS.OS2 RUN=D:\IBMLAN\NETPROG\LSDAEMON.EXE DEVICE=D:\OS2\LOG.SYS DEVICE=D:\IBMCOM\PROTOCOL\INET.SYS DEVICE=D:\IBMCOM\PROTOCOL\IFNDIS.SYS RUN=D:\OS2\SYSTEM\LOGDAEM.EXE RUN=D:\OS2\EPWROUT.EXE 1 RUN=D:\OS2\EPW.EXE SET ETC=E:\TCPIP\ETC SET TMP=E:\TCPIP\TMP RUN=E:\TCPIP\BIN\CNTRL.EXE IFS=E:\TCPIP\BIN\NFS200.IFS SET TELNET.PASSWORD.ID=dragon SET HOSTNAME=host1 DEVICE=E:\ CMLIB\ACSLANDD.SYS DEVICE=E:\CMLIB\CMKFMDE.SYS SET DRVLTR=D RUN=D:\IBMCOM\PROTOCOL\LANDLL.EXE RUN=D:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=D:\IBMCOM\LANMSGEX.EXE DEVICE=E:\WAL\WCLVPCM.OS2 DEVICE=D:\IBMCOM\MEMMAN.OS2 DEVICE=D:\IBMCOM\VLAN.OS2 RUN=D:\IBMCOM\VLANINIT.EXE DEVICE=D:\IBMCOM\MACS\MACFH.OS2 DEVICE=D:\IBMCOM\MACS\WCLCPMAC.OS2 DEVICE=D:\IBMCOM\MACS\PDFH.OS2 ═══ 24.3. MS Windows LAN Distance Remote Configuration Files ═══ ═══ 24.3.1. Example PROTOCOL.INI for a MS Windows LAN Distance Remote ═══ [PROTOCOL_MANAGE] DriverName=PROTMAN$ [NETBEUI] DriverName=NETBEUI$ Bindings=SOCKDD_MOD NCBS=32 Sessions=32 Names=17 MaxDatarcv=4168 MaxTransmits=6 TI=60000 T1=10000 T2=2000 [DXME0_NIF] DriverName = DXME0$ Bindings=SOCKDD_MOD [IBM_TCPIP_V21] DriverName=DOSNDIS$ Bindings=SOCKDD_MOD [SOCKDD_MOD] DriverName=VLANMAC$ LanType="TokenRing" Mode="Flows" MaxFrame=618 ═══ 24.3.2. Example AUTOEXEC.BAT for a MS Windows LAN Distance Remote ═══ @ECHO OFF C:\WAL\DOSBIND SET ETC=D:\TCPDOS\ETC LH /L:0;3,42432/S C:\DOS\SMARTDRV.EXE LH /L:2,6400 C:\DOS\DOSKEY PROMPT $P$G PATH C:\WAL;C:\WINDOWS;C:\DOSLAN;C:\DOS;C:\TOOLS;D:\NOTES;D:\TCPDOS\BIN; SET TEMP=C:\DOS NET START CALL TCPSTART ═══ 24.3.3. Example CONFIG.SYS for a MS Windows LAN Distance Remote ═══ DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS HIGHSCANX=D800-DBFFX=CC00-CDFF BUFFERS=10 FILES=40 DOS=UMB LASTDRIVE=Z FCBS=4,0 DEVICEHIGH /L:2,12048 =C:\DOS\SETVER.EXE DOS=HIGH SHELL=C:\COMMAND.COM /E:2000 /P STACKS=9,256 DEVICEHIGH=C:\DOS\ANSI.SYS DEVICE=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\PCMDD.SYS DEVICEHIGH=D:\TCPDOS\BIN\DOSTCP.SYS ═══ 25. Security Database Tools ═══ This appendix discusses the security database tools available in LAN Distance 5.0. The LAN Distance Security Database Tools allow the LAN Distance security administrator to manage the security database and perform the following tasks:  Add users without using the User Account Management window  Print a report of the security database  Back up the security database without shutting down LAN Distance. The security database tools are:  CMBACKUP  CMPRINT  CMPROCES ═══ 25.1. CMBACKUP ═══ CMBACKUP provides a command line interface that allows you to back up the database while LAN Distance is running. The database can be backed up to a specific file. This tool accepts an input file name as a parameter and copies the security database using this file name. SYNTAX: CMBACKUP where: is the name of the backup file the user wants to save the security database to. If this option is ignored, the default backup file is WCBUSRF.BAK. ═══ 25.2. CMPRINT ═══ CMPRINT provides a command line interface that you can use to print a list of the users in the security database. All of the userIDs and user comments in the LAN Distance security database are printed in to a specified file. SYNTAX: CMPRINT where: /FI:input_file specifies the name of the input LAN Distance Security Database file. The default is WCBUSRF.ISF. /FO:output_file specifies the name of the output file. The default is CMPRINT.REP. ═══ 25.3. CMPROCES ═══ The CMPROCES tool provides a batch processing capability for LAN Distance. This tool reads user information from a Script file and adds user data to the security database. SYNTAX: CMPROCES where: CT: Control parameter AD for add user to database ME for merge the database /FO: output file name The output filename is the name of the report file. This report file contains the userIDs and the return code of the requested action. The default output file for adding a user is CMADD.REP. /FI: input file name If the control parameter is ADb, the input file is a Script file containing user information to be added. If the control parameter is ME, the input file is the security database to be merged. The default file name of the input file is WCBUSRF.INI. The format of the Script file for adding a user is one line of user information per user. The user information line contains the control key and user information in the following format: /ID: userID /PS :passphrase /CM: user comment /UT: user type where: /ID: The maximum length of the userID is 10 characters. This control key is required. The userID is not case-sensitive. /PW: The maximum length of the passphrase is 32 characters. This control key is ignored when the passphrase of user account is set to "not required." The passphrase is case-sensitive. /CM: The user comment is optional. The maximum length of user comment is 40 characters and it is not case-sensitive. /UT: The user type is optional and the default is user. There are three types of user available: U = USER A = ADMINISTRATOR S = SECURITY ADMINISTRATOR ═══ 26. Developing Security User Exits ═══ This appendix discusses the security user exits available in LAN Distance 5.0. ═══ 26.1. Security User Exit Enablement ═══ LAN Distance now supports two optional levels of security for restricted access to the LAN and its resources. One level is the existing LAN Distance security (User Account Management), included in the LAN Distance product. The second level is a security user exit package that is distributed separately from the LAN Distance product. LAN Distance supports any OEM-provided security user exit package that is developed in conformance with the LAN Distance Generalized Security User Exit API. What Is a Security User Exit Package? A security user exit package consists of two user exit modules: one for the client and one for the server. The client and server user exit modules work together to implement the user authentication protocol defined by the security user exit package. A user authentication protocol is a series of user exit messages/tokens exchanged between the client and server user exit modules when validating the user of a LAN Distance client workstation that is calling a LAN Distance connection server. Using Multiple Security User Exit Packages One LAN Distance client workstation can use a different security user exit package to access each different LAN Distance server workstation it calls. A LAN Distance server workstation must use only one security user exit package to allow access from all LAN Distance client workstations that call it. Using Security User Exit Packages with LAN Distance Security Security user exit packages can be used with or without LAN Distance security (User Account Management). If LAN Distance security is used with the security user exit package, the authentication will take place first through the user exit and second through LAN Distance security. Enabling Security User Exit To enable the user-supplied security exit, follow the OEM-provided security exit instructions. LAN Distance Security User Exit Development Toolkit A development toolkit for the LAN Distance Security User Exit for OS/2 and Windows is available. The toolkit contains: - Specification of the LAN Distance Generalized Security User Exit API - Description of how a LAN Distance security user exit can be installed/registered at LAN Distance workstations - Sample source code for developing your own LAN Distance security user exit package The toolkit is available through IBM Service and Support by referencing APAR IC07742. ═══ 27. Notices ═══ Sixth Edition (April 1997) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. This publication was developed for products and services offered in the United States of America. IBM may not offer the products, services, or features discussed in this document in other countries, and the information is subject to change without notice. Consult your local IBM representative for information on the products, services, and features available in your area. Requests for technical information about IBM products should be made to your IBM reseller or IBM marketing representative. ═══ 27.1. Copyright Notices ═══ (C)Copyright International Business Machines Corporation 1992, 1997. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. ═══ 27.2. Disclaimers ═══ References in this book to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Subject to IBM's valid intellectual property or other legally protectable rights, any functionally equivalent product, program, or service may be used instead of the IBM product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, are the responsibility of the user. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation 500 Columbus Avenue Thornwood, NY 10594 U.S.A. Asia-Pacific users can inquire, in writing, to the IBM Director of Intellectual Property and Licensing, IBM World Trade Asia Corporation, 2-31 Roppongi 3-chome, Minato-ku, Tokyo 106, Japan. Licensees of this program who wish to have information about it for the purpose of enabling:(i)the exchange of information between independently created programs and other programs (including this one) and (ii)the mutual use of the information which has been exchanged, should contact IBM Corporation, Department LZKS, 11400 Burnet Road, Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. ═══ 27.3. Trademarks ═══ For a list of IBM and non-IBM trademarks, refer to the online book Trademarks in the Information folder. ═══ 28. Glossary ═══ ═══ 28.1. A ═══ ═══ 28.1.1. ad hoc conferencing ═══ ad hoc conferencing A dynamic environment in which two or more LAN Distance workstations dial in to a common LAN Distance workstation (the hub) and conference with each other across the virtual LAN connections. See also hub. ═══ 28.1.2. administrator ═══ administrator See LAN Distance administrator. ═══ 28.1.3. Advanced Network Driver Interface Specification (ANDIS) ═══ Advanced Network Driver Interface Specification (ANDIS) An upgraded version of the Network Driver Interface Specification (NDIS). It is the interface between the LAN Distance logical adapter and the WAN adapter MAC. ═══ 28.1.4. Advanced Peer-to-Peer Networking (APPN) ═══ Advanced Peer-to-Peer Networking (APPN) An implementation of the Systems Network Architecture (SNA) LU 6.2 protocol that allows interconnected systems to communicate and share the processing of programs. APPN conforms to the IEEE 802.2 interface; applications using it are supported by the LAN Distance product. ═══ 28.1.5. Advanced Program-to-Program Communications (APPC) ═══ Advanced Program-to-Program Communications (APPC) An implementation of the Systems Network Architecture (SNA) LU 6.2 protocol that allows interconnected systems to communicate and share the processing of programs. APPC conforms to the IEEE 802.2 interface; applications using it are supported by the LAN Distance product. ═══ 28.1.6. alert ═══ alert A message sent to a system services control point to report that an error occurred that requires operator intervention or attention. For the LAN Distance product, alerts for communications errors are generated through FFST/2. FFST/2 can be configured to forward the alerts to NetView or central LAN management point. ═══ 28.1.7. ANDIS ═══ ANDIS See Advanced Network Driver Interface Specification (ANDIS). ═══ 28.1.8. answer ═══ answer To acknowledge an attempt from a remote workstation to establish a LAN Distance connection. Answering a call does not imply a successful connection. The dialing and answering workstations must negotiate to establish the connection. ═══ 28.1.9. answer criteria ═══ answer criteria The set of specifications that enables a particular Answer Mode. ═══ 28.1.10. answer mode ═══ answer mode A workstation state that allows incoming calls to be acknowledged, depending on their conformity to a defined set of specifications. See also answer criteria. Multiple answer modes (answering states based on different call acceptance specifications) can be configured for a workstation. ═══ 28.1.11. APPC ═══ APPC See Advanced Program-to-Program Communications (APPC). ═══ 28.1.12. APPN ═══ APPN See Advanced Peer-to-Peer Networking (APPN). ═══ 28.1.13. ARTIC ═══ ARTIC An IBM WAN adapter that provides asynchronous and synchronous transmission support for up to 8 communication ports. ═══ 28.1.14. asynchronous transmission ═══ asynchronous transmission A type of data communication in which transmission of a character or a block of characters can begin at any time, but in which the bits that represent the character or block have equal time duration. ═══ 28.1.15. audit log ═══ audit log A record of all LAN Distance connection attempts, successful LAN Distance connection activity, link statistics, and security events at a LAN Distance Remote or LAN Distance Connection Server. ═══ 28.2. B ═══ ═══ 28.2.1. Basic Settings ═══ Basic Settings A highly guided, simplified path for installing and configuring a LAN Distance Remote. Basic Settings supports asynchronous and ISDN switched line connection types. ═══ 28.2.2. binding ═══ binding The configurable association between two layers of communications software. Two bindings are required by the LAN Distance product. First, the LAN protocol must be bound to the LAN Distance logical adapter. Second, the LAN Distance logical adapter must be bound to the WAN adapter MAC. ═══ 28.2.3. bridge ═══ bridge A functional unit that connects two local area networks (LANs) that use the same logical link control protocol but may use different medium access control protocols. ═══ 28.2.4. broadcast message ═══ broadcast message Synonymous with broadcast frame. A message that is transmitted to all destinations on a local area network (LAN). ═══ 28.3. C ═══ ═══ 28.3.1. callback ═══ callback A feature, active during LAN Distance connection establishment, in which the answering workstation re-initiates the connection by placing a call back to the dialing workstation. The original dialing workstation must be a LAN Distance Remote. This feature provides a level of security and can be used to manage telephone charges by placing call control at the answering workstation. ═══ 28.3.2. callback type ═══ callback type The method, fixed or variable, of obtaining the callback telephone number. It determines whether the telephone number is already configured or if it is supplied by the dialing user at connection time. ═══ 28.3.3. carbon copy ═══ carbon copy A remote access technology in which keyboard and screen data are routed between two workstations across a WAN connection. This technology is supported by LAN Distance if it is NDIS enabled; however, it is not used by the LAN Distance product. ═══ 28.3.4. CID ═══ CID See Configuration, Installation and Distribution (CID). ═══ 28.3.5. communication port ═══ communication port An access point for data to enter or exit a communication device. For example, a serial port to which a modem is attached is a communication port. ═══ 28.3.6. Configuration, Installation and Distribution (CID) ═══ Configuration, Installation and Distribution (CID) An IBM architecture for standard LAN installation and configuration operations. The portions of CID implemented by the LAN Distance product are (1) installation from a redirected drive and (2) use of a response file. ═══ 28.4. D ═══ ═══ 28.4.1. device driver replacement ═══ device driver replacement The technology, implemented by the LAN Distance product, in which a LAN adapter is replaced by a WAN adapter MAC to transmit data across wide area connections. The LAN Distance logical adapter and WAN adapter MAC send and receive LAN data frames across a LAN Distance connection. This technology enables transparent support of LAN applications and LAN protocols. ═══ 28.4.2. dial ═══ dial To initiate a LAN Distance connection by placing a call to a target location. This term applies to connections over switched and nonswitched lines, even though the act of dialing a telephone number does not actually apply to nonswitched lines. ═══ 28.4.3. dial-in ═══ dial-in The action of establishing a LAN Distance connection to a LAN, by dialing a LAN Distance Connection Server on the LAN. ═══ 28.4.4. dial-in port ═══ dial-in port A LAN Distance communication port designated by the LAN Distance product to answer incoming calls. ═══ 28.4.5. Dial Services Interface (DSI) ═══ Dial Services Interface (DSI) A program interface to the dialing services of the LAN Distance product. ═══ 28.4.6. directed frame ═══ directed frame A data frame that is intended to be delivered to a specific location and thus contains the address of its destination. ═══ 28.4.7. duplicate address checker ═══ duplicate address checker A LAN Distance feature to ensure that workstations dialing in to a LAN have a unique LAN adapter address. ═══ 28.5. E ═══ ═══ 28.5.1. error log ═══ error log A workstation log of error information, for use in problem determination by your designated support organization. The LAN Distance product uses FFST/2 to record error log information. ═══ 28.5.2. error message log ═══ error message log A workstation file containing a copy of all error and warning messages generated at that workstation. It might also contain Error Reports. (See also Error Report). ═══ 28.5.3. error report ═══ error report An error message generated by a remote LAN Distance Connection Server, sent to a LAN Distance administrator as a pop-up, and written to the LAN Distance administrator's error message log. ═══ 28.5.4. Ethernet ═══ Ethernet A 10-megabit baseband local area network that allows multiple stations to access the transmission medium without prior coordination. It avoids contention by using carrier sense and deference, and resolves contention by using collision detection and transmission. ═══ 28.6. F ═══ ═══ 28.6.1. filtering ═══ filtering Synonymous with traffic filtering. A LAN Distance feature that limits the LAN traffic that flows across a LAN Distance connection to only the data frames that apply to the participating workstations. Filtering criteria are configurable and can be based on the type of LAN data frame being transmitted and the source or destination of that data. ═══ 28.6.2. First Failure Support Technology/2 (FFST/2) ═══ First Failure Support Technology/2 (FFST/2) A software product that provides a set of Application Program Interfaces for OS/2 programs to invoke for aid in problem determination. Functions provided by FFST/2 include logging and displaying errors, formatting and routing alerts, and generating data dumps. FFST/2 is included in the LAN Distance product packages. ═══ 28.6.3. fixed callback ═══ fixed callback A type of callback in which the telephone number to be dialed is always the same. ═══ 28.6.4. frame ═══ frame A data structure consisting of fields defined by a protocol for the transmission of user and control data. ═══ 28.6.5. functional address ═══ functional address A Token-Ring destination address used to identify widely-used functions. It is typically used to specify the destination for a broadcast message. ═══ 28.7. G ═══ ═══ 28.8. H ═══ ═══ 28.8.1. hang up ═══ hang up To end a LAN Distance connection. ═══ 28.8.2. homologation ═══ homologation The enforcement of certain country or network requirements regarding the use of telephone circuits and other networks by computers. The LAN Distance product requires the modems that it uses to be homologated. ═══ 28.8.3. hub ═══ hub A LAN Distance Connection Server workstation acting as an intermediary for ad hoc conferencing among multiple LAN Distance workstations. The hub workstation typically runs LAN application server software, such as OS/2 LAN Server, to manage communications among the conferencing workstations. The hub must be an OS/2 workstation. ═══ 28.9. I ═══ ═══ 28.9.1. IBM LAN Distance Remote ═══ IBM LAN Distance Remote The IBM product that provides security and remote LAN access for individual workstations to other workstations and LANs. ═══ 28.9.2. IBM LAN Distance Connection Server ═══ IBM LAN Distance Connection Server The IBM product that provides security and routing capabilities to allow remote workstations to access LAN resources. ═══ 28.9.3. IEEE 802.2 ═══ IEEE 802.2 A standard defined by the Institute of Electrical and Electronics Engineers (IEEE) for logical link control within a local area network. IEEE 802.2 is one of the standards supported by the LAN Distance product for LAN protocol software. ═══ 28.9.4. IEEE 802.5 ═══ IEEE 802.5 A standard defined by the Institute of Electrical and Electronics Engineers (IEEE) for framing and error detection within a Token-Ring network. IEEE 802.5 is the framing standard used by the LAN Distance logical adapter. ═══ 28.9.5. integrated services digital network (ISDN) ═══ integrated services digital network (ISDN) A digital end-to-end telecommunication network that supports multiple services including, but not limited to, voice and data. ═══ 28.9.6. ISDN ═══ ISDN See integrated services digital network (ISDN). ═══ 28.10. J ═══ ═══ 28.11. K ═══ ═══ 28.12. L ═══ ═══ 28.12.1. LAN ═══ LAN See local area network (LAN). ═══ 28.12.2. LAN adapter ═══ LAN adapter A card which is installed on a workstation and is used to attach the workstation to a local area network (LAN). ═══ 28.12.3. LAN Adapter Protocol Support (LAPS) ═══ LAN Adapter Protocol Support (LAPS) LAN networking software that allows selection and binding of LAN protocols to LAN adapters. It is required by and shipped with the LAN Distance product. ═══ 28.12.4. LAN application ═══ LAN application A program that shares data and resources among workstations through the transmission of data across a local area network (LAN). LAN applications must adhere to an NDIS-compliant LAN protocol, such as NetBIOS IEEE 802.2, or TCP/IP, to be supported by the LAN Distance product. ═══ 28.12.5. LAN workstation ═══ LAN workstation A workstation physically residing on a local area network (LAN). Contrast to a stand-alone workstation. ═══ 28.12.6. LAN Distance administrator ═══ LAN Distance administrator A user-type designation for the user who performs LAN Distance system management tasks. See user and see also LAN Distance security administrator for the other user types defined by the LAN Distance product. ═══ 28.12.7. LAN Distance bridge ═══ LAN Distance bridge A bridge established by a LAN Distance Connection Server for the wide area connections to its LAN. The LAN Distance bridge routes and filters LAN traffic for the LAN Distance wide area network. ═══ 28.12.8. LAN Distance Connection Server ═══ LAN Distance Connection Server See IBM LAN Distance Connection Server. ═══ 28.12.9. LAN Distance Connection Server ═══ LAN Distance Connection Server The LAN Distance connection agent for a LAN. It is the location of central answering, system management, and security resources for the LAN Distance connection to a LAN. ═══ 28.12.10. LAN Distance Remote ═══ LAN Distance Remote See IBM LAN Distance Remote. ═══ 28.12.11. LAN Distance Remote ═══ LAN Distance Remote A workstation on which the LAN Distance Remote product is installed. It can establish LAN Distance connections to or from a LAN Distance Remote and a LAN Distance Connection Server. ═══ 28.12.12. LAN Distance security administrator ═══ LAN Distance security administrator A user-type designation for the user who manages LAN Distance security, including configuration of the security policy and administration of the user account database. See user and see also LAN Distance administrator for the other user types defined by the LAN Distance product. ═══ 28.12.13. LAN Distance system ═══ LAN Distance system The set of workstations that a LAN Distance administrator supports. It includes the workstations on which the LAN Distance product is installed and all the workstations that can participate in LAN Distance wide area connections. ═══ 28.12.14. LAN Distance wide area network ═══ LAN Distance wide area network The set of workstations that can communicate with each other over their interrelated LAN Distance connections. In the remote-to-remote environment, it includes the entire virtual LAN. In the remote-to-LAN environment, it includes remote workstations, the LAN Distance Connection Server to which they are connected, and the LAN-attached workstations that are allowed to communicate with the remote workstations. ═══ 28.12.15. LAN protocol ═══ LAN protocol The protocol used for information transfer among the workstations attached on a LAN. The LAN protocols supported by the LAN Distance product must be NDIS-compliant (for example, IEEE 802.2, NetBIOS, and TCP/IP). ═══ 28.12.16. LAN resource ═══ LAN resource A directory or file resource, printer, or serial device that is physically attached to a LAN and is managed by the LAN's administrative software. ═══ 28.12.17. LAN Requester ═══ LAN Requester A component of the OS/2 program that allows users to access shared network resources made available by an OS/2 LAN Server. Using the client/server model, the LAN Requester component would reside on the client workstation. ═══ 28.12.18. LAN Server ═══ LAN Server See OS/2 LAN Server. ═══ 28.12.19. LAN transport protocol ═══ LAN transport protocol Synonymous with LAN protocol. ═══ 28.12.20. LAPS ═══ LAPS See LAN Adapter Protocol Support (LAPS). ═══ 28.12.21. leased line ═══ leased line A telecommunications line on which connections do not have to be established by dialing a telephone number; the line is reserved for use between specific locations and is activated directly. See also nonswitched line. ═══ 28.12.22. line ═══ line The physical medium, such as a telephone wire, used to transmit data. ═══ 28.12.23. local area network (LAN) ═══ local area network (LAN) A network comprising two or more units physically connected for the purpose of local resource sharing. The network is generally limited to a moderate-sized geographic area, such as a single office building or campus. ═══ 28.12.24. logical adapter network address ═══ logical adapter network address A unique identifier for a workstation or resource participating in a LAN Distance wide area network. The LAN Distance product uses this address to accomplish LAN traffic filtering and routing. ═══ 28.13. M ═══ ═══ 28.13.1. media access control (MAC) ═══ media access control (MAC) The communications software that controls the interface between the LAN protocol software and the workstation's LAN or WAN adapter. ═══ 28.13.2. modem (modulator/demodulator) ═══ modem (modulator/demodulator) A device that converts digital data to an analog signal that can be transmitted on a telecommunication line, and converts the analog signal received to digital data. ═══ 28.13.3. modem type ═══ modem type An item in the LAN Distance product used to configure a modem. A modem type can be synchronous or asynchronous. Many modem types are listed as modem brand names. ═══ 28.13.4. Multi-Protocol Transport Services (MPTS). ═══ Multi-Protocol Transport Services (MPTS). LAN networking software that allows selection and binding of LAN protocols to LAN adapters. MPTS is a successor product to NTS/2 and contains the LAPS function. ═══ 28.14. N ═══ ═══ 28.14.1. NDIS ═══ NDIS See Network Driver Interface Specification (NDIS). ═══ 28.14.2. NetBIOS ═══ NetBIOS A LAN protocol that provides application program interfaces to the network adapter for establishing sessions and transmitting data. It is one of the LAN protocols supported by the LAN Distance product. ═══ 28.14.3. NetBIOS name ═══ NetBIOS name The name by which a node is known. It is used as the basis for communication between application programs. ═══ 28.14.4. NetView/2 ═══ NetView/2 An OS/2 program product for central LAN management. Configuring the interface between FFST/2 and NetView/2 provides NetView/2 access to LAN Distance information. ═══ 28.14.5. Network Driver Interface Specification (NDIS) ═══ Network Driver Interface Specification (NDIS) An industry standard interface between network adapter software and LAN transport protocols. The interface into the LAN Distance logical network adapter is compliant with NDIS, and supports any LAN protocol that is also compliant, such as IEEE 802.2, NetBIOS, and TCP/IP. ═══ 28.14.6. Network Transport Services/2 (NTS/2) ═══ Network Transport Services/2 (NTS/2) A software product that includes the particular LAN networking software, LAPS, required by the LAN Distance product. It also includes support for the Configuration, Installation and Distribution (CID) facility. ═══ 28.14.7. non-directed frame ═══ non-directed frame A data frame whose destination is not limited to a single location. Its destination is specified as a functional address, group address, or All Stations. ═══ 28.14.8. nonswitched line ═══ nonswitched line A telecommunications line on which connections do not have to be established by dialing a telephone number; that is, the line is reserved for use between specific locations and is activated directly. Contrast with switched line. For PSTN connections, nonswitched lines are referred to as leased lines. ═══ 28.14.9. notebook ═══ notebook A graphical representation that resembles a bound notebook containing pages separated into sections by tabbed dividers. A user can turn the pages of a notebook to move from one section to another. ═══ 28.15. O ═══ ═══ 28.15.1. object ═══ object A visual component of a user interface on which an action can be performed. ═══ 28.15.2. object-oriented user interface ═══ object-oriented user interface A type of user interface that implements the object-action paradigm of selecting an object and then selecting an action to apply to that object. ═══ 28.15.3. OEM ═══ OEM Original Equipment Manufacturer. The designation applied to hardware and software developed by a company other than IBM. ═══ 28.15.4. OS/2 LAN Server ═══ OS/2 LAN Server A program that allows resources to be shared with other computers on a local area network (LAN). It contains both the client and server components. ═══ 28.16. P ═══ ═══ 28.16.1. passphrase ═══ passphrase A secret string of characters known to a computer system and a particular user who must specify it to gain access to the system and its data. A passphrase allows imbedded spaces and mixed case characters to support more flexible and complex combinations than a password allows. LAN Distance security relies on a user ID to identify a user and can optionally require a passphrase to authenticate that user. ═══ 28.16.2. personal account ═══ personal account An entry in the user account database that contains security specifications for a particular user. A Personal Account is the subset of fields that the specific user can alter, the passphrase and user description. The complete set is managed by the LAN Distance security administrator. ═══ 28.16.3. phone book ═══ phone book The LAN Distance product contains two type of phone books. Each entry in the phone book notebook under the Settings tab contains all information needed for dialing a particular workstation. Open as leads to a phone book used to dial other LAN Distance workstations. ═══ 28.16.4. phone book entry ═══ phone book entry A single named object within the phone book settings notebook. ═══ 28.16.5. point-to-point protocol (PPP) ═══ point-to-point protocol (PPP) A protocol that is used throughout the networking industry as a standardized method for interconnecting a variety of hosts, bridges, and routers from one or more vendors. ═══ 28.16.6. port ═══ port See communication port. ═══ 28.16.7. PPP ═══ PPP See point-to-point protocol (PPP). ═══ 28.16.8. privilege ═══ privilege A security designation that entitles a user to perform a set of tasks. Privileges are based on the user-type definitions of user, LAN Distance administrator, and LAN Distance security administrator, and are assigned within a user account. ═══ 28.16.9. protocol ═══ protocol The set of rules governing the operation of functional units of a communication system that must be followed for communication to take place. ═══ 28.16.10. protocol stack ═══ protocol stack Within the LAN Distance product, a synonym for LAN protocol. ═══ 28.16.11. protocol stack timer ═══ protocol stack timer A configurable parameter associated with the operation of a LAN protocol. ═══ 28.16.12. PSTN ═══ PSTN See Public Switched Telephone Network (PSTN). ═══ 28.16.13. Public Switched Telephone Network (PSTN) ═══ Public Switched Telephone Network (PSTN) Any switching system that provides a circuit switched to many customers. Four types exist in the USA: Telex, TWS, telephone, and Broadband Exchange. Within the LAN Distance product, PSTN encompasses asynchronous and synchronous connections. ═══ 28.17. Q ═══ ═══ 28.18. R ═══ ═══ 28.18.1. README ═══ README A file included in a software package to document very recent information. It supplements formal product documentation and ensures that information is up-to-date when a product is shipped to users. In the LAN Distance product, the file is located in the /WAL subdirectory. ═══ 28.18.2. redirected drive ═══ redirected drive A LAN feature allowing one LAN-attached workstation to access a drive on another LAN-attached workstation using a simple drive designation uniquely equated to the target workstation's drive. ═══ 28.18.3. remote-to-LAN ═══ remote-to-LAN A LAN Distance environment in which a standalone workstation connects to a LAN and accesses its workstations and resources. The standalone workstation connects to the LAN by dialing a LAN Distance Connection Server on the LAN. See also dial-in. ═══ 28.18.4. remote-to-remote ═══ remote-to-remote A LAN Distance environment in which two workstations are connected to form a LAN Distance wide area network. Each workstation can access the other's resources and LAN applications over the LAN Distance connection. See also virtual LAN. ═══ 28.18.5. response file ═══ response file A CID file used to supply answers to an installation program's prompts. These answers are the responses users specify during a window-driven installation. ═══ 28.18.6. ring ═══ ring A network configuration in which devices are connected by unidirectional transmission links to form a closed path. ═══ 28.19. S ═══ ═══ 28.19.1. SAP ═══ SAP Service Access Point. A logical protocol identifier that allows a system to route data between a remote device and the appropriate communications support. For example, the SAP value for NetBIOS is hex F0. ═══ 28.19.2. secure LAN Distance workstation ═══ secure LAN Distance workstation A LAN Distance workstation on which LAN Distance security is enabled. LAN Distance security helps to prevent unauthorized users from accessing the LAN Distance workstation. See also security policy. ═══ 28.19.3. Security Administrator ═══ Security Administrator See LAN Distance security administrator. ═══ 28.19.4. security policy ═══ security policy The set of rules that can be customized to enable the security requirements of a particular user environment. Examples of configurable items include Maximum allowed logon attempts and passphrase durations. ═══ 28.19.5. Settings ═══ Settings Also Settings Notebook. The object within the LAN Distance product through which configuration tasks are performed. ═══ 28.19.6. shuttle ═══ shuttle The LAN Distance feature that allows a workstation to switch between a stand-alone LAN Distance Remote and a Non-LAN Distance LAN-attached workstation. It is associated with physically moving the workstation on and off the LAN. ═══ 28.19.7. stand-alone workstation ═══ stand-alone workstation A workstation that runs application programs independently of another system, and is not LAN-attached. Contrast to LAN workstation. ═══ 28.19.8. switched line ═══ switched line A telecommunication line in which the connection is established by dialing. Contrast with nonswitched line. This terms applies to both PSTN and ISDN connections. ═══ 28.19.9. switched link ═══ switched link A wide area connection between workstations. ═══ 28.19.10. synchronous transmission ═══ synchronous transmission A type of data communication in which the sending and receiving of characters are controlled by timing signals. ═══ 28.20. T ═══ ═══ 28.20.1. TCP/IP ═══ TCP/IP Transport Control Protocol/Internet Protocol. An NDIS-compliant communications protocol that integrates unlike computer systems and networks. An NDIS-compliant version of TCP/IP for OS/2 is one of the LAN protocols supported by the LAN Distance product. ═══ 28.20.2. Token-Ring ═══ Token-Ring A LAN with a ring topology that passes tokens from one attaching device to another using the NetBIOS protocol. ═══ 28.20.3. traffic filtering ═══ traffic filtering Synonymous with filtering. A configurable LAN Distance Connection Server feature that reduces the amount of LAN traffic that flows across a connection to only the data frames that are needed by the participating workstations. ═══ 28.21. U ═══ ═══ 28.21.1. user ═══ user A security classification for the user who performs the LAN Distance tasks associated with establishing and using LAN Distance connections, for example, dialing and running LAN applications. See LAN Distance administrator and see also LAN Distance security administrator for the other user types defined by the LAN Distance product. ═══ 28.21.2. user account ═══ user account A record in the user account database that contains security specifications for a particular user. It is organized by user ID and includes information such as passphrase and privilege. It is managed by a LAN Distance security administrator. ═══ 28.21.3. user account database ═══ user account database A directory of LAN Distance user information. It is used to perform user identification and authentication for establishing LAN Distance connections and restricting access to certain tasks. ═══ 28.21.4. user ID ═══ user ID User identification; a unique name that identifies a user. ═══ 28.21.5. user type ═══ user type A specific type of user that is granted a fixed set of privileges. Each different type of user is granted a different set of privileges. See User, see administrator, and see Security Administrator. ═══ 28.22. V ═══ ═══ 28.22.1. variable callback ═══ variable callback A type of callback in which the telephone number to be dialed changes according to the location of the workstation. ═══ 28.22.2. virtual LAN ═══ virtual LAN A network consisting of individual workstations connected through the LAN Distance product. It operates just as a physically connect LAN, through the applications and LAN protocols supported transparently across the LAN Distance connections. ═══ 28.23. W ═══ ═══ 28.23.1. WAN ═══ WAN See Wide Area Network (WAN). ═══ 28.23.2. wide area network (WAN) ═══ wide area network (WAN) A network that provides communication services to a geographic area larger than that served by a local area network (LAN). In relation to the LAN Distance product, communication on a WAN is accomplished across telephone lines. ═══ ═══ Some modems may not support this value. ═══ ═══ Some modems may not support this value. ═══ ═══ Some modems may not support this value.