home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IBM Presents OS/2 Software Hits 1995
/
OS-2_SW_HITS_2ND_EDITION_1995.ISO
/
i17
/
us7050b1.dsk
/
IP07050.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1994-10-03
|
36KB
|
1,019 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
IBM OS/2 LAN Distance 1.1 ServicePak IP07050
IBM PTF IP07050
This ServicePak applies to:
IBM LAN Distance Connection Server for OS/2, 8 port - Version 1.1
For use with OS/2 2.0 or higher.
IBM LAN Distance Connection Server for OS/2 - Version 1.1
For use with OS/2 2.0 or higher.
IBM LAN Distance Remote for OS/2 - Version 1.1
For use with OS/2 2.0 or higher.
IBM LAN Distance Remote for Windows - Version 1.1
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 7050WIN.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 ΓòÉΓòÉΓòÉ
Installing the ServicePak is essentially a three phase process:
Phase 1 - Quiesce the Target System
Render the system serviceable by insuring that there will be no
Locked Files during the install phase.
Phase 2 - Install the ServicePak
Select one of the following methods to replace system files with
those provided on this ServicePak.
Full Install
Selective Install
Redirected (CID) Install
Phase 3 - Return the Serviced System to Normal Operation
Perform a normal system boot.
ΓòÉΓòÉΓòÉ 2.1. Full Install ΓòÉΓòÉΓòÉ
This method will apply all fixes to all partitions and directories:
It is the simplest and safest method to install ServicePaks to systems that do
not have multiple versions of the product being serviced. It does require
booting from diskette to insure that there are no Locked Files during the
install phase.
1. Boot from the Bootable Standalone Service Diskettes.
2. Establish A: as the Current Directory.
3. Replace the Boot Diskette with ServicePak diskette #1.
4. At the A: prompt type "FSERVICE" and press Enter.
5. At the panel titled "Updating Default Directories" press Enter (Option 1).
6. Follow the prompts provided by the Installation Aid.
7. Reboot the system normally.
ΓòÉΓòÉΓòÉ 2.2. Selective Install ΓòÉΓòÉΓòÉ
This method will apply fixes to selected subsystems, partitions, and
directories: The Installation Aid will check for Locked Files.
1. Boot the system from fixed-disk.
2. Insert ServicePak diskette #1 in the A drive.
3. Establish A: as the Current Directory.
4. At the A: prompt type "SERVICE" and press Enter.
5. Make selections from the panel. If the Locked Files panel with the Reboot
push button is presented, continue with the following steps. Otherwise go
to the last step.
6. Choose "Reboot".
7. Perform the system Shutdown procedure.
8. Boot from the Bootable Standalone Service Diskettes.
9. Establish A: as the Current Directory.
10. Replace the Boot Diskette with ServicePak diskette #1.
11. At the A: prompt type "FSERVICE" and press Enter.
12. Follow the prompts provided by the Installation Aid.
13. Reboot the system normally.
ΓòÉΓòÉΓòÉ 2.3. Redirected Installation (CID) Method ΓòÉΓòÉΓòÉ
This method is useful for those who are using the CID (Configuration,
Installation, and Distribution) Services as provided by IBM NTS/2. The Full
Install or Selective Install methods are recommended for Servers exploiting 386
HPFS function; Fault Tolerance and/or Access Control Lists.
While setting up a CID server is beyond the scope of this document, we have
provided a sample LAN CID Utility REXX Command file (IP_7050.cid) that may
prove useful in setting up a CID server for this ServicePak.
The sample IP_7050.cid assumes the following:
o The ServicePak files are placed on the code server using "XCOPY A:\*.* /S"
(or equivalent) at 'x:\img\csd\ld11\IP_7050' where 'x:' is the drive seen by
the client.
o The following CID server directory structure contains the ServicePak
contents.
img\csd\ld11\IP_7050\ * Root directory of ServicePak
img\csd\ld11\IP_7050\FIX * No files
img\csd\ld11\IP_7050\FIX\LDA * 32 Port Server Fixes
img\csd\ld11\IP_7050\FIX\LDE * 8 Port Server Fixes
img\csd\ld11\IP_7050\FIX\LDR * Requester Fixes
o A log directory exists at 'x:\log\csd\ld11\IP_7050' for the log files.
ΓòÉΓòÉΓòÉ 2.4. 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. 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:
Making OS/2 2.x Standalone Boot Diskettes.
Making 386 HPFS Standalone Boot Diskettes.
CAUTION:
LAN Servers that utilize the Advanced features, Access Control Lists or 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 access control profiles.
ΓòÉΓòÉΓòÉ 2.4.1. Making OS/2 2.x Standalone Boot Diskettes ΓòÉΓòÉΓòÉ
1. Make a copy of the OS/2 2.x Installation Diskette and Diskette #1. Call
them SA#1 and SA#2 respectively.
2. Delete SYSINST2.EXE from Diskette SA#2.
3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 2.1 only).
4. Modify CONFIG.SYS on SA#2 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 SA#2.
ΓòÉΓòÉΓòÉ 2.4.2. Making 386 HPFS Standalone Boot Diskettes ΓòÉΓòÉΓòÉ
MAKEDISK is a LAN 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 Installation Diskette and Diskette #1. Call
them SA#1 and SA#2 respectively.
2. Delete SYSINST2.EXE from Diskette SA#2.
3. Delete BUNDLE from Diskette SA#2 (this will be on OS/2 2.1 only).
4. With Boot Diskette SA#2 in drive a: or b: run MAKEDISK from an OS/2 prompt.
Note: Syntax is MAKEDISK /BOOTDRIVE:d where d is the drive on which OS/2
2.x is installed.
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 SA#2.
6. Verify that the 386 HPFS Bootable Standalone Service Diskettes work
properly.
o Shutdown the system.
o Insert the Bootable Standalone Service Diskette SA#1 in the A drive.
o Reboot the system (Ctrl+Alt+Del, or other method).
o Determine if Local Security is working.
o Determine if Fault Tolerance is working.
ΓòÉΓòÉΓòÉ 2.4.3. Adding Fault Tolerance to 386 HPFS Standalone Boot Diskettes ΓòÉΓòÉΓòÉ
386 HPFS Standalone Boot 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
this ServicePak to your Bootable Standalone Service Diskette SA#2.
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 SA#2.
DEVICE=DISKFT.SYS
3. At an OS/2 command prompt, make the current drive A:, and have the 386 HPFS
Bootable Standalone Service Diskette SA#2 in drive A. Type "FTCOPY" to copy
the customized Fault Tolerance configuration information to the 386 HPFS
Bootable Standalone Service Diskette SA#2.
Warning: 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.
ΓòÉΓòÉΓòÉ <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> Getting the A: Prompt from OS/2 1.3 Install Diskettes ΓòÉΓòÉΓòÉ
To obtain the familiar A: prompt when using the OS/2 1.3 Product installation
diskettes as Bootable Standalone Service Diskettes:
o Boot the system with Install Diskette in drive A.
o At the IBM Logo Screen - Press Esc to Exit
The A: prompt should appear. OS/2 Programs, including FSERVICE.EXE, can be run
from here.
ΓòÉΓòÉΓòÉ <hidden> Getting the A: Prompt from OS/2 2.x Install Diskettes ΓòÉΓòÉΓòÉ
To obtain the familiar A: prompt when using the OS/2 2.x 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
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
Volume1: Planning and Installation
Version 3.0
ΓòÉΓòÉΓòÉ <hidden> LAN Server Utilities ΓòÉΓòÉΓòÉ
Refer to Appendix C,
Miscellaneous Utilities MAKEDISK in:
Operating System/2 Local Area Network Server
Network Administrator Reference
Volume3: Network Administrator Tasks
Version 3.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. NETBIOS over TCP/IP ΓòÉΓòÉΓòÉ
The LAN Distance product does not support NETBIOS over TCP/IP (device driver
TCPBEUI.OS2).
ΓòÉΓòÉΓòÉ 3.5. Deselecting Manual Bridge Filter ΓòÉΓòÉΓòÉ
For LAN Distance connection servers, on page 2 of the Bridge tab in the
Settings notebook, deselecting a filter criteria with the mouse is not working
correctly. To deselect a filter criteria, select it with the mouse, then
press the space bar on the keyboard.
ΓòÉΓòÉΓòÉ 3.6. 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.7. 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, publications, 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:
o IC07431 - WCLNET.INI File Incorrect for Created Modem Types
WCLNET.INI may become corrupted when using created modem types.
o IC07600 - Automatic Filtering Fails with Callback
When the connection server was executing a callback sequence, the connection
was re-established with automatic filtering disabled.
LAN Distance has been changed to activate automatic filtering in the callback
sequence. For this fix, only the connection server needs to be updated.
o IC07601 - Banyan VINES Token Ring for OS/2 Remote Client Support
Banyan VINES OS/2 client could not connect to a Banyan server over LAN
Distance when the LAN was token ring. The Banyan VINES protocol stack does
not set the source address field in the token ring frame.
LAN Distance now fills in the address. For this fix, only the remote
workstations need to be updated.
o IC07973 - WCL0535 Error Message Unclear
WCL0535 error message indicates a processing error in dial services. One of
the reasons this message is issued is when no adapter address exists for the
LAN Distance logical adapter on OS/2 workstations.
o IC07982 - Leased Line Connection Cannot Be Completed Because NRZI in the
Answer Criteria Changed to NRZ Incorrectly by LD Settings
In order for a syncronous leased line connection to be completed
successfully, the encoding scheme must match everywhere in the configuration.
The LAN Distance answer criteria allows the encoding scheme to be specified
as NRZ or NRZI. Leased line connection cannot be completed because the
answer criteria was incorrectly changed from NRZI to NRZ in the WCLDIAL.CXD
file when settings was saved.
o IC08251 - Copying Large Files Using Banyan VINES
Copying large files using Banyan VINES over LAN Distance may cause the copy
to fail and the redirected drive to be disconnected. The fix for this
problem was a change to automatic filtering. This problem occurs in an
Ethernet or token ring environment when automatic filtering is enabled.
ΓòÉΓòÉΓòÉ 4.3. New Features ΓòÉΓòÉΓòÉ
The following sections discuss new and enhanced LAN Distance features.
ΓòÉΓòÉΓòÉ 4.3.1. Security User Exit Enablement ΓòÉΓòÉΓòÉ
LAN Distance now supports two optional levels of security for restricted access
to the LAN and its resources. One level is the existing LAN Distance security
(User Account Management), included in the LAN Distance product. The second
level is a security user exit package that is distributed separately from the
LAN Distance product. LAN Distance supports any OEM-provided security user
exit package that is developed in conformance with the LAN Distance Generalized
Security User Exit API.
What Is a Security User Exit Package?
A security user exit package consists of two user exit modules: one for the
client and one for the server. The client and server user exit modules work
together to implement the user authentication protocol defined by the security
user exit package. A user authentication protocol is a series of user exit
messages/tokens exchanged between the client and server user exit modules when
validating the user of a LAN Distance client workstation that is calling a LAN
Distance connection server.
Using Multiple Security User Exit Packages
One LAN Distance client workstation can use a different security user exit
package to access each different LAN Distance server workstation it calls. A
LAN Distance server workstation must use only one security user exit package to
allow access from all LAN Distance client workstations that call it.
Using Security User Exit Packages with LAN Distance Security
Security user exit packages can be used with or without LAN Distance security
(User Account Management). If LAN Distance security is used with the security
user exit package, the authentication will take place first through the user
exit and second through LAN Distance security.
Enabling Security User Exit
To enable the user-supplied security exit, this ServicePak must be applied 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:
- specification of the LAN Distance Generalized Security User Exit API
- description of how a LAN Distance security user exit can be
installed/registered at LAN Distance workstations
- sample source code for developing your own LAN Distance security user
exit package
The toolkit is available through IBM Service and Support by referencing APAR
IC07742.
ΓòÉΓòÉΓòÉ 4.3.2. 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.3. 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.4. 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 to install the adapter device driver and configure the adapter for
LAPS.
5. Edit your \WAL\WCLLOCAL.INI file and add the following lines (it doesn't
matter where these lines are added):
[TOKENRINGMACS]
IBMTOK.NIF
IBMMPC.NIF
[IBMMPC.NIF]
LLCONLY = "YES"
LOOPBACK = "NO"
6. Start LAN Distance
7. Open the Settings Notebook
8. Select the Address/LAN tab
9. After the Settings Notebook has finished initializing, you will see a list
of adapters available for bridging in the "Adapter for Bridging" listbox.
Find the "IBM Streamer Family adapter (IBMMPC.OS2)" entry and select it.
10. When you close the Settings Notebook, your LAN Distance Connection Server
will be set up for bridging with the IBM Auto or Dual LANStreamer adapter.
Shutdown and restart the workstation.
ΓòÉΓòÉΓòÉ 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.
ΓòÉΓòÉΓòÉ 7.2. Restarting ServicePak Installation ΓòÉΓòÉΓòÉ
If the installation procedure stops after selecting the "Continue" button on
the Start Service Panel and before service is complete, the system may be in an
indeterminate state. To complete the service process:
o Insert the Bootable Standalone Service Diskette
o Restart the system - Ctrl+Alt+Del or Power On.
o From the A: Prompt type "FSERVICE" and Enter.
ΓòÉΓòÉΓòÉ <hidden> Initiating Service ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé--Γöé Initiating Service Γöé
Γö£ΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé
Γöé Continuing at this point will cause all selected Γöé
Γöé directories to be updated. If you want to change the Γöé
Γöé selected directories, click on Cancel and then click Γöé
Γöé on Select Directories. Γöé
Γöé Γöé
Γöé The application of service cannot be interrupted. Γöé
Γöé After this point you will not be able to exit the Γöé
Γöé service process. Γöé
Γöé Γöé
Γöé Do not start those applications being serviced Γöé
Γöé Γöé
Γöé Do you want to continue? Γöé
Γöé Γöé
Γöé ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù ΓòöΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòù Γöé
Γöé Γòæ Continue Γòæ Γòæ Cancel Γòæ Γòæ Help Γòæ Γöé
Γöé ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ ΓòÜΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓòÉΓò¥ Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ <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.