Protocol Failure Causes Browser Events 8021 and 8032

 Last reviewed: January 14, 1998
Article ID: Q153811
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SYMPTOM

Your Windows NT Server or Workstation may log the following events at startup: 

   Event ID: 8021
   Source: WINS
   Description: The browser was unable to retrieve a list of servers from
   the browser master <PDC> on the network \device\<protocol_netcard>. The
   data is the error code.

   Event ID: 8032
   Source: WINS
   Description: The browser service has failed to retrieve the backup list
   too many times on transport of <protocol_netcard>. The backup browser
   is stopping.

CAUSE

There is a problem with one of the installed protocols or the browser service is not functioning properly on one or more of the installed protocols.

RESOLUTION

To troubleshoot this problem, start with one of the following steps:

  1. In the Control Panel Services tool, stop and start the Computer browser.

    -or-

  2. Restart the computer.

After either of these steps, wait at least 10 minutes to see if the errors still occur. If they do, continue troubleshooting by cross-referencing two pieces of information. The first is to check the transport that failed in the event log. For example, error 8021 displays a message similar to the following: 

   The browser was unable to retrieve a list of servers from the
   browser master \\<server_name> on the network
   \Device\NetBT_<driver_name>. The data is the error code.
The important data is \NetBT_<driver_name>, that indicates the protocol and netcard binding, also known as an "endpoint." The potential protocols you may see are: 

   Nbf_netcard    =  NetBEUI
   NetBT_netcard  =  TCP/IP (or NetBIOS over TCP/IP)
   NwlnkIpx       =  IPX/SPX (NwLink)    [will not indicate netcard]
   NwlnkNB        =  NetBIOS over NwLink [will not indicate netcard]
After you have determined the failed protocol endpoint, check the working status of the browser service on all installed protocols with the Windows NT Resource Kit program Browstat.exe. At a command prompt, type the following command: 

   browstat status
This will enumerate the browser status on all endpoints. Look for the message Browser is NOT active on domain under each endpoint. Disregard data about endpoints that list "NdisWanX" (such as \Device\NetBT_NdisWan5); these are RAS endpoints and will usually list the error anyway.

You should find a protocol match between these two steps. The next step is to record any important information about the protocol from Protocol Setup in the Control Panel Network tool. Then remove the protocol, restart the computer, and see if the error no longer gets logged (remember to wait at least 10 minutes). Then try reinstalling the protocol, checking for the error, and reapplying the service pack that exists on the current Windows NT installation.

If the error persists after a protocol reinstallation, you may have problems with the network adapter card. Check with the vendor to see if there is an updated driver, or try another network adapter card.

MORE INFORMATION

The computer running Windows NT does not have to be multihomed for this problem to occur, and this problem is not localized to any specific protocol or combination of protocols. Also, this condition may occur if the browser service functions properly over one protocol, but fails over another. Thus, your Windows NT system may be getting a partial or complete browse list as far as you can tell, yet still logging these errors.

Additional query words: prodnt
Keywords : nthowto ntnetserv NTPROTOCOL NTSrvWkst kbnetwork
Version : WinNT:3.5,3.51
Platform : winnt

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 14, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.