The following issues will help you troubleshoot Novell Client for Windows NT/2000/XP. For additional issues, check the Novell Client Readme.
Workstations using IPX Compatibility Mode cannot have an IPX internal network number configured. If you have configured an IPX internal network number on your workstation and you plan to install the Novell IP Client with IPX Compatibility Mode, then remove the IPX internal network number before installing the client.
We recommend that you use the Typical Installation option for most installations of Novell Client software. If you are installing Novell Client and you select Custom Installation, note that the Novell IP gateway is not compatible with NetWare IP or CMD (IPX Compatibility Mode Driver).
If you plan to use Remote Management, make sure that Workstation Manager is installed on all workstations that will be managed remotely.
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 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.
The TCP/IP Source Path parameter has been added to the unattended network installation. This parameter is not included in Novell Client Install Manager. To use this parameter, you must add it manually to the UNATTEND.TXT file:
!TCPIP_SOURCE_PATH = path
This parameter is used with Automatic Client Upgrade (ACU) to upgrade an IP client. Specify the full path to the source files for the Microsoft TCP/IP installation files. If this parameter is not specified, the location where the ACU was run from will be used as the default.
Additionally, all parameters to configure TCP/IP are available as well. These are the same parameter names that are specified by Microsoft for use during an unattended operating system install. They should be added under the Novell Client section of the unattend file.
For more information on unatteded network installations, see Installing Clients from the Network.
We recommend that administrators configure NT workstations to not use any of the Microsoft password restrictions available in User Manager. Novell Client for Windows NT/2000/XP works best if password restrictions are left up to NDS.
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\WINNT\I386\LIBS32\MFC42.DLL
Copy the .DLL to the following directory on your workstation:
%SystemRoot%\system32
Copying MFC42.DLL will fail if some component is using the file. If the copy fails, try renaming %SYSTEMROOT%\SYSTEM32\MFC42.DLL to %SYSTEMROOT%\SYSTEM32\MFC42.OLD and then try copying the new version again.
Symptom: Login restrictions are set for IPX/SPX 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 eDirectoryTM 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 eDirectory.
Solution: Do not bind IP to the server until static IP addresses have been assigned. Or, change your protocol preference to IPX.
If you use a login script that contains an external CAPTURE command using CAPTURE.EXE, the screen might go blank with a blinking cursor in the upper-left corner. The capture eventually executes and the screen returns to normal.
This happens if Windows NT or Windows 2000 is set to "full screen" when the CAPTURE command is executed from the login script. Although the system might be working correctly, a slow server performing the capture with a blank screen may make it appear otherwise.
To correct this problem, do the following:
Double-click My Computer and then click Control Panel > MS-DOS Console.
In the Console Windows Properties dialog box, click the Options tab.
From the Display Options group, click Window.
Novell Client for Windows NT/2000/XP Properties > Advanced Settings contains a Set Station Time property.
When this setting is On, the workstation time is always synchronized with the network during GINA Login. The login script SET_TIME command has no effect on time synchronization, because the time is being synchronized before the script command is processed.
When the setting is Off, the SET_TIME ON script command will have an effect when scripts are run and the workstation time will be synchronized with the network.
Windows 2000 and XP both ignore the SET_TIME script command regardless of the client property setting Set Station Time=On|Off' and update the time/date to the Netware Server Time/Date at Gina Login only. Subsequent script executions do not make any difference as the script command seems to be ignored.
The MAP.EXE utility might function improperly if the computer's DOS environment size is too small. If you encounter problems while running MAP.EXE, increase the DOS environment size by adding or editing the SHELL= line in the WINNT\SYSTEM32\CONFIG.NT file. For example:
SHELL=%SYSTEMROOT%\SYSTEM32\COMMAND.COM /E:2048
MAP.EXE was not designed as a Windows NT/2000/XP executable and, therefore, does not recognize drives mapped to NT servers as network drives. Consequently, MAP will not list NT network drives. The Windows NT NET USE command can be used to correctly connect and list network drives for both NetWare and NT servers.
MAP.EXE is not IP-aware for eDirectory objects. As a result, MAP.EXE might fail if you try to use it to map a drive to an eDirectory object---for example, with a command like the following:
MAP N .mydir.organization.company
The failure will result in a message such as the following:
MAP-4.13-195: Directory [N .mydir.organization.company cannot be located
This error can be avoided by using one of the following solutions:
In Windows NT/2000, all drive mappings made using the NetWare Login are root mapped. Because of this, programs cannot access directories above the directory that the drive is mapped to. This feature affects only MAP commands performed in a login script. Once Windows NT has been started, NT allows you to map only to the root.
You can turn off the default by adding SET MAPROOTOFF="1" as the first line in the login script. This will globally force all NT workstations using the login script to not map root drives.
Or, you can perform the following procedure on a local workstation:
Right-click My Computer.
Click Properties > Environment.
Enter MAPROOTOFF as a variable.
Set the value of the MAPROOTOFF variable to 1.
Click Select.
In Windows NT 4.0, users might encounter an error when restoring permanent drive mappings to NetWare servers in different trees. These mappings will be authenticated through Novell eDirectory. The user might get an Invalid Password prompt when restoring these drives. This is not because the password is invalid but because the client does not have a valid context for the secondary tree.
If this problem occurs, enter the default context for all eDirectory trees on the Client tab of the Novell Client Configuration page. This is accessed by right-clicking Network Neighborhood and then clicking Properties > Services > Novell Client for Windows NT > Properties.
If you have a permanent drive mapping that conflicts with a drive mapping made in your login script, a dialog box appears indicating that an error occurred while reconnecting the drive and that the local device name is already in use. One of the options in this dialog box has some confusing results. If you check Do Not Try to Restore the Connection in the Future, and then click Yes or OK, the drive mapping made from your login script is removed.
If you do not check this check box, the drive mapping from your login script is preserved. This is a bug in Windows NT. By default, Windows NT removes any mappings on that drive letter without checking to see whether the existing drive mapping is the same path as the permanent connection.
You might experience difficulties printing through NDPS if your network connection is dropped and later auto-reconnects. You could receive the following error messages:
Error writing to <printer>: Space to store the file waiting to be printed is not available on the server.A write fault occurred while printing.
To resolve this problem, you must download and install NetWare 5 Support Pack 2 or later. Then complete the following:
At the server console, load NDPSM.NLM to load NDPS Manager on the server.
From the NDPS Manager main menu, click Printer Agent List.
Select a Printer Agent.
Once the Printer Agent information is displayed, click Configuration: (See Form).
From the configuration screen, change the Security Level from High to Medium.
If you support a large number of RAS users in your network and you experience problems with users not being able to log in because of insufficient NetWare connections, try setting the Watchdog configuration parameters so that connections time out quickly when RAS connections terminate abnormally.
If you rely on SLP to provide the resolution of server names to IP addresses in your network and your RAS server does not forward IP multicast packets between the client and the network, then you must set up and configure SLP Directory Agents.
You can configure SLP Directory Agents through the Novell Client property pages or through DHCP.
IPX Compatibility Mode requires the services of SLP. For more information, see SLP Requirements for Server Name Resolution from RAS Clients.
Before installing the Novell IP Client with IPX Compatibility support, make sure that the RAS Client is configured to perform only IP networking over the RAS connections.
You must restart your workstation before re-establishing a RAS connection if
You can avoid the changing address problem over RAS connections if you statically configure the IP address that your workstation uses over the dial-up adapter.
You should be aware that limitations of the IPX stack present in Windows NT and limitations of 16-bit IPX/SPX applications complicate operations of multihomed workstations. These limitations impose additional configuration requirements to make use of the services of IPX Compatibility from your multihomed Novell IP Client.
Workstations connected to the network through more than one network attachment are considered to be multihomed workstations. LAN connections and RAS connections qualify as network attachments.
On Windows NT, the IPX stack does not allow IPX applications to detect more than one network attachment to segments with the same network number. This limitation forces you to configure different IPX Compatibility Network Numbers (also known as CMD Network Numbers) for each adapter used by your workstation to access the network if you want to allow your Novell IP Client to simultaneously access IPX Servers through each one of the adapters. For example, you could allow IPX Compatibility to use the default IPX Compatibility Network Number over the LAN adapter but configure a different network number for IPX Compatibility to use over the RAS connection (WAN adapter). You should be aware that nodes utilizing IPX Compatibility on the same network should be configured to use the same network number in order to directly communicate when using Client/Server IPX applications.
The IPX stack arbitrarily selects a network attachment for 16-bit IPX/SPX applications because those applications expect to operate on workstations with only one network attachment. For this reason, you might find that your 16-bit IPX/SPX applications are capable of communicating over your LAN adapter only when you also have a RAS connection over a WAN adapter.
If you have a multihomed Novell IP Client and you want to use the service of IPX Compatibility over only one of the network attachments and you are getting unwanted results, then you can disable IPX Compatibility over the other network attachments. For example, if you have a workstation connected to the corporate network through LAN adapter A and connected to a lab network through LAN adapter B, and IPX Compatibility only seems to work over LAN adapter B, you can force IPX Compatibility to work over LAN adapter A by opening the IPX Compatibility property page, selecting LAN adapter B, and unchecking the Enabled check box.
When the IP address of a given interface changes, you might not be able to restore the connections that you had to IPX servers from your Novell IP Client, or your IPX/SPX applications might stop working. If this occurs, you will have to restart your workstation to recover.
IP interface addresses can change because of TCP/IP manual configuration changes, because a DHCP lease expires and is renewed with a different address, or because your network connection goes down and then back up (such as when you re-establish a RAS connection).
You can avoid the changing address problem over RAS connections if you statically configure the IP address that your workstation uses over the dial-up adapter.
DOS utilities (CX, MAP, CAPTURE, etc.) are supported only when used with IPX or IP Compatibility Mode. Use the equivalent GUI-based utilities when accessing resources that are available only from IP servers.
Novell Client for Windows NT/2000/XP coexists with the Microsoft SMB Client over IPX networks. The Microsoft SMB Client utilizes NetBIOS when communicating over IPX, which increases the utilization of your network.
If you want to prevent the Microsoft SMB Client from communicating over NetBIOS, modify your workstation configuration by unbinding the workstation and server from NWLink NetBIOS in the Network Properties page.
Novell Client for Windows NT software does not work with Microsoft File and Print Services for NetWare (FPNW). This is because FPNW advertises itself as a NetWare 3.12 server but does not emulate a NetWare 3.12 server. It more closely emulates a NetWare 2.2 server. When the client attaches, it attempts to use features that are available on NetWare 3.12 servers. Since FPNW does not support these features, the client is unable to use FPNW.
A fix is available from Microsoft, but Novell testing indicates that the fix still does not provide a complete solution.