OS/2 WARP SERVER READ ME December 14, 1995 When viewing this document with the OS/2 Warp System Editor, use the System Monospaced font in the Normal style for best results. To display a window with font and style settings, select OPTIONS from the menu bar, then select SET FONT.... CONTENTS CHAPTER 1. INSTALLATION NOTES . . . . . . . . . . . . . . . . . . . . . 1 Warp Fixpack 16 (or Later) Will Not Migrate Some Enhancements . . . . . . 1 Upgrading LAN Distance Connection Server . . . . . . . . . . . . . . . . 1 Installation Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 1 If Your OS/2 Desktop Is Incomplete . . . . . . . . . . . . . . . . . . 2 If DDNS is Not Enabled in TCP/IP after it Has Been Installed . . . . . 2 Change the Password for LAN Distance Connection Server/Remote Access 2 How to Cancel a Server Installation after Selecting Install . . . . . . . 2 SystemView Windows TCP/IP Client Requires IBM TCP/IP for DOS Version 2.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 If SystemView Network Interfaces are Not Enabled after Install . . . . 3 Adding File and Print Sharing Components . . . . . . . . . . . . . . . 3 RIPL Disk Space Is Not Checked . . . . . . . . . . . . . . . . . . . . 3 CD-ROM Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . 3 Message-"OS/2 Warp Server CD-ROM Was Not Found" . . . . . . . . . . . . . 3 Adding a CD-ROM Driver to Installation Diskette 1 . . . . . . . . . . . 4 Default Cache size for HPFS386 . . . . . . . . . . . . . . . . . . . . . 4 Installation Problems that are Caused By Improper Hard Disk Format . . . 5 Performing a Long Hard Disk Format . . . . . . . . . . . . . . . . . . . 5 OS/2 Warp Server Installation Over FixPack 10 . . . . . . . . . . . . . . 6 Warp FixPack 15 is Not Compatible with OS/2 Warp Server . . . . . . . . . 6 Adding TCP/IP when Installing over OS/2 2.11 . . . . . . . . . . . . . . 6 Sharing NFS-mounted Volumes . . . . . . . . . . . . . . . . . . . . . . . 7 S-3 Trio Chip Video Support . . . . . . . . . . . . . . . . . . . . . . . 7 Installing LAN Distance Server Using Diskette . . . . . . . . . . . . . . 7 If Your NIF Driver Is in a Compressed Format . . . . . . . . . . . . . . 8 CHAPTER 2. ADAPTERS AND PROTOCOL SERVICES INSTALLATION AND CONFIGURATION 9 Select Configure When Upgrading MPTS . . . . . . . . . . . . . . . . . . 9 CID Migration of MPTS (2.60.2) on ThinkPad Is Incompatible (PCMCIA)-Ring Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installing Previous Versions of LAN Transport . . . . . . . . . . . . . . 9 Cannot start MPTS Due to Locked Files . . . . . . . . . . . . . . . . . 10 SystemView Netfinity Disk Error Data Available on IBM SCSI Devices . . 10 File Handles Used by the Shell . . . . . . . . . . . . . . . . . . . . 11 If You Have Installed Fault Tolerance, DISKFT.SYS Must Be the First Statement in the CONFIG.SYS File . . . . . . . . . . . . . . . . . . . 11 Run RPLSETD on an ISA Workstation to Setup the CONFIG.SYS and Drivers . 11 Added Parameters in CONFIG.SYS Cleared . . . . . . . . . . . . . . . . 11 NewsReader Lists of Followed Forums Is Lost after Migration . . . . . . 11 NetWare Adapter Restrictions . . . . . . . . . . . . . . . . . . . . . 12 Configuring a LAN Interface for TCP/IP . . . . . . . . . . . . . . . . 12 Installing MPTS Over CD-ROM Version of LAN Server 3.0 . . . . . . . . . 13 IBM Token-Ring Adapter Detection Conflict: . . . . . . . . . . . . . . 13 Additional Information for Installing and Configuring MAC Drivers . . . 13 NetBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 The Maximum Combined TCPBEUI and NetBEUI Limit . . . . . . . . . . . 14 Installing NetBIOS for TCP/IP Over IBM NetBIOS Version 1 . . . . . . 14 (C) Copyright IBM Corp. 1994, 1995 ii NetBIOS Ram Usage . . . . . . . . . . . . . . . . . . . . . . . . . . 14 NetBEUI Ram Calculations . . . . . . . . . . . . . . . . . . . . . . 15 New NetBEUI PROTOCOL.INI Parameters . . . . . . . . . . . . . . . . . 15 OS/2 NetBIOS Over TCP/IP . . . . . . . . . . . . . . . . . . . . . . . 16 Native Sockets Over NetBIOS . . . . . . . . . . . . . . . . . . . . . 16 Mobile File Sync (MFS) . . . . . . . . . . . . . . . . . . . . . . . . 17 CHAPTER 3. INSTALLING OS/2 WARP SERVER CLIENT PRODUCTS . . . . . . . . 18 Security and the Remote Installation Server . . . . . . . . . . . . . . 18 ADMIN Authority Needed when Logging on after Local Security is Installed 18 Client Hard Disk Space Requirements . . . . . . . . . . . . . . . . . . 18 If the Progress Indicator Stops . . . . . . . . . . . . . . . . . . . . 18 Canceling a Local Client Installation after Selecting Install . . . . . 19 Installation Problem with Empty 5.25-Inch Diskette Drive . . . . . . . 19 Serviceability and Diagnostic Aids . . . . . . . . . . . . . . . . . . 19 Existing PCMCIA Drivers Cause Incomplete Client Installation . . . . . 19 Client LAN Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Installing Clients without a LAN Adapter . . . . . . . . . . . . . . 20 Adding a LAN Adapter after Client Installation . . . . . . . . . . . . 20 Client IBM ThinkPad Information . . . . . . . . . . . . . . . . . . . . 21 Using an IBM PS/2 Model 76 or IBM ThinkPad Client . . . . . . . . . . 21 IBM ThinkPad 755CD Clients . . . . . . . . . . . . . . . . . . . . . 22 IBM ThinkPad 755C or 755CS in Docking Station I Clients . . . . . . . 22 IBM ThinkPad 701 Clients . . . . . . . . . . . . . . . . . . . . . . 22 IBM Dock II Docking Station Clients . . . . . . . . . . . . . . . . . 23 Individual Client Installation of Networking Products . . . . . . . . . 23 OS/2 Warp Server Windows Client Remote Install of SystemView and DLS . 23 If OS/2 RIPL Clients Do Not Boot . . . . . . . . . . . . . . . . . . 24 To Remove SytemView/System Management after an OS/2 Warp Server Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 CID and SystemView Considerations . . . . . . . . . . . . . . . . . . . 24 CHAPTER 4. CREATING DOS LAN SERVICES CLIENT DISKETTES . . . . . . . . 25 CHAPTER 5. DOS LAN SERVICES RESTRICTIONS . . . . . . . . . . . . . . . 26 Run TCPSTOP Before Upgrading from DLS 4.0 . . . . . . . . . . . . . . . 26 Ctrl-C During NET LOGON Causes GPF . . . . . . . . . . . . . . . . . . 26 System Hangs while Exiting Windows . . . . . . . . . . . . . . . . . . 26 Copies Stop when Exiting Windows . . . . . . . . . . . . . . . . . . . 26 DLS Memory Restrictions with Multiple Transports . . . . . . . . . . . 26 Extended ASCII Characters Not Supported . . . . . . . . . . . . . . . . 27 CHAPTER 6. DOS LAN SERVICES FOR WINDOWS 95 . . . . . . . . . . . . . . 28 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 LAN Server Not In Network Neighborhood . . . . . . . . . . . . . . . . 28 Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Sharing Restriction in non-NT Domains . . . . . . . . . . . . . . . . 28 Installing Virtual Net API Support for WIN-OS/2 . . . . . . . . . . . 29 CHAPTER 7. ADVANCED PRINT SERVICES . . . . . . . . . . . . . . . . . . 30 Required Changes to IBMLAN.INI for Printing with Multiple Printers . . 30 Printing from the OS/2 Help Facility to a PSF/2 Printer Object . . . . 30 LAN Notification and PSF/2 . . . . . . . . . . . . . . . . . . . . . . 31 PSF/2 Print Submitter and Print Queues not Connected to PSF/2 . . . . . 31 Contents iii QREADER.NLM Problems . . . . . . . . . . . . . . . . . . . . . . . . . 31 Online Documentation Printing Problems . . . . . . . . . . . . . . . . 31 DBCS Languages and SystemView . . . . . . . . . . . . . . . . . . . . 32 CHAPTER 8. LAN DISTANCE OS/2 REMOTE AND OS/2 TCPBEUI TROUBLESHOOTING . 33 CHAPTER 9. LAN DISTANCE FOR WINDOWS AND NETBEUI CONFIGURATION . . . . 34 Read the Following Before You Begin Setup Steps . . . . . . . . . . . . 34 Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . 35 Sample Configuration Files . . . . . . . . . . . . . . . . . . . . . . 35 CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 PROTOCOL.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 CHAPTER 10. LAN DISTANCE FOR WINDOWS AND TCPBEUI CONFIGURATION . . . . 38 Read the Following Before You Begin Setup Steps . . . . . . . . . . . . 38 Setup Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Sample Configuration Files for TCPBEUI Real Mode . . . . . . . . . . . 41 CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 PROTOCOL.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 NETWORK.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Sample Configuration Files for TCPBEUI Virtual Mode . . . . . . . . . . 43 CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 PROTOCOL.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 SYSTEM.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 NETWORK.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 CHAPTER 11. SYSTEM MANAGEMENT SERVICES . . . . . . . . . . . . . . . . 49 SystemView Server Installation . . . . . . . . . . . . . . . . . . . . 49 SystemView Client for Windows Installation . . . . . . . . . . . . . . 49 CHAPTER 12. VIEWING ONLINE DOCUMENTATION . . . . . . . . . . . . . . . 50 APPENDIX A. NOTICES . . . . . . . . . . . . . . . . . . . . . . . . . 52 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Contents iv CHAPTER 1. INSTALLATION NOTES Review the following notes before installing OS/2 Warp Server. WARP FIXPACK 16 (OR LATER) WILL NOT MIGRATE SOME ENHANCEMENTS Installation of OS/2 Warp Server will not migrate the following OS/2 Warp enhancements provided by OS/2 Warp FixPack 16 or later. 1. Security API support for the Security Enabling Services (SES) portion of the OS/2 Installable Security Subsystem (ISS) 2. IBM Developer API Extensions (DAX) for OS/2 If one or more OS/2 Warp Server workstations require OS/2 Warp support for DAX or SES, then OS/2 Warp Fixpack 16 (or later) Must Be Reapplied following installation OS/2 Warp Server. UPGRADING LAN DISTANCE CONNECTION SERVER If you plan to upgrade an installed LAN Distance Connection Server, you must backup your current security user definition file before installing Warp Server. The existing user definition file will be overwritten during the Warp Server installation process. To backup the user definition file, copy the file named WCBUSRF.ISF from the WAL directory onto a diskette. (This file contains the user definitions.) After the installation of Warp Server is completed, copy the backed up file from diskette back into the WAL directory. INSTALLATION RESTRICTIONS Each service included in OS/2 Warp Server can be installed over the same or previous versions of that service, except for the following restrictions: o OS/2 Warp Server software cannot be installed over a previously-installed LAN Distance Connection Server or LAN Distance Remote. Run LDREMOVE to remove LAN Distance Connection Server before installing any OS/2 Warp Server software. o The HPFS386 file system must be removed before migrating the operating system. If 386HPFS is on your system, see the "Migrating or Installing on 386HPFS" section in the online book, Planning, Installation, and Configuration Guide. To view this book type the following command at an OS/2 command prompt and press Enter: VIEW d:\CID\SERVER\BOOKS\A3A61M02.INF (C) Copyright IBM Corp. 1994, 1995 1 where d is the workstation's CD-ROM drive. IF YOUR OS/2 DESKTOP IS INCOMPLETE If after your final reboot of the OS/2 Warp Server Installation, your Desktop is incomplete, shutdown and reboot your workstation. IF DDNS IS NOT ENABLED IN TCP/IP AFTER IT HAS BEEN INSTALLED If you install the DDNS client code, complete the following steps after OS/2 Warp Server installation. 1. Open the TCP/IP folder. 2. Open the TCP/IP Configuration Program. 3. On the Network page, select the ALSO USING DDNS check box to enable this code. CHANGE THE PASSWORD FOR LAN DISTANCE CONNECTION SERVER/REMOTE ACCESS After OS/2 Warp Server installation, LAN Distance requires a minimum of an eight character password. After installation, start LAN Distance/Remote Access. You will be prompted for an ID and password. Use the ID and password you created during the installation. When prompted to create a new passphrase, specify one that is a minimum of eight characters. HOW TO CANCEL A SERVER INSTALLATION AFTER SELECTING INSTALL To cancel the installation before it begins, just select CANCEL on the following Workplace Shell message: Are you sure you want to close all windows and active programs... Then type the following command at an OS/2 command prompt: c:\WARPSRV\CLEANUP d: where c: is the drive you selected for the installation subdirectory and where d: is the OS/2 system boot drive. Chapter 1. Installation Notes 2 SYSTEMVIEW WINDOWS TCP/IP CLIENT REQUIRES IBM TCP/IP FOR DOS VERSION 2.1.1 When installing a SystemView Windows client on a Microsoft Windows 3.1 workstation and configuring it for TCP/IP, use IBM TCP/IP for DOS 2.1.1 instead of the TCP/IP protocol provided by DOS LAN Service 5.0. IF SYSTEMVIEW NETWORK INTERFACES ARE NOT ENABLED AFTER INSTALL If you wish to run SystemView on IPX and TCP/IP and the protocol is not installed previous to OS/2 Warp Server; you must install the protocol during the OS/2 Warp Server installation. After OS/2 Warp Server installation, open the SystemView icon and select configuration. Configure the proper protocol (IPX or TCP/IP) again. ADDING FILE AND PRINT SHARING COMPONENTS After you use the OS/2 Warp Server installation program to install the File and Print Sharing feature (LAN Server), you cannot use it again to add or remove LAN Server components (such as Replicator or Timesource). Instead Use OS/2 Installation/Configuration: 1. Open the LAN Services folder. 2. Open the OS/2 Installation/configuration. 3. Complete the install program. RIPL DISK SPACE IS NOT CHECKED For this version, disk space for RIPL is not checked. RIPL can put Rpldrive and Rpluserdrive on different drives than LAN Server itself. Rpldrive needs 70MB and Rpluserdrive needs 40MB (110MB total). CD-ROM INSTALLATION NOTES The following notes apply to CD-ROM installation. MESSAGE-"OS/2 WARP SERVER CD-ROM WAS NOT FOUND" During the installation, OS/2 Warp Server attempts to detect your CD-ROM and load the CD-ROM driver. If the driver for your CD-ROM is not on Install Diskette 1 you will get the following message. Please Insert CD-ROM To find a driver for your CD-ROM, contact the manufacture of your system, the IBM BBS, or IBM OS/2 Driver home page. After you download the driver for Chapter 1. Installation Notes 3 your CD-ROM, complete the following instructions to place the driver on Install Diskette 1. ADDING A CD-ROM DRIVER TO INSTALLATION DISKETTE 1 If a driver for your CD-ROM is not included on Install OS/2 Warp Server Diskette 1, you can add the driver to the diskette with the following steps: Before OS/2 Warp Server installation: 1. Make a copy of Diskette 1. Type "diskcopy a: a:" at a command prompt. 2. Remove other CD-ROM drivers to provide enough room for the new CD ROM driver. CD-ROM drivers that can be removed include: AHA154X.ADD, AHA164X.ADD, AHA174X.ADD, SONY535.ADD, or SONY31A.ADD. 3. Copy your *.ADD onto Installation Diskette 1. 4. Edit CONFIG.SYS on Installation Diskette 1. Place "REM " in front of the BASEDEV= for the drivers you just removed, and add a call to the new driver, for example type BASEDEV=AIC7870.ADD for driver AIC7870. 5. Also add "SET SAVECONNECT=1" to the CONFIG.SYS. After OS/2 Warp Server installation: 1. Copy a:\OS2CDROM.DMD to c:\OS2 2. Copy a:\CDFS.IFS to c:\OS2 3. Copy the new driver to c:\OS2 4. Edit CONFIG.SYS to add the following lines: DEVICE=c:\OS2\OS2CDROM.DMD /Q IFS=C:\OS2\CDFS.IFS /Q BASEDEV=AIC7870.ADD (or your driver name) 5. Save CONFIG.SYS and reboot your system. DEFAULT CACHE SIZE FOR HPFS386 HPFS386 will use a default cache size if one is not specified. To view the cache size, at the command line type: CACHE386 /0 Chapter 1. Installation Notes 4 INSTALLATION PROBLEMS THAT ARE CAUSED BY IMPROPER HARD DISK FORMAT The following are indications that a hard disk is improperly formatted and requires a long format, as described in "Performing a Long Hard Disk Format": o During installation, a red screen is displayed with an XCOPY error message that says the OS/2 Warp Server installation failed. If the installation runs without errors, the following symptoms might still occur: o If you use the DIR command, it displays the message: SYS0278: The system cannot find the extended attribute. o The volume label has strange symbols and characters in it. o When you run CHKDSK, FDISK, or FDISKPM, the file system displayed for a partition is FAT, even though you formatted the partition as HPFS. o When you run CHKDSK, it displays either of the following errors: - C:\ (drive label) attempted to claim an extended attribute that does not exist. - The first cluster number of C:\(drive label) is incorrect. - The entry has been truncated. o If you try to boot up from installation disks and run CHKDSK /F, the following error is displayed: The current hard disk drive is: C: The type of file system for the disk is FAT SYS0108: The disk is in use or locked by another process. PERFORMING A LONG HARD DISK FORMAT If a hard disk exhibits any of the symptoms described in "Installation Problems that are Caused By Improper Hard Disk Format," you can use the following steps to perform a long format of the drive: 1. Reboot with the Installation Diskette and Install Diskette 1 2. At the blue Welcome screen, press F3 to get to an OS2 command line 3. At an OS/2 command prompt, type one of the following commands and press Enter: o For a FAT partition: e:\OS2IMAGE\DISK_2\FORMAT d: /FS:FAT /L Chapter 1. Installation Notes 5 o For an HPFS partition: e:\OS2IMAGE\DISK_2\FORMAT d: /FS:HPFS /L where e: is the CD-ROM drive and d: is the partition you are installing OS/2 Warp Server on. OS/2 WARP SERVER INSTALLATION OVER FIXPACK 10 OS/2 Warp Server installation will run on all prior versions of OS/2 Warp. However, OS/2 Warp Server install will not run on a system with IBM OS/2 Warp Family FixPack 10, XRW010. Any system with this FixPack installed must migrate to the OS/2 Warp on the OS/2 Warp Server CD. WARP FIXPACK 15 IS NOT COMPATIBLE WITH OS/2 WARP SERVER If you have a workstation with FixPack 15, it must be replaced with Fixpack 16 or later to do an OS/2 Warp Server migration installation. ADDING TCP/IP WHEN INSTALLING OVER OS/2 2.11 When installing over OS/2 2.11 on workstations that do not already have TCP/IP installed, OS/2 Warp Server TCP/IP cannot be configured in MPTS during the OS/2 Warp Server installation. You can add the TCP/IP protocol to MPTS after installing OS/2 Warp Server by performing the following steps: 1. Shut down and restart your workstation. 2. In the OS/2 System folder, open System Setup; then open the Adapters and Protocol Services MPTS object. 3. Select CONFIGURE. 4. In the Configure window, select LAN ADAPTERS AND PROTOCOLS; then select CONFIGURE. 5. In the Current Configuration area of the LAPS Configuration window, select the adapter to which you are adding TCP/IP. 6. In the Protocols area, select IBM TCP/IP from the list; then select ADD. 7. Select OK. 8. Select CLOSE in the Configure window; then select EXIT to close MPTS. 9. Shut down and restart your workstation. Chapter 1. Installation Notes 6 SHARING NFS-MOUNTED VOLUMES Before using OS/2 Warp Server to share an NFS-mounted volume, increase the NFS retry timeout when you start NFS. Setting a timeout of about 15 seconds can prevent excessive processor use or lost connections that might otherwise occur if the NFS server is stopped. If you start NFS by creating an NFSSTART or NFSCTL object in the Startup folder, you can add the parameter -t15 to the object's settings to set a 15-second timeout. If you start NFS manually or in the STARTUP.CMD file, add the -t parameter to the command (for example, NFSSTART -t15). S-3 TRIO CHIP VIDEO SUPPORT The S-3 Trio Video chip will default to SVGA during OS/2 Warp Server install. When S-3 Trio drivers become available, you can download the driver from the IBM BBS or the IBM OS/2 World Wide Web Home page, http://www.europe.ibm.com/getdoc/psmemea/progserv/device Install the S-3 video driver as follows: 1. Open the OS/2 System folder on the Desktop. 2. Open the System Setup folder. 3. Open the System. 4. Open the Device Driver Install. 5. Follow the instructions that come with the device driver. 6. Close the System object, shut down OS/2, and restart your system to have these changes take effect. INSTALLING LAN DISTANCE SERVER USING DISKETTE To install LAN Distance using diskettes, do the following: 1. Run the program INSTUTIL which is on the root of the CD-ROM. 2. Select create 3.5 diskettes. 3. Select create MPTS diskettes. 4. Select create LAN Distance diskettes. 5. MPTS must be installed before LAN Distance can be installed. 6. Install MPTS. 7. Install LAN Distance. Chapter 1. Installation Notes 7 IF YOUR NIF DRIVER IS IN A COMPRESSED FORMAT If your NIF driver is in a compressed format, you must first decompress it on your support diskette, before you use the OS/2 Warp Server installation. The OS/2 Warp Server installation will not detect drivers in a compressed format. Chapter 1. Installation Notes 8 CHAPTER 2. ADAPTERS AND PROTOCOL SERVICES INSTALLATION AND CONFIGURATION The following notes apply to Adapters and Protocol Services (MPTS). SELECT CONFIGURE WHEN UPGRADING MPTS When upgrading an existing configuration when installing this new release of MPTS the user must select Configure and validate their LAPS Configuration and also update the CONFIG.SYS file. This new MPTS includes new TCP/IP transport drivers with new driver names, so unless CONFIG.SYS is updated the configuration will not be successfully migrated. CID MIGRATION OF MPTS (2.60.2) ON THINKPAD IS INCOMPATIBLE (PCMCIA)-RING SUPPORT When you do a CID migration of MPTS from Version 2.60.2 to Version 5.00.0 on a system configured with IBM PCMCIA Token-Ring Network adapter (IBMTOKCS.OS2 driver), the MPTS response file must have the following section: PRO_SECTION = ( NIF = IBMTOKCS.NIF SECTION_NANE = IBMTOKCS_NIF DRIVERNAME = IBMTCS$ ) This section updates the PROTOCOL.INI file with the correct driver name for the latest IBMTOKCS device driver. If the driver name has not been updated to IBMTOCS$ (from IBMTOK$) the following error will occur during IPL: ltg0099: Could not find a section with DriverName=IBMTCS$ in PROTOCOL.INI If this error occurs during IPL, going through MPTS' configuration utility (MPTS.EXE) will automatically update the PROTOCOL.INI file with the correct driver name in the IBMTOKCS_NIF section. INSTALLING PREVIOUS VERSIONS OF LAN TRANSPORT Some IBM services include earlier versions of the LAN Transport as a feature of their programs. These earlier versions of LAN Transport may be NTS/2 or MPTS. If you install one of these products, outside of the OS/2 Warp Server installation program, that include an earlier version of LAN Transport after installing the current version of MPTS, do not reinstall the LAN Transport from that product. Earlier versions of NTS/2 and MPTS are functional subset of the current MPTS and must never overlay the current version of MPTS. Since the current version of MPTS is a superset of earlier LAN Transports, products that use the current version of MPTS will function normally running (C) Copyright IBM Corp. 1994, 1995 9 over it. So, all CSD's and APAR fixes must be for the version that is installed. If attempting an earlier version of the Transport over the current MPTS, prior to the installation a panel will warn you that you are about to install an earlier version of LAPS than the one already on your system. You should select "NO" to exit the installation. For a CID install, set the upgrade_level = same (or old) in the inst_section of your response file to prevent overlaying MPTS with an older version of the Transport. The OS/2 command "syslevel" will give the user information on the version of LAN Transport that is currently installed on the system. The syslevel files for MPTS are: IBM OS/2 LAN Adapter and Protocol Support (syslevel.trp) IBM OS/2 Socket/Multi-Protocol Transport Services (syslevel.mpt) CANNOT START MPTS DUE TO LOCKED FILES Occasionally, the MPTS configuration utility will not allow the user to reconfigure due to Locked Files. The following message will appear: You have re-installed MPTS. Locked files will not allow you to start MPTS. You must exit MPTS, shutdown, and restart your workstation before you can start MPTS. If you have not re-installed MPTS, then delete the file IBMLANLK.LST found in the \OS2\INSTALL directory on the boot drive. This will allow you to start MPTS. DO NOT delete this file if you have re-installed MPTS and have not yet executed a shutdown and booted on the same boot drive. SYSTEMVIEW NETFINITY DISK ERROR DATA AVAILABLE ON IBM SCSI DEVICES When SystemView is installed, the BASEDEV=NFDASD.FLT is placed in your CONFIG.SYS, if you have a IBM SCSI disk drive. Although this DASD filter is designed to work with IBM SCSI devices it will also collect data on most IDE disk drivers. To use Netfinity DASD data collection on a driver other than IBM SCSI add the BASEDEV=NFDASD.FLT to your CONFIG.SYS file. Chapter 2. Adapters and Protocol Services Installation and Configuration 10 FILE HANDLES USED BY THE SHELL SET SHELLHANDLESINC=5 causes the shell process to increment the number of file handles available by 5 during the system boot up. This statement is added to CONFIG.SYS when Novell NetWare Gateway or SystemView is installed. IF YOU HAVE INSTALLED FAULT TOLERANCE, DISKFT.SYS MUST BE THE FIRST STATEMENT IN THE CONFIG.SYS FILE In most cases, the DISKFT.SYS statement should be the first statement in the CONFIG.SYS file. The DEVICE=DISKFT.SYS statement should precede IFS=HPFS386 and any device drivers that write to mirrored drives. For more information on DISKFT.SYS, see the Commands and Utilities Guide found in the LAN Services - File and Print folder within the Information folder on the Desktop. RUN RPLSETD ON AN ISA WORKSTATION TO SETUP THE CONFIG.SYS AND DRIVERS RPLSETD should be run on ISA workstation to correctly setup the CONFIG.SYS and drivers (VDM in this case). The \IBMLAN\RPL\FITS directory is where the *.fit files are located for the individual RIPL requesters. In this file, the VDMA.SYS should be mapped to VDMAAT.SYS for ISA workstations, or to VDMPS2.SYS for MCA workstations. ADDED PARAMETERS IN CONFIG.SYS CLEARED If parameters have been added to drivers in the CONFIG.SYS file, and those drivers are part of the MPTS configuration, MPTS will not maintain the parameters if you do a new MPTS configuration where CONFIG.SYS is updated. Parameters can be specified on the AFNB.SYS driver in order to configure Native NetBIOS socket support. If an update of CONFIG.SYS is performed by MPTS the original version of CONFIG.SYS is saved as CONFIG.MPT. NEWSREADER LISTS OF FOLLOWED FORUMS IS LOST AFTER MIGRATION The new NR/2 has support for several users. The active user is set in TCPOS2.INI when you run either the IBM dialer or Dial Other Internet Providers. If you are going to continue to use the same news reader after migration, you can copy the news*.* files from your ETC directory to ETC\RNSPOOL\USERNAME, where username is the ID you use to connect to the Internet. Users that are connected to a news server over the LAN are not affected because the files in the ETC are still used in this case. Chapter 2. Adapters and Protocol Services Installation and Configuration 11 NETWARE ADAPTER RESTRICTIONS The NetWare Requester Support Protocol can only be applied to a maximum of two adapters. The OS/2 Warp Server installation will let you to configure more than two adapters for NetWare support, but this will result in errors when you reboot. CONFIGURING A LAN INTERFACE FOR TCP/IP When the IBM TCP/IP is not installed on the workstation, you can configure the workstation for TCP/IP services as follows: 1. Using the LAPS panel, assign the TCP/IP protocol to a PHYSICAL adapter (e.g. IBM Token-Ring Compatible adapter). If desired, you can also configure the TCP/IP OVER NetBIOS protocol. Note that if you already have NetBIOS configured for this adapter, you will be required to change the "LOGICAL ADAPTER" number. These values apply to this panel only and have no relationship to selections on other panels. NOTE: You do not have to change the LOGICAL ADAPTER number for any of the other protocols unless prompted to do so. 2. Return to the "Configure" panel and select TCP/IP Configuration and press the Configure button. 3. From the "TCP/IP Configuration" panel, select "Network interface parameters" and press the Configure button. 4. On the "Configure TCP/IP Network Interface Parameters" panel, highlight the PHYSICAL LAN adapter that you have installed on the workstation and to which you previously assigned the TCP/IP protocol. 5. Press the Activate button to activate the interface. For example: if you had only an IBM Token Ring Compatible adapter installed, you would only activate adapter 0 (since there's only one PHYSICAL adapter) even though in step 1 above you referred to two LOGICAL adapters. 6. Enter the appropriate IP information (or check the Enable DHCP box) and save the information. 7. Returning to the previous panels and exiting MPTS will configure the system and update CONFIG.SYS (if selected). 8. Reboot to activate the new configuration. Chapter 2. Adapters and Protocol Services Installation and Configuration 12 INSTALLING MPTS OVER CD-ROM VERSION OF LAN SERVER 3.0 If installing MPTS over a version of LAPS that was previously installed with the CD-ROM version of LAN Server 3.0, the READONLY file attribute must be removed from all files in the \IBMCOM directory and all of its sub-directories prior to installing MPTS. To remove the READONLY file attribute, execute the following command from an OS/2 command prompt: ATTRIB -R \IBMCOM\*.* /S IBM TOKEN-RING ADAPTER DETECTION CONFLICT: A workstation with an IBM Token-Ring or IBM Token-Ring compatible adapter card may run into the following condition if MPTS was originally installed without using the adapter detection function (MPTS was installed as a stand-alone product). When reinstalling or upgrading MPTS with various products (LAN Server 4.0, OS/2 Warp Connect, etc....) that use MPTS' adapter detection function, the adapter detection function will detect all IBM Token-Ring and IBM Token-Ring Compatible adapters as "IBM Token-Ring Compatible". This may cause OS/2 Warp Server's MPTS to configure the adapter card as two adapter cards (1) IBM Token-Ring and (2) IBM Token-Ring Compatible. If this condition occurs, remove one of the configured Token-Ring drivers using the CONFIGURE option in the Adapters and Protocol Services MPTS object. Open this object from System Setup in the OS/2 System folder. ADDITIONAL INFORMATION FOR INSTALLING AND CONFIGURING MAC DRIVERS A complete list of supported adapter cards and information on MAC drivers can be found in the READMAC.TXT file located in the IBMCOM\MACS subdirectory on a system installed with MPTS. Prior to installation, this file may be extracted from the product diskette containing the MACS.ZIP file by using the following command: pkunzip2 macs.zip ibmcom\macs\readmac.txt MPTS also provides specific readme files for various MAC drivers. These files have the file extension of .TXT and are located in the IBMCOM\MACS subdirectory on a system installed with MPTS. Prior to installation, these files may be extracted from the product diskettes containing the MACS.ZIP file. To view which MAC drivers have a README text file associated with it, issue the following command on the MACS.ZIP file: pkunzip2 macs.zip *.txt /v To extract a specific file, use the following command on the appropriate ZIP file: pkunzip2 macs.zip ibmcom\macs\driver_name.txt Chapter 2. Adapters and Protocol Services Installation and Configuration 13 NETBIOS The following sections discuss NetBIOS and NetBEUI. THE MAXIMUM COMBINED TCPBEUI AND NETBEUI LIMIT The maximum combined limit IBM OS/2 NetBIOS and NetBIOS Over TCP/IP to be configured in MPTS is four. TCPBEUI consumes NetBIOS overhead for NCB's in the same manner as NetBEUI. NetBIOS Bindings Limit The limit on NetBIOS binding is four physical adapters, Unless LAN Distance has been or is now being installed. If you choose to install LAN Distance, this lowers the available bindings to three (LAN Distance uses the fourth as the logical adapter). INSTALLING NETBIOS FOR TCP/IP OVER IBM NETBIOS VERSION 1 When installing MPTS on a workstation that was previously configured for NetBIOS for TCP/IP using the "IBM NetBIOS Version 1 for OS/2 program" the new MPTS device drivers are not compatible with the IBM NetBIOS Version 1 product. You must complete the following steps: 1. Using the newly installed MPTS, reconfigure the system using MPTS and select the NetBIOS over TCP/IP protocol. 2. Configure the NetBIOS socket interface using MPTS. 3. BEFORE rebooting, edit the config.sys file and make the following changes: A. Delete the DEVICE=:\\NBDRIVER.SYS statement. B. Edit the LIBPATH statement to remove the reference to the netbios2 product path. 4. You can remove the IBM NetBIOS for TCPIP product. NETBIOS RAM USAGE The NetBIOS API device driver uses a single 64K data area for allocate of resources. To determine the resources to allocate for NetBIOS API you need to know the RAM usage of the NetBIOS API driver to stay within the 64K limitation. The sum of the following must be less than or equal to 64KB: Chapter 2. Adapters and Protocol Services Installation and Configuration 14 11310 Constant overhead + 95 * (how many NCBs available to NetBIOS API, which is a total NCB's in the PROTOCOL.INI minus redirector allocation) + 15* (How many NCBs available to the NetBIOS API minus (-) 15) + 990 * (How many NB bound adapters including LAN Distance and TCPBEUI bindings) - 990 * (How many redirector named adapters (net_statements in IBMLAN.INI) ) Total bytes < or = 64KB (65535 bytes) Examples for the NetBIOS API RAM utilization are in the LAN Technical Reference. If you have exceeded the 64K limitation the following error will occur during IPL: LT00065: The configuration parameters defined in PROTOCOL.INI exceed the 64KB work area. NetBIOS 4.0 support has ended. NETBEUI RAM CALCULATIONS The calculation of NetBEUI RAM usage can be automatically calculated using the NB64K utility found in the MPTSAPLT.ZIP file. The formula to determine the NetBEUI RAM usage can be found Appendix C in the MPTS* Configuration Guide. If you have exceeded the 64K limitation the following error will occur during IPL: LT00097: System resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM* NETBEUI did not load. NEW NETBEUI PROTOCOL.INI PARAMETERS The NetBEUI section of the PROTOCOL.INI file has two configurable parameters that are not listed in the documentation, SIDEBAND and BALANCE. These parameters should not be changed from their default values. When not present in the PROTOCOL.INI file, these two parameters are set to the correct values automatically. The default values (when not present in PROTOCOL.INI) are as follows: SIDEBAND = 1 BALANCE = 2 Setting SIDEBAND to 1 enables a performance enhancement used by LAN Server* for sending small frames. Setting SIDEBAND to 0 disables this performance enhancement. BALANCE is used to control how NETBEUI chooses which adapters are used when an NCB.LISTEN command is issued on a workstation with multiple Chapter 2. Adapters and Protocol Services Installation and Configuration 15 network adapters. If two network adapters on the same machine are on the same network segment (bridged segment) then setting BALANCE to 0 disables load balancing, setting BALANCE to 1 puts it into load balancing mode and setting BALANCE to 2 lets NETBEUI decide the appropriate load balancing mode. OS/2 NETBIOS OVER TCP/IP NATIVE SOCKETS OVER NETBIOS The SO_SNDTIMEO and SO_RCVTIMEO options are no longer supported on the GETSOCKOPT and SETSOCKOPT calls for AF_INET or AF_NB. When coding sockets calls using the AF_NB protocol, the following should be noted: o AF_NB does not support connect-connect. o The NetID coded in the address structure is the local adapter, and not the target machine's adapter. o AF_NB does not support OOB data. You may get either ENOPROTOOPT 10042 or EOPNOTSUPP 10045 error code. o If you issue a bind followed by a connect, AF_NB will verify that the NetID on the connect call is the same as the NetID on the bind call. o If you do an implicit bind, AF_NB will use the NetID specified on the connect call. o AF_NB does not support shutdown type 1 or shutdown type 2. Issuing either results in a error code of 10045. However, if shutdown type 2 was requested, a shutdown type 0 will be performed. Customization considerations: o In order to use AF_NB, USEMAXDATAGRAMS must be set to YES in \IBMCOM\PROTOCOL.INI. The default for USEMAXDATAGRAMS is NO. o The maximum number of NCBs available to each session is configurable to a maximum of 255. Running out of NCBs results in a program hang. o If you manually modify statements in CONFIG.SYS, be aware that the modifications will be lost if you re-install or upgrade MPTS. o The default customization for NetBIOS is not sufficient to support the maximum backlog that may be coded on a listen. Also, when the backlog is reached, AF_NB connect reports a successful connection. A NetBIOS connection is considered successful when the listening and connect NCBs are completed. The server does not know that the backlog has been reached until later. The server will hang up the session, making it unusable. o \IBMCOM\PROTOCOL.INI and \IBMLAN\IBMLAN.INI defaults for maximum number of names are not sufficient when running on a multiple LAN adapter system with either LAN Server or LAN Requester installed. o When using AF_NB protocol, error code 10055 may mean that you have run out of names in the names table. Increasing the maximum in \IBMCOM\PROTOCOL.INI and CONFIG.SYS should alleviate the problem. Chapter 2. Adapters and Protocol Services Installation and Configuration 16 MOBILE FILE SYNC (MFS) If you have previously installed MFS from the Warp AttachPak CD-ROM you must first remove MFS using the REMMFS command. Run REMMFS from the OS/2 Warp Server CD-ROM 2 using the following command: d:\BPIU\MFS\REMMFS where d: is your CD-ROM drive. Continue to the MFS installation by running d:\Install on the OS/2 Warp Server CD-ROM 2, and selecting the MFS product on the installation screen. Chapter 2. Adapters and Protocol Services Installation and Configuration 17 CHAPTER 3. INSTALLING OS/2 WARP SERVER CLIENT PRODUCTS SECURITY AND THE REMOTE INSTALLATION SERVER When a server system is running as a remote installation server it sets up SRVIFS thus giving free access to the entire drive where the images are stored. If you have confidential or private information also installed on the same drive as the images, then you will have a security risk with that confidential information. ADMIN AUTHORITY NEEDED WHEN LOGGING ON AFTER LOCAL SECURITY IS INSTALLED If you have installed local security, you need to log on with ADMIN authority. If you do not, programs in the Startup folder will not run and errors will be returned. CLIENT HARD DISK SPACE REQUIREMENTS The OS/2 disk space includes 4MB for the OS/2 Warp Server Remote Client Installation program. This installation program can be deleted after OS/2 Warp Server Remote Client is installed. An additional disk space of 5 to 10MB is used during installation for swap space and temporary file space. The OS/2 Warp Server Remote Client integrated installation program does not accurately check hard disk space. Ensure that there is enough available to install and use the services you have selected. If you select to install all OS/2 Warp Server client software, you might need as much as 200MB free hard disk space to install client software and use the workstation, depending on the applications you use. Using individual installation, you can install more services than the integrated installation might allow. However, after using this installation method, you might have to closely monitor your usable hard disk space to avoid problems. IF THE PROGRESS INDICATOR STOPS If the progress indicator for OS/2 Warp Server Remote Client Installation stops moving and the CD-ROM and Disk lights on your workstation indicate no install activity, you can press Alt+Shift+F3 to remove the progress indicator and see any commands in the OS/2 Warp Server Remote Client install window. (C) Copyright IBM Corp. 1994, 1995 18 CANCELING A LOCAL CLIENT INSTALLATION AFTER SELECTING INSTALL To cancel the installation before it begins, just select CANCEL on the following Workplace Shell message: Are you sure you want to close all windows and active programs... Then type the following command at an OS/2 command prompt: c:\OS2CLNT\CLIENTS\CASCLEAN d: where c: is the drive you selected for the installation subdirectory and where d: is the OS/2 system boot drive. INSTALLATION PROBLEM WITH EMPTY 5.25-INCH DISKETTE DRIVE Some 5.25-inch diskette drives create installation problems with LAN Requester and IBM Peer for OS/2. If the 5.25-inch diskette drive light stays on, and the installation appears to stop or slow down, insert a blank diskette in the 5.25-inch drive and restart the workstation to continue the installation. SERVICEABILITY AND DIAGNOSTIC AIDS OS/2 Warp Server Remote Client requires the Serviceability and Diagnostic Aids of OS/2 Warp be installed. Do not deselect this OS/2 Warp install option. The message "(SYS1718) The System cannot find the file: \OS2\LOG.SYS and \OS2\MDOS\LPTDD.SYS and \OS2\SYSTEM\LOGDAEM.EXE" might be displayed at reboot if you deselect this option. EXISTING PCMCIA DRIVERS CAUSE INCOMPLETE CLIENT INSTALLATION Before installing OS/2 Warp Server client software over an existing version of OS/2 Warp on a PCMCIA workstation, edit the workstation's CONFIG.SYS file and remove or comment out lines that contain any of the following driver names: o PCM2ATA.SYS o ICMEMMTD.SYS o ICMEMCDD.SYS To comment out a line in the CONFIG.SYS file, add the keyword REM to the beginning of the line. Save the changed CONFIG.SYS file; then shut down and restart the workstation. If any of these drivers are present, the file and print sharing client installation program will fail. Chapter 3. Installing OS/2 Warp Server Client Products 19 CLIENT LAN ADAPTERS For more information on installing specific adapter cards, see the READMAC.TXT file located in the \CID\NIFS directory on CD-ROM 1. If you encounter a problem, you may need to contact the manufacturer of your adapter card for technical support. INSTALLING CLIENTS WITHOUT A LAN ADAPTER Select NO ADAPTER from the adapter driver list. This selection will install the IBM Parallel Port adapter on your workstation, and will allow you to install any combination of OS/2 Warp Server Remote Client products. At startup time you will see the following message: The IBM Parallel Port ANDIS MAC Driver is installed. Without a LAN Adapter you are limited in the connectivity functions that you can perform; however, you can use the TCP/IP async connection (SLIP or PPP) to connect to other TCP/IP systems or you can use LAN Distance Remote to connect over an async modem to a LAN Distance Connection Server and use IBM Peer for OS/2 or IBM LAN Requester to access a LAN. ADDING A LAN ADAPTER AFTER CLIENT INSTALLATION If you have installed OS/2 Warp Server Remote Client using the NO ADAPTER selection, you can add an adapter by performing the following steps: 1. Shut down and turn off your workstation. 2. Install the new LAN Adapter. 3. Turn on your workstation. NOTE: If you have installed LAN Distance Remote, you must remove it before continuing. You can use the LDREMOVE command, located in the \WAL directory, to remove LAN Distance Remote. 4. In the OS/2 System folder, open System Setup; then open the Adapters and Protocol Services MPTS object. 5. Select CONFIGURE. 6. In the Configure window, select LAN ADAPTERS AND PROTOCOLS; then select CONFIGURE. 7. In the Current Configuration area of the LAPS Configuration window, select IBM OS/2 NETBIOS under IBM Parallel Port in the list. 8. Select REMOVE; then select YES in the confirmation window. 9. The IBM Parallel Port is now highlighted. Select REMOVE; then select YES in the confirmation window. Chapter 3. Installing OS/2 Warp Server Client Products 20 10. In the Network Adapters area, select the adapter type you installed; then select ADD. 11. In the Protocols area, select IBM OS/2 NETBIOS; then select ADD. 12. Select OK. 13. Select CLOSE in the Configure window; then select EXIT to close MPTS. 14. Shut down and restart your workstation. CLIENT IBM THINKPAD INFORMATION USING AN IBM PS/2 MODEL 76 OR IBM THINKPAD CLIENT If you are installing OS/2 on an IBM PS/2 Model 76 or an IBM ThinkPad 700, 700C, 720, or 720C, you need to replace the ABIOS files on the OS/2 Installation Diskette with files from the Reference Diskette. Do the following: 1. If you are using a ThinkPad, detach it from the docking station. Create a Reference Diskette by following the documentation that came with your computer. 2. Make a copy of the Installation Diskette. Type "diskcopy a: a:" and press Enter. Remove and insert diskettes when prompted to do so. 3. Remove the copy from drive A and insert the original Installation Diskette. 4. Turn your computer on. If your computer is already on, press Ctrl+Alt+Del to restart it. 5. When you are prompted to do so, remove the Installation Diskette, insert Diskette 1, and press Enter. 6. When the Welcome screen is displayed, press F3 to display the command prompt. 7. Insert the copy of the Installation Diskette into drive A. 8. Type "a:\del *.bio" and press Enter. 9. Remove the copy of the Installation Diskette and insert the Reference Diskette you created into drive A. If your computer has more than one diskette drive, insert the copy of the Installation Diskette into drive B. In the next two steps, you will be prompted to insert diskettes into both drive A and drive B. If your computer has only one diskette drive, when you are asked to insert a diskette into drive A, insert the Reference Diskette into the diskette Chapter 3. Installing OS/2 Warp Server Client Products 21 drive. When you are asked to insert a diskette into drive B, insert the copy of the Installation Diskette into your diskette drive. 10. Type "copy a:\*.bio b:\" and press Enter. 11. Type "copy a:\abios.sys b:\" and press Enter. 12. Turn off your computer. 13. If you are using a ThinkPad, return it to the docking station. IBM THINKPAD 755CD CLIENTS The OS/2 Warp Server Remote Client does not automatically detect the ThinkPad 755CD adapter type. You must select the PCMCIA option during installation. The IBM ThinkPad 755CD's default audio configuration of Memory IO = X'220' can conflict with many PCMCIA (credit card) LAN cards. The PCMCIA cards' Memory IO = X'A20' so the conflict with the X'220' sound feature is not obvious. However, the sound feature is an emulation of the Sound Blaster 16 card which only has 10 bit addressing, and the last 10 bits of both the PCMCIA and Sound Blaster 16 cards are the same '10 0010 0000' in binary. To install a PCMCIA Token Ring or a PCMCIA Ethernet card into an IBM ThinkPad 755CD you must change the audio Memory IO address to X'240' (or some other unused address). If you have conflicting IRQs or Memory IO addresses you will see an error flashed on the screen for 10 seconds during restart that says the IBM2SS01.SYS file did not load. Then you receive a restart message that your LAN device driver did not load. IBM THINKPAD 755C OR 755CS IN DOCKING STATION I CLIENTS PCMCIA Token-Ring cards and the Future Domain SCSI adapter can interact to cause I/O errors on a CD-ROM attached to the SCSI adapter. To avoid these I/O errors, change the SCSI Controller Memory Address on the Docking Station I from CA00 to an unused memory address (CE00 or DE00). Refer to the IBM ThinkPad Dock I Users Guide (part number 71G4054) page 5-5 for instructions on how to change the SCSI Controller Memory Address. IBM THINKPAD 701 CLIENTS The 701 ThinkPad Chips and Technology Video comes set to MMIO=CC00. This conflicts with the MMIO default on several PCMCIA cards. Reset the MMIO on the 701 video to D400 to avoid conflicts with PCMCIA cards. The 701 audio can also conflict with the IRQ and IOAddress of the PCMCIA cards. To get started you can disable the audio function, install OS/2 Warp Server Remote Client, then enable the audio at addresses and IRQs that are not used by the PCMCIA cards. Chapter 3. Installing OS/2 Warp Server Client Products 22 IBM DOCK II DOCKING STATION CLIENTS ThinkPads on Dock II docking stations with Adaptec SCSI adapters can hang during OS/2 Warp Server Remote Client install. To prevent this hang, change the SCSI port address from 340h to 140h using the switch block switch number 4. Page 78-79 of the IBM ThinkPad Dock II User's Guide, 84G9682, describes where the switch block is located and how to change the port address of the SCSI adapter. INDIVIDUAL CLIENT INSTALLATION OF NETWORKING PRODUCTS Individual installation programs for the networking products are included on OS/2 Warp Server Remote Client. But to install these networking products individually you should be an experienced system and LAN administrator. Here are some examples where you might want to use the individual product installation: o Complex configurations may require individual product installation. OS/2 OS/2 Warp Server Remote Client installation uses defaults for many configuration parameters. To explicitly set every configuration parameter use the individual installation programs. o The OS/2 Warp Server Remote Client installation program does not support multiple LAN adapters. If you have multiple LAN adapters in your workstation you will get unpredictable results. You can use the individual networking product installation to install and configure multiple LAN Adapters. Always install LAN Distance Remote last so it can create a shuttle function to allow operation of your workstation on or off the LAN. ATTENTION: IF YOU HAVE TO REINSTALL ANY NETWORKING PRODUCT AFTER LAN DISTANCE REMOTE, FIRST REMOVE LAN DISTANCE REMOTE. NOTE: You can use the LDREMOVE command, located in the \WAL directory, to remove LAN Distance Remote. OS/2 WARP SERVER WINDOWS CLIENT REMOTE INSTALL OF SYSTEMVIEW AND DLS If the following message is received during the OS/2 Warp Server Windows Client installation: "STOP" It was not possible to write the distribution configuration due to TCP/IP (or NetBIOS) Problems. Select CANCEL. After you complete the installation, open the SystemView icon and re-configure these protocols. Chapter 3. Installing OS/2 Warp Server Client Products 23 IF OS/2 RIPL CLIENTS DO NOT BOOT If you use the Advanced server, and installed the \IBMLAN\RPL or the \IBMLAN\RPLUSER directories on a FAT volume, the \IBMLAN\IBMLAN.INI file must be updated to increase the MAXOPENS parameter in the [server] section. The recommended values are as follows: For OS/2 only, MAXOPENS = (# of RIPL clients) * 70. For OS/2 + CM/2, MAXOPENS = (# of RIPL clients) * 115. Other applications that use RIPL clients, who have their file trees located in the \IBMLAN\RPL directory tree (or somewhere else on the FAT volume), will also contribute to the number of open files and must be accounted for in the MAXOPENS parameter. TO REMOVE SYTEMVIEW/SYSTEM MANAGEMENT AFTER AN OS/2 WARP SERVER CLIENT INSTALLATION To remove SystemView: 1. Open the SYSTEM MANAGEMENT - SYSTEMVIEW icon on the Desktop. 2. Open the INSTALL UTILITY icon. 3. From the Actions menu, select DELETE. CID AND SYSTEMVIEW CONSIDERATIONS To avoid conflict of CID directory structures, put the OS/2 Warp Server remote client images on a different partition than your SystemView code images. Chapter 3. Installing OS/2 Warp Server Client Products 24 CHAPTER 4. CREATING DOS LAN SERVICES CLIENT DISKETTES To install client workstations for DOS LAN Services, use installation diskettes created from the OS/2 Warp Server CD-ROM at an OS/2 Workstation. You need 4 blank, formatted, 1.44MB 3.5-inch diskettes. TO CREATE DOS LAN SERVICES DISKETTES: 1. Insert the OS/2 Warp Server CD-ROM. 2. Type the following command at an OS/2 command prompt and press Enter: d: where d is the CD-ROM drive. 3. Type the following command and press Enter: CD \CID\SERVER\IBMLS 4. Insert a blank diskette labeled DOS LAN Services Installation Disk 1; then type the following command and press Enter: XCOPY IBM500D1\*.* A: 5. When the copy is finished, remove the diskette. Insert another blank diskette, labeled DOS LAN Services Installation Disk 2. Then type the following command and press Enter: XCOPY IBM500D2\*.* A: 6. When the copy is finished, remove the diskette. Insert another blank diskette, labeled DOS LAN Services Installation Disk 3. Then type the following command and press Enter: XCOPY IBM500D3\*.* A: 7. When the copy is finished, remove the diskette. Insert another blank diskette, labeled DOS LAN Services Installation Disk 4. Then type the following command and press Enter: XCOPY IBM500D4\*.* A: For information about installing DOS LAN Services, see the online Network Administrator Reference Vol. 1: Planning and Installation. To view this book type the following command at an OS/2 command prompt and press Enter: VIEW d:\CID\SERVER\BOOKS\A3A61M02.INF where d is the workstation's CD-ROM drive. (C) Copyright IBM Corp. 1994, 1995 25 CHAPTER 5. DOS LAN SERVICES RESTRICTIONS Review the following restrictions before installing or using DOS/Windows file and print client workstations. RUN TCPSTOP BEFORE UPGRADING FROM DLS 4.0 Run TCPSTOP before installing OS/2 Warp Server client software on a workstation that already has DLS 4.0 and IBM TCP/IP for DOS installed. If you do not stop IBM TCP/IP for DOS, a TRAP exception will occur when the INSTALL program for DLS 5.0 starts. CTRL-C DURING NET LOGON CAUSES GPF After running the NET LOGON command in a Windows DOS prompt, do not press Ctrl-C at the workstation password prompt. Doing so causes a general protection fault (GPF). SYSTEM HANGS WHILE EXITING WINDOWS If the Peer service has been started and the system hangs when you exit Windows, try increasing the size of the STACKS command in the CONFIG.SYS file. COPIES STOP WHEN EXITING WINDOWS Do not exit Windows while the Peer service is running if a client is copying files from your DOS peer workstation. If you exit Windows while a copy is in progress, the copy will stop. DLS MEMORY RESTRICTIONS WITH MULTIPLE TRANSPORTS If you select both the NetBEUI and TCPBEUI real-mode transports when you install DOS LAN Services, you might not be able to start Windows. This is because of memory requirements below 640K. With both transports installed, Windows will not start if the Peer service is running, or if the Full redirector is running with the Messaging and Netpopup services. Windows will start if only the Full redirector and Messaging service are running. If you install only NetBEUI or only TCPBEUI, but not both, then you can start Windows with all DLS services running. (C) Copyright IBM Corp. 1994, 1995 26 EXTENDED ASCII CHARACTERS NOT SUPPORTED If you use extended ASCII characters (decimal codes 128-255) to name a network resource, users at DOS/Windows workstations might not be able to display or use that resource in DLS in Windows or in the DLS graphical user interface. This is because of the way character sets are converted for display on different workstations. DLS in Windows does not support extended ASCII characters (decimal codes 128-255) that do not have equivalents in the ANSI character set. This is a current restriction of Windows. Windows converts most unsupported characters to either an underscore (_) or vertical bar (|). Refer to your Windows documentation for information about the ANSI character set. On DLS workstations that use code page 437 to display characters (primarily in the United States) the DLS graphical user interface does not support the following extended ASCII codes (decimal): 155 226-229 249 157-159 231-240 251 169 242-245 252 176-224 247 254 Chapter 5. DOS LAN Services Restrictions 27 CHAPTER 6. DOS LAN SERVICES FOR WINDOWS 95 The DOS LAN Services for Windows 95 product allows your Windows 95 computer to access IBM LAN Server functions such as ALIAS names, DASD Limits, Shared Applications etc. This product is an add on to the Windows 95 Microsoft Network function. It gives you all of the LAN Server server function, in addition to what Windows 95 has already provided. INSTALLATION LAN SERVER NOT IN NETWORK NEIGHBORHOOD If your IBM LAN Server (Logon Server) is not showing up in your Network Neighborhood dialog you may have to modify some of your network settings. Following are the settings you will need to change: 1. Select "Control Panel" from the Task Bar (Start) 2. Select "Network" 3. Highlight "File and Printer Sharing for Microsoft Networks" and press the button "Properties" 4. Set the Property "Browse Master" to the Value "Enabled" 5. Set the Property "LM Announce" to the Value "Yes" 6. Select the "OK" button on the "File and Printer Sharing for Microsoft Network Properties" panel 7. Select the "OK" button on the "Network" panel At this point you should be prompted to restart the system. You must restart the system to activate these changes. KNOWN PROBLEMS SHARING RESTRICTION IN NON-NT DOMAINS If you log on to a non-NT domain or workgroup from a Windows 95 peer workstation, you can use only share-level access control for shared files and printers. If you attempt to set user-level access, the list of users cannot be displayed. (C) Copyright IBM Corp. 1994, 1995 28 INSTALLING VIRTUAL NET API SUPPORT FOR WIN-OS/2 The ability to have Virtual Net API (VNETAPI) support from a WIN-OS/2 session is new to OS/2 Warp Server. Installation is by running the VNETDLS.CMD. When the REXX file is run to install this support there are two parameters that are usually required (if these are not entered the VNETDLS.CMD prompts the user for these parameters). The first is the source path. The second is the target path. SOURCE PATH This is the location where the program will be found. Although this could be a redirected drive, the diskette drive or a CD-ROM drive, users installing from a CD-ROM will find it convenient to simply use the CD-ROM drive. As an example, E:\CID\CLIENT\DLS (where E:\ is the CD-ROM and \CID\CLIENT\DLS is the directory location of the DLS program). TARGET PATH The target path is the drive and directory where the program is installed. The user typically will create a directory where the program is installed. As an example, D:\VWINOS2 (where D:\ is the drive and VWINOS2 is the directory location for the program). In order for the Virtual Net API support for WIN-OS/2 to work it must NOT be installed in \IBMLAN\NETPROG (this directory is where OS/2 Warp Server's executables reside). You must use another, user-created, directory as the target install directory. Chapter 6. DOS LAN Services for Windows 95 29 CHAPTER 7. ADVANCED PRINT SERVICES The following notes apply to Print Services Facility/2. REQUIRED CHANGES TO IBMLAN.INI FOR PRINTING WITH MULTIPLE PRINTERS If you want to operate multiple printers using PSF/2, and you choose to store print resources on a network drive attached to a remote file server, you will need to change the values of two parameters in the IBMLAN.INI file on the remote file server. The two parameters are MAXOPENS and MAXSESSOPENS. The default value for MAXOPENS is 64, and the default value for MAXSESSOPENS is 50. To each value, add: 30 * (the number of DPF spools + the number of PSF/2 printer objects) For example, if MAXOPENS is 64, and MAXSESSOPENS is 50, and if you have 16 DPF spools and 10 PSF/2 printer objects, then set MAXOPENS to 844, and set MAXSESSOPENS to 830. If you do not increase these values, you may receive the following PSF/2 error messages on the screen: AIN0228E PSF/2 cannot open the resource in the file . Make sure that this file exists and that the drive is available. AIN0585E All attempts to open resource in file failed. PRINTING FROM THE OS/2 HELP FACILITY TO A PSF/2 PRINTER OBJECT If you want to print from the OS/2 Help Facility to an OS/2 or PSF/2 print queue, follow the instructions below to make sure that the print data is created correctly. You may want to follow these instructions if you have trouble printing from other applications. 1. Select the printer object and access the pop-up menu using the right mouse button. 2. Open the "Settings" view of the object and select the "Queue options" tab. 3. Select the "Printer-specific format" check box, then close the settings view of the printer object. You should now be able to print successfully to a print queue from the OS/2 Help Facility. (C) Copyright IBM Corp. 1994, 1995 30 LAN NOTIFICATION AND PSF/2 If LAN notification is activated and a job is printed successfully, a message is sent to the user who submitted the print job; but the message erroneously states that the job was deleted and did not print. This message only appears when PSF/2 has printed the job successfully and has removed it from the print queue. If the print job cannot be printed successfully by PSF/2, the user receives no notification from the LAN. PSF/2 PRINT SUBMITTER AND PRINT QUEUES NOT CONNECTED TO PSF/2 If the PSF/2 Print Submitter or APRINT command is used to print a job on a printer object serviced by the PMPRINT queue processor, the following message will appear from the PMPrint Spooler Queue Processor: "Unrecognized queue driver parameter. The print job will be printed using the default parameters. (PMV6012)" In most cases, ASCII print jobs submitted this way will still print. NOTE: AFPDS print jobs will not print correctly if submitted to a print queue that is not connected to PSF/2. QREADER.NLM PROBLEMS 1. When using QREADER.NLM and NWPSF2.EXE to transfer large jobs from the NetWare server to the PSF/2 system, and the OS/2 spool runs out of space, QREADER.NLM will cause the NetWare server to fail. 2. Do not use QREADER.NLM on NetWare 4.02, it cannot open the queue and read the job, and eventually will`hang the server. If you have NetWare 4.02 or the problem described in item #1 is encountered, you should stop using QREADER.NLM and NWPSF2.EXE and start using NetWare's PSERVER.NLM on the NetWare server, and the Novell Network Printer Support that is located in the Novell object on the PSF/2 system. The problems should also be reported to PSF/2 Software Support. ONLINE DOCUMENTATION PRINTING PROBLEMS If you want to print online documentation on OS/2 Warp Server make sure the default printer is not a PSF/2 defined printer. A PSF/2 printer is a printer defined in the PSF/2 Control Panel. If you get the error message of "F1DUMMY cannot be found." when the default printer is set to a PSF/2 printer, (it happens when you select the print button on the online doc panels.), change the printer to other than a PSF/2 printer. Chapter 7. Advanced Print Services 31 DBCS LANGUAGES AND SYSTEMVIEW The online publications, provided with OS/2 Warp Server, are in .INF file format. Most of these books are viewable and printable in the language of your country or English. For SystemView, some of the publications are duplicated in BookMaster (.BOO) format. Note that these .BOO files are not viewable/printable in DBCS languages. You should use the .INF versions for DBCS. Chapter 7. Advanced Print Services 32 CHAPTER 8. LAN DISTANCE OS/2 REMOTE AND OS/2 TCPBEUI TROUBLESHOOTING If you experience any of the following symptoms, your OS/2 LAN Distance Connection Server may not have the LAN Distance logical adapter configured as adapter 0. On the OS/2 LAN Distance Connection Server, use MPTS to reorder the adapters so that the LAN Distance logical adapter is adapter 0. Then use TCP/IP configuration to activate the adapter 0 interface. o After you dial the LAN Distance Connection Server, the connection status never changes from "connecting" to "connected". o After about a minute, this message may be displayed: WCL0348: The LAN Distance product could not establish a NetBIOS conversation with the called workstation. The call could not be connected. (C) Copyright IBM Corp. 1994, 1995 33 CHAPTER 9. LAN DISTANCE FOR WINDOWS AND NETBEUI CONFIGURATION ATTENTION: These configuration steps are not needed if you require 802.2 to run over NetBEUI or if your machine is not an ISA bus machine. READ THE FOLLOWING BEFORE YOU BEGIN SETUP STEPS Before completing the following steps in this README, complete these prerequisites: o Any Windows applications that you are using should operate correctly in the LAN environment BEFORE you install the LAN Distance product. o The DOS LAN Services product for MS Windows should be installed. o The LAN Distance Remote product for MS Windows should be installed. 1. LAN Distance installation prompts you to restart your workstation to make configuration changes active. It's only necessary to restart your workstation ONCE--after you complete the steps that follow. 2. In addition to the steps provided here, sample configuration files are provided as a reference. NOTE: The PROTOCOL.INI that is generated by these configuration steps is the result of merging the DLS PROTOCOL.INI into the LAN Distance PROTOCOL.INI. 3. You need to execute the configuration steps if the following information message is displayed when you logon through IBM DOS LAN Services: You were logged on, but you have not been validated by a server. Therefore, you may not have permission to use some network resources. (C) Copyright IBM Corp. 1994, 1995 34 CONFIGURATION PROCEDURE 1. Edit configuration files: (**required**) See the appropriate sample configuration files in STEP 6 below. 2. LAN Distance settings (**optional**) Complete any additional configuration required to set up the MS Windows LAN Distance Remote product. For assistance configuring the LAN Distance product, see the LAN Distance publications. 3. Update shuttle files (**required**) Update the *.RWS files (config.rws, autoexec.rws, protocol.rws, and system.rws) with the new configuration files. 4. Other possible PROTOCOL.INI changes (**optional**) If you receive a Protocol Manager binding error message when you restart your workstation, then it's likely that sections of your PROTOCOL.INI file are not bound to the SOCKDD_MOD. Modify the binding statements (BINDINGS=) in the Windows PROTOCOL.INI which do not list SOCKDD_MOD as the first parameter. If a bindings statement has only one parameter, the parameter is replaced with SOCKDD_MOD. 5. Restart your workstation (**required**) After completing Steps 1 - 3 and making any other necessary changes described 4, restart your workstation. 6. Review sample configuration files (**optional**) In the following configuration files, statements that were changed or added are marked with an ---> at the beginning of the statement. SAMPLE CONFIGURATION FILES CONFIG.SYS Chapter 9. LAN Distance for Windows and NetBEUI Configuration 35 FILES=30 BUFFERS=10 DOS=HIGH DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\SETVER.EXE DEVICE=C:\DOS\POWER.EXE DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER STACKS=9,256 LASTDRIVE=Z --> DEVICE=C:\net\PROTMAN.DOS /i:C:\WAL DEVICE=c:\WAL\taplf.dos --> rem DEVICE=c:\WAL\dxmj0mod.sys DEVICE=c:\WAL\dosvmac.sys DEVICE=c:\WAL\winamac.sys DEVICE=c:\WAL\pcmdd.sys DEVICE=C:\NET\DLSHELP.SYS AUTOEXEC.BAT C:\WINDOWS\SMARTDRV.EXE @ECHO OFF SET PATH=c:\WAL\;C:\NET;C:\NWDBPATH;C:\WINDOWS;C:\DOS;%PATH%; SET TEMP=C:\DOS C:\DOS\MOUSE.COM C:\DOS\DOSKEY.COM SHARE --> rem c:\WAL\DOSBIND --> c:\net\net start PROTOCOL.INI --> [network.setup] --> version=0x3100 --> netcard=sockdd_mod,1,SOCKDD_MOD --> transport=netbeui,NETBEUI --> lana0=sockdd_mod,1,netbeui --> [protman] --> DriverName=PROTMAN$ --> PRIORITY=netbeui Chapter 9. LAN Distance for Windows and NetBEUI Configuration 36 [NETBEUI] DriverName=NETBEUI$ Bindings=SOCKDD_MOD NCBS=32 Sessions=32 Names=17 MaxDatarcv=4168 MaxTransmits=6 TI=60000 T1=10000 T2=2000 --> LANABASE=0 [SOCKDD_MOD] DriverName=VLANMAC$ LanType="TokenRing" Mode="Flows" NetAddress=T400000000D62 MaxFrame=1080 [COM1] MaxFrame=1080 MACTYPE="802.5" DRIVERNAME="COM1MAC$" PCMSUPPORT="YES" CONN_TYPE="SWITCHED" PORTNAME="COM1" TX_FIFO_SIZE=7 Chapter 9. LAN Distance for Windows and NetBEUI Configuration 37 CHAPTER 10. LAN DISTANCE FOR WINDOWS AND TCPBEUI CONFIGURATION This section describes steps that you need to take to use the LAN Distance Remote product for MS Windows to run with the Network TeleSystems TCPBEUI that is included in the DOS LAN Services product. ATTENTION 1. Do not run Settings for the LAN Distance Remote for MS Windows product until after you have completed the following configuration steps. Settings will change the configuration files to add support for NetBEUI if it does not find TCPBEUI configured. 2. Do not invoke the Microsoft Setup program after you have configured for the TCPBEUI real mode driver. The Microsoft Setup program will change PROTOCOL.INI to remove the NDIS Extender. READ THE FOLLOWING BEFORE YOU BEGIN SETUP STEPS Before completing the following steps in this README, complete these prerequisites: o Any Windows applications that you are using should operate correctly in the LAN environment BEFORE you install the LAN Distance product. o The DOS LAN Services product for MS Windows should be installed. o The LAN Distance Remote product for MS Windows should be installed. 1. LAN Distance installation prompts you to restart your workstation to make configuration changes active. It's only necessary to restart your workstation ONCE--after you complete the steps that follow. 2. If you experience any of the following symptoms, you may need to increase the OS/2 TCPBEUI NETBIOSTIMEOUT value on the LAN Distance Connection Server. Use MPTS to configure (edit) the OS/2 TCPBEUI protocol NETBIOSTIMEOUT value. a. After you dial the LAN Distance Connection Server, the connection status never changes from "connecting" to "connected". After about a minute, this message may be displayed: (C) Copyright IBM Corp. 1994, 1995 38 WCL0338: A processing error occurred in the LAN Distance connection software. The call to 'your phonebook entry name' cannot be completed. The return code from Dial Services was 'a'. b. Or, after about a minute, your workstation hangs hard and you must power off and power on to restart your workstation. 3. If you experience any of the following symptoms, your OS/2 LAN Distance Connection Server may not have the LAN Distance logical adapter configured as adapter 0. On the OS/2 LAN Distance Connection Server, use MPTS to reorder the adapters so that the LAN Distance logical adapter is adapter 0. Then use TCP/IP configuration to activate the adapter 0 interface. a. After you dial the LAN Distance Connection Server, the connection status never changes from "connecting" to "connected". After about a minute, this message may be displayed: WCL0338: A processing error occurred in the LAN Distance connection software. The call to 'your phonebook entry name' cannot be completed. The return code from Dial Services was 'e'. b. If you experience any of the following symptoms, you may need to change the maxframe values in your PROTOCOL.INI file. o After you connect to the LAN Distance Server, you cannot connect to an alias, or o After you connect via a network name, you cannot copy or access files. Example sections in PROTOCOL.INI that may need to be changed: [SOCKDD_MOD] maxframe=2040 [COM1] maxframe=2040 4. In addition to the steps provided here, sample configuration files are provided as a reference. NOTE: The PROTOCOL.INI that is generated by these configuration steps is the result of merging the DLS PROTOCOL.INI into the LAN Distance PROTOCOL.INI. Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 39 SETUP STEPS 1. EDIT CONFIGURATION FILES: (**Required**) See the appropriate sample configuration files below. 2. LAN DISTANCE SETTINGS (**Optional**) Complete any additional configuration required to set up the MS Windows LAN Distance Remote product. For assistance configuring the LAN Distance product, see the LAN Distance publications. 3. UPDATE SHUTTLE FILES (**Required**) Update the *.RWS files (config.rws, autoexec.rws, protocol.rws, and system.rws) with the new configuration files. 4. OTHER POSSIBLE PROTOCOL.INI CHANGES(**Optional**) If you receive a Protocol Manager binding error message when you restart your workstation, then it's likely that sections of your PROTOCOL.INI file are not bound to the SOCKDD_MOD. Modify the binding statements (BINDINGS=) in the Windows PROTOCOL.INI which do not list SOCKDD_MOD as the first parameter. If a bindings statement has only one parameter, the parameter is replaced with SOCKDD_MOD. 5. RESTART YOUR WORKSTATION (**Required**) After completing Steps 1 - 3 and making any other necessary changes described Step 4, restart your workstation. 6. REVIEW SAMPLE CONFIGURATION FILES (**Optional**) In the following configuration files, statements that were changed or added are marked with an ---> at the beginning of the statement. Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 40 SAMPLE CONFIGURATION FILES FOR TCPBEUI REAL MODE CONFIG.SYS DEVICE=C:\DOS\SETVER.EXE DEVICE=C:\DOS\HIMEM.SYS device=c:\windows\emm386.exe noems DOS=HIGH,umb FILES=30 STACKS=9,256 LASTDRIVE=Z REM The following are LAN Distance configuration statements DEVICE=c:\WAL\protman.dos /I:c:\WAL DEVICEHIGH=c:\WAL\taplf.dos --> rem DEVICEHIGH=c:\WAL\dxmj0mod.sys DEVICEHIGH=c:\WAL\dosvmac.sys DEVICEHIGH=c:\WAL\winamac.sys DEVICEHIGH=c:\WAL\pcmdd.sys REM The following are NTS TCPBEUI configuration statements DEVICE=c:\net\ntsts.dos --> DEVICE=c:\net\ntsnx.dos DEVICE=c:\net\dlshelp.sys AUTOEXEC.BAT c:\WAL\DOSBIND PROMPT $p$g PATH c:\;c:\WAL\;C:\NET;C:\NWDBPATH;C:\WINDOWS;C:\DOS; SET TEMP=C:\DOS doskey PROTOCOL.INI Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 41 [network.setup] version=0x3100 --> netcard=SOCKDD_MOD,1,SOCKDD_MOD --> transport=nts$ntsts,NTS$NTSTS --> lana0=SOCKDD_MOD,1,nts$ntsts [PROTOCOL_MANAGER] DriverName=PROTMAN$ [NTS$NTSTS] NetSubNetMask=[255.255.240.0] IPAddr=[129.35.66.6] DriverName=ntsts$ VCs=16 VCReceiveLarge=6 VCSends=6 RcvWindow=2920 --> BINDINGS=NTS_NX LANABASE=0 Token-Ring --> [NTS_NX] --> DriverName=NTSNX$ --> Bindings=SOCKDD_MOD --> [SOCKDD_MOD] --> DriverName=VLANMAC$ --> LanType="TokenRing" --> Mode="FLOWS" --> NetAddress=T4000763F6106 --> MaxFrame=1080 --> [COM1] --> MaxFrame=1080 --> MACTYPE="802.5" --> DRIVERNAME="COM1MAC$" --> PCMSUPPORT="YES" --> CONN_TYPE="SWITCHED" --> PORTNAME="COM1" --> TX_FIFO_SIZE=7 NETWORK.INI Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 42 [network] computername=501 lanroot=C:\NET --> autologon=no --> autostart= guiconfig=1,0,1 username=TB501 domain=TB176DOM --> lslogon=no reconnect=yes passwordcaching=yes timesync=no [Password Lists] TB501=C:\NET\TB501.PWL USERID=C:\NET\USERID.PWL [Domain List] TB176DOM= SAMPLE CONFIGURATION FILES FOR TCPBEUI VIRTUAL MODE CONFIG.SYS FILES=30 BUFFERS=10 DOS=HIGH DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\SETVER.EXE DEVICE=C:\WFW\SMARTDRV.EXE /DOUBLE_BUFFER STACKS=9,256 LASTDRIVE=Z --> rem DEVICE=C:\WFW\IFSHLP.SYS --> rem DEVICE=C:\NET\ibmtok.dos REM The following are LAN Distance configuration statements --> DEVICE=C:\WAL\PROTMAN.DOS /i:C:\WFW DEVICEHIGH=c:\wal\taplf.dos --> DEVICEHIGH=c:\wal\dosvmac.sys --> DEVICEHIGH=c:\wal\winamac.sys DEVICEHIGH=c:\WAL\pcmdd.sys REM The following are NTS TCPBEUI configuration statements DEVICE=C:\NET\VTCPPRO.EXE DEVICE=C:\NET\DLSHELP.SYS Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 43 AUTOEXEC.BAT C:\WFW\SMARTDRV.EXE /L /X @ECHO OFF SET PATH=C:\NET;C:\NWDBPATH;C:\WFW;C:\NWDBPATH;C:\DOS;%PATH%; SET TEMP=C:\DOS SET WIN$=D:\OS2\MDOS\WINOS2 C:\DOS\MOUSE.COM C:\DOS\DOSKEY.COM SHARE --> c:\wal\dosbind PROTOCOL.INI [network.setup] version=0x3100 --> netcard=sockdd_mod,1,SOCKDD_MOD --> transport=nts$tcppro,NTS$TCPPRO --> lana0=sockdd_mod,1,nts$tcppro [NTS$TCPPRO] NetSubNetMask=[255.255.240.0] IPAddr=[129.35.66.7] DriverName=ntsth$ VCs=16 VCReceiveLarge=6 VCSends=6 RcvWindow=2920 --> BINDINGS=SOCKDD_MOD LANABASE=0 [protman] DriverName=PROTMAN$ PRIORITY=nts$tcppro --> [SOCKDD_MOD] --> DriverName=VLANMAC$ --> Mode="FLOWS" --> MaxFrame=1080 --> LANTYPE="TokenRing" --> NetAddress=T4000763f6107 --> [COM1] --> MaxFrame=1080 --> MACTYPE="802.5" --> DRIVERNAME="COM1MAC$" --> PCMSUPPORT="YES" --> CONN_TYPE="SWITCHED" --> PORTNAME="COM1" --> TX_FIFO_SIZE=7 --> PCMCIA="No" Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 44 SYSTEM.INI [boot] shell=progman.exe network.drv=dlsnet.drv mouse.drv=mouse.drv language.dll= sound.drv=mmsound.drv comm.drv=comm.drv keyboard.drv=keyboard.drv system.drv=system.drv 386grabber=vga.3gr oemfonts.fon=vgaoem.fon fixedfon.fon=vgafix.fon fonts.fon=vgasys.fon display.drv=vga.drv drivers=mmsystem.dll [keyboard] subtype= type=4 keyboard.dll= oemansi.bin= [boot.description] keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards mouse.drv=Microsoft, or IBM PS/2 language.dll=English (American) system.drv=MS-DOS System codepage=437 woafont.fon=English (437) aspect=100,96,96 display.drv=VGA network.drv=IBM DOS LAN Services secondnet.drv=No Additional Network Installed Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 45 [386Enh] network=*vnetbios,,vnetsup.386,vredir.386 device=C:\NET\vntstid.exe device=*vpd mouse=*vmd ebios=*ebios woafont=dosapp.fon display=*vddvga EGA80WOA.FON=EGA80WOA.FON EGA40WOA.FON=EGA40WOA.FON CGA80WOA.FON=CGA80WOA.FON CGA40WOA.FON=CGA40WOA.FON keyboard=*vkd netheapsize=24 --> DEVICE=c:\wal\ldvcd.386 device=*vpicd device=*vtd device=*reboot device=*vdmad device=*vsd device=*v86mmgr device=*pageswap device=*dosmgr device=*vmpoll device=*wshell device=*PAGEFILE device=*BLOCKDEV device=*vfd device=*parity device=*biosxlat device=*vmcpd device=*combuff device=*cdpscsi device=vtdapi.386 device=vpmtd.386 device=vcomm.386 device=serial.386 device=lpt.386 device=ifsmgr.386 device=vcache.386 device=vshare.386 Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 46 local=CON FileSysChange=off COM3Irq=4 COM3Base=03E8 COM4Irq=3 COM4Base=02E8 PagingFile=C:\WFW\WIN386.SWP MaxPagingFileSize=36864 netmisc=ndis.386,ndis2sup.386 netcard=ibmtok.386 transport=netbeui.386 InDOSPolling=FALSE --> TimerCriticalSection=8 --> COMBoostTime=10 --> COM1FIFO=ON --> COM1Buffer=300 [NonWindowsApp] localtsrs=dosedit,ced [vcache] minfilecache=512 [mci] WaveAudio=mciwave.drv Sequencer=mciseq.drv CDAudio=mcicda.drv [drivers] timer=timer.drv midimapper=midimap.drv [DDEShares] CHAT$=winchat,chat,,31,,0,,0,0,0 SCHAT$=winchat,chat,,31,,0,,0,0,0 CLPBK$=clipsrv,system,,31,,0,,0,0,0 HEARTS$=mshearts,hearts,,15,,0,,0,0,0 [Network] domain=yyyyyyyy lanroot=C:\NET winnet=wfwnet/00025100 multinet=nonet FileSharing=Yes PrintSharing=Yes LogonDisconnected=yes EnableSharing=Yes UserName=xxxxxxxx Workgroup=WORKGROUP computername=TB038 Comment=XXXXX YYYYYYYY --> MaintainServerList=NO --> SlowLanas=0 Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 47 [network drivers] --> netcard= transport=ndishlp.sys,*netbeui devdir=C:\WFW --> LoadRMDrivers=No [Password Lists] *Shares=C:\WFW\Share000.PWL NETWORK.INI [network] computername=TB038 lanroot=C:\NET --> autologon=no --> autostart= username=xxxxxxxx domain=yyyyyyyy --> lslogon=no reconnect=yes passwordcaching=yes timesync=no Chapter 10. LAN Distance for Windows and TCPBEUI Configuration 48 CHAPTER 11. SYSTEM MANAGEMENT SERVICES The following information applies to installation of the SystemView system management services: NOTE: After installing SystemView on either a server or OS/2 client workstation, open SYSTEMVIEW on the Desktop, then open INFORMATION. Open and read the README document for more information about SystemView limitations in this release. SYSTEMVIEW SERVER INSTALLATION When installing System Management Services and selecting MORE, leave all the components selected. SYSTEMVIEW CLIENT FOR WINDOWS INSTALLATION To start the SystemView client installation on a Windows workstation. Use the following procedure to start the installation. TO INSTALL A SYSTEMVIEW WINDOWS CLIENT: 1. Insert the OS/2 Warp Server CD-ROM. 2. Make sure that Windows is running on your workstation. 3. Select RUN from the pull-down menu of the Windows Program Manager or File Manager. 4. In the Command Line box, type the following command and select OK: d:\CID\CLIENT\SYSVIEW2\CLIENT_W\INSTALL where d is your CD-ROM drive. The installation program starts. The remainder of the client installation proceeds as described in the Client Installation section of the Using IBM SystemView for OS/2 online book. 5. To open the online book before starting the installation, type the following command at an OS/2 command prompt and press Enter: VIEW d:\CID\SERVER\BOOKS\IKOO0MST.INF where d is the workstation's CD-ROM drive. (C) Copyright IBM Corp. 1994, 1995 49 CHAPTER 12. VIEWING ONLINE DOCUMENTATION Online documentation is provided on the OS/2 Warp Server CD-ROM. If you select to install online documentation when you install OS/2 Warp Server, it is place in the Information Folder on the Desktop. If you have not installed OS/2 Warp Server, you can view a document from the OS/2 command prompt, type the following command and press Enter: VIEW d:\CID\SERVER\BOOKS\name where d is the CD-ROM drive and name is the book's file name. The following table shows file names for the online books included on the OS/2 Warp Server CD-ROM: +---------------------------------------------------------------------------+ | Table 1 (Page 1 of 2). OS/2 Warp Server Online Documentation | +-------------------------------------+-------------------------------------+ | ABBREVIATED TITLE | FILE NAME | +-------------------------------------+-------------------------------------+ | | | FILE AND PRINT SHARING | +-------------------------------------+-------------------------------------+ | Easy Start! | A3A83M02.INF | +-------------------------------------+-------------------------------------+ | Up and Running! | A3A41M02.INF | +-------------------------------------+-------------------------------------+ | Network Administrator Reference | A3A61M02.INF | | Volume 1: Planning and | | | Installation | | +-------------------------------------+-------------------------------------+ | Network Administrator Reference | A3A4GM02.INF | | Volume 2: Performance Tuning | | +-------------------------------------+-------------------------------------+ | Network Administrator Reference | A3A62M02.INF | | Volume 3: Administrator Tasks | | +-------------------------------------+-------------------------------------+ | OS/2 LAN Requester User's Guide | A3A4IM02.INF | +-------------------------------------+-------------------------------------+ | DOS LAN Services and Windows User's | A3A4HM02.INF | | Guide | | +-------------------------------------+-------------------------------------+ | Problem Determination Guide | A3A4FM02.INF | +-------------------------------------+-------------------------------------+ | Commands and Utilities | A3A53M02.INF | +-------------------------------------+-------------------------------------+ | Programmer's Guide and Reference | A3A4AM02.INF | +-------------------------------------+-------------------------------------+ (C) Copyright IBM Corp. 1994, 1995 50 +---------------------------------------------------------------------------+ | Table 1 (Page 2 of 2). OS/2 Warp Server Online Documentation | +-------------------------------------+-------------------------------------+ | ABBREVIATED TITLE | FILE NAME | +-------------------------------------+-------------------------------------+ | LAN CID Utility Guide | A3S12M02.INF | +-------------------------------------+-------------------------------------+ | | | ADAPTERS AND PROTOCOL SERVICES | +-------------------------------------+-------------------------------------+ | MPTS: Configuration Guide | A3V10M02.INF | +-------------------------------------+-------------------------------------+ | | | ADVANCED PRINT SERVICES | +-------------------------------------+-------------------------------------+ | Print Services Facility/2 Online | PSF2MST.INF | | Reference | | +-------------------------------------+-------------------------------------+ | PSF/2 What's New | NWMST.INF | +-------------------------------------+-------------------------------------+ | | | SYSTEM MANAGEMENT SERVICES | +-------------------------------------+-------------------------------------+ | Using IBM SystemView for OS/2 | IKOO0MST.INF | +-------------------------------------+-------------------------------------+ | IBM SystemView License Use | I4DU2MST.INF | | Management Administrator and User | | | Guide | | +-------------------------------------+-------------------------------------+ | | | SOFTWARE BACKUP AND RECOVERY SERVICES | +-------------------------------------+-------------------------------------+ | Personally Safe'n'Sound v3.01 | PSNS.INF | +-------------------------------------+-------------------------------------+ | | | REMOTE ACCESS | +-------------------------------------+-------------------------------------+ | LAN Distance Advanced Guide | A3T12MST.INF | +-------------------------------------+-------------------------------------+ | LAN Distance Remote Guide | A3T11MST.INF | +-------------------------------------+-------------------------------------+ Chapter 12. Viewing Online Documentation 51 APPENDIX A. NOTICES References in this publication 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. 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. 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. (C) Copyright IBM Corp. 1994, 1995 52 TRADEMARKS The following terms are trademarks of the IBM Corporation in the United States or other countries or both: +-------------------------------------+-------------------------------------+ | BookMaster | IBM | +-------------------------------------+-------------------------------------+ | IBM Peer for OS/2 | LAN Distance | +-------------------------------------+-------------------------------------+ | LAN Server | OS/2 | +-------------------------------------+-------------------------------------+ | Print Services Facility | PS/2 | +-------------------------------------+-------------------------------------+ | PSF | SystemView | +-------------------------------------+-------------------------------------+ | ThinkPad | Workplace Shell | +-------------------------------------+-------------------------------------+ The following terms are trademarks of other companies: LaunchPad is a trademark of Berkeley Systems, Inc. Windows is a trademark of Microsoft Corporation. Appendix A. Notices 53 +--- NOTE -----------------------------------------------------------+ | | | Before using this information and the product it supports, be sure | | to read the general information under Appendix A, "Notices" on | | page 52. | | | +--------------------------------------------------------------------+ FIRST EDITION 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. It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Requests for copies of this publication and for technical information about IBM products should be made to your IBM Authorized Dealer or your IBM Marketing Representative. (C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1994, 1995. 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.