             NOV*IX Quick evaluation software - Troubleshooting
             ==================================================

This file will assist in resolving connectivity problems experienced when
using the NOV*Ix evaluation software.

Server Problems
===============


The file server appears to hang when I load the NLM

     If your file server console screen clears and reports 'Waiting for BIND
     command', this is normal.  Switch to the system console screen and enter
     the appropriate bind command.  Switching back to the NOV*IX console
     screen, you should see the NLM load message which will end with
     'Advertising service XXXX'.

     If the file server does not get as far a waiting for the bind command,
     check that you have sufficient memory in the file server.  A minimum of
     4Mb is recommended.  Remove other NLM's to free up space for NOV*IX.


The NLM will not load on the file server.

     Part of this quick installation process includes the creation of a
     NetWare user (TCPIPGATEWAY) which the NLM uses to login to the file
     server and a bindery object.  If a problem occurred during this process.
     it will inhibit the NLM from logging in.

     A batch file TCPSETUP.BAT is provided to perform this function.  You must
     be user SUPERVISOR and your current drive must be SYS:TCPGWAY.  A series
     of messages will be displayed.  If they end in '00', this reports a
     successful operation.

     Another possible cause of failure to load the NLM relates to the account
     restrictions applied to the TCPIPGATEWAY user.  If you are running
     accounting, an unlimited credit limit will be required.  Check that your
     intruder lockout facilities of the file server are not preventing the
     user from logging in.

     From a workstation, attempt to login as the TCPIPGATEWAY user.  This
     password is (and must be) OSLAN.  If you obtain a successful connection,
     logout and attempt to load the NLM again.


Workstation Problems
====================


The NOV*IX Elite VT220 or FTP program does not find a server

     The workstation program attempts to establish an SPX connection to the
     NOV*IX server when it loads.  When this connection is made, the
     workstation programs receive details of the services available.  Use
     program SERV.EXE supplied as part of the evaluation to list the name(s)
     of NOV*IX servers found on the network.  If SERV does not report your
     NOV*IX server, the problem probably lies with the NLM.

     Check that the NLM loads correctly and reports 'Advertising service xxx'.


The server is found but no services are listed

     Use the NVCONFIG program to check that you have configured the services
     with the appropriate access type.  When using the Firefox DOS workstation
     programs, access type 'VT/Telnet' is required for interactive access
     using the VT220 program and 'FTP Client' is required for file transfers
     using NVFTP.EXE

A connection to the TCP/IP host is not possible

     Messages will appear on the NOV*IX console if attempts to connect from
     the NLM to the host are unsuccessful.  A report of 'No ARP response'
     implies that the NLM has not been able to resolve the host's IP Address
     using the default mechanism of Address Resolution Protocol.  Check that
     the IP address you have is correct.  The NVCONFIG program allows you to
     enter the physical network address of the host.  This will bypass the use
     of ARP.

No login prompt is received from the TCP/IP host

     Check that you are using the correct TCP port for the connection.  Port
     23 is usually required for Telnet.

     If it appears that a connection has been established (because the VT220
     screen cleared and the cursor is top left) the problem is probably due to
     incorrect Telnet negotiation.  Some TCP/IP hosts require to know the
     terminal type during the negotiation of Telnet parameters and the VT220
     program will be default identify itself as a DEC VT200.  If this terminal
     type is incompatible  with your system, use the VT220 configuration
     pop-up (CTRL- LEFTSHIFT-F5) and set the answerback string to an
     alternative terminal type.

A connection from HostPresenter is not possible

     A LAN WorkPlace for NOV*IX socket driver must be present at the
     workstation.  This driver is supplied either as a Terminate and Stay
     Resident program or as a Windows Dynamic Link Library.  The DOWNLOAD
     program will transfer the selected driver to the correct location on the
     PC LAN Workstation.

     For a connection to be possible through either form of this driver, the
     workstation user must have a current valid NetWare logon. NOV*IX includes
     extensive security features to restrict access.  If you have followed the
     simplified instructions in this guide you will not have enabled any of
     the security features and therefore this should not be the cause of your
     connection failure.

     If using the TSR version of the socket driver, NVLWN.EXE must be either
     be loaded prior to loading Windows.  A number of messages report the
     status of the driver at load time.

     If using the DLL version of the driver, the appropriate DLL files must be
     present in the Windows directrory.

     During the DOWNLOAD process, a number of initialisation files are edited.
     The LAN WorkPlace software remains on the file server and
     \NOVIX\LANWP\BIN must be in the workstation search path.

     With the LAN WorkPlace for NOV*IX driver loaded in the workstation, before
     loading Windows software, load the DOS TNVT220 program.  This should be
     in your search path as it is in directory SYS:\NOVIX\LANWP\BIN.  Attempt
     a connection using this software by following the instructions for the
     use of TNVT220 in this guide.

     If this connection is successful, the problem lies in the Windows and LAN
     WorkPlace .INI files.

     Check that the following changes have been made correctly by the DOWNLOAD
     program:
     

     File C:\NET.CFG must include the following lines:

          Protocol TCPIP
               PATH SCRIPT      <lwndrive>:\NOVIX\LANWP\SCRIPT
               PATH PROFILE     <lwndrive>:\NOVIX\LANWP\PROFILE
               PATH LWP_CFG     <lwndrive>:\NOVIX\LANWP\HSTACC
               PATH TCP_CFG     <lwndrive>:\NOVIX\LANWP\TCP

     The following Windows file should include the following additions:

     File <windir>\WIN.INI

          [Extensions]
          pfx=rapfiler.exe ^.pfx
          prf=rapfiler.exe ^.prf
          php=presentr.exe ^.php

          [fonts]
          Host Presenter font 12,13,15,(vga res)=nov_vga.fon

     File <windir>\SYSTEM.INI
     
          [386Enh]
          device=<lwndrive>:\NOVIX\LANWP\BIN\vtcpip.386
          TimerCriticalSection=10000

          [NetWare]
          NWShareHandles=TRUE

               
     For the DOS programs TNVT220 to operate correctly, the Workstation will
     need to be running the DOS ANSI.SYS driver.

     DEVICE=<dosdrive>:\<dospath>\ANSI.SYS


When running DLL drivers for LAN WorkPlace for NOV*IX or the NOV*IX ELite
Windows programs, my workstation reports IPX/SPX not loaded or workstation
hangs:

     To run applications in a Windows environment that require access to
     IPX/SPX communications will need the Novell Workstation shell patch
     releases version 7 or later. If using the NetWare VLM shells, you will
     require version 8.

     The current version of these patches are called WINUP9 and DOSUP9 and
     complete copies are available from NetWire or your Novell dealer. Firefox
     have included an extract from the patches on the NOV*IX evaluation
     diskettes.

     Files FFDOSUP9.ZIP and FFWINUP9.ZIP are held on the first NOV*IX
     evaluation diskette.  You will need to use the PKUNZIP program to unzip
     the files to a suitable location.  FFDOSUP9 should be unzipped to your
     workstation shell directory (e.g. A:PKUNZIP A:FFDOSUP9 C:\NETWARE) and
     FFWINUP9 should be unzipped to your Windows directory (e.g. A:PKUNZIP
     A:FFWINUP9 C:\WINDOWS).


     FFDOSUP9 contains LSL.COM, IPXODI.COM, NETX.EXE, IPX.OBJ etc.
     FFWINUP9 contains NETWARE.DRV, VNETWARE.386, VIPX.386, NWPOPUP.EXE

     The symptoms of running shells that are too old are:
           - Application reporting that IPX/SPX is not loaded
           - Windows crashing on termination
           - Workstation freezing requiring re-boot.


 
