Article ID: 194827 - View products that this article applies to.
This article was previously published under Q194827
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you are working in a mixed network server environment, connecting to Novell NetWare servers (using Novell's IntraNetWare Client [Client32] version 2.2) and to Microsoft Windows NT and other SMB-based servers (using Microsoft's Client for Microsoft Networks), connecting to a NetWare server may sometimes take a long time.
This problem can occur if all of the following conditions exist:
Under these conditions, Windows attempts to resolve the server name first using the NetWare network client, then using the Microsoft Networking client. When the NetWare server does not respond to the request to resolve the server name using Service Advertising Protocol (SAP), the Microsoft Networking client attempts to resolve the name using DNS. Because the NetWare server is registered with the DNS server, the DNS server may be able to resolve the NetWare server name sooner than the NetWare server itself can respond to the SAP request.
If this behavior occurs when the conditions listed above exist, the NetWare server name may be incorrectly marked as a Microsoft (SMB-based) server name when it is saved in the local registry. Subsequently, attempts to connect to that server name refer to the information stored in the registry and use the Microsoft Networking client first, and try to connect using the NetWare client only after the first attempt times out. Because of the length of the time-outs specified for DNS name resolution and TCP/IP connection operations, it may take one minute or more for the first attempt to connect to the NetWare server to time out, after which Windows tries to connect using the NetWare client.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You can work around this issue by using any of the following methods:
This functionality is included in Microsoft Windows 98, and can be enabled by setting the "MaxElements" registry value to zero, as documented above.
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2).
This issue is documented in the Novell Knowledge Base as document 2929988, "Slow Client Performance Due to DNS Query." The Novell Knowledge Base can be accessed from the following Internet location:
The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Microsoft in no way guarantees the accuracy of this third-party contact information.
For additional information about Windows 98 and Windows 98 Second Edition hotfixes, click the article number below to view the article in the Microsoft Knowledge Base:
206071For additional information about Windows 95 hotfixes, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/206071/EN-US/ )General Information About Windows 98 and Windows 98 Second Edition Hotfixes
(http://support.microsoft.com/kb/161020/EN-US/ )Implementing Windows 95 Updates
Contact us for more help
Connect with Answer Desk for expert help.