Test 002 - OS/2 LAN Server and Netware Client Coexistence

OBJECTIVES
SECTION 1 - INTRODUCTION
 * 1.1 Differentiate between coexistence and interoperability.
 * 1.2 Identify the elements of the OSI model and their role in network transmissions.
 * 1.3 Idenfify the functions of LOGIN and LOGON.
 * 1.4 Define the term 'NDIS.'
 * 1.5 Define the term 'ODL.'
 * 1.6 Define the term 'protocol stack.'
 * 1.7 List the different types of NetBIOS and their incompatibilities.

SECTION 2 - IBM DOS LAN REQUESTER AND NETWARE COEXISTENCE
 * 2.1 Identify the LAN Support Program (LSP) drivers in the correct sequence required to support coexistence.
 * 2.2 Configure the LSP Drivers to support coexistence.
 * 2.3 Modify the CONFIG.SYS and AUTOEXEC.BAT files to accommodate coexistence between DLR and the NetWare shell.
 * 2.4 Identify the correct sequence for loading requester modules.
 * 2.5 Generate an IPX.COM using the PC LAN Support Driver.
 * 2.6 Identify the correct modules and sequence for starting the NetWare client after the DLR started.
 * 2.7 Identify the proper LOGON/LOGIN sequence, if required.

SECTION 3 - IBM OS/2 LAN REQUESTER AND NETWARE COEXISTENCE
 * 3.1 State the purpose of the PROTOCOL.INI and NET.CFG files.
 * 3.2 Recognize the major sections of the PROTOCOL.INI and their purposes.
 * 3.3 Recognize the major sections of the NET.CFG and their purposes.
 * 3.4 Define the term 'LAPS' and what it provides.
 * 3.5 List the benefits of using the ODI2NDI protocol driver that comes with LAPS.
 * 3.6 Identify which protocol is required by NetWare to support named pipes and network printing.
 * 3.7 Identify the installation sequence of network software for coexistence on an OS/2 2.1 platform.
 * 3.8 Identify the protocols required for OS/2 and NetWare Requester coexistence.
 * 3.9 State how to obtain a LAN Adapter universal address or create a locally administered address.
 * 3.10 Recognize why an adapter address must be specified in PROTOCOL.INI when using ODI2NDI.LANSUP.
 * 3.11 Determine which protocol stack (LANSUP, ODINSUP, ODI2NDI) to use depending on the primary network server in use and requester hardware.
 * 3.12 Describe what OS/2 Workstation utilities must be installed on the NetWare server to support OS/2 NetWare Requesters, and differentiate this utility from NetWare Workstation tools.
 * 3.13 Recognize the functions and limitations with messaging, drive redirection, and printer redirection in the coexistence environment.
 * 3.14 Discriminate between the naming functions of NETBIOS and NetWare, and their use in the coexistence environment:
 * NETBIOS user name vs. NetWare user name.
 * NETBIOS server name vs. NetWare server name.
 * NETBIOS domain name and machine name.

SECTION 4 - NETWARE REQUESTERS IN VIRTUAL DOS MACHINES (VDM)
 * 4.1 Describe the terms 'global' and 'private' in reference to the NetWare client installation.
 * 4.2 Match the NetWare shells, NETx.COM and VSHELL.SYS to the private and global network resource access within VDM and OS/2 sessions.
 * 4.3 Recognize how the Search Drive function of NetWare is implemented in an OS/2 VDM running NetWare Requester for OS/2.

SECTION 5 - REMOTE PRINTER INSTALLATION ON OS/2 2.x
 * 5.1 Configure an OS/2 NetWare client to provide a locally attached printer as a remote printer.
 * 5.2 Identify which print queues must be configured to support remote printing for an OS/2 client.

Sample Test

 * 1) On an OS/2 workstation, coexistence of Netware Requester for OS/2 and OS/2 LAN Requester is possible only with multiple
 * a. adapter drivers
 * b. network adapter cards
 * c. installable file systems
 * d. Media Access Control (MAC) drivers


 * 1) Which are components of the ODI stack?
 * a. Link Layer Support (LSL)
 * b. Multiple Link Interface Driver (MLID)
 * c. Network Proficient Protocool Display (NPPD)
 * d. Multiple Layer Interface Device Driver Spec (MLIDDS)