Microsoft KB Archive/262963

= Client Cannot Find New System When NetBIOS Name Is Removed and Reregistered =

Article ID: 262963

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition

-



This article was previously published under Q262963



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:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
The NetBIOS functionality enables client computers to register more than one NetBIOS name. If the NetBIOS name is unregistered by one system, and then registered by another system, the Windows 2000-based client does not find the new system that registered the name if the Windows 2000-based client has already resolved the NetBIOS name.



CAUSE
This issue occurs because Windows 2000-based clients do not clear the NetBIOS over TCP/IP (NBT) name cache after they receive a negative session response from a server. This behavior causes the Windows 2000 clients to attempt to connect to the server that had the name registered the first time the name was resolved to an IP address.



RESOLUTION
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.

To resolve this issue, add or change the following registry value on the client computer:  Start Registry Editor (Regedt32.exe). Locate the following key in the registry:

HKEY_LOCAL_MACHINE\CurrentControlSet\System\Services\netbt\parameters

 On the Edit menu, click Add Value, and then add the following registry value:

Value Name: TryAllNameServers

Data Type: REG_DWORD

Value: 1

 Quit Registry Editor.



MORE INFORMATION
You can use the nbtstat -R command to manually clear the NBT cache.

The following sequence demonstrates the issue described in the &quot;Summary&quot; section:
 * 1) Create a directory share named &quot;Test&quot; on both   and.
 * 2) Register &quot;Vcom&quot; as an additional NetBIOS name on   by using the NetServerComputerNameAdd API.
 * 3) On a Windows 2000-based client, run the following command: dir \\vcom\test. This command completes successfully.
 * 4) Delete the &quot;Vcom&quot; NetBIOS name on   by using the NetServerComputerNameDel API.
 * 5) Register the NetBIOS name &quot;Vcom&quot; on   by using the NetServerComputerNameAdd API.
 * 6) On the Windows 2000-based client, run the following command: dir \\vcom\test. The command does not complete successfully.

Keywords: kbenv kbfaq kbfix kbnofix kbprb KB262963

-

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

© Microsoft Corporation. All rights reserved.