The following issues will help you troubleshoot Novell ClientTM for Windows 95/98. For additional issues, check the Novell Client Readme.
Drag-and-drop operations between applications on the desktop might not work immediately after the client is installed and the workstation is rebooted. To solve this problem, reboot again to ensure proper registration of the ActiveX* controls included in the client.
An update to NDPS® is required to solve a client hang. Install the DPRPCNLM.NLM file, dated 22Nov2000 or later. This update is included in NetWare® 5.1 Support Pack 3. Refer to TID 10062546.
NetWare 4.11 and NetWare 4.2 servers require an update on the server prior to the installation of this Novell Client. The server update information is located in TID 2952441. This update addresses an issue in which a file opened once by different threads (one open in each thread) in an application and then closed leaves an instance of the file open, even after exiting the application. This problem could cause the server to run out of memory or hang.
When using the IP with IPXTM Compatibility client configuration, make sure that the TCP/IP stack has been configured with a TCP/IP gateway. This can be configured through DHCP or defined locally. The IPX Compatibility driver and IP routing will not work properly without a TCP/IP gateway configured. Under Windows 95/98, the gateway can be configured by opening the TCP/IP Properties page from the Network Properties page. If your network is configured to use DHCP, you do not need to configure the gateway locally.
If you are using the IP with IPX Compatibility configuration on the client and are trying to connect to servers running IPX only, make sure that you have configured a Migration Agent (MA) on the network.
For more information on setting up a Migration Agent on the network, see the NetWare® 5 documentation. To troubleshoot a Novell Client's MA visibility or configuration, enter CMDINFO at the DOS prompt. This command should list all configured or discovered MAs, depending on the IPX compatibility configuration.
If you upgraded Novell Client software and chose to update Remote Management during installation, Remote Management will not function if you do not have ZENworksTM for Desktops 3. If you have inadvertently upgraded Remote Management and do not have ZENworks 3 for Desktops, do the following:
Uninstall Novell Client for Windows 95/98.
Install a previous version (with the Remote Management option selected) of Novell Client for Windows 95/98.
This replaces the Remote Management functionality.
Install Novell Client for Windows 95/98 without selecting Remote Management.
If you have new workstations that require ZENworks for Desktops 2 Remote Management and Novell Client for Windows 95/98, do one of the following.
Install Novell Client for Windows 95/98 without selecting Remote Management.
Use the NAL Remote-OS Application Object to install Remote Management.
Install a previous version of Novell Client for Windows 95/98.
This installs the Remote Management functionality.
Install Novell Client for Windows 95/98 without selecting Remote Management.
Novell Client runs with MFC42.DLL version 4.21.7022 or later. MFC42.DLL version 6.00.8267.0 is installed when you install Novell Client. If an older version is installed over the version installed by Novell Client, the client login fails with an error message similar to the following:
The ordinal 6453 could not be located in the dynamic link library MFC42.DLL.
The actual message might vary, depending on the version of MFC42.DLL you are using.
To recover from this error, reinstall the correct version of MFC42.DLL. You can find the correct file on the ZENworks CD at
D:\PRODUCTS\WIN95\IBM_ENU\MFC42.DLL
Copy the .DLL to the following directory on your workstation:
C:\WINDOWS\SYSTEM
Symptom: Login restrictions are set for IPX/SPXTM and the node address. When the administrative workstation is reset, the new client files are automatically updated and the reboot prompt is displayed. After restarting, the workstations that are placed in the restriction list as being able to log in as Admin and which now have the new client cannot log in and no administration of the server can be done.
Cause: This is a problem with preferring the IP protocol. The allowed addresses assigned in NDS® are IPX addresses. If the server is bound to IP, the clients are designed to prefer this protocol by default. The result is that the client is attempting to log in to the server using IP but the address is restricted to only allow IPX addresses, causing an authentication failure. This is due to the IP address not being stored in NDS.
Solution: Do not bind IP to the server until static IP addresses have been assigned. Or, change your protocol preference to IPX.
In order to use SLP name resolution with dial-up networking, you must add the directory agent's IP address to the directory agent list on the Novell NetWare Client Properties Service Location tab.
Right-click the N icon in the system tray and then click Novell Client Properties.
Click the Service Location tab.
Add the directory agent IP address to the directory agent list and then click OK.
If you are using dial-up networking on the client and are unable to log in or browse the network, do the following:
Make sure that you can resolve NetWare 5 or later IP server names.
For dynamic discovery of servers, make sure that your client can locate an SLP Directory Agent. The agent can be configured statically or it can be configured through DHCP if your dial-up host supports DHCP and is configured with the proper Discovery Agent.
By default, the client uses DHCP to locate a Discovery Agent. (This assumes that a Discovery Agent is configured on the dial-up host network.)
The client uses an NWHOST file, if present, which contains server names and their addresses. This might be a preferred way to run your client. (The file is created in the NOVELL\CLIENT32 directory on the workstation.)
The client also supports DNS names. After connecting to the dial-up host, make sure that your DNS server is working properly by attempting to ping your server using its DNS name. If the ping was successful, then use that same DNS name as your server name in the login dialog.
HINT: Isolate the problem down to name resolution by using an IP address instead of the server name. If the login works, the problem is in name resolution.
Make sure that the IP stack is still functioning properly by pinging known active IP nodes that are on the dial-up host network.
If you are using IP with Compatibility Mode on the client and cannot see any IPX servers, make sure that the clients Migration Agent is configured properly.
In order to use Compatibility Mode to locate IPX services over a dial-up connection, you should statically configure the Migration Agent on the Compatibility Mode Driver property page.
NOTE: If your dial-up host supports DHCP Inform requests and is configured to hand out Migration Agents, you shouldn't need to set the Migration Agent statically.
Click Start > Settings > Control Panel.
Double-click Network > Compatibility Mode Driver (CMD).
Uncheck the Use DHCP check box and then add a Migration Agent, using an IP address in dotted format (for example: 137.65.1.5).
You can also use a DNS name, keeping in mind the dial-up environment that you are using.
Press OK to save the changes.
Do not configure a local NPRINTER with interrupts. Use the default Polled Mode instead.