Troubleshooting and Optimizing NetWare Client 32 for Windows 95
Articles and Tips: article
Software Developer/Consultant
RoseWare (Asheville, N.C.)
01 Nov 1996
Discusses troubleshooting steps and provides optimization tips for Client 32.
Thanks to Ben Hendrick at Novell for his help with this article.
Introduction
Once you have NetWare Client 32 for Windows 95 installed and configured properly, it should perform reliably in a variety of network environments. As with all software, there will invariably be issues that arise with certain components, or situations in which performance could be improved.
This AppNote outlines steps you should you take to troubleshoot problems with Client 32. It also gives some tips for tweaking the client for optimal performance.
This AppNote is excerpted, by permission, from an article entitled "Novell's NetWare Client 32" which was published in the March/April 1996 issue of NetWare Conneciton magazine. For more information about NetWare Connection, visit http://www.nwconnection.com on the World Wide Web.
Troubleshooting the Client
Since NetWare Client 32 for Windows 95 offers so many configuration options, it's not surprising that there are occasional conflicts with hardware or software. The trick is to pinpoint the problem as quickly as possible. Troubleshooting a system problem is like solving a mystery: You look for clues, eliminate suspects, and eventually discover the culprit.
Because anticipating every networking problem is difficult, this AppNote explains where to look for troubleshooting clues and outlines some common problems users encounter. You can start your investigation by asking logical questions such as the following:
Did the previous NetWare client work before you upgraded? If it did work,what changes did you make to the workstation? For example, did you install any new hardware such as a new network interface board?
After you upgraded the NetWare client, were you ever able to log in to the network successfully?
Is the problem occurring on other workstations?
Do you receive an error message when you load the NetWare Client 32 for Windows 95?
The answers to these questions will determine your next course of action. For example, if the previous NetWare client worked properly and you have not changed your hardware configuration, the problem may be software-based, rather than hardware-based. If you were not able to log in after you upgraded the NetWare client, you may suspect a configuration problem. For example, your Name Context setting may be incorrect.
The NetWare Client 32 Log File
When you are troubleshooting a problem, one of the best ways to find clues is to enable the NetWare Client 32's log file. This file keeps a record of the NetWare loadable modules (NLMs) that are loaded on the workstation, the properties that are used, and any diagnostic messages from the NLMs. To enable the log file, you must edit your SYSTEM.INI file. (You can use the SYSEDIT utility to quickly edit SYSTEM.INI.) Under the [386Enh] section, the NWEnableLogging field should be set to True, as the following shows:
[386Enh] NWEnableLogging=True
After you enable this option, the NetWare client will create a log file called NIOS.LOG, which is stored by default in the NetWare Client 32 home directory (C:\NOVELL\CLIENT32). You can change the filename by modifying the Log File option, and you can change the size of the log file by editing the Log File Size option. (To change these options, access Control Panel | Network, highlight the Novell NetWare Client 32 and click on Properties. Then select Advanced Settings.)
If you encounter a problem such as an error message appearing during the login process or the workstation hanging, you can check the log file to find the cause of the error. The log file will record problems such as an NLM did not load, IPX failed to bind successfully to a network interface board, or all of the NLMs loaded properly, but the NetWare Client 32 could not find a file server.
If your workstation hangs during the boot process, you can reboot and push the F8 key after you see the "Starting Windows 95 . . ." message. You will then see a menu of boot options. Have the workstation boot to DOS. Then at the DOS prompt, you can access the DOS EDIT program and read the NIOS.LOG file.
As an alternative, you can run Windows 95 in Safe Mode and view the NIOS.LOG file from Notepad. To do this, reboot your workstation and press the F8 key when you see the "Starting Windows 95 . . ." message. This time, choose Safe Mode from the menu of boot options. Safe Mode runs Windows 95 in real mode with the normal 32-bit optimizations disabled. If system conflicts prevent you from booting Windows 95, you can use Safe Mode to boot Windows 95. Then you can go to Control Panel | Network and change the settings for the NetWare Client 32 or for Windows 95 itself.
Enabling the log file will slow the boot process because the NetWare Client 32 must write information to the NIOS.LOG file. As a result, you may want to enable this option only when you are troubleshooting a problem.
The MODULES Command
If you are experiencing an intermittent problem, you may find the NetWare MODULES command useful. If you type MODULES in a DOS window, you will see a list of the currently installed NLMs. You can use this list to double-check which client NLMs you are using. You can also make sure that you are using the most current version of these NLMs. Installing the latest version of the client NLMs may solve your problem.
You can compare this information to another workstation's setup or report it to a technical support engineer. If you want to redirect this information to an ASCII text file, you can enter the following command:
MODULES > CLIENT32.TXT
Hardware Setup
If you suspect a hardware problem, you should make sure you are using at least a 386 computer; a 486 computer or better is recommended. The workstation should also have at least 8MB of RAM.
In addition, remember that the NetWare Client 32 for Windows 95 does not support Remote Program Load (RPL), so you cannot run it on a diskless workstation. If you need to support diskless workstations, you should use Microsoft's client for NetWare or Novell's NetWare DOS Requester (virtual loadable module, or VLM, client). Novell plans to support RPL in a later release of the NetWare Client 32 for Windows 95.
You should also check the link status light on all network interface boards, hubs, or other equipment to which your workstation is connected. If the light is not on, you should make sure the network interface board or PCMCIA adapter is inserted properly. If other workstations are unable to log in to the network, you may also want to check the physical route between the workstations and the file server. Make sure the routers (or repeaters or bridges) are working properly. Also, inspect your cabling and ensure that the server's network interface board is plugged in. (If you can log in successfully with Novell's 16-bit client, the path to your file server is probably not the problem.)
The I/O addresses of video boards and network interface boards may also be an area of conflict. Because the NetWare Client 32 for Windows 95 will use all of the I/O address space on the boards, new conflicts may arise. Choosing the wrong driver can cause what will appear to be a hardware problem. For example, NE2000 clone boards typically have problems with a driver written specifically for the hardware, such as the CNE2000.LAN, a 32-bit server Open Data-link Interface (ODI) driver.
To factor out driver-related issues (as opposed to hardware issues), you should switch from Network Driver Interface Specification (NDIS) drivers to ODI drivers. For example, if you are using the Intel Pro 100 board, you will not be able to run NetWare Client 32 with the NDIS driver provided with Windows 95. You should contact Intel and get the latest version of E100.SYS, which works with NetWare Client 32 for Windows 95.
The Process of Elimination
If you determine that your problem is software-based, you may want to check the following:
If terminate-and-stay-resident (TSR) programs, drivers, or system files are not being loaded, make sure the PATH statement is less than 128 bytes. Anything in your path beyond 128 bytes will be ignored. In addition, you should not load your PATH statement with network drives: The client's GUI login utility will delete network drives from the path if they are invalid when the client is initialized.
If you cannot log in to NetWare 4, you should make sure your Name Context is set properly. (To check the Name Context, go to the Windows Control Panel | Network. Highlight Novell NetWare Client 32 and click on Properties.) If you are logging in to a NetWare 2 or 3 server in bindery emulation, make sure your Preferred Server is set properly.
If you are having problems logging in to NetWare servers or using RCONSOLE to connect to remote NetWare servers, make sure IPX is bound to only one frame type. As mentioned earlier, you can verify if this is the problem by enabling the NetWare Client 32 log file. If IPX is bound to more than one frame type, you can open Control Panel | Network and select Novell NetWare 32-bit IPX Protocol. Then click on Properties and select Advanced IPX. Select the correct frame type in the menu that appears.
If you receive an error message such as "An attempt to load CLIENT32.NLM failed because the module references an undefined external," you may still be loading the 16-bit client in your AUTOEXEC.BAT file. Check both the AUTOEXEC.BAT file and the CONFIG.SYS file to make sure you are not trying to load the 16-bit NetWare client.
Finally, if you cannot access a Windows 95 machine that is using Microsoft's File and Print Services for NetWare Networks (NWSERVER.VXD), you should be aware of the following: Although the Microsoft NWSERVER announces itself as a NetWare 3.12 server, it actually behaves as a NetWare 2 server, using older NetWare Core Protocols (NCPs). When NetWare Client 32 queries the Windows 95 server for its network operating system version, it responds that it is a NetWare 3.12 server. NetWare Client 32 then tries to communicate with the Windows 95 server using Novell's Case 87 NCP set, which all NetWare 3.1x and 4.x servers understand. Because Microsoft's NWSERVER software doesn't support these NCPs, the communication fails.
If Microsoft continues to claim NetWare 3.x compatibility, this problem should be fixed: NWSERVER.VXD should support Novell's Case 87 NCP set. Or it must be updated to report its actual network operating system version (NetWare 2.2 clone). This issue also occurs when you try to use Microsoft's Windows NT File and Print Services for NetWare with the NetWare Client 32 for Windows 95. (For more help on this issue, you should contact Microsoft Product Support Service.)
If you try the suggestions outlined in this AppNote and still cannot solve the problem, you may want to resolve it through your normal support channels.
Finally, if you cannot access a Windows 95 machine that is using Microsoft's File and Print Services for NetWare Networks (NWSERVER.VXD), you should be aware of the following: Although the Microsoft NWSERVER announces itself as a NetWare 3.12 server, it actually behaves as a NetWare 2 server, using older NetWare Core Protocols (NCPs). When NetWare Client 32 queries the Windows 95 server for its network operating system version, it responds that it is a NetWare 3.12 server. NetWare Client 32 then tries to communicate with the Windows 95 server using Novell's Case 87 NCP set, which all NetWare 3.1x and 4.x servers understand. Because Microsoft's NWSERVER software doesn't support these NCPs, the communication fails.
If Microsoft continues to claim NetWare 3.x compatibility, this problem should be fixed: NWSERVER.VXD should support Novell's Case 87 NCP set. Or it must be updated to report its actual network operating system version (NetWare 2.2 clone). This issue also occurs when you try to use Microsoft's Windows NT File and Print Services for NetWare with the NetWare Client 32 for Windows 95. (For more help on this issue, you should contact Microsoft Product Support Service.)
If you try the suggestions outlined in this AppNote and still cannot solve the problem, you may want to resolve it through your normal support channels.
You can post a question to the NetWire system operators (sysops) on CompuServe. Type GO NETWIRE and follow the prompts for the Novell Client Forum, or type GO NOVCLI.
On the Internet, you can post a message to one of the comp.os.netware.*newsgroups.
You will find helpful information on Novell's World Wide Web site athttp://support.novell.com. Check the frequently asked questions (FAQs) for NetWare Client 32 for Windows 95. The FAQs cover issues such as installation, NIOS, the Client 32 Requester, LAN drivers, the GUI Login utility, the NetWare Application Manager (NAM) utility, printing, and TCP/IP connectivity. You can download all the FAQs from http://support.novell.com/home/client/client32/faq.htm.
You can also find white papers, feature lists, and product overviews on Novell's WWW site or CompuServe (type GO NWCL32).
Tuning NetWare Client 32
Once the NetWare Client 32 for Windows 95 is working properly, you will probably want to optimize its performance. We will first examine ways you can get the most speed from your configuration, and then we will examine ways to make your system more functional.
The Need for Speed
To realize the best performance from the NetWare Client 32 for Windows 95, you should focus on the following areas:
Protocol overhead
Delayed writes
File cache level
Performance cache
Protocol Overhead. Each communications protocol you use (such as IPX/SPX or TCP/IP) consumes system resources and can potentially slow down the system. For maximum performance, you should bind protocols (such as IPX) only to the boards that use them. For example, if you are using IPX on only one Ethernet board, don't bind IPX to the other boards in your workstation. To change this setting, access Control Panel | Network. You will see a list of network components, including network interface boards and protocols. If you are not using one of the protocols listed, select the protocol and then click on the Remove button.
Delayed Writes. You can also increase the speed of the NetWare Client 32 for Windows 95 by allowing file writes to be delayed beyond the close of an application. The Delay Writes option allows actual network writes to lag behind an application's request to close a file, allowing the application to continue working without waiting for data to be written to the server.
To delay file writes, you can modify the Close Behind Ticks option. However, you should be aware that changing this setting can risk data integrity.
File Cache Level. The File Cache Level option can also increase performance. You can choose whether to disable file caching (which saves extended memory but decreases speed), to enable warehouse caching (which essentially caches everything), or to use one of the caching levels in between.
Performance Cache. One final suggestion to improve the speed of the NetWare Client 32 involves using the Performance, Cache option.
You can configure all of these options by accessing Control Panel | Network. Select Novell NetWare Client 32 and click on Properties. Then select Advanced Settings. You can right-click on any of these options to get more information, or you can use the online documentation for a more detailed explanation.
As you optimize the NetWare Client 32 for Windows 95, you will often have to choose between speed and complete data integrity. Before you decide how to balance speed and data integrity, you should understand the options that affect both.
Options such as True Commit, Cache Writes, Close Behind Ticks, and Delay Writes can be set for optimal data integrity. For example, True Commit ensures that a write operation will not be completed until the data is safely written to the server's hard disk. When the user is working with mission-critical data such as a database or an accounting system, turning on True Commit can provide additional insurance that each transaction has been successfully written to the NetWare server's hard disk.
Doing More with Less
You can also tune the NetWare Client 32 for Windows 95 so that it uses less disk space and less memory. To reduce the amount of disk space used by the NetWare Client 32, you will first want to remove unnecessary files. The NetWare Client 32 help files (such as SETUPNW.HLP) list all of the client files and explain how each file is used. You can use this list to determine the files you will not use and can, therefore, discard. Some decisions will be simple. For example, if you are not using an FDDI network adapter, you won't need the FDDITSM.NLM, so you can delete this driver from the C:\CLIENT32 directory. (You may want to back up any files you delete to a temporary directory.)
You can further reduce the NetWare Client 32's memory footprint by reducing caching. To change file caching, you must modify the Maximum Cache Size option. (See Appendix B for a description of Client 32 parameters.)
There is a tradeoff between speed and available memory. A large client cache will provide a faster network client but will leave less memory available for other Windows applications. On the other hand, reducing the memory footprint consumed by the cache will give more memory back to the system for other applications, but the NetWare Client 32 will not be able to cache as much data from the NetWare server.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.