home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
ld8175b1.dsk
/
IP08175.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-12-13
|
65KB
|
1,811 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
IBM OS/2 LAN Distance 1.1 and 1.11 ServicePak IP08175
IBM PTF IP08175
This ServicePak applies to:
IBM LAN Distance Connection Server for OS/2, 8 port - Version 1.1 and 1.11
For use with OS/2 2.0 or higher.
IBM LAN Distance Connection Server for OS/2 - Version 1.1 and 1.11
For use with OS/2 2.0 or higher.
IBM LAN Distance Remote for OS/2 - Version 1.1 and 1.11
For use with OS/2 2.0 or higher.
IBM LAN Distance Remote for Windows - Version 1.1 and 1.11
For use with MicroSoft Windows 3.1 or higher.
Installation instructions for IBM LAN Distance Remote for Windows fixes and
enhancements can be found in the 8175WIN.RME file located on the first diskette
of this ServicePak. Installation instructions for the OS/2 versions of LAN
Distance are in the next section of this document.
Some of the new features/enhancements include LAN Distance related changes in
the LAN Adapter and Protocol Support directory tree (IBMCOM.)
Warning: - Please review the entire Installation section before proceeding.
Service to workstations with LAN Servers which use "Advanced Features" can be
complex.
Good Insurance!
Have appropriate Bootable Standalone Service Diskettes.
ΓòÉΓòÉΓòÉ 1.1. Affected SYSLEVEL Files ΓòÉΓòÉΓòÉ
SYSLEVEL.LDA IBM OS/2 LAN Distance Connection Server (Advanced)
SYSLEVEL.LDE IBM OS/2 LAN Distance Connection Server, 8 port (Entry)
SYSLEVEL.LDR IBM OS/2 LAN Distance Remote
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
The following are trademarks of IBM Corporation:
o IBM
o LAN Distance
o LAN Support Program
o LANStreamer
o Operating System/2
o OS/2
o PC LAN Program
o Presentation Manager
o Win-OS/2
The following are trademarks of other Corporations:
o AttachMate (Attachmate Corporation)
o Chameleon (NetManage)
o LAN Workplace for DOS (Novell, Inc.)
o Microcom (Microcom, Inc.)
o Microsoft (Microsoft Corporation)
o MSNET (Microsoft Corporation)
o NetWare (Novell, Inc.)
o Pentium (Intel Corporation)
o Ungermann-Bass (Ungermann-Bass, Inc.)
o VINES (Banyan Systems, Inc.)
o Windows (Microsoft Corporation)
ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ
This ServicePak uses Corrective Service Facility (CSF) Version 2-B (provided on
the tool diskette of this ServicePak) for installation.
Complete instructions for the use of the updated SERVICE and FSERVICE commands
are provided with the CSF Version 2-B README.INF file on the ServicePak Tool
Diskette. Please read the CSF instructions for information on the use of CSF
Version 2-B backup and restore capabilities.
Note: - Archiving is not enabled for this ServicePak.
Installing the ServicePak is essentially a three phase process:
Phase 1 - Quiesce the Target System
Stop all running applications so that LAN Server/Requester is not
in use. (This includes doing a 'net stop server').
Phase 2 - Install the ServicePak
Use one of the following methods to replace system files with those
provided on this ServicePak:
Selective Install
Redirected (CID) Install
Phase 3 - Return the Serviced System to Normal Operation
Perform a normal system boot.
ΓòÉΓòÉΓòÉ 2.1. Selective Install ΓòÉΓòÉΓòÉ
This method will apply fixes to selected subsystems, partitions, and
directories: The Corrective Service Facility will handle Locked Files
automatically so boot diskettes are not required before applying service.
1. At an OS/2 command prompt, perform a 'net stop server'.
2. Insert ServicePak Tool diskette in the A drive.
3. At an OS/2 command prompt, type "A:ARCHOFF" to execute this pre-install
program (if you haven't already done so).
4. At an OS/2 command prompt, type "A:SERVICE" and press Enter.
5. Insert ServicePak diskette 1 when prompted.
6. Follow the prompts to the CSF SERVICEABLE PRODUCTS panel. Review the
serviceable products selected on the panel and deselect any products that
you do not want to service at this time. Then choose the SERVICE push
button.
7. Enter (optional) backup path then choose the OK push button.
8. If the APPLICATION IN USE locked files panel is presented, choose CONTINUE.
9. Follow prompts to complete the process.
10. Remove the diskette from drive A:, then perform the system Shutdown
procedure.
11. Reboot the system normally.
If the system to be serviced is a multiboot system with LAN Advanced Server
using IBM386FS on a drive other than the "C" drive, use the Special Situation
Install method to complete the installation on each bootdrive.
When problems such as insufficient disk space are encountered when performing
the Selective Install, use the Special Situation Install method to perform
service.
ΓòÉΓòÉΓòÉ 2.2. Redirected Installation (CID) Method ΓòÉΓòÉΓòÉ
This method is useful for those who are using the CID (Configuration,
Installation, and Distribution) Services as provided by IBM MPTS. The Selective
Install method is recommended for Servers exploiting 386 HPFS function, Fault
Tolerance, and/or Local Security.
CAUTION:
Before using FSERVICE to apply corrective service, review the sample response
file (RESPONSE.FIL) located on the Service Tool diskette. Edit the
RESPONSE.FIL, if necessary, to ensure the service logfile is created in the
correct location on the target workstation.
:LOGFILE d:\os2\install\SERVICE.LOG
where d:\os2\install is the drive and location for the service logfile.
While setting up a CID server is beyond the scope of this document, we have
provided a sample LAN CID Utility REXX Command file segment (IP_8175.CID) that
may prove useful in setting up a CID server for this ServicePak.
The sample IP_8175.CID assumes the following:
o The ServicePak Tool diskette files are placed on the code server using "XCOPY
A:\*.* /S" (or equivalent) in 'x:\img\csd\landist\ip_8175' where 'x:' is the
drive seen by the client.
o The ServicePak files are placed on the code server using "XCOPY A:\*.* /S"
(or equivalent) in 'x:\img\csd\landist\ip_8175.'
o The sample RESPONSE.FIL (or equivalent) is placed on the code server in
x:\rsp\csd\landist\ip_8175.
o The following CID server directory structure contains the contents of the
ServicePak and the tool diskette.
img\csd\landist\ip_8175 * Root directory of ServicePak diskette 1
img\csd\landist\ip_8175 * ServicePak Tool diskette files
img\csd\landist\ip_8175\FIX * No files
img\csd\landist\ip_8175\FIX\LDA * 32 Port Server Fixes
img\csd\landist\ip_8175\FIX\LDE * 8 Port Server Fixes
img\csd\landist\ip_8175\FIX\LDR * Remote Workstation Fixes
o A log directory exists at 'x:\log\csd\landist\ip_8175' for the log files.
ΓòÉΓòÉΓòÉ 2.3. Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ
Sometimes it becomes necessary to boot from diskette in order to perform
certain operations on fixed-disk, like installing this ServicePak or running
CHKDSK /f.
All necessary files must be contained on diskette. Files from the fixed-disk
should not be referenced in A:\CONFIG.SYS or A:STARTUP.CMD. Otherwise Locked
Files can still exist on the fixed-disk.
Should the need arise to boot from diskette for any reason, you may:
o Use the Install diskette and Diskette 1 of OS/2 2.x or OS/2 3.x. Escape to A:
o Create custom Bootable Standalone Service Diskettes from your licensed
materials. The makeup of these is dependent on the system to be serviced.
Instruction is available for:
Requesters and Entry Version Servers.
Advanced Version Servers.
CAUTION:
LAN Servers that utilize the Advanced features such as Local Security and Fault
Tolerance must use custom Bootable Standalone Service Diskettes. Regular HPFS
boot diskettes, such as the OS/2 Installation diskettes, CANNOT mirror changes
to Fault Tolerance partitions or access files/directories which are controlled
by local security.
ΓòÉΓòÉΓòÉ 2.3.1. Making OS/2 Bootable Diskettes ΓòÉΓòÉΓòÉ
Instructions for creating OS/2 bootable diskettes for Requesters and Entry
Version Servers are dependent on the OS/2 version.
o For OS/2 2.x versions:
1. Make a copy of the OS/2 2.x Installation Diskette and Diskette 1. Call
them SA1 and SA2 respectively.
2. Delete SYSINST2.EXE from Diskette SA2.
3. Delete BUNDLE from Diskette SA2 (this will be on OS/2 versions 2.1 or
greater).
4. Modify CONFIG.SYS on SA2 as follows:
buffers=50
memman=noswap
protshell=a:\cmd.exe
protectonly=yes
libpath=a:\;
ifs=hpfs.ifs /c:64
set path=a:\;
set dpath=a:\;
5. Copy UHPFS.DLL from OS/2 Diskette 2 or C:\OS2\DLL to SA2.
o For OS/2 3.x versions:
Use the Install diskette and Diskette 1 of OS/2 3.x. Escape to A:
ΓòÉΓòÉΓòÉ 2.3.2. Making Advanced Server Bootable Diskettes ΓòÉΓòÉΓòÉ
MAKEDISK is an Advanced Server utility designed to make the necessary Bootable
Standalone Service Diskettes used in periodic maintenance of 386 HPFS systems.
1. Make a copy of the OS/2 2.x or 3.x Installation Diskette and Diskette 1.
Call them SA1 and SA2 respectively.
2. Delete SYSINST2.EXE from Diskette SA2.
3. Delete BUNDLE from Diskette SA2 (this will be on OS/2 versions 2.1 or
greater).
4. With Boot Diskette SA2 in drive a: or b: run MAKEDISK from an OS/2 prompt.
Note: Syntax is MAKEDISK /BOOTDRIVE:d where d is the OS/2 boot drive.
For additional Information see the Network Administrators Reference:
Creating a 386 HPFS Boot Diskette, or LAN Server Utilities.
5. If using Fault Tolerance, add the Fault Tolerance files to the Bootable
Diskette SA2.
6. Ensure the country code, codepage, and the keyboard information in the
config.sys file on the boot diskette matches the corresponding information
on the target workstation's config.sys. Verify that the 386 HPFS Bootable
Standalone Service Diskettes work properly and that, after rebooting, Local
Security and Fault Tolerance are working as expected.
ΓòÉΓòÉΓòÉ 2.3.3. Adding Fault Tolerance to 386 HPFS Bootable Standalone Service Diskettes ΓòÉΓòÉΓòÉ
386 HPFS Bootable Standalone Service diskettes require additional customizing
in order to properly update files on partitions which are mirrored.
The following steps may have to be done for each LAN Server with Fault
Tolerance since the configuration information transferred in step 3 can be
unique for each such system.
1. Copy the following four Fault Tolerance files from the first diskette of
the LAN Server 4.0 ServicePak to your Bootable Standalone Service Diskette
SA2.
1) DISKFT.SYS 2) FTD.MSG 3) FTATTRIB.EXE 4) FTCOPY.CMD
2. Add the following line to the CONFIG.SYS on the Bootable Standalone Service
Diskette SA2.
DEVICE=DISKFT.SYS
3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS
Bootable Standalone Service Diskette SA2 in drive A. Type "FTCOPY" to copy
the customized Fault Tolerance configuration information to the 386 HPFS
Bootable Standalone Service Diskette SA2.
Warning: Ensure the country code, codepage, and the keyboard information in
the config.sys file on the boot diskette matches the corresponding information
on the target workstation's config.sys. Test your 386 HPFS Bootable Standalone
Service Diskette before you make any alterations to your system. This Diskette
is the Master Key should your system ever fail to boot from its hard drive.
ΓòÉΓòÉΓòÉ 2.4. Special Situation Install ΓòÉΓòÉΓòÉ
This method will apply all fixes to all partitions and directories:
FSERVICE is used for CID installation of this ServicePak, for multiboot systems
with IBM386FS on a drive other than the 'C' drive, or when problems, such as
insufficient memory for the locked file device driver or corrupted disk drives,
are encountered using the Selective Install method. It does require booting
from diskette to insure that there are no Locked Files during the install
phase.
Warning: - Ensure that all drives to be updated are clean by performing a
CHKDSK /F on each drive before FSERVICE is invoked. There will be no
opportunity to clean up the drives after FSERVICE is invoked.
1. Review the FSERVICE Response File (RESPONSE.FIL on the ServicePak tool
diskette) and modify as needed to reflect the configuration of the system
to be serviced. Ensure the service logfile is created in the correct
location on the target workstation.
:LOGFILE d:\os2\install\SERVICE.LOG
where d:\os2\install is the drive and location for the service logfile.
2. Boot from the Bootable Standalone Service Diskettes.
3. Establish A: as the Current Directory.
4. Replace the Boot Diskette with the ServicePak Tool Diskette.
5. From the A: prompt, type "ARCHOFF" and press enter to execute a pre-install
program (if you haven't already done so).
6. From the A: prompt, type "FSERVICE" and press Enter. Click here for
additional steps needed for multi-boot systems.
7. At the panel titled "Installing this Service Pak" press Enter (Option 1).
8. Follow the prompts provided by the Corrective Service Facility.
9. Reboot the system normally.
ΓòÉΓòÉΓòÉ 2.4.1. Updating IBM386FS Directory on a Multiboot System ΓòÉΓòÉΓòÉ
A new parameter has been added to the FSERVICE command to enable servicing the
IBM386FS directory when it resides on a bootdrive other than C:. Specify the
bootdrive containing the IBM386FS directory to be serviced as the /b parameter
on the FSERVICE command:
FSERVICE /b:d
(where d is the drive letter assigned to bootdrive)
Note: There is NO colon after the bootdrive 'd'.
Two methods are available for servicing the IBM386FS directories on multiple
bootable drives:
1. Run FSERVICE iteratively. That is, run FSERVICE /b: for each bootable drive
containing an IBM386FS directory.
2. Edit the RESPONSE.FIL (on the Tool diskette of this ServicePak) to add the
following parameter set after the :SYSLEVEL label:
:DIRLIST
d1:\IBM386FS where d1 = a bootable drive requiring IBM386FS service,
d2:\IBM386FS and d2 = another bootable drive requiring IBM386FS service.
:ENDDIRLIST
ΓòÉΓòÉΓòÉ <hidden> Locked Files ΓòÉΓòÉΓòÉ
Sometimes it is essential that programs own (become the master of) system
resources such as Memory Blocks, Communication Ports, and Files. When a program
stakes claim to a file, that file is said to be Locked; no other program is
allowed to alter (replace or write to) it until the owning program explicitly
removes the lock.
.DLL Files can become Locked by residing in a directory that is included in
the LIBPATH string of CONFIG.SYS.
For example, NETAPI.DLL can be locked when \MUGLIB\DLL exists in the LIBPATH of
CONFIG.SYS.
ΓòÉΓòÉΓòÉ <hidden> Escape to A: from OS/2 Install Diskettes ΓòÉΓòÉΓòÉ
To obtain the A: prompt when using the OS/2 Product installation diskettes as
Bootable Standalone Service Diskettes:
o Boot the system with Install Diskette in drive A.
o At the IBM Logo Screen - Insert Diskette 1, press Enter.
o At the Welcome Screen - Press Esc to Exit. (F3 for OS/2 3.x)
The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run
from here.
ΓòÉΓòÉΓòÉ <hidden> Creating a 386 HPFS Boot Diskette Refer to ΓòÉΓòÉΓòÉ
Appendix H in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume 1: Planning and
Installation
Version 4.0
ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ
Refer to Appendix B, Miscellaneous Utilities MAKEDISK in:
Operating System/2 Local Area Network Server
Network Administrator Reference Volume 3: Network Administrator
Tasks
Version 4.0
ΓòÉΓòÉΓòÉ 3. Known Problems and Restrictions ΓòÉΓòÉΓòÉ
This section discusses restrictions known about the LAN Distance product at the
time this ServicePak was shipped.
ΓòÉΓòÉΓòÉ 3.1. MPTS ΓòÉΓòÉΓòÉ
To use MPTS with the LAN Distance product, you must have MPTS Version 2.60.2 or
later.
NOTE: LAN Server 4.0 is shipped with MPTS Version 2.60.2.
NetBIOS 3.0 interface (provided with MPTS) supports only four adapters. If four
NetBIOS logical adapters are configured before LAN Distance installation or
configuration, LAN Distance will assign VLAN MAC (PDFH.NIF) the fifth NetBIOS
logical adapter number. Since this fifth adapter is not supported by MPTS, you
must delete one of the previous NetBIOS logical adapter configurations, then
configure VLAN MAC through MPTS configuration.
The VLAN MAC must also be configured through MPTS configuration if NetBIOS is
not configured before LAN Distance installation or during LAN Distance
configuration.
ΓòÉΓòÉΓòÉ 3.2. LAN Server 4.0 with LAN Distance Advanced Server ΓòÉΓòÉΓòÉ
When running IBM LAN Server/Requester 4.0 with IBM LAN Distance Advanced Server
you may experience problems with insufficient NETBIOS resources. Two possible
symptoms indicate this problem:
o When starting LAN Distance, error message WCL554 appears stating that the LAN
Distance product requires more NETBIOS resources than are available.
o The NETBIOS protocol does not load at system startup.
If either of these symptoms occur, the following steps are recommended:
NOTE: Restart your workstation after each step to see if the problem is
solved. If the problem remains, try the next step.
1. Remove any unnecessary NETBIOS applications.
2. Edit the \IBMLAN\IBMLAN.INI file.
In the [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.
o Edit the \WAL\WCLLOCAL.INI file with any ASCII editor.
o 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.
o Change COMMANDS = 90 to the new SESSIONS value times 3.
For example, if the new SESSIONS value is 16, then set COMMANDS to 48.
This reduces the number of NETBIOS resources that the LAN 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
ΓòÉΓòÉΓòÉ 3.3. Microcom Modem ΓòÉΓòÉΓòÉ
The following problems occasionally occur when using the Microcom modem with
the LAN Distance product:
o After having successfully connected with the Microcom modem, attempts to
reconnect with the modem or to connect with another modem have failed.
o The Microcom modem will not initially connect with certain modems.
The following are symptoms of the above problems:
o The modem appears "deaf" to dialing strings.
o The modem fails to go off hook.
o The modem DTR signal fails to turn on.
Using other PIF files, specifically MICROPRT.PIF, will alleviate the problems
in a few cases.
For assistance in using the Microcom modem, please contact your Microcom
dealer.
ΓòÉΓòÉΓòÉ 3.4. Deselecting Manual Bridge Filter ΓòÉΓòÉΓòÉ
If you have defined bridge filter on page 2 of the bridge tab in the settings
notebook on a Connection Server and want to disable the selected filter
criteria, press the space bar on the keyboard to deselect the active filter.
ΓòÉΓòÉΓòÉ 3.5. Communications Manager/2 V1.11 ΓòÉΓòÉΓòÉ
If you are installing or upgrading to Communications Manager/2 V1.11 please
note the following:
o To use the "SNA Phone Connections" feature of CM/2 V1.11 on the same machine
with "LAN Distance using PSTN", you must get a CM/2 fix through IBM Service
and Support by referencing APAR JR08194.
o To use "LAN Distance using ISDN", follow these steps:
1. Backup NETWORK.INI by renaming \CMLIB\NETWORK.INI to \CMLIB\NETWORK.BAK.
This prevents you from using the "SNA Phone Connections" feature of CM/2
V1.11.
2. Reinstall the ISDN Coprocessor Support Program Version V1.2 software.
3. Reconfigure LAN Distance using ISDN.
ΓòÉΓòÉΓòÉ 3.6. ES 1.0 Communications Manager ΓòÉΓòÉΓòÉ
If ES Communciations Manager is on a machine with LAN Distance, the following
messages may be received after installing LAN Distance and rebooting:
o MaxFrameSize is too small
o General Failure when program tried to bind BRIDGE$ to vector
This problem can be corrected by changing the IBMTOK_nif section of
PROTOCOL.INI to remove the XMITBUFSIZE= statement.
ΓòÉΓòÉΓòÉ 4. Things that Changed ΓòÉΓòÉΓòÉ
The following sections describe changes that have been made to the product's
executables, and messages/helps.
ΓòÉΓòÉΓòÉ 4.1. Publication Addendum ΓòÉΓòÉΓòÉ
This section discusses corrections/additions to the publications.
ΓòÉΓòÉΓòÉ 4.1.1. Redirected Install of LAN Distance Remote Workstations ΓòÉΓòÉΓòÉ
The LAN Distance Advanced Guide, Installing the Product (Chapter 4) section
"Steps to Install from a Redirected Drive Using a Response File" states for LAN
Distance Remotes, after you restart the workstation, the workstation is
automatically set up to operate as a stand-alone LAN Distance Remote. This is
incorrect.
When installing a LAN Distance Remote workstation from a redirected drive using
a response file, after restarting, the workstation will continue to be
configured as a LAN workstation. To use the workstation as a stand-alone LAN
Distance Remote workstation, use the shuttle feature to switch from a LAN
workstation to a Remote workstation configuration.
ΓòÉΓòÉΓòÉ 4.1.2. IBM7855.EXE Tool ΓòÉΓòÉΓòÉ
The IBM7855.EXE tool used to externally configure the IBM 7855 Modem is
available from these sources:
o CompuServ users can access the PSPAPROD forum and access this file in the LAN
Distance product's library section.
o Users with access to IBMLink through OS2BBS can access this file in the
REMOTE section of the OS/2 Software Library (3).
ΓòÉΓòÉΓòÉ 4.1.3. Configuring a LAN Distance Remote Workstation ΓòÉΓòÉΓòÉ
When configuring a LAN Distance Remote Workstation through the Settings
notebook, the workstation must be shuttled to a Remote Workstation, not a LAN
workstation.
ΓòÉΓòÉΓòÉ 4.2. Fixed APARs ΓòÉΓòÉΓòÉ
The following APARs were fixed in this ServicePak for LAN Distance Advanced
Connection Server.
o APAR= IC07742 LAN DISTANCE SECURITY USER EXIT ENABLEMENT (Fixed in ip07050)
LAN Distance 1.1 will support any security user exit package developed in
conformance with the LAN Distance Generalized Security User Exit API. A LAN
Distance Security User Exit development toolkit for OS/2 and Windows will be
provided. The toolkit contains:
- A specification for the LAN Distance Generalized Security User Exit API.
- A description of how to install or register a LAN Distance security user
exit on LAN Distance workstations.
- Sample source code to develop your own LAN Distance security user exit
package. A LAN Distance security user exit package consists of a client
user exit module and a server user exit module. These modules work together
to implement a customer defined user authentication protocol that can
restrict access to the LAN and its resources.
o APAR= IC07431 WCLNET.INI FILE INCORRECT FOR CREATED MODEM TYPES (Fixed in
ip07050)
Customer tried to define one modem type per modem. By starting a single modem
instead of all modems of the same type, connected users would not be
affected. The following steps recreate the problem:
1. Create a port and assign a modem. Specify you want to create a new type.
Change the title to be unique.
2. Close settings and stop LAN Distance. Start the system again.
3. Create another port. Go to the modem panel. Notice COM1 is listed in the
Assignments for modem types box.
4. Assign a modem to COM2 using the same modem type as a model.
5. Select the Create new modem type box and change the type so that it is
unique.
6. Close the windows and return to the Assignments for modem types list.
Only COM2 is listed. COM1 is deleted and the WCLNET.INI file is
incorrect. Note, this does not occur without the reboot in the middle.
The WCLNET.INI file is correct if you define COM1, COM2, COM3, assign each
COM port a modem in the Create a new definition box, and change the title.
The broken WCLNET.INI file follows:
DONOTREMOVE
KEYWORD = VALUE
REMOTELAN01
DLL = WCLVPCM
ENTRY = StartVPCM
AUTOSTART = YES
PIF = USRSPO01.PIF
TITLE = USRobotics Sportster 14400 Modem 02
PCMNAME = USRSPO01
USRSPO01
DialogType = "ATCMD.DDF"
PortName = "COM2"
PermConnection = "NO"
PhoneNumber = "Unspecified"
Synchronicity = "Asynchronous"
ModemClass = "V.32bis"
AutoBaudDetect = "Off"
SerialPortSpeed = 38400
FlowControl = "RTS/CTS"
Initialization1 = "ATB0E1F1M3Q0V1X4&A3&B1&C1&D2\CR"
Initialization2 = "AT&H1&I0&K1&M4&N0&R2&S1S0=2\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"
REMOTELAN02
DLL = WCLVPCM
ENTRY = StartVPCM
AUTOSTART = YES
PIF = USRSPO01.PIF
TITLE = USRobotics Sportster 14400 Modem 02
PCMNAME = USRSPO01
o APAR= IC08134 THE LAN DISTANCE WINDOW WILL NOT DISPLAY ALL THE CONNECTION
SERVERS ON THE RING WHEN THERE ARE 15+ ON THE SAME RING
Starting the LAN Distance Connection Server ICON brings up the LAN Distance
Workstation Window. The Workstation Window is designed to display all
Connection Servers found on the network. However, it only displays 8 to 12
Connection Servers at a time. Refresh shows a different set of Connection
Servers.
For example, a customer has 30 LAN Distance 1.1 Connection Servers on the
same physical ring. Not one is set to connect to a Non-LAN Distance
Workstation; all are using NETBIOS. However, from any one of them, the
customer only sees 8 to 12 of the 30 Connection Servers on the ring.
o APAR= IC08683 MULTIPLE ATTEMPTS TO LOGON THE LAN DISTANCE CONNECTION SERVER
WITH INCORRECT PASSPHRASE RESULT IN MISLEADING ERROR MESSAGE
The maximum logon attempts is 4. When the maximum is met, the "MSG001: Access
Denied" error appears. The expected error is: "MSG002: Your account is not
active".
The "MSG002" error does not appear until the 8th attempt to logon with an
incorrect PASSPHRASE. The first attempt to re-activate the user is
unsuccessful after receiving "MSG002". Instead, "MSG005: Access denied"
displays when you first logon with a valid passphrase. Once again the
account is inactive. The second attempt to reactivate the user is
successful.
o APAR= IC08864 INCORRECT VALUES FOR NCB, TI, T1, T2 PARAMETERS ON MPTS (LAPS)
PAGE OF LAN DISTANCE SETTINGS NOTEBOOK
The environment is a LAN Distance Connection Server or OS/2 Remote
workstation running on LS 4.0 (MPTS).
If you change and save the values for the NCB, TI, T1, and T2 parameters they
do not appear in the NETBIOS section on the MPTS (LAPS) page of the LAN
Distance Settings notebook. Instead you see the default values. MPTS from
the command line correctly displays the values. The following steps recreate
the problem:
- Open the LAN Distance Settings notebook and select the LAPS tab.
- Edit NETBIOS and change the parameters listed above to non-default values.
Save and exit.
- Reopen LAPS from the Settings notebook.
o APAR= IC08988 PROBLEMS USING AUTOFILTERING WITH ASYNCH LEASED LINES
The customer experiences problems using autofiltering with leased lines.
Symptoms are slow response times, failure to logon to the domain controller,
and problems using OS2ping to reach another machine on the ring.
o APAR= IC09167 CONFIGURING LD 1.11 ON AN ETHERNET WORKSTATION WITH MPTS FOR
TRANSPARENT BRIDGING RESULTS IN A LT00093 ERROR AFTER REBOOT
The following binding statements are in the PROTOCOL.INI file after you
install LAN Distance 1.11 on a Ethernet workstation with MPTS.
NETBIOS
DriverName = netbios$
ADAPTER0 = netbeui$,0
ADAPTER1 = netbeui$,1
NETBEUI_nif
DriverName = netbeui$
Bindings = MACETH_nif,PDFH_nif
If you now open the LAN Distance 1.11 Connection Server settings, the
bindings statements for the NETBEUI_NIF section changes to Bindings =
PDFH_nif. The NETBIOS section remains the same. If the system is rebooted,
it receives a LT00093 error, as NETBEUI is no longer binding to two adapter
drivers.
o APAR= IC09226 LAN DISTANCE CONNECTION SERVER DOES NOT CLEAN UP WCLLOCAL.INI
AFTER DELETING A PORT
Running a LAN Distance, v1.11, 32 port server, When adding a port and modem
the PROTOCOL.INI, WCLNET.INI, AND WCLLOCAL.INI are updated. Then delete the
port (COM1). The PROTOCOL.INI and WCLNET.INI change appropriately, but the
WCLLOCAL.INI still refers to the COM1 port.
o APAR= IC09297 LDREMOVE DOES NOT WORK IF EXECUTED FROM DISKETTE OR IF THE
WCLINIRC.DLL FILE CANNOT BE FOUND
The LDREMOVE.EXE module found in LAN Distance 1.11 does not update the
IBMLVL.INI file to reflect the removal of LD 1.11 when executed from the LAN
Distance v1.11 diskettes. This worked correctly in LAN Distance v1.1.
o APAR= IC09590 LAN DISTANCE SECURITY DATABASE BECOMES CORRUPTED AND PREVENTS
ACCESS BY THE SECURITY ADMINISTRATORS
The User Account Management database file, WCBUSRF.ISF, becomes corrupted.
The Security Administrator is able to logon as Secadmin but cannot access the
User Accounts file. LAN Distance terminates and returns the user to the
desktop. The user receives the normal message that the User Account database
is being accessed and then LAN Distance terminates. Early symptoms of
database corruption are:
- Double entries of users
- Failures in deleting users
- Failures in adding new users The problem occurs with LAN Distance versions
1.10 and 1.10 with IP07050.
o APAR= IC09975 LAN DISTANCE DOCUMENTATION DOES NOT STATE SUPPORTED BAUD RATES
LAN Distance documentation does not indicate speeds below 9600 baud are not
supported.
o APAR= IC10184 LAN DISTANCE 1.1 WITH ARTIC CARDS DOES NOT ALLOW CONNECTIONS (
WCL0336)
After the Connection Server operates for some time, (hours to days), it stops
answering remote connections. The established connections may or may not
remain live, depending on the activity on ARTIC.
Remote work stations are able to call, the modems answer and connect, but the
LAN Distance connection is never made. The Connecting status never changes
to the Connected status.
Call and Port Management does not cycle through normal states. The status
stays at Disconnecting on the ARTIC ports. The Transmit light on the remote
modem blinks but never gets data back. The Receive light on the remote never
blinks. Then the WCL errors are displayed. When using OS/2, the WCL0336
message appears. The only fix is to reboot the Connection Server when the
problem occurs. Below are the environments in which this problem occurs:
Environment Ethernet LAN; Novel is the LAN application
CPU Various machines. (Site uses IBM MOD 77's and 90's as
Connection Servers)
Multiport card ARTIC
Modem Tested various supported modems; also used Null-modem
CS software LAN Distance 1.1 with ip07050, LD 1.11, OS/2 2.11
Remote software LAN Distance 1.1 with ip07050 and OS/2
ARTIC 53f2607 (supported card and EIB) (96 ports total)
o APAR= IC10650 ISDN MC PRIMARY RATE DRIVER CONFLICTS WITH STARGATE MC DRIVER
AND STARGATE PORTS ARE NO LONGER RECOGNIZED BY LAN DISTANCE
If you autostart both the ISDN microchannel and Stargate microchannel ports
in LAN Distance, the modems on the Stargate panel do not initialize. Errors
WCL0326, WCL0323 and WCl0222 occur. If neither is autostarted, the same
problem occurs when you manually start Stargate first and then manually start
the ISDN port in Call and Port Management.
The following APARs were fixed in this ServicePak for LAN Distance Entry
Connection Server.
o APAR= IC07390 TRACE AUDITING FEATURE DOES NOT DISPLAY BYTES TRANSMITTED OVER
ASYNC CONNECTIONS
The Number of Bytes Transmitted field always shows the value of zero when
using async connections. If a device driver does not support this field, LAN
Distance should display a -1. ISDN connections set the value correctly.
o APAR= IC07598 SUPPORT FOR X.25 NATIVE ADAPTERS (Fixed in ip07050)
If an X.25 native adapter is used in the Connection Server or OS/2 Remote
workstation, this fix must be used.
o APAR= IC07599 SUPPORT FOR THE IBM ISDN PRIMARY RATE ADAPTER (Fixed in
ip07050)
If an IBM ISDN Primary Rate Adapter is used on the Connection Server or the
OS/2 Remote workstation, this fix must be used.
o APAR= IC07600 CALLBACK FROM CONNECTION SERVER TO REMOTE FAILS WITH AUTOMATIC
FILTERING ENABLED AT THE CONNECTION SERVER (Fixed in ip07050)
Callback from the Connection Server to the Remote workstation fails when
automatic filtering is enabled at the Connection Server. Note this is a
problem in LD 1.1 and NOT in LD 1.0.
o APAR= IC07974 WCL0349 BY LD REMOTE IF THE LD CONNECTION SERVER HAS SAME
ADAPTER ADDRESS FOR THE REAL AND LD LOGICAL ADAPTER
The LAN Distance Remote workstation receives a WCL0349 error while connecting
or shortly after connecting to the Connection Server. This occurs if the LAN
Distance logical adapter (PDFH_NIF section of protocol.ini) address and the
real adapter (IBMTOK_NIF, or other adapter, section of the protocol.ini)
address are the same on the LD Connection Server. The WCL0349 error does not
indicate this as the problem.
o APAR= IC07982 LAN DISTANCE SETTINGS INCORRECTLY CHANGES NRZI TO NRZ, CAUSING
LEASED LINE CONNECTIONS TO FAIL (Fixed in ip07050)
To successfully complete a synchronous leased line, the encoding scheme must
match everywhere in the configuration. You can specify the LAN Distance
answer criteria encoding scheme as NRZ or NRZI. If you select NRZI and save
the settings, NRZI is in the entry for the answer criteria in the WCLDIAL.CXD
file. However, if you open Settings again, select the Answer tab and save
settings, LAN Distance saves NRZ instead of NRZI. The unexpected change in
the encoding scheme causes connections to fail.
o APAR= IC08043 UNABLE TO INITIALIZE MODEM WITH SUPRAFAX V32BIS PIF FILE
Use the following to initialize the modem and establish a 14400 connection:
INITIALIZATION1 = "AT&F2\CR" INITIALIZATION2 = "ATS0=2\CR"
o APAR= IC08102 RETURN CODES FOR LINK STATISTICS IN THE LAN DISTANCE AUDIT FILE
ARE NOT DOCUMENTED
The return codes in the Link Statistics section of the audit file are not
documented in the LAN Distance Advanced Guide. Some common return codes:
- 3410 - Normal Call Clearing
- 332D - Timeout on Call
- 3396 - Modem Not Responding
o APAR= IC08124 SOME MODEMS RESPOND SLOWLY TO AT COMMANDS AND DO NOT INITIALIZE
FOR LAN DISTANCE
The problem appears two different ways:
1. The modem initializes intermittently
2. The modem never initializes. However, when LAN Distance tracing is on
for modem specific trace points, the modem initializes. The solution is
a new ATCMD.DDF file to add a delay between issuing the first and second
initialization string.
o APAR= IC08251 LARGE FILE TRANSFERS FAIL USING BANYAN OVER LAN DISTANCE (Fixed
in ip07050)
With automatic filtering enabled, copying of large files (or lots of smaller
files) fails and the redirected driver is lost. The problem occurs on DOS and
OS/2 Banyan clients in ethernet and token ring environments. The problem
does not occur if automatic filtering is disabled.
o APAR= IC08269 "A PROCESSING ERROR OCCURRED" MESSAGE APPEARS WHEN OPENING LAN
DISTANCE SETTINGS NOTEBOOK
Customer tried to open the Settings notebook at the LAN Distance Connection
Server and received the message "a processing error occurred". When this
message appears you cannot open the notebook.
o APAR= IC08292 PROBLEMS COMMUNICATING TO/FROM A MICROCOM QX/4232BIS MODEM
USING LAN DISTANCE (AND MICROCOM.PIF)
Various problems occur when using the Microcom QX/4232bis modem and LAN
Distance. Problems include modem failure to answer and callback.
o APAR= IC08434 ARTIC 8 PORT NEVER ANSWERS CALL FROM WAC ON SYNCHRONOUS LINE
The answering LAN Distance Server has OS/2 2.1, LD 1.1, and an Artic 8 port
adapter. The dialing LD Server has OS/2 2.1, LD 1.1, a WAC adapter and dials
over a leased line. The servers run a LAN to LAN bridge via WAC port to Artic
port. The dialing server with the WAC receives the WCL0336 message and the
connection is not made.
To make the connection, activate Autoanswer on the LD Server with the Artic
adapter as the LD Server with the WAC adapter is dialing in.
o APAR= IC08536 SYS3170 ERROR SHUTTING DOWN LAN DISTANCE USING IP07050
SYS3170 error with CS:EIP ae77:0000bd9f occurs when shutting down LAN
Distance on IP07050.
o APAR= IC08555 TOKENRING ADAPTERS NOT LISTED IN THE TOKENRINGMACS SECTION OF
THE WCLLOCAL FILE ARE REPLACED WITH PDFH IN PROTOCOL.INI FILE
After the installation of IP07050 on a LAN Distance v1.1 Connection Server, a
new section called TOKENRINGMACS is added. If a customer wants to add a Token
Ring NIF file to the list and configure that driver, LAN Distance replaces
the driver name with PDFH information in the PROTOCOL.INI file. For example,
LAN Distance substitutes PDFH_NIF for OLITOK16_NIF.
o APAR= IC08630 LAN DISTANCE REMOTE WINDOWS CLIENT ON ASYNC LEASED LINE NOT
WORKING
LAN Distance 1.1 Remote Windows Client on Async leased line does not work.
o APAR= IC08720 THE README FILE FOR LAN DISTANCE CSD IP07050 LISTS SUPPORT FOR
AN UNAVAILABLE ADAPTER
IP07050.INF on Disk #1 of the LAN Distance CSD IP07050 lists support for an
IBM Auto LANStreamer ISA Adapter. This adapter is unavailable and should not
be listed.
o APAR= IC08729 LACK OF RETURN CODE AND ERROR CODE DOCUMENTATION IN ALL LAN
DISTANCE PACKAGES
Return code information is not readily available. Available error code
documentation is limited and not helpful to support and application
development personnel.
o APAR= IC08871 VALUES FOR BINDINGS= ARE NOT SET CORRECTLY IN ALL THE PROTOCOLS
The configuration is 2 LAN adapters, one Autostreamer and one Ethernet. When
LAN Distance is installed, the bindings= values in the protocol.ini file are
not set correctly in all the protocols. After the LD install, some of the
bindings had bindings= pdfh_nif. Some had bindings enet,pdfh_nif. LD did not
keep the positions of the token ring adapter 0. Instead it set PDFH adapter
0 for some protocols, and adapter 1 for others. The same happens with
ethernet adapters.
o APAR= IC08956 LAN DISTANCE LAPS TAB FROM SETTINGS DOES NOT WORK ON WARP
If you select the LAPS tab in the LAN Distance Settings notebook when running
on WARP, you cannot select any fields. All fields appear protected. LAPS
works fine from the command line.
o APAR= IC09737 ADDRESSES STARTING WITH 00 DO NOT WORK WITH LAN DISTANCE
(WCL0567)
Any LAN adapter starting with an address of 00 will not work with LAN
Distance. LAN Distance returns a WCL0567 error.
o APAR= IC09738 THE CID ADDRESS RANGE FOR LAN DISTANCE DOES NOT ALLOW FOR
ADDRESSES LESS THAN 4000
An address range from 0000000000001 to 400000000000 is not allowed in CID
installs of LAN Distance. The address during a CID install has to be from
40000000000 to 7FFFFFFFFFFF. LAN Distance 1.1 allows an address range of
00000000001 to 7FFFFFFFFFF.
o APAR= IC10334 THE LAN DISTANCE CONNECTION SERVER ICON INTERMITTENTLY DISPLAYS
GREEK SYMBOLS
Customer intermittently sees his LAN Distance Connection Server Icons with
Greek lettering. He is unable to recreate at will.
o APAR= IC10808 CALLBACK FAILURE HANGS CONNECTION SERVER IF REMOTE IS RUNNING
WARP
The LAN Distance Connection Server hangs after an OS/2 Remote LAN Distance
workstation dials in requiring callback. The Remote LD workstation runs the
MPTS version shipped with WARP Connect (2.60.5). The failure may not occur
on the first dial in, but it does occur after two or three attempts. At that
point, the CS does not accept any new calls and the Remote fails to go into a
connected state. After a few more users attempt to logon, the Connection
Server hangs. The LAN Distance code cannot be closed.
The following APARs were fixed in this ServicePak for LAN Distance Remote
Workstation.
o APAR= IC07973 UNCLEAR WCL0535 ERROR ISSUED WHEN THE LAN DISTANCE LOGICAL
ADAPTER HAS NO ADDRESS (Fixed in ip07050)
WCL0535 appears when there is no adapter address for the LAN Distance Logical
Adapter. This occurs when you delete the LAN Distance logical adapter in LAPS
and then add it again without setting the address. WCL0535 indicates a
processing error in dial services. This provides no information about the
real problem.
o APAR= IC07601 BANYAN REQUESTER CANNOT LOGON TO BANYAN SERVER OVER LAN
DISTANCE WHEN THE LAN IS A TOKEN RING (Fixed in ip07050)
The Banyan protocol stack does not fill in the source address in the token
ring frame. Therefore, a Banyan requester running over LAN Distance cannot
logon to the Banyan server. The problem only occurs in a token ring
environment. A fix is provided for LD 1.1 and not LD 1.0.
o APAR= IC08716 WCL0321 WHEN DIALING FROM THE LAN DISTANCE PHONEBOOK
If you select Dial from the Phonebook on a LAN Distance Remote workstation
with LD, V.1.1 and CSD IP07050 or 1.11, a WCL0321 message appears. The same
message appears if you start the LAN Distance Connection Server. The message
says "A processing error occurred. The LAN Distance product cannot read
configuration data for '***'".
o APAR= IC08717 PROBLEMS OPENING THE LAN DISTANCE SETTINGS NOTEBOOK
The following problems occur on LAN Distance 1.1 (with or without CSD
IP07050) when you open the Settings notebook.
- The message box indicates Settings will open.
- After awhile the message box disappears.
- The notebook DOES NOT open.
- A processing error appears and the notebook does open.
o APAR= IC09046 LAN DISTANCE CONNECTION FAILS IF SECOND CALL HITS THE PORT
DURING CALLBACK FOR FIRST CALL
A customer wants to install LAN Distance for a community of about 400 people.
The customer configuration:
- 2 LD Servers IBM 9585, 54 MB HD, 80486DX2, 24 MB RAM each
- 3 RIC Portmaster Adapters peer server (2MB)
- Each Portmaster adapter attached to 8 modems (Motorola 3265) The error
description is below:
- User "A" calls in with a variable callback id on CS port 0000
- User "A" logs on with userid TEST01 & password & callback #
- Logon is successful
- CS disconnects the session
- User "A" waits for callback (callback on CS is set to ANY port)
- The modem on port 0000 initializes successfully
- CS initiates a callback on port 0000 and sends the dial string to the
modem
- The modem switches in dial wait mode (for 2 seconds)
- In the meantime, user "B" has started a call to CS port 0000
- The first ring of user "B"s call hits the port 0000 modem while the modem
is in dial wait mode for the callback
- The CS gets a RING RING & CONNECT .... message fom the modem on port 0000
- The CS assumes a successful callback to user "A" and wants to verify user
"A"
- User "B" gets a CONNECT message in his phone book, but no 'logon in
process" message.
- The trace on the CS looks like the server cannot handle this situation.
The user information for user "A" and "B" get mixed up.
- The Remote of user "B" cannot handle this either.
- User "B" gets a 'no port available - waiting for redial' message on the
phone book status line
- As Remote of user "B" hangs up, the CS assumes a successful callback and
that the callback party disconnected upon request of user "A". We guess
this is why user A never gets a callback.
- For the CS everything seems to be OK. The modem on port 0000
reinitializes and prepares for the next call without an error message.
Additional information is in the attached PMR. Lisa Goetze and Annah Lewis
have traces.
o APAR= IC09059 CANNOT EXIT CFMODEM BUILD STRING NOTEBOOK ON WARP
Selecting the build string option of CFMODEM on WARP causes a problem. You
cannot exit the notebook and the task list does not come up. You must reboot
the machine to recover.
o APAR= IC09338 LAN DISTANCE DOES NOT HONOR SPECIFIC PORTS WHEN LD 1.1, OR LD
1.11 IS USED
With LAN Distance 1.10 plus 7050, the customer wants to configure a
Waverunner (ISDN) on COM2, and a Hayes Optima 14.4 on COM1. When he tries to
dial out, it always dials from COM1, regardless of the selected Phonebook
entry. Level 2.5 has recreated this using modems on Com Ports.
o APAR= IC09437 755CE WITH DSP MWAVE SUPPORT REQUIRES COMX SECTION OF THE
PROTOCOL.INI FILE TO HAVE PCMCIA = YES
To setup LAN Distance on a 755CE/CD with DSP MWave support you must set
PCMCIA = "YES" in the COMx port section of the PROTOCOL.INI. If it is set to
NO, the following errors OCCUR at boot time:
- CPM0008 Adapter specified for MAC COMx does not exist.
- SYS1201 .... WCLCPMAC.OS2 did not load. DSP Mwave modem is not a PCMCIA
modem.
o APAR= IC10166 WCL0012 MESSAGE POPS UP WHEN CLOSING LAN DISTANCE WITH SHUTTLE
The following setup was done with the Advanced path on a Pentium machine:
- WARP
- OS/2 PEER with NetBIOS
- TCPIP
- NETWARE
- LAN Distance The following is a description of the problem:
- After installation, start LAN Distance, open the Phonebook, close the
Phonebook, and close the LAN Distance container. WCL0012 appears. The
Shuttle panel appears after WCL0012 is dismissed, but the Help button is
inactive.
- Start LAN Distance, open the Phonebook, close the Phonebook, and close the
LAN Distance container.
- Display the Help for the close confirmation prompt. The Shuttle panel is
not displayed after the close confirmation prompt is dismissed.
o APAR= IC10348 BASEDEV= BECOMES DEVICE= WHEN SHUTTLING LAN DISTANCE REMOTE TO
LAN ATTACHED WITH OS/2 WARP SOCKET SERVICES DRIVERS LOADED
You use the Shuttle feature of LAN Distance Remote to switch from Remote PC
to LAN attached. The Shuttle function places the WARP Socket Services
drivers in the config.sys file as DEVICE= statements instead of the BASEDEV=
statements required by Socket Services. The drivers will not load at boot
time.
o APAR= IC10905 STARTING LAN DISTANCE FROM THE CLI WITH LDIST DIAL /D:ENTRY
CAUSES THAT OS/2 SESSION TO HANG
LAN Distance starts successfully from the command line with LDSTART. Next
you enter LDIST DIAL /D:entry to dial and establish a connection. LAN
Distance is supposed to display the returned modem strings as the connection
is made. Instead, the OS/2 window session hangs in the middle of displaying
the modem strings. However, the connection is there and you can work over
the connection in another window session.
System setup includes Thinkpad Models 345-c and 345-cs, a Hayes Optima 14400
modem, OS/2 WARP with Communications Manager, DCAF, and a started System
Perform Monitor.
o APAR= IC11000 INCORRECT PARAMETER SYNTAX FOR THE LD_REM.RSP FILE IN THE LAN
DISTANCE, V.1.1 ADVANCED GUIDE
Page 4-9 of the LAN Distance Advanced Guide, v.1.1 indicates the address
syntax should be in double quotes. On page 4-8 the sample is without double
quotes. If the LD_REM.RSP file is set up as described on page 4-9, then the
workstation receives WAL0113 and WAL0074 errors.
Also, the LANtype is defined to be Token-Ring for 802.5 token-ring networks.
Token-ring is incorrect. The correct term is TOKENRING.
ΓòÉΓòÉΓòÉ 4.3. New Features ΓòÉΓòÉΓòÉ
The following sections discuss new and enhanced LAN Distance features.
ΓòÉΓòÉΓòÉ 4.3.1. Inactivity Timeout for Connection Servers ΓòÉΓòÉΓòÉ
The administration of a Connection Server will be able to specify conditions
for detecting a lack of activity over the various established connections, and
force a disconnection of the link when that inactivity condition is present.
How Inactivity Timeout Works
Every connection established by a machine on which the inactivity timer is
installed and operating will be 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. The first piece of information determines how many minutes to
tolerate inactivity on the link before forcing a disconnection, and the second
piece of information specifies the minimum number of LAN frames that must
across the link (in either direction) within a one minute period for the link
to be considered active.
This information is provided to the Connection Server through values assinged
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 minimun number of frames that must cross an active link in a minute.
The value of Inactivity threshold can be anywhere from 0 to 99999, although 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.
Additional Information
When disconnected, the remote workstation will display a WCL0310 message. In
this version, no other indication will be given to a user, and there will be 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, and will 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 really will
be broken, but also set low enough so that low-intensity applications doing
real work are not accidentally disconnected.
Experimentation will be required for each LAN environment on which this feature
is installed. A simple LAN Distance link, with the LAN parameters configured as
recommended in the LAN Distances guides, 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 will be necessary to experiment with
the value of Inactivity threshold in the environment being used to determine an
acceptable value.
ΓòÉΓòÉΓòÉ 4.3.2. Security Shared Database ΓòÉΓòÉΓòÉ
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.
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.
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, 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.
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 connectin server only.
2. In the User Exit Name field, type the user exit DLL name. The maximun
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.
Enabling Share Security Database
To share a secured database with others on the LAN.
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.
Security Database Tools
This appendix discusses the security database tools available in LAN Distance
1.12.
The LAN Distance Security Database Tools allow the LAN Distance security
administrator to manage the security database and perform the following tasks:
o Add users with using the User Account Management window
o Print a report of the security database
o Back up the security database with out shutting down LAN Distance
The security database tools are comprised of these tools:
o BACKUP: - provides a command line interface that allows the user 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 <output_file>
where:
<output_file> 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.
o PRINT: - provides a command line interface that the user 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 </FI:input_file> </FO:output_file>
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.
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 </CT:control> </FI:infile> </FO:outfile>
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 ADD user is CMADD.REP.
/FI: input file name
If the control parameter is ad, 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 maximun length of the userID is 10 characters. This control
key is reqired. 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
ΓòÉΓòÉΓòÉ 4.3.3. Developing User Exits ΓòÉΓòÉΓòÉ
This appendix discussed the user exits available in LAN Distance 1.12.
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 wityout 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, apply version 1.11 of the LAN
Distance product to the connection server and remote workstations that will use
the user exit.
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:
o specification of the LAN Distance Generalized Security User Exit API
o description of how a LAN Distance security user exit can be
installed/registered at LAN Distance workstations
o 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.
ΓòÉΓòÉΓòÉ 4.3.4. X.25 Native Adapters Support ΓòÉΓòÉΓòÉ
Changes were made to LAN Distance to support adapters that are enabled for
native X.25 under LAN Distance. If this support is required, then this
ServicePak must be applied to the connection server and the OS/2 remote
workstations using the X.25 native adapter.
APAR IC07598 was created to add this support to the LAN Distance product.
ΓòÉΓòÉΓòÉ 4.3.5. IBM ISDN Primary Rate Adapter Enablement ΓòÉΓòÉΓòÉ
Support has been added to LAN Distance to allow the use of the IBM ISDN Primary
Rate Adapter. This ServicePak must be applied to all connection servers and
remote workstations using this adapter.
APAR IC07599 was created to add this support to the LAN Distance product.
ΓòÉΓòÉΓòÉ 4.3.6. IBM Auto/Dual LANStreamer Adapters (Token Ring Promiscuous Mode) Support ΓòÉΓòÉΓòÉ
The LAN Distance product supports the following IBM Auto or Dual LANStreamer
Adapters:
o IBM Auto LANStreamer MC 32 Adapter
o IBM Dual LANStreamer MC 32 Adapter
o IBM Auto LANStreamer ISA Adapter
NOTE: Before using these adapters contact IBM Support and Service to obtain
the device drivers: IBMMPC.NIF and IBMMPC.OS2.
To use the above IBM Auto or Dual LANStreamer Adapters for bridging on a LAN
Distance Connection Server, do the following:
1. Install the LANStreamer adapter according to the adapter installation
instructions.
2. If using the ISA version of the adapter, configure the adapter with the
adapter installation diskette.
3. If using the MC Adapter, configure the adapter with the reference diskette.
4. Use LAPS or MPTS to install the adapter device driver and configure the
adapter for LAPS.
5. Start LAN Distance
6. Open the Settings Notebook
7. Select the Address/LAN tab
8. After the Settings Notebook has finished initializing, you will see a list
of adapters available for bridging in the "Adapter for Bridging" listbox.
Find the "IBM Streamer Family adapter (IBMMPC.OS2)" entry and select it.
9. When you close the Settings Notebook, your LAN Distance Connection Server
will be set up for bridging with the IBM Auto or Dual LANStreamer adapter.
Shutdown and restart the workstation.
ΓòÉΓòÉΓòÉ 5. LAN Applications and Hardware Considerations ΓòÉΓòÉΓòÉ
The following sections discuss additional considerations for using specific LAN
Applications and hardware with the LAN Distance product.
ΓòÉΓòÉΓòÉ 5.1. NetWare ΓòÉΓòÉΓòÉ
This section discusses additional considerations for using NetWare with the LAN
Distance product.
NetWare Server
o 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.
o In a token ring environment, make sure that ROUTE.NLM is loaded on the
NetWare server. Since the LAN Distance connection server is a token ring
bridge, source level routing information must be in frames to be delivered to
the WAN by the connection server.
OS/2 NetWare Requester
The following recommendations are for running OS/2 NetWare Requester. Note
that a few of the steps only apply to a token ring environment.
o To improve performance, copy frequently used NetWare utilities to the OS/2
NetWare requester. For example: LOGON.EXE, LOGOUT.EXE, MAP.EXE and SLIST.EXE.
o The following is a sample NET.CFG. Use this configuration when first
attempting to use the OS/2 NetWare requester over LAN Distance. Do not use
the normal buffer size of 4202 for a token ring environment, use 1514.
NetWare Requester
Default Login Drive L
cache buffers 30
directory services off
Link Support
Buffers xx 1514
o For a token ring environment, LAN Distance requires that all frames have
source routing information. This means that ROUTE.NLM must be loaded on the
NetWare server and ROUTE.SYS must be loaded for the OS/2 NetWare requester.
o The OS/2 NetWare requester must have 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.
o Make sure the OS/2 NetWare requester is version 2.1. Otherwise NWDAEMON must
be executed after the LAN Distance connection has been established by issuing
DETACH C:\NETWARE\NWDAEMON.
ΓòÉΓòÉΓòÉ 5.2. WAC Adapter Setup ΓòÉΓòÉΓòÉ
NOTE: The WAC Adapter must be configured through LAPS in LAN Distance. DO NOT
configure this adapter through LAPS outside of LAN Distance.
After installing the WAC Adapter, the ROM address will be displayed on your
screen while your workstation is restarting. Write this ROM address down and
enter it during LAPS configuration.
To configure the WAC Adapter:
1. Open the Settings notebook
2. Select the LAPS tab
3. Select LAPS
4. Edit or add the WAC adapter to the list of already-installed adapters.
5. On the WAC Adapter configuration panel, note the following items:
o Enter the ROM address of the WAC Adapter recorded above.
o For "Line Mode" enter 0 for Constant RTS.
o For "MAC Type Description" enter HDLC.
o When selecting NRZ vs NRZI, be consistent with the way you configured your
modem in LAN Distance. If you used V.35 connection, select NRZ by
entering 0 for No. If you used generic synchronous switched or synchronous
leased line, select NRZI by entering 1 for Yes.
NOTE: You may also use NRZ for generic synchronous switched or
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.
o For "ANDIS PCM Support" enter 1 for YES.
o For "Slot Number" enter the slot number in which the adapter is inserted.
o For "Port Number" enter the port for which the adapter is configured. The
upper port is the one farthest from the system board; the lower port is
the one closest to the system board.
o For "Link Connection type" enter 1 for switched or 0 for non-switched
(leased line) connections.
o For "Portname displayed in the PPAT table" enter a name to identify the
adapter to the port connection manager.
o Typically, you can use default values for the rest of the parameters.
ΓòÉΓòÉΓòÉ 5.3. Banyan VINES ΓòÉΓòÉΓòÉ
This section discusses Banyan VINES fixes and setup information to run Banyan
VINES with the LAN Distance product.
Banyan Fixes
The following Banyan fix is in the Banyan Maintenance release 5.54(5). If this
release is not available, then contact your Banyan SE.
o 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
Banyan OS/2 Workstation Setup
See the LAN Distance Advanced Guide, Chapter 10, section "Configuring the LAN
Distance Remote for Banyan VINES" for setting up a Banyan OS/2 workstation with
LAN Distance. The following are 2 additional steps that are required for a
token ring environment:
1. In a token ring environment, run PCCONFIG and make sure End Node Source
Routing is enabled.
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.
ΓòÉΓòÉΓòÉ 6. Support and Feedback ΓòÉΓòÉΓòÉ
Refer to the License Information booklet in the LAN Distance package for
problem reporting and assistance with the LAN Distance product.
While not support mechanisms, the following two fora contain feedback, updates,
and information on the LAN Distance product:
- OS2BBS, REMOTE section
- CompuServe, GO PSPAPROD, LAN DISTANCE section
ΓòÉΓòÉΓòÉ 7. Appendix ΓòÉΓòÉΓòÉ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 7.1. Printing Information from this On-line Document ΓòÉΓòÉΓòÉ
The OS/2 view function provides a print capability to the printer defined as
the "default" printer for your system. From the "Services" popup, selecting
print provides several options; Print All, Marked, or This Section(s),
Contents, or Index.
All but the Print Marked Sections are fairly self explanatory. To Print
"Marked" sections one must first know how to "Mark". It is best to do this with
the contents window fully expanded, ie. every section shows up in the content
panel. Then simply press the space bar when the section you chose is
highlighted or point and click the left mouse button while also holding the
ctrl key to "mark" a section for print.
The highlighting for "marked sections" is slightly larger than normal
highlighting. To notice the difference, select an item in the contents and
repeatedly press the space bar.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of IBM Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Microsoft Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Ungermann-Bass, Inc.