Microsoft KB Archive/288801

= Slow Computer Browsing from Multihomed Clients =

Article ID: 288801

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition

-



This article was previously published under Q288801





SYMPTOMS
With certain multihomed or multiple-transport configurations, computer browsing can be slow. This behavior may be normal.



CAUSE
This behavior can occur because of the following scenario:

If the browser client is trying to locate a browser server on each endpoint, it waits until it either one receives valid information or times out on each endpoint before returning. This process can be slow if there is an endpoint that does not contain browser servers. When this is completed, the lists are merged into one master list that is presented to the user.



RESOLUTION
To work around this behavior, use one of the following methods:
 * Use fewer protocols or network cards on a computer. In general, computer browser performance improves with fewer protocols or network cards on a computer.
 * The computer browser is dependent on NetBIOS; therefore, you may be able to disable NetBIOS on secondary interfaces. The computer browser client will not use interfaces with NetBIOS disabled.
 * Having a browser server available on all endpoints will speed up the process.
 * Ensure that WINS is available for TCP\IP networks.



STATUS
This behavior is by design.



MORE INFORMATION
The job of the computer browser client is to display a directory of all known computers or domains that the computer can reach. The client retrieves the list from the active browser servers on each of its active endpoints.

These endpoints include each network protocol that is running on each network card. For example, a computer with TCP/IP and IPX installed on the network interface cards A and B would have four endpoints for the computer browser client.

In this case, the browser client is trying to locate a browser server on each endpoint. It waits until it either one receives valid information or times out on each endpoint before returning. This process can be slow if there is an endpoint that does not contain browser servers. When this is completed, the lists are merged into one master list that is presented to the user.

This problem can also occur on remote access servers. The computer browser client will enumerate incoming remote access connections as valid endpoints. This will result in the following problem: From the remote access servers you can quickly browse the network neighborhood. After a remote access server client dials in, browsing becomes slow.

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

191611 Symptoms of Multihomed Browsers

133241 Browsing Domain Master Browsers with Multiple NICs and Protocols

Keywords: kbenv kbnetwork kbprb KB288801

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.