Category : Network Files
Archive : DOSUP9.ZIP
Filename : READVLM.TXT
Output of file : READVLM.TXT contained in archive : DOSUP9.ZIP
To print this file to a local printer,
1. Insert the workstation diskette containing this file into
drive A: (or B:).
2. At the DOS prompt, type "A:" (or "B:") and press
3. At the DOS prompt, type "COPY READVLM.TXT PRN" and press
NOTE: If you have a postscript printer, import this file into
a word processing application and print from the application.
------------------------------------------------------------------
CONTENTS
1. Current Issues Concerning the 1.1 NetWare DOS Requester
and Client Kit
2. Setting Up Desktop SNMP on Your Client
3. Description of NetWare DOS Requester Software
4. NET.CFG Parameters for the NetWare DOS Requester Option
5. Additional Information on the NetWare DOS Requester
-------------------------------------------------------------------
1. Current Issues Concerning the 1.1 NetWare DOS Requester and
Client Kit
A> Availability of NetWare Utilities
The following utilities documented in the Workstation
Basics and Installation manual are not included in this
version of the NetWare Client Kit.
NETUSER.EXE "Using NETUSER" page 80
WSUPGRD.EXE "Using the WSUPGRD Utility" page 125
WSUPDATE.EXE "Using the WSUPDATE Utility" page 135
The NETUSER and WSUPGRD utilities are currently available
in NetWare 4 packages only. The WSUPDATE utility is
available in NetWare 3 and NetWare 4 packages only.
B> Documentation Error in NETWARE PROTOCOL and LINK DRIVER
Parameters
The parameter documented in "NetWare DOS Requester
Option" in Appendix B of "Workstation for DOS and MS
Windows" as "NETWARE PROTOCOLS" should be listed as to
"NETWARE PROTOCOL."
The parameter documented in "Link Driver Option" in
Appendix B of "Workstation for DOS and MS Windows" as
"LINK DRIVER=driver_name" should be listed as to "LINK
DRIVER driver_name."
The VLM.EXE file will not recognize these parameters if
you use them as documented in Appendix B.
C> Installing Network Board Drivers to a Workstation Floppy
Diskette on a Workstation with Only One Floppy Drive
When the installation program prompts you to enter the
the drive letter for the target drive where you will find
the network board drivers, enter the drive letter B:.
This way, DOS will recognize your A: drive as drive B:,
and prompt you to insert the driver disk without
disrupting the function of the installation program.
D> Using the Client Installation Program to Copy or Modify
Read-only Files
The Client installation program will prompt you to make
a decision about replacing or not replacing read-
only files. If you choose to not replace the read-only
file, the installation program will try to save a copy of
the necessary changes to the filename with an extension
of .BNW. If a read-only file already exist with the .BNW
extension (for example AUTOEXEC.BNW), then the
installation program will not save changes to any file.
E> Ensuring that Old Client Drivers and Shells are Not Loaded
It is important that after you have run the installation
program, you locate and disable any previous client
driver or shell files from loading. The NetWare DOS
Requester is not compatible with the NETX files.
F> Loading the NetWare DOS Requester Memory Managers Under MS
Windows 3.0
If you experience any problems running MS Windows 3.0
with the NetWare DOS Requester, load the VLM.EXE program
in conventional memory using the command line parameter
/MC. It is also important that if the VLM.EXE file is
loaded into high memory that is loaded before any
other program.
G> Avoid Loading VLMs in Expanded Memory with MS Windows
Don't use the expanded memory option (/ME). Run MS
Windows with the NetWare DOS Requester only if you use
the extended memory option (/MX, preferred) or the
conventional memory option (/MC).
H> Setting Up MS Windows to Support Global Drive Mappings In
MS Windows DOS Boxes
The current version of the VNETWARE.386 2.02 (06/29/93)
software is default enabled to support unique drive
mappings for each DOS box.
To enable MS Windows to support global drive mappings
across multiple DOS Boxes in MS Windows, add the
following heading and command in the MS Windows'
SYSTEM.INI file:
[NETWARE]
NWSharehandles=true
I> Modifying the "TimerCriticalSection" Parameter of Your
MS Windows SYSTEM.INI File
The "TimerCriticalSection" parameter under the [386Enh]
section in the MS Windows SYSTEM.INI file needs to be set
to a value of "10000" or greater. You should add the
following line to the [386Enh] section in the SYSTEM.INI
file, by typing
TimerCriticalSection=
For example:
TimerCriticalSection=10000
J> Documentation Change in PREFERRED WORKGROUP Parameter
The parameter documented as "WORKGROUP NAME" has been
changed to "PREFERRED WORKGROUP" name.
K> If Your MS Windows SYSTEM Directory Is on the Network
The workstation installation creates a SYSTEM directory
on the workstation and copies files into that directory.
Make sure after installation that you copy those files to
the MS Windows SYSTEM directory on the network.
L> Map Roots Paths over 64 Characters in Length
DR-DOS 6.0 and Novell DOS 7 allows paths longer than
64 characters on local drives only. To use paths on
network drives longer than 64 characters, map a root in
the path before you reach the 64 character limit and then
continue your path from the root map.
M> Path Names Must Be Under 64 Characters
DOS limits the number of characters the NetWare DOS
Requester can support in a path name. To use longer
paths, map a root drive and continue from there.
N> Avoid Using DR DOS MOVE Command
The MOVE.EXE file in DOS causes the loss of the fake
root mapping. This is because MOVE obtains the current
path and attempts to perform a CD command on that path.
O> NDIR Error in Compaq DOS 5.0 and DR DOS 6.0
In Compaq DOS 5.0 and DR DOS 6.0, the following commands
produce an error:
NDIR servername/volume:
DIR servername/volume:
CD servername/volume:
This is because DOS treats "/" as an option specifier
when it does its preprocessing. Users can instead map a
drive and use drive letters instead of the server/volume
syntax.
P> The RENDIR.EXE File Does not Update The Current Directory
Structure in DOS
NetWare Core Protocols (NCPs) that use the renamed path
won't function properly. To fix this problem, RENDIR.EXE
will be changed to back up a directory before renaming
the current one and will then forward to it.
Q> IPXODI.COM Version 2.0 or Greater Required
To support the packet burst ODI, the SFT III checksums,
and the NetWare management responder, the IPXNCP.VLM file
requires the IPXODI.COM file version 2.0 or greater to be
loaded with support for checksums and GNMA enabled (the
version and the API support level are treated separately
in IPXODI).
R> Unicode Tables Copied to Workstation
The workstation installation program copies unicode
tables for all languages and code pages to the
workstation. For American English you only need the
following:
UNI_COL.001
UNI_MON.001
1252_UNI.001
UNI_1252.001
437_UNI.001
UNI_437.001
If you use only American English, consider deleting other
unicode tables to conserve disk space.
S> Locating the Necessary Files for Installing a Remote Boot
Client
All of the necessary files you need to setup a NetWare
Remote Boot Client are located in a directory called
"RPL" on Diskette 1 (WSDOS_1).
Refer to Chapter 9, "Booting DOS Workstations from the
Network" for instrcutions on installation and use of the
RPL files.
T> Updating Packet Burst for Slow Data Transfer Over Wide Area
Network (WAN) Links
If you experience any slowing in data transfer over wide
area network (WAN) links when connected to a server with
Packet Burst support, first update your copy of the
PBURST.NLM file or run a fix for the Packet Burst support
built-in to NetWare 3.12 and 4.01.
NETWARE VERSION PATCH DIRECTORY FILE FORUM
--------------- ----- --------- ---- -----
NetWare 3.12 PBWANFIX.NLM PBWANFIX.312 DOSUP9.EXE NOVFILES
NetWare 4.01 PBWANFIX.NLM PBWANFIX.401 DOSUP9.EXE NOVFILES
NetWare 3.xx PBURST.NLM PBURST DOSUP9.EXE NOVFILES
and ealier
You can obtain a copy of the PBURST.NLM file containing the patches
you need from your NetWare Distributor or by accessing the NOVFILES
forum on Compuserve or the Internet TechServer. If you cannot
obtain a copy of these files, contact a Novell Tech Support person
at 1-800-NetWare or 1-801-429-5588.
U> Logging Into a Personal NetWare Server
Windows: Use the NetWare User Tools for Windows to log in
to a Personal NetWare server. Ensure that the "Personal"
checkbox is marked in the "Resource Display Option" box
under NetWare Settings in the NetWare User Tools. If the
"Personal" checkbox is not marked, Personal NetWare
resources will not be accessable.
DOS: Use the NET.EXE utility provided in the Personal
NetWare package to log in and access Personal NetWare
resources in DOS. Ensure the following:
þ The PNW.VLM file is loaded
(Check the NETWARE PROTOCOL line in your NET.CFG file)
þ The PNW.DLL file is copied to the WINDOWS\SYSTEM
directory
þ The NET.EXE file is copied to your NetWare
workstation directory (default is C:\NWCLIENT)
þ The NETC.MSG file is copied to the NLS\ENGLISH
directory under the NetWare workstation directory.
2. Setting Up Desktop SNMP on Your Client
CONTENTS
I. Introduction to Desktop SNMP
II. Components of Desktop SNMP
III. Enabling Desktop SNMP Services
IV. Sample NET.CFG File for Desktop SNMP Services
V. Conventional Memory Usage
VI. Unloading the Desktop SNMP Software
VII. Where to Go from Here
-------------------------------------------------------------------
I. Introduction to Desktop SNMP
Simple Network Management Protocol (SNMP) is an
industry-standard protocol for communication between a network
management console and the network devices that the console is
to monitor. This chapter explains how to enable desktop SNMP
services on your computer, and how to modify the NET.CFG file
to implement additional SNMP options.
The chapter is primarily for supervisors of networks in which
an SNMP-based network management system is implemented.
The Desktop SNMP agent provided with the NetWare Client
Kit 1.1, allows you to manage your NetWare clients from
Novell's NMS (NetWare Management System) and other
industry-standard SNMP management consoles.
II. Components of Desktop SNMP
The NetWare Client Kit 1.1 includes the following components
for the Desktop SNMP agent:
HRMIB.EXE - the Host Resources manager, which collects
information about a computer that is
running DOS on the network.
HRMIB.INI - the configuration file for the HRMIB.EXE
file.
WSSNMP.VLM - Desktop SNMP module, which includes support
for MIB-II System and SNMP groups
WSREG.VLM - MIB registration module
WSASN1.VLM - ASN.1 translation module
WSTRAP.VLM - Trap module
MIB2IF.VLM - MIB-II interface groups support
MIB2PROT.VLM - MIB-II support for the TCP/IP groups
STPUDP.COM - Transport provider module for UDP/IP
STPIPX.COM - Transport provider for IPX
These files are copied the client directory on your
computer (default is C:\NWCLIENT.)
NOTE: Refer to the documentation provided with the SNMP
management software for information on specific configurations
for the management software.
III. Enabling Desktop SNMP Services
A. You can set up Desktop SNMP on your client to act as an
SNMP agent for any SNMP-based management consoles.
To set up Desktop SNMP Agent services on your client, you will
need to perform the following tasks:
þ Install the NetWare Client 1.1 on your client computer.
þ Modify the NET.CFG file to reflect the presence of
Desktop SNMP .VLM files, and then set the required .VLM
file options in the NET.CFG file. See section "IV,"
"Sample NET.CFG File for Desktop SNMP Services" in this
file.
þ Set the "TRAP TARGET" address of the NetWare Services
Management (NSM) consoles or other SNMP-based managers in
the NET.CFG file. See section "IV," "Sample NET.CFG File
for Desktop SNMP Services" in this file.
þ Modify the STARTNET.BAT file to load either STPIPX.COM or
STPUDP.COM.
þ Load the NetWare client software by running the
STARTNET.BAT file in the client directory.
NOTE: You must have either IPX or IP transport installed
on your system. IPX transport (IPXODI) is provided by the
NetWare DOS requester provided in the NetWare Client
Kit 1.1. IP transport for UDP/IP is provided by LAN
Workplace for DOS 4.1 (LAN Workplace). You can use both
types of transport on a single client.
By default, desktop SNMP services are not enabled when you
install the NetWare client. To enable desktop SNMP services,
do the following:
1. Ensure that the Desktop SNMP files are copied to the
client directory (default is C:\NWCLIENT).
2. Modify the NET.CFG file to load the Desktop SNMP .VLM
file suite.
IMPORTANT: When the Desktop SNMP .VLM file suite is
loaded, the WSSNMP.VLM must be loaded first. The
WSTRAP.VLM and WSREG.VLM files must be loaded prior to
loading the WSASN1.VLM file.
To load the Desktop SNMP .VLM file suite, modify the
NET.CFG file on your client in either of the following
two ways:
a. To load Desktop SNMP in addition to the NetWare
DOS Requester software, add the following lines to
the NET.CFG file under the "NetWare DOS Requester"
section:
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
b. To load only Desktop SNMP, without the NetWare
DOS Requester modules, add the following lines to
the NET.CFG file under the "NetWare DOS Requester"
section:
USE DEFAULTS = OFF
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
3. Modify client configuration files for setting up
Desktop SNMP. See "Desktop SNMP Option" in Appendix B of
"Workstation for DOS and MS Windows" for information and
details on how to set up and configure your client for
the following Desktop SNMP parameters:
þ Transport providers
þ MIB-II support
þ Community names
þ Asynchronous timeout
4. Modify the C:\NWCLIENT\STARTNET.BAT file to load the
Desktop SNMP transport files. Add the following commands
in the STARTNET.BAT after the line which loads the
VLM.EXE file.
If you are using IPX transport, add the following
line by typing:
STPIPX
If you are using UDP/IP transport, add the following
line by typing:
STPUDP
NOTE: You can add both commands if your client uses
both IPX and UDP/IP transport.
NOTE: If you are running LAN Workplace, make sure you are
do not load the SNMP.EXE file, provided with the LAN
Workplace package. The installation program for LAN
Workplace creates a file called "LANWP.BAT" that loads
the LAN Workplace software. Check this file for a line
reading "SNMP." It should be listed directly following
the line "TCPIP." If the SNMP line is present, delete it
or comment it out.
5. Use DOS SET command at the system prompt or in a batch
file to set the correct time zone for your area, as
follows:
SET TZ = time_zone
Refer to your DOS manual for the exact syntax for your
particular time zone.
If the time zone is not set in your computer's
environment, traps for SNMP may report an incorrect time.
6. Reboot your computer. The VLM manager will load the
Desktop SNMP .VLM file suite along with any other .VLM
files your client is configured to load.
B. The Desktop SNMP workstation support includes the
HRMIB.EXE and HRMIB.INI files. These files enable the console
to view data collected at each Desktop SNMP workstation. The
files are located in the client directory (default is
C:\NWCLIENT).
To enable the SNMP console to view data about a Desktop SNMP
workstation, you will need to perform the following tasks:
þ Install the NetWare Client 1.1 on your client computer.
þ Load the HRMIB.EXE software on the client you want data
collected from.
1. Ensure that the HRMIB.EXE and HRMIB.INI files exist
in your client directory (default is C:\NWCLIENT).
2. Load the HRMIB.EXE file by typing
HRMIB.EXE
NOTE: Ensure that the DOS SNMP Agent softwared is set up
and loaded on your client before loading the HRMIB.EXE
file.
3. Configuring the HRMIB.INI File
The Host Resources MIB does not return information about
devices attached to the host computers, such as printers,
modems, and tape drives. If the network management
console is to view details of such devices, you must
list them in the HRMIB.INI file.
The HRMIB.INI file is located in the directory to which
you installed the NetWare client (C:\NWCLIENT by default)
on your computer. Use a ASCII text editor to enter a
short description of each device. For example:
Sample configuration file (HRMIB.INI) for HRMIB.EXE
# List of all printers connected to host
[printers]
HP LaserJet IIIp on LPT1:
NEC P20 on LPT2:
# List of all modems connected to host
[modems]
Hayes Optima 144 on COM1:
# List of all tape drives connected to host
[tapes]
Colorado DJ10
HP 35480A SCSI DAT (4-8 GB)
# other devices obtained via DOS APIs
IV. Sample NET.CFG File for Desktop SNMP Services
A sample of the NET.CFG for SNMP agent services is as follows:
Link Driver NE2000
PORT 300
INT 3
FRAME Ethernet_802.2
MEM D0000
NetWare DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
VLM = MIB2PROT.VLM
Desktop SNMP
enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Suzanne Morley x893"
sysLocation = "Building 2"
sysContact = "[email protected]"
snmpEnableAuthenTraps = on
Transport Provider IPX
trap target = ab123456:0123456789ab
trap target = cd654321:ba9876543210
Transport Provider UDP
trap target = 999.88.77.66
trap target = 888.11.22.33
V. Conventional Memory Usage
If you are willing to trade conventional memory for
performance, you can load one or more Desktop SNMP .VLM files
in conventional memory.
To load all .VLM files in conventional memory, use the VLM /MC
switch when running the VLM manager.
To load a Desktop SNMP .VLM files in conventional memory,
place lines of the following form in the NET.CFG file:
Netware DOS Requester
VLM = vlm_name.VLM
LOAD LOW vlm_name = ON
For example, to load Desktop SNMP while loading the WSASN1.VLM
and WSREG.VLM files in conventional memory, place the
following lines in the NET.CFG file:
Netware DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
Load low WSREG = ON
Load low WSASN1 = ON
VI. Unloading the Desktop SNMP Software
The following commands, issued in the order given, unload
Desktop SNMP.
NOTE: The VLM -u command unloads all VLM files, not just
Desktop SNMP.
1. Unload STPUDP if UDP/IP support has been loaded:
STPUDP -u
2. Unload STPIPX if IPX support has been loaded:
STPIPX -u
3. Unload all VLM files:
VLM -u
IMPORTANT: Always unload the modules in reverse order from the
order in which you loaded them. For example, if you loaded the
VLM manager followed by STPUDP and then STPIPX, you must
unload them as follows:
STPIPX -u
STPUDP -u
VLM -u
Unloading the modules in any order other than reverse order
causes an error.
VII. Where to Go from Here
After you have completed the initial configuration of the
desktop SNMP agent, you can further modify the Desktop SNMP
options in the NET.CFG file to meet your specific network
requirements. Refer to"Desktop SNMP Option" in Appendix B of
"Workstation for DOS and MS Windows" for a description of
these modifications.
3. Description of NetWare DOS Requester Software
The NetWare DOS Requester consists of a number of files that
provide NetWare support for a DOS client. Unlike previous
versions of the NetWare DOS client, the Requester is built on
a number of Virtual Loadable Modules (VLMs). The VLM.EXE (VLM
manager) is responsible for loading the required modules.
NOTE: The NetWare DOS Requester is NOT compatible with
NETX.COM or NETX.EXE. Use NETX.VLM for compatibility with
shell calls.
The following table lists the current core modules in their
default load order. The table also includes descriptions,
default values, and flags indicating whether the module is
"Required" or "Optional" for each of NetWare Directory
Services or bindery services.
MODULE DESCRIPTION NDS BIND PNW
====== =========== === ==== ===
CONN.VLM Connection table manager R R R
IPXNCP.VLM Transport protocol R R R
implementation using IPX
TRAN.VLM Transport protocol multiplexor R R R
SECURITY.VLM NetWare enhanced security O O O
NDS.VLM NetWare protocol implementation R O O
using Directory Services
BIND.VLM NetWare protocol implementation O R O
using the Bindery
PNW.VLM NetWare protocol implementation O O R
using Personal NetWare
NWP.VLM NetWare protocol multiplexor R R R
FIO.VLM File Input/Output R R R
PRINT.VLM Printer Redirection O O O
GENERAL.VLM Miscellaneous functions for R R R
NETX.VLM and REDIR.VLM
REDIR.VLM DOS redirector R R R
NETX.VLM NetWare shell compatibility O O O
RSA.VLM RSA encryption for directory O O O
services reauthentication
WSSNMP.VLM Desktop SNMP module, which O O O
includes support for MIB-II
System and SNMP groups
WSREG.VLM MIB registration module O O O
WSASN1.VLM ASN.1 translation module O O O
WSTRAP.VLM Trap module O O O
MIB2IF.VLM MIB-II interface groups support O O O
MIB2PROT.VLM MIB-II support for the O O O
TCP/IP groups
AUTO.VLM Auto-reconnect/auto-retry O O O
NMR.VLM NetWare management responder O O O
4. NET.CFG File Parameter for the NetWare DOS Requester Option
The following table lists the parameters for the various
modules of the NetWare DOS Requester.
The following list is complete. Any parameters which may
have been used previously by the NetWare DOS Requester but are
not listed here are invalid.
Parameter/Default Minimum Maximum Module
SET STATION TIME = ON VLM.EXE
USE DEFAULTS = ON -- -- VLM.EXE
VLM =
EXCLUDE VLM =
MESSAGE LEVEL = 1 0 4 VLM.EXE
0 = V_LEVEL_STD; always display message and critical errors
1 = V_LEVEL_WARNING; display warning type messages
2 = V_LEVEL_PROG; display the program load message
3 = V_LEVEL_CONFIG; display configuration information
4 = V_LEVEL_DIAG; display diagnostic information
NETWARE PROTOCOL =
Note: The
protocols to be used (NDS.VLM, BIND.VLM and PNW.VLM)
by the Requester in the order of their priority.
Each protocol is separated by a comma or space
in the list (NDS,BIND,PNW). If you exclude any one of
the protocol .VLM files from the list, the excluded
.VLM file will not load.
CONNECTIONS = 8 2 50 CONN.VLM
FIO.VLM
NDS.VLM
SECURITY.VLM
AUTO.VLM
AVERAGE NAME LENGTH = 48 2 48 CONN.VLM
MAX TASKS = 31 5 254 CONN.VLM
LOAD LOW CONN = ON -- -- CONN.VLM
LOAD CONN TABLE LOW = OFF -- -- CONN.VLM
CHECKSUM = 1 0 3 IPXNCP.VLM
NWP.VLM
0 = disabled
1 = enabled but not preferred
2 = enabled and preferred
3 = required
LARGE INTERNET PACKETS = ON -- -- IPXNCP.VLM
NWP.VLM
LOAD LOW IPXNCP = ON -- -- IPXNCP.VLM
HANDLE NET ERRORS = ON -- -- IPXNCP.VLM
PREFERRED TREE =
NAME CONTEXT = "
Note: Quotation marks are required.
PREFERRED SERVER =
MESSAGE TIMEOUT = 0 0 10000 NWP.VLM
SIGNATURE LEVEL = 1 0 3 NWP.VLM
SECURITY.VLM
0 = disabled
1 = enabled but not preferred
2 = preferred
3 = required
NOTE: This parameter designates the level of enhanced security
support. Enhanced security includes the use of a message
digest algorithm and a per-connection/pre-request
session state for increased protection against intruder
attacks. When this parameter is set to 0 (disabled),
the SECURITY.VLM will not load.
CACHE BUFFERS = 5 0 64 FIO.VLM
CACHE BUFFER SIZE =(Media dependent) -- FIO.VLM
CACHE WRITES = ON -- -- FIO.VLM
TRUE COMMIT = OFF -- -- FIO.VLM
PB BUFFERS = 3 0 10 FIO.VLM
IPXNCP.VLM
0 = off
nonzero = on
PBURST READ WINDOW SIZE = 16 2 64 FIO.VLM
PBURST WRITE WINDOW SIZE = 10 2 64 FIO.VLM
PRINT HEADER = 64 0 1024 PRINT.VLM
PRINT TAIL = 16 0 1024 PRINT.VLM
PRINT BUFFER SIZE = 64 0 256 PRINT.VLM
NETWORK PRINTERS = 3 0 9 PRINT.VLM
NOTE: If set to 0, PRINT.VLM will not load.
LOCAL PRINTERS = 3 0 9 PRINT.VLM
FIRST NETWORK DRIVE =
NETX.VLM
NOTE: If FIRST NETWORK DRIVE is not specified, it will default
to the first available drive letter.
SEARCH MODE = 1 0 7 GENERAL.VLM
READ ONLY COMPATIBILITY = ON -- -- REDIR.VLM
SHOW DOTS = OFF -- -- REDIR.VLM
DOS NAME = MSDOS 1 5 chars NETX.VLM
GENERAL.VLM
LONG MACHINE TYPE = IBM_PC 1 6 chars NETX.VLM
GENERAL.VLM
SHORT MACHINE TYPE = IBM 1 4 chars NETX.VLM
GENERAL.VLM
AUTO RECONNECT = ON -- -- AUTO.VLM
NDS.VLM
Note: When this parameter is OFF, the AUTO.VLM load fails at
pre-initialization time.
AUTO RETRY = 0 0 3640 AUTO.VLM
AUTO LARGE TABLE = OFF -- -- AUTO.VLM
Note: When this parameter is OFF, the user name and password
maximum lengths are 16 chars each for auto reconnect.
BIND RECONNECT = OFF -- -- AUTO.VLM
BIND.VLM
BROADCAST RETRIES = 2 0 255 PNW.VLM
BROADCAST SEND DELAY = 0 0 255 PNW.VLM
BROADCAST TIMEOUT = 3 1 255 PNW.VLM
MOBILE MODE = 0 0 65535 PNW.VLM
RESPONDER = ON -- -- PNW.VLM
PREFERRED WORKGROUP =
WORKGROUP NET =
MINIMUM TIME TO NET =
5> Additional Information on the NetWare DOS Requester
A> Loading VLMs from a Directory Other Than the Current
Directory
The current directory is used for VLMs. To load VLMs from
another directory, use the "VLM =" command in the NET.CFG
file.
For example
VLM=C:\NWCLIENT\CONN.VLM
B> Specifying a NET.CFG File Outside the Current Directory
To specify a path for the NET.CFG file, type a command
similar to the following (or put the command in
AUTOEXEC.BAT):
VLM /C=C:\NWCLIENT\NET.CFG
C> Understanding the Load Order for VLM Software
The VLM software must be loaded in a specific order to
operate correctly. For example, the NWP.VLM file is a
multiplexor for NetWare protocol modules. Therefore, you
should load the NetWare protocols (NDS.VLM and BIND.VLM)
before the NWP.VLM file. The Load order for the VLM
software is as follows:
CONN.VLM
IPXNCP.VLM
TRAN.VLM
SECURITY.VLM
NDS.VLM
BIND.VLM
PNW.VLM
NWP.VLM
FIO.VLM
PRINT.VLM
GENERAL.VLM
REDIR.VLM
NETX.VLM
See section "2. Description of NetWare DOS Requester
Modules," in this README file for a description of each
of these modules.
D> Disabling Specific VLM Software
Disable specific VLM software in one of the following
ways:
1> Rename the module with an extension other than .VLM.
Use the NETWARE PROTOCOL parameter. See section 3,
"Configurable Parameters" in this README for
information on how to use this parameter.
2> Use the EXCLUDE VLM parameter. See section 3,
"Configurable Parameters" in this README for
information on how to use this parameter.
3> Rename the module with a different extension (for
example,.SAV).
4> Delete the module (not recommended).
For example, to configure your workstation for running on
a NetWare 3.x network only, type one of the following in
your NET.CFG file:
NETWARE DOS REQUESTER
NETWARE PROTOCOL BIND
or,
NETWARE DOS REQUESTER
EXCLUDE VLM = NDS.VLM
EXCLUDE VLM = PNW.VLM
E> Specifying the Load Order for Specific NetWare protocols
Use the "NETWARE PROTOCOL" parameter to specify the
NetWare protocol VLM software (NDS.VLM, BIND.VLM, and
PNW.VLM) you wish to load, in the order you wish to
load them:
NETWARE PROTOCOL = NDS,BIND,PNW
F> Using the NETX.COM File or Related Shells with the
VLM Software
You cannot load NETX.COM and NETX.VLM simultaneously. Use
the NETX.VLM file instead of the NETX.COM file or related
shells such as NET3.COM, NETX.EXE, BNETX.EXE,
XMSNETX.EXE, etc.. These files conflict with the
REDIR.VLM file; the REDIR.VLM will not load if the
NETX.COM file is loaded.
However, the NETX.VLM file is designed to replace
NETX.COM and related NETX shells, and is compatible with
the NetWare DOS Requester.
G> The IPXNCP.VLM File is not a Replacement for the IPXODI.COM
File
The IPXNCP.VLM requires the IPXODI.COM File to be loaded
in order to operate.
H> The Personal NetWare Client Software Components are Now
Included in The NetWare Client Kit
The PNW.VLM file is now included in the Client Kit. This
will allow you to connect to a Personal NetWare Server
from your client. However, the Personal NetWare utilities
are not included.
I> First Available Drive Is Different
The conventional NetWare Shell for DOS used drives after
the LASTDRIVE parameter; NetWare DOS Requester starts
using the first available drive before the LASTDRIVE
parameter.
Consequently, users who had, for example, a LASTDRIVE=G:
setting in their CONFIG.SYS are used to seeing drive H:
as the first NetWare drive rather than drive F:. To
maintain compatibility with existing batch files, you may
want to add the command like "FIRST NETWORK DRIVE = H"
under the NetWare DOS Requester portion of the NET.CFG
file. Otherwise, batch files assuming drive H: as the
first drive must be altered.
J> Login Drive Prompt Appears To Be a Root Mapped Drive
Because NetWare DOS Requester is a redirector on the
back-end of DOS, no directory path can be in the drive
structure maintained by DOS when the parent of the
directory is unaccessible.
This is the case with an unauthenticated connection and
the drive mapped to the SYS:LOGIN directory. Users see
"F:\>" instead of "F:\LOGIN>" when they first load the
DOS client software.
K> Search Mode Now Uses the DOS ENVIRONMENT Variable
The "SEARCH MODE" function uses the "PATH" DOS
ENVIRONMENT variable rather than the public search mode
table provided in the NETX.VLM file. You will experience
no change unless users corrupt their workstation
environment. If you exceed the PATH limitation, your
search drive mappings will not be included in the PATH.
L> Difference In Diagnostic Information Reported In the
NETX.VLM File Compared to the NETX.COM and Related Files
Some of the current diagnostic information supported
in the NETX.COM file will appear to be invalid in the
NETX.VLM file. This is because the NetWare DOS Requester
is responsible for much of the diagnostics information
previously maintained in the NetWare Shell for DOS. Some
of the information maintained in the diagnostics
responder will not be updated. Such information includes
the following:
Bad reply header (InvalidReplyHeaderCount)
Bad slot (InvalidSlotCount)
Bad sequence number
(InvalidSequenceNumberCount)
No router found (NoRouterFoundCount)
Request in process (BeingProcessedCount)
Bad server slot (InvalidSlotFromServerCount)
Bad net address (NetworkGoneCount)
Bad local address (BadLocalAddressCount)
Allocate slot errors
(AllocateSlotCannotFindRoute,
AllocateNoSlotsAvailable, AllocateServerIsDown)
The NetWare Management Responder (NMR.VLM) file will now
provide diagnostic information similar to that mentioned
above.
------------------------------------------------------------------
DISCLAIMER
Novell, Inc., makes no representations or warranties with respect
to any NetWare software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose.
Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc. Further, Novell reserves
the right to discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of recreating lost data, the
cost of any substitute equipment or program, or claims by any party
other than you.
Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at
the discretion of Novell.
NETWARE DOS REQUESTER AND CLIENT KIT README (12/09/93)
To print this file to a local printer,
1. Insert the workstation diskette containing this file into
drive A: (or B:).
2. At the DOS prompt, type "A:" (or "B:") and press
3. At the DOS prompt, type "COPY READVLM.TXT PRN" and press
NOTE: If you have a postscript printer, import this file into
a word processing application and print from the application.
------------------------------------------------------------------
CONTENTS
1. Current Issues Concerning the 1.1 NetWare DOS Requester
and Client Kit
2. Setting Up Desktop SNMP on Your Client
3. Description of NetWare DOS Requester Software
4. NET.CFG Parameters for the NetWare DOS Requester Option
5. Additional Information on the NetWare DOS Requester
-------------------------------------------------------------------
1. Current Issues Concerning the 1.1 NetWare DOS Requester and
Client Kit
A> Availability of NetWare Utilities
The following utilities documented in the Workstation
Basics and Installation manual are not included in this
version of the NetWare Client Kit.
NETUSER.EXE "Using NETUSER" page 80
WSUPGRD.EXE "Using the WSUPGRD Utility" page 125
WSUPDATE.EXE "Using the WSUPDATE Utility" page 135
The NETUSER and WSUPGRD utilities are currently available
in NetWare 4 packages only. The WSUPDATE utility is
available in NetWare 3 and NetWare 4 packages only.
B> Documentation Error in NETWARE PROTOCOL and LINK DRIVER
Parameters
The parameter documented in "NetWare DOS Requester
Option" in Appendix B of "Workstation for DOS and MS
Windows" as "NETWARE PROTOCOLS" should be listed as to
"NETWARE PROTOCOL."
The parameter documented in "Link Driver Option" in
Appendix B of "Workstation for DOS and MS Windows" as
"LINK DRIVER=driver_name" should be listed as to "LINK
DRIVER driver_name."
The VLM.EXE file will not recognize these parameters if
you use them as documented in Appendix B.
C> Installing Network Board Drivers to a Workstation Floppy
Diskette on a Workstation with Only One Floppy Drive
When the installation program prompts you to enter the
the drive letter for the target drive where you will find
the network board drivers, enter the drive letter B:.
This way, DOS will recognize your A: drive as drive B:,
and prompt you to insert the driver disk without
disrupting the function of the installation program.
D> Using the Client Installation Program to Copy or Modify
Read-only Files
The Client installation program will prompt you to make
a decision about replacing or not replacing read-
only files. If you choose to not replace the read-only
file, the installation program will try to save a copy of
the necessary changes to the filename with an extension
of .BNW. If a read-only file already exist with the .BNW
extension (for example AUTOEXEC.BNW), then the
installation program will not save changes to any file.
E> Ensuring that Old Client Drivers and Shells are Not Loaded
It is important that after you have run the installation
program, you locate and disable any previous client
driver or shell files from loading. The NetWare DOS
Requester is not compatible with the NETX files.
F> Loading the NetWare DOS Requester Memory Managers Under MS
Windows 3.0
If you experience any problems running MS Windows 3.0
with the NetWare DOS Requester, load the VLM.EXE program
in conventional memory using the command line parameter
/MC. It is also important that if the VLM.EXE file is
loaded into high memory that is loaded before any
other program.
G> Avoid Loading VLMs in Expanded Memory with MS Windows
Don't use the expanded memory option (/ME). Run MS
Windows with the NetWare DOS Requester only if you use
the extended memory option (/MX, preferred) or the
conventional memory option (/MC).
H> Setting Up MS Windows to Support Global Drive Mappings In
MS Windows DOS Boxes
The current version of the VNETWARE.386 2.02 (06/29/93)
software is default enabled to support unique drive
mappings for each DOS box.
To enable MS Windows to support global drive mappings
across multiple DOS Boxes in MS Windows, add the
following heading and command in the MS Windows'
SYSTEM.INI file:
[NETWARE]
NWSharehandles=true
I> Modifying the "TimerCriticalSection" Parameter of Your
MS Windows SYSTEM.INI File
The "TimerCriticalSection" parameter under the [386Enh]
section in the MS Windows SYSTEM.INI file needs to be set
to a value of "10000" or greater. You should add the
following line to the [386Enh] section in the SYSTEM.INI
file, by typing
TimerCriticalSection=
For example:
TimerCriticalSection=10000
J> Documentation Change in PREFERRED WORKGROUP Parameter
The parameter documented as "WORKGROUP NAME" has been
changed to "PREFERRED WORKGROUP" name.
K> If Your MS Windows SYSTEM Directory Is on the Network
The workstation installation creates a SYSTEM directory
on the workstation and copies files into that directory.
Make sure after installation that you copy those files to
the MS Windows SYSTEM directory on the network.
L> Map Roots Paths over 64 Characters in Length
DR-DOS 6.0 and Novell DOS 7 allows paths longer than
64 characters on local drives only. To use paths on
network drives longer than 64 characters, map a root in
the path before you reach the 64 character limit and then
continue your path from the root map.
M> Path Names Must Be Under 64 Characters
DOS limits the number of characters the NetWare DOS
Requester can support in a path name. To use longer
paths, map a root drive and continue from there.
N> Avoid Using DR DOS MOVE Command
The MOVE.EXE file in DOS causes the loss of the fake
root mapping. This is because MOVE obtains the current
path and attempts to perform a CD command on that path.
O> NDIR Error in Compaq DOS 5.0 and DR DOS 6.0
In Compaq DOS 5.0 and DR DOS 6.0, the following commands
produce an error:
NDIR servername/volume:
DIR servername/volume:
CD servername/volume:
This is because DOS treats "/" as an option specifier
when it does its preprocessing. Users can instead map a
drive and use drive letters instead of the server/volume
syntax.
P> The RENDIR.EXE File Does not Update The Current Directory
Structure in DOS
NetWare Core Protocols (NCPs) that use the renamed path
won't function properly. To fix this problem, RENDIR.EXE
will be changed to back up a directory before renaming
the current one and will then forward to it.
Q> IPXODI.COM Version 2.0 or Greater Required
To support the packet burst ODI, the SFT III checksums,
and the NetWare management responder, the IPXNCP.VLM file
requires the IPXODI.COM file version 2.0 or greater to be
loaded with support for checksums and GNMA enabled (the
version and the API support level are treated separately
in IPXODI).
R> Unicode Tables Copied to Workstation
The workstation installation program copies unicode
tables for all languages and code pages to the
workstation. For American English you only need the
following:
UNI_COL.001
UNI_MON.001
1252_UNI.001
UNI_1252.001
437_UNI.001
UNI_437.001
If you use only American English, consider deleting other
unicode tables to conserve disk space.
S> Locating the Necessary Files for Installing a Remote Boot
Client
All of the necessary files you need to setup a NetWare
Remote Boot Client are located in a directory called
"RPL" on Diskette 1 (WSDOS_1).
Refer to Chapter 9, "Booting DOS Workstations from the
Network" for instrcutions on installation and use of the
RPL files.
T> Updating Packet Burst for Slow Data Transfer Over Wide Area
Network (WAN) Links
If you experience any slowing in data transfer over wide
area network (WAN) links when connected to a server with
Packet Burst support, first update your copy of the
PBURST.NLM file or run a fix for the Packet Burst support
built-in to NetWare 3.12 and 4.01.
NETWARE VERSION PATCH DIRECTORY FILE FORUM
--------------- ----- --------- ---- -----
NetWare 3.12 PBWANFIX.NLM PBWANFIX.312 DOSUP9.EXE NOVFILES
NetWare 4.01 PBWANFIX.NLM PBWANFIX.401 DOSUP9.EXE NOVFILES
NetWare 3.xx PBURST.NLM PBURST DOSUP9.EXE NOVFILES
and ealier
You can obtain a copy of the PBURST.NLM file containing the patches
you need from your NetWare Distributor or by accessing the NOVFILES
forum on Compuserve or the Internet TechServer. If you cannot
obtain a copy of these files, contact a Novell Tech Support person
at 1-800-NetWare or 1-801-429-5588.
U> Logging Into a Personal NetWare Server
Windows: Use the NetWare User Tools for Windows to log in
to a Personal NetWare server. Ensure that the "Personal"
checkbox is marked in the "Resource Display Option" box
under NetWare Settings in the NetWare User Tools. If the
"Personal" checkbox is not marked, Personal NetWare
resources will not be accessable.
DOS: Use the NET.EXE utility provided in the Personal
NetWare package to log in and access Personal NetWare
resources in DOS. Ensure the following:
þ The PNW.VLM file is loaded
(Check the NETWARE PROTOCOL line in your NET.CFG file)
þ The PNW.DLL file is copied to the WINDOWS\SYSTEM
directory
þ The NET.EXE file is copied to your NetWare
workstation directory (default is C:\NWCLIENT)
þ The NETC.MSG file is copied to the NLS\ENGLISH
directory under the NetWare workstation directory.
2. Setting Up Desktop SNMP on Your Client
CONTENTS
I. Introduction to Desktop SNMP
II. Components of Desktop SNMP
III. Enabling Desktop SNMP Services
IV. Sample NET.CFG File for Desktop SNMP Services
V. Conventional Memory Usage
VI. Unloading the Desktop SNMP Software
VII. Where to Go from Here
-------------------------------------------------------------------
I. Introduction to Desktop SNMP
Simple Network Management Protocol (SNMP) is an
industry-standard protocol for communication between a network
management console and the network devices that the console is
to monitor. This chapter explains how to enable desktop SNMP
services on your computer, and how to modify the NET.CFG file
to implement additional SNMP options.
The chapter is primarily for supervisors of networks in which
an SNMP-based network management system is implemented.
The Desktop SNMP agent provided with the NetWare Client
Kit 1.1, allows you to manage your NetWare clients from
Novell's NMS (NetWare Management System) and other
industry-standard SNMP management consoles.
II. Components of Desktop SNMP
The NetWare Client Kit 1.1 includes the following components
for the Desktop SNMP agent:
HRMIB.EXE - the Host Resources manager, which collects
information about a computer that is
running DOS on the network.
HRMIB.INI - the configuration file for the HRMIB.EXE
file.
WSSNMP.VLM - Desktop SNMP module, which includes support
for MIB-II System and SNMP groups
WSREG.VLM - MIB registration module
WSASN1.VLM - ASN.1 translation module
WSTRAP.VLM - Trap module
MIB2IF.VLM - MIB-II interface groups support
MIB2PROT.VLM - MIB-II support for the TCP/IP groups
STPUDP.COM - Transport provider module for UDP/IP
STPIPX.COM - Transport provider for IPX
These files are copied the client directory on your
computer (default is C:\NWCLIENT.)
NOTE: Refer to the documentation provided with the SNMP
management software for information on specific configurations
for the management software.
III. Enabling Desktop SNMP Services
A. You can set up Desktop SNMP on your client to act as an
SNMP agent for any SNMP-based management consoles.
To set up Desktop SNMP Agent services on your client, you will
need to perform the following tasks:
þ Install the NetWare Client 1.1 on your client computer.
þ Modify the NET.CFG file to reflect the presence of
Desktop SNMP .VLM files, and then set the required .VLM
file options in the NET.CFG file. See section "IV,"
"Sample NET.CFG File for Desktop SNMP Services" in this
file.
þ Set the "TRAP TARGET" address of the NetWare Services
Management (NSM) consoles or other SNMP-based managers in
the NET.CFG file. See section "IV," "Sample NET.CFG File
for Desktop SNMP Services" in this file.
þ Modify the STARTNET.BAT file to load either STPIPX.COM or
STPUDP.COM.
þ Load the NetWare client software by running the
STARTNET.BAT file in the client directory.
NOTE: You must have either IPX or IP transport installed
on your system. IPX transport (IPXODI) is provided by the
NetWare DOS requester provided in the NetWare Client
Kit 1.1. IP transport for UDP/IP is provided by LAN
Workplace for DOS 4.1 (LAN Workplace). You can use both
types of transport on a single client.
By default, desktop SNMP services are not enabled when you
install the NetWare client. To enable desktop SNMP services,
do the following:
1. Ensure that the Desktop SNMP files are copied to the
client directory (default is C:\NWCLIENT).
2. Modify the NET.CFG file to load the Desktop SNMP .VLM
file suite.
IMPORTANT: When the Desktop SNMP .VLM file suite is
loaded, the WSSNMP.VLM must be loaded first. The
WSTRAP.VLM and WSREG.VLM files must be loaded prior to
loading the WSASN1.VLM file.
To load the Desktop SNMP .VLM file suite, modify the
NET.CFG file on your client in either of the following
two ways:
a. To load Desktop SNMP in addition to the NetWare
DOS Requester software, add the following lines to
the NET.CFG file under the "NetWare DOS Requester"
section:
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
b. To load only Desktop SNMP, without the NetWare
DOS Requester modules, add the following lines to
the NET.CFG file under the "NetWare DOS Requester"
section:
USE DEFAULTS = OFF
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
3. Modify client configuration files for setting up
Desktop SNMP. See "Desktop SNMP Option" in Appendix B of
"Workstation for DOS and MS Windows" for information and
details on how to set up and configure your client for
the following Desktop SNMP parameters:
þ Transport providers
þ MIB-II support
þ Community names
þ Asynchronous timeout
4. Modify the C:\NWCLIENT\STARTNET.BAT file to load the
Desktop SNMP transport files. Add the following commands
in the STARTNET.BAT after the line which loads the
VLM.EXE file.
If you are using IPX transport, add the following
line by typing:
STPIPX
If you are using UDP/IP transport, add the following
line by typing:
STPUDP
NOTE: You can add both commands if your client uses
both IPX and UDP/IP transport.
NOTE: If you are running LAN Workplace, make sure you are
do not load the SNMP.EXE file, provided with the LAN
Workplace package. The installation program for LAN
Workplace creates a file called "LANWP.BAT" that loads
the LAN Workplace software. Check this file for a line
reading "SNMP." It should be listed directly following
the line "TCPIP." If the SNMP line is present, delete it
or comment it out.
5. Use DOS SET command at the system prompt or in a batch
file to set the correct time zone for your area, as
follows:
SET TZ = time_zone
Refer to your DOS manual for the exact syntax for your
particular time zone.
If the time zone is not set in your computer's
environment, traps for SNMP may report an incorrect time.
6. Reboot your computer. The VLM manager will load the
Desktop SNMP .VLM file suite along with any other .VLM
files your client is configured to load.
B. The Desktop SNMP workstation support includes the
HRMIB.EXE and HRMIB.INI files. These files enable the console
to view data collected at each Desktop SNMP workstation. The
files are located in the client directory (default is
C:\NWCLIENT).
To enable the SNMP console to view data about a Desktop SNMP
workstation, you will need to perform the following tasks:
þ Install the NetWare Client 1.1 on your client computer.
þ Load the HRMIB.EXE software on the client you want data
collected from.
1. Ensure that the HRMIB.EXE and HRMIB.INI files exist
in your client directory (default is C:\NWCLIENT).
2. Load the HRMIB.EXE file by typing
HRMIB.EXE
NOTE: Ensure that the DOS SNMP Agent softwared is set up
and loaded on your client before loading the HRMIB.EXE
file.
3. Configuring the HRMIB.INI File
The Host Resources MIB does not return information about
devices attached to the host computers, such as printers,
modems, and tape drives. If the network management
console is to view details of such devices, you must
list them in the HRMIB.INI file.
The HRMIB.INI file is located in the directory to which
you installed the NetWare client (C:\NWCLIENT by default)
on your computer. Use a ASCII text editor to enter a
short description of each device. For example:
Sample configuration file (HRMIB.INI) for HRMIB.EXE
# List of all printers connected to host
[printers]
HP LaserJet IIIp on LPT1:
NEC P20 on LPT2:
# List of all modems connected to host
[modems]
Hayes Optima 144 on COM1:
# List of all tape drives connected to host
[tapes]
Colorado DJ10
HP 35480A SCSI DAT (4-8 GB)
# other devices obtained via DOS APIs
IV. Sample NET.CFG File for Desktop SNMP Services
A sample of the NET.CFG for SNMP agent services is as follows:
Link Driver NE2000
PORT 300
INT 3
FRAME Ethernet_802.2
MEM D0000
NetWare DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
VLM = MIB2PROT.VLM
Desktop SNMP
enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Suzanne Morley x893"
sysLocation = "Building 2"
sysContact = "[email protected]"
snmpEnableAuthenTraps = on
Transport Provider IPX
trap target = ab123456:0123456789ab
trap target = cd654321:ba9876543210
Transport Provider UDP
trap target = 999.88.77.66
trap target = 888.11.22.33
V. Conventional Memory Usage
If you are willing to trade conventional memory for
performance, you can load one or more Desktop SNMP .VLM files
in conventional memory.
To load all .VLM files in conventional memory, use the VLM /MC
switch when running the VLM manager.
To load a Desktop SNMP .VLM files in conventional memory,
place lines of the following form in the NET.CFG file:
Netware DOS Requester
VLM = vlm_name.VLM
LOAD LOW vlm_name = ON
For example, to load Desktop SNMP while loading the WSASN1.VLM
and WSREG.VLM files in conventional memory, place the
following lines in the NET.CFG file:
Netware DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
Load low WSREG = ON
Load low WSASN1 = ON
VI. Unloading the Desktop SNMP Software
The following commands, issued in the order given, unload
Desktop SNMP.
NOTE: The VLM -u command unloads all VLM files, not just
Desktop SNMP.
1. Unload STPUDP if UDP/IP support has been loaded:
STPUDP -u
2. Unload STPIPX if IPX support has been loaded:
STPIPX -u
3. Unload all VLM files:
VLM -u
IMPORTANT: Always unload the modules in reverse order from the
order in which you loaded them. For example, if you loaded the
VLM manager followed by STPUDP and then STPIPX, you must
unload them as follows:
STPIPX -u
STPUDP -u
VLM -u
Unloading the modules in any order other than reverse order
causes an error.
VII. Where to Go from Here
After you have completed the initial configuration of the
desktop SNMP agent, you can further modify the Desktop SNMP
options in the NET.CFG file to meet your specific network
requirements. Refer to"Desktop SNMP Option" in Appendix B of
"Workstation for DOS and MS Windows" for a description of
these modifications.
3. Description of NetWare DOS Requester Software
The NetWare DOS Requester consists of a number of files that
provide NetWare support for a DOS client. Unlike previous
versions of the NetWare DOS client, the Requester is built on
a number of Virtual Loadable Modules (VLMs). The VLM.EXE (VLM
manager) is responsible for loading the required modules.
NOTE: The NetWare DOS Requester is NOT compatible with
NETX.COM or NETX.EXE. Use NETX.VLM for compatibility with
shell calls.
The following table lists the current core modules in their
default load order. The table also includes descriptions,
default values, and flags indicating whether the module is
"Required" or "Optional" for each of NetWare Directory
Services or bindery services.
MODULE DESCRIPTION NDS BIND PNW
====== =========== === ==== ===
CONN.VLM Connection table manager R R R
IPXNCP.VLM Transport protocol R R R
implementation using IPX
TRAN.VLM Transport protocol multiplexor R R R
SECURITY.VLM NetWare enhanced security O O O
NDS.VLM NetWare protocol implementation R O O
using Directory Services
BIND.VLM NetWare protocol implementation O R O
using the Bindery
PNW.VLM NetWare protocol implementation O O R
using Personal NetWare
NWP.VLM NetWare protocol multiplexor R R R
FIO.VLM File Input/Output R R R
PRINT.VLM Printer Redirection O O O
GENERAL.VLM Miscellaneous functions for R R R
NETX.VLM and REDIR.VLM
REDIR.VLM DOS redirector R R R
NETX.VLM NetWare shell compatibility O O O
RSA.VLM RSA encryption for directory O O O
services reauthentication
WSSNMP.VLM Desktop SNMP module, which O O O
includes support for MIB-II
System and SNMP groups
WSREG.VLM MIB registration module O O O
WSASN1.VLM ASN.1 translation module O O O
WSTRAP.VLM Trap module O O O
MIB2IF.VLM MIB-II interface groups support O O O
MIB2PROT.VLM MIB-II support for the O O O
TCP/IP groups
AUTO.VLM Auto-reconnect/auto-retry O O O
NMR.VLM NetWare management responder O O O
4. NET.CFG File Parameter for the NetWare DOS Requester Option
The following table lists the parameters for the various
modules of the NetWare DOS Requester.
The following list is complete. Any parameters which may
have been used previously by the NetWare DOS Requester but are
not listed here are invalid.
Parameter/Default Minimum Maximum Module
SET STATION TIME = ON VLM.EXE
USE DEFAULTS = ON -- -- VLM.EXE
VLM =
EXCLUDE VLM =
MESSAGE LEVEL = 1 0 4 VLM.EXE
0 = V_LEVEL_STD; always display message and critical errors
1 = V_LEVEL_WARNING; display warning type messages
2 = V_LEVEL_PROG; display the program load message
3 = V_LEVEL_CONFIG; display configuration information
4 = V_LEVEL_DIAG; display diagnostic information
NETWARE PROTOCOL =
Note: The
protocols to be used (NDS.VLM, BIND.VLM and PNW.VLM)
by the Requester in the order of their priority.
Each protocol is separated by a comma or space
in the list (NDS,BIND,PNW). If you exclude any one of
the protocol .VLM files from the list, the excluded
.VLM file will not load.
CONNECTIONS = 8 2 50 CONN.VLM
FIO.VLM
NDS.VLM
SECURITY.VLM
AUTO.VLM
AVERAGE NAME LENGTH = 48 2 48 CONN.VLM
MAX TASKS = 31 5 254 CONN.VLM
LOAD LOW CONN = ON -- -- CONN.VLM
LOAD CONN TABLE LOW = OFF -- -- CONN.VLM
CHECKSUM = 1 0 3 IPXNCP.VLM
NWP.VLM
0 = disabled
1 = enabled but not preferred
2 = enabled and preferred
3 = required
LARGE INTERNET PACKETS = ON -- -- IPXNCP.VLM
NWP.VLM
LOAD LOW IPXNCP = ON -- -- IPXNCP.VLM
HANDLE NET ERRORS = ON -- -- IPXNCP.VLM
PREFERRED TREE =
NAME CONTEXT = "
Note: Quotation marks are required.
PREFERRED SERVER =
MESSAGE TIMEOUT = 0 0 10000 NWP.VLM
SIGNATURE LEVEL = 1 0 3 NWP.VLM
SECURITY.VLM
0 = disabled
1 = enabled but not preferred
2 = preferred
3 = required
NOTE: This parameter designates the level of enhanced security
support. Enhanced security includes the use of a message
digest algorithm and a per-connection/pre-request
session state for increased protection against intruder
attacks. When this parameter is set to 0 (disabled),
the SECURITY.VLM will not load.
CACHE BUFFERS = 5 0 64 FIO.VLM
CACHE BUFFER SIZE =(Media dependent) -- FIO.VLM
CACHE WRITES = ON -- -- FIO.VLM
TRUE COMMIT = OFF -- -- FIO.VLM
PB BUFFERS = 3 0 10 FIO.VLM
IPXNCP.VLM
0 = off
nonzero = on
PBURST READ WINDOW SIZE = 16 2 64 FIO.VLM
PBURST WRITE WINDOW SIZE = 10 2 64 FIO.VLM
PRINT HEADER = 64 0 1024 PRINT.VLM
PRINT TAIL = 16 0 1024 PRINT.VLM
PRINT BUFFER SIZE = 64 0 256 PRINT.VLM
NETWORK PRINTERS = 3 0 9 PRINT.VLM
NOTE: If set to 0, PRINT.VLM will not load.
LOCAL PRINTERS = 3 0 9 PRINT.VLM
FIRST NETWORK DRIVE =
NETX.VLM
NOTE: If FIRST NETWORK DRIVE is not specified, it will default
to the first available drive letter.
SEARCH MODE = 1 0 7 GENERAL.VLM
READ ONLY COMPATIBILITY = ON -- -- REDIR.VLM
SHOW DOTS = OFF -- -- REDIR.VLM
DOS NAME = MSDOS 1 5 chars NETX.VLM
GENERAL.VLM
LONG MACHINE TYPE = IBM_PC 1 6 chars NETX.VLM
GENERAL.VLM
SHORT MACHINE TYPE = IBM 1 4 chars NETX.VLM
GENERAL.VLM
AUTO RECONNECT = ON -- -- AUTO.VLM
NDS.VLM
Note: When this parameter is OFF, the AUTO.VLM load fails at
pre-initialization time.
AUTO RETRY = 0 0 3640 AUTO.VLM
AUTO LARGE TABLE = OFF -- -- AUTO.VLM
Note: When this parameter is OFF, the user name and password
maximum lengths are 16 chars each for auto reconnect.
BIND RECONNECT = OFF -- -- AUTO.VLM
BIND.VLM
BROADCAST RETRIES = 2 0 255 PNW.VLM
BROADCAST SEND DELAY = 0 0 255 PNW.VLM
BROADCAST TIMEOUT = 3 1 255 PNW.VLM
MOBILE MODE = 0 0 65535 PNW.VLM
RESPONDER = ON -- -- PNW.VLM
PREFERRED WORKGROUP =
WORKGROUP NET =
MINIMUM TIME TO NET =
5> Additional Information on the NetWare DOS Requester
A> Loading VLMs from a Directory Other Than the Current
Directory
The current directory is used for VLMs. To load VLMs from
another directory, use the "VLM =" command in the NET.CFG
file.
For example
VLM=C:\NWCLIENT\CONN.VLM
B> Specifying a NET.CFG File Outside the Current Directory
To specify a path for the NET.CFG file, type a command
similar to the following (or put the command in
AUTOEXEC.BAT):
VLM /C=C:\NWCLIENT\NET.CFG
C> Understanding the Load Order for VLM Software
The VLM software must be loaded in a specific order to
operate correctly. For example, the NWP.VLM file is a
multiplexor for NetWare protocol modules. Therefore, you
should load the NetWare protocols (NDS.VLM and BIND.VLM)
before the NWP.VLM file. The Load order for the VLM
software is as follows:
CONN.VLM
IPXNCP.VLM
TRAN.VLM
SECURITY.VLM
NDS.VLM
BIND.VLM
PNW.VLM
NWP.VLM
FIO.VLM
PRINT.VLM
GENERAL.VLM
REDIR.VLM
NETX.VLM
See section "2. Description of NetWare DOS Requester
Modules," in this README file for a description of each
of these modules.
D> Disabling Specific VLM Software
Disable specific VLM software in one of the following
ways:
1> Rename the module with an extension other than .VLM.
Use the NETWARE PROTOCOL parameter. See section 3,
"Configurable Parameters" in this README for
information on how to use this parameter.
2> Use the EXCLUDE VLM parameter. See section 3,
"Configurable Parameters" in this README for
information on how to use this parameter.
3> Rename the module with a different extension (for
example,.SAV).
4> Delete the module (not recommended).
For example, to configure your workstation for running on
a NetWare 3.x network only, type one of the following in
your NET.CFG file:
NETWARE DOS REQUESTER
NETWARE PROTOCOL BIND
or,
NETWARE DOS REQUESTER
EXCLUDE VLM = NDS.VLM
EXCLUDE VLM = PNW.VLM
E> Specifying the Load Order for Specific NetWare protocols
Use the "NETWARE PROTOCOL" parameter to specify the
NetWare protocol VLM software (NDS.VLM, BIND.VLM, and
PNW.VLM) you wish to load, in the order you wish to
load them:
NETWARE PROTOCOL = NDS,BIND,PNW
F> Using the NETX.COM File or Related Shells with the
VLM Software
You cannot load NETX.COM and NETX.VLM simultaneously. Use
the NETX.VLM file instead of the NETX.COM file or related
shells such as NET3.COM, NETX.EXE, BNETX.EXE,
XMSNETX.EXE, etc.. These files conflict with the
REDIR.VLM file; the REDIR.VLM will not load if the
NETX.COM file is loaded.
However, the NETX.VLM file is designed to replace
NETX.COM and related NETX shells, and is compatible with
the NetWare DOS Requester.
G> The IPXNCP.VLM File is not a Replacement for the IPXODI.COM
File
The IPXNCP.VLM requires the IPXODI.COM File to be loaded
in order to operate.
H> The Personal NetWare Client Software Components are Now
Included in The NetWare Client Kit
The PNW.VLM file is now included in the Client Kit. This
will allow you to connect to a Personal NetWare Server
from your client. However, the Personal NetWare utilities
are not included.
I> First Available Drive Is Different
The conventional NetWare Shell for DOS used drives after
the LASTDRIVE parameter; NetWare DOS Requester starts
using the first available drive before the LASTDRIVE
parameter.
Consequently, users who had, for example, a LASTDRIVE=G:
setting in their CONFIG.SYS are used to seeing drive H:
as the first NetWare drive rather than drive F:. To
maintain compatibility with existing batch files, you may
want to add the command like "FIRST NETWORK DRIVE = H"
under the NetWare DOS Requester portion of the NET.CFG
file. Otherwise, batch files assuming drive H: as the
first drive must be altered.
J> Login Drive Prompt Appears To Be a Root Mapped Drive
Because NetWare DOS Requester is a redirector on the
back-end of DOS, no directory path can be in the drive
structure maintained by DOS when the parent of the
directory is unaccessible.
This is the case with an unauthenticated connection and
the drive mapped to the SYS:LOGIN directory. Users see
"F:\>" instead of "F:\LOGIN>" when they first load the
DOS client software.
K> Search Mode Now Uses the DOS ENVIRONMENT Variable
The "SEARCH MODE" function uses the "PATH" DOS
ENVIRONMENT variable rather than the public search mode
table provided in the NETX.VLM file. You will experience
no change unless users corrupt their workstation
environment. If you exceed the PATH limitation, your
search drive mappings will not be included in the PATH.
L> Difference In Diagnostic Information Reported In the
NETX.VLM File Compared to the NETX.COM and Related Files
Some of the current diagnostic information supported
in the NETX.COM file will appear to be invalid in the
NETX.VLM file. This is because the NetWare DOS Requester
is responsible for much of the diagnostics information
previously maintained in the NetWare Shell for DOS. Some
of the information maintained in the diagnostics
responder will not be updated. Such information includes
the following:
Bad reply header (InvalidReplyHeaderCount)
Bad slot (InvalidSlotCount)
Bad sequence number
(InvalidSequenceNumberCount)
No router found (NoRouterFoundCount)
Request in process (BeingProcessedCount)
Bad server slot (InvalidSlotFromServerCount)
Bad net address (NetworkGoneCount)
Bad local address (BadLocalAddressCount)
Allocate slot errors
(AllocateSlotCannotFindRoute,
AllocateNoSlotsAvailable, AllocateServerIsDown)
The NetWare Management Responder (NMR.VLM) file will now
provide diagnostic information similar to that mentioned
above.
------------------------------------------------------------------
DISCLAIMER
Novell, Inc., makes no representations or warranties with respect
to any NetWare software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose.
Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc. Further, Novell reserves
the right to discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of recreating lost data, the
cost of any substitute equipment or program, or claims by any party
other than you.
Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at
the discretion of Novell.
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/