|
|
| |
Novell Netware NLM Checklist
COMMENTS Novell NLM Checklist
Workstation Settings:
Make sure
minimal protocol/adapter bindings exist.
Remove all unnecessary protocols
and/or Clients.
Set ?Frame Type? to Ethernet_802.2(or 802.3) in all IPX
protocols, and not set to
AUTO. This should match the Frame Type that is set
on the server explicitly.
Client32 version should be 3.1 without any service
packs. It is actually
preferable to use the Client32 version 2.2 if possible.
Client32 version 3.2 is not
supported. Deselect the line that states?
?Primary Logical Board? located
in ?Advanced IPX settings? and make sure that
IPX/SPX is set to be the Default
Protocol. Edit Config.sys (or Config.nt for
NT/2000 based machines) and
increase the file handlers by setting "FILES =
200"
Verify that the application is not being run from the root directory of
a mapped
drive.
If so, map to parent directory of application directory.
Check that the REVPARAM
file is included in the DM, DMW, DOCAPPR, and LENDER
directories. The
REVPARAM file must include the following
information?
ServerOnly = True
Server Settings:
Make
certain that the following NLM's are
loaded:
LH.NLM
LHIPXSER.NLM
Service Commands:
Lhstart
(starts the service)
Lhstop (stops the service)
Check the Frame Type
on the Server; the recommended Frame Type is 802.2
because it is fully IEEE
compliant. You may also use 802.3. Any other Frame
Type is not supported. If
you have a router on your network, you must configure
the router to allow the
SAP (Server Advertising Protocol) broadcast message to
get through. The SAP
number is Ox5B8.
Troubleshooting:
Launch the NETDRV.EXE utility
from your DSI\DMW directory. In the section
titled "Open Insight Network
Driver Information", Verify that this set to
IPX/Netware Multi-user Driver.
If you see any other driver (All Network Driver,
Byte Range Lock, etc.) you
must rerun the Workstation portion of the NLM
installation. Refer back to the
NLM Installation Instructions.
Background processes such as anti-virus
software or backup software may cause
?slow-downs? during application
execution. Performance improvements may be
obtained by shutting these
applications down during execution of your
application. For anti-virus
software, we suggest you specify that the .ov files not
be examined for
viruses. The anti-virus software frequently confuses .ov files
with .ovi
files, which are frequently a source of viruses. Power Management may
also be
turned off. NOTE: Some versions of Norton Anti-Virus have been known
to cause
problems with our software, causing lockups when accessing the
Worksheet
Screen.
You can modify the autoexec.ncf file in the Novell SYSTEM
directory, replace
HSTART with Load LH.NLM /s: #. The number should be
between 1 and 16, the
default being 16 if the parameter is not specified. The
higher this number is the
better the performance of the NLM, but it will
decrease NetWare's response time
to service other requests. If you get the
message Error FS466 "No Server
Response" this parameter is set too
high.
Adding additional RAM to the NetWare server generally improves the
overall
performance of the server and may significantly improve the
performance of the
Revelation NLM.
| |
 |
|
| Creation
Date : 04/03/2001 |
Department
:
Tech Support
|
|
Type : DocMagic |
|
|
|
|
|
|
|
|
|
|
|
|