The "NBTSTAT -RR" Command Does Not Refresh All Names on Multihomed Computers (304559)



The information in this article applies to:

  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server 4.0

This article was previously published under Q304559

SYMPTOMS

When you run the nbtstat -RR command to release and refresh the NetBIOS names on a multihomed computer, all names are released on all adapters. However, the names are refreshed on only the primary network adapter, instead of being refreshed on all adapters.

This issue causes Windows Internet Name Service (WINS) name registrations to be lost for non-primary adapters, which can prevent other computers on the network from communicating with the multihomed computer.

CAUSE

This issue occurs because an incorrect parameter is passed to the function that starts the refresh operation. The incorrect parameter inhibits the refreshing of names on all but the primary network adapter.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date         Time   Size     File name  Platform
   ------------------------------------------------
   08-Aug-2001  00:49  124,688  Netbt.sys  Intel
   08-Aug-2001  00:43  224,976  Netbt.sys  Alpha
				
NOTE: Because of file dependencies, this hotfix requires Windows NT 4.0 Service Pack 6a (SP6a).

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbenv kbfix kbQFE KB304559