Troubleshooting Windows 95 Using Novell NetWare Clients

This section describes some common problems that might occur when running a Novell-supplied client with Windows 95.

As a general troubleshooting step, make sure that the NETWARE.DRV file version 3.03.94.280 or later for VLM is present, plus version 2.02 or later for NETX. If necessary, restore this file from the Novell-supplied installation source.

• Check the version numbers of all Novell-supplied NetWare workstation shell components, including IPX, NETX, VLM, LSL, IPXODI, and the ODI driver files. Make sure the latest versions are being used.

  To get the version number for the Novell-supplied software you are using, run driver_name i or driver_name ? at the command prompt. For example, type netx i to get the version number for the Novell-supplied NET*.COM or NET*.EXE file.

  If you are not using the latest software, upgrade as described in "Obtaining Current Novell-Supplied Files" earlier in this chapter.

• Check for multiple instances of the NetWare files, specifically the ODI driver and NET.CFG. If there are multiple instances, remove all but the most recent version.
• Verify that IPXODI is binding to the network adapter by running the NetWare NVER utility, using the same settings as NET.CFG and the same [link driver ODI_driver] name. If IPXODI is not bound to the network adapter, change the entries in NET.CFG to correct this problem.
• For a monolithic configuration, verify that the configuration does not use the /o# switch on IPX.COM or the config option= statement in SHELL.CFG.
• If the user is running a shared copy of Windows 95, verify that the home directory and shared Windows directory are the first two items in the path.

Setup requires Novell Workstation Shell Installation Program.

If, during installation, Setup fails to load Novell drivers and displays a message that it requires the Novell Workstation Shell Install Program for installing the VLM network client with Windows 95, follow the instructions presented in "VLM Technical Notes" earlier in this chapter.

You cannot attach to the NetWare file server after installing Windows 95.

Verify the frame type being used by the NetWare server. If the NetWare server is using a different frame type from the one configured for the computer running Windows 95, the user cannot see the server. The Novell-supplied IPXODI protocol binds only to the first logical board, which is the first frame type in the link driver ODI_driver section in NET.CFG.

To correct this problem, manually edit NET.CFG so that the correct frame type is first in the link driver ODI_driver section.

You cannot see other computers running Windows 95 or NetWare server.

• Determine which frame type is used at your site, and then verify that the correct frame type you want to use on the network are listed in NET.CFG. The frame type that IPXODI will use must be first or must be set explicitly.
• Verify that the correct NET.CFG is being processed by LSL.COM. To do this, check the local drive for other NET.CFG files. There should be only one, and it should be in the same directory as the NetWare driver files. If you are loading these files from AUTOEXEC.BAT or another batch file, modify the batch file to change to this directory, run the necessary ODI drivers, and change back to the directory you want. This ensures that the current directory is the same as the location of the LSL.COM file when it is being loaded.
• Verify that NET.CFG contains the correct settings for the network adapter. If necessary, restore this file from a correct backup version, or edit it to include correct settings.
• Verify that you are running the latest version of the Novell-supplied ODI drivers and support files. Check with your network adapter manufacturer to determine whether a newer ODI driver is available.
• Verify that both client computers are running the same protocols. If the client computers are on different sides of a router, make sure that an IPX/SPX-compatible protocol is being used on both computers.

You cannot access the login drive after installing Windows 95.

A common misconception is that users must log on to their NetWare server using the drive letter F. However, this is not true. For a client computer using the NETX workstation shell, the NetWare login drive is the next drive letter available after the LastDrive= statement in the Registry.

You can alter the LastDrive= statement to change the login drive, but you must leave enough drives before the LastDrive= that Windows 95 can use for its own connections.

Computer doesn't run after installing VLM support under Windows 95.

If a message says that the system cannot find a device file needed to run Windows, make sure that the VLM client has been installed using the Network option in Control Panel. This step ensures that the correct VLM information is placed in SYSTEM.INI. (The Novell-supplied installation program for VLM sets the path in SYSTEM.INI to the Windows SYSTEM directory rather than to VMM32.)