1 - MUP.SYS mishandling UNC requests:
Obtain the latest MUP.SYS from Microsoft. Reference document Q171386 when requesting this file. A hot fix has not been generated for this file, but should be available in the next service pack. Then promote the NetWare redirector by going to Control Panel, Network, Services, NetWork Access Order button, and promote NetWare Services to the top of the network provider list.
Use Microsoft Service Pack 4.
This solution is acceptable, even for networks using a lot of Microsoft Networking. Because Microsoft's name resolution time can be extreme (up to 30 seconds), compared to Novell's name resolution time (usually 1 second), the change in speed for Microsoft networking will hardly be noticed.
2 - Unnecessary requests made by the intraNetWare Client v4.11a for NT:
Obtain CLNWIN32.DLL dated 7-10-97 or later. This dll is included in the patch to the 4.11a client called nt411p1.exe. To obtain this file, use the File Finder on http://support.novell.com.
*NOTE* This version of CLNWIN32.DLL applies ONLY to the 4.11a build of the client. It will cause problems with later revisions (eg. the 4.12 NDS for NT client) since they were written to different code bases.
OR use the NT client version 4.3 or later.
This fix will not impact performance as much as the other options listed.
3 - NT machine configured as an H-Node:
Configure the workstation as an P-Node. If a WINS server is implemented, in contrast to the H-Node configuration, the P-Node configuration will only query the WINS servers. If all WFWG, WIN95 and WINNT machines are using the WINS server, the Netbios broadcasts will not be missed because all the Microsoft machine names will be resolved.
The node type can most easily be changed by using DHCP. The node type is configured when the IP stack gets and IP address assignment from the DHCP server.
The Microsoft redirector's name resolution is time consuming when the MUP is looking for Netware server, a 3rd party server or if the server name does not exist. Switching the computer type from an H-Node to an P-Node is highly recommended when a WINS server is available.
Note: All of these solutions are interrelated, and depends on individual environments. As explained previously, not all environments are affected by poor performance. Any one solution may not be appropriate for your environment.
Understanding all the implications of these changes is beyond the scope of this TID, but the most useful information and facts are highlighted in this TID.