Microsoft KB Archive/255195

From BetaArchive Wiki
Knowledge Base

NetBIOS Scope ID Causes Windows 2000 Domain Controller to Stop Responding on Boot

Article ID: 255195

Article Last Modified on 2/28/2007


  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Datacenter Server

This article was previously published under Q255195

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


When a Windows 2000 domain controller has a NetBIOS scope ID defined, it may appear to stop responding (hang) during boot with a "Preparing Network Connections" message. If the computer is allowed to sit for two hours or longer, the boot process may finish.


To resolve this issue, remove the NetBIOS scope ID from the registry of the Windows 2000 domain controller, using the following steps.

NOTE: This action can break communication with other NetBIOS-based computers that have the scope ID defined.

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.

  1. Allow the domain controller to boot completely, or reboot into Safe mode.
  2. After the computer is completely booted, log on as an administrator.
  3. Run Regedt32.exe.
  4. Delete the following registry key:


  5. Reboot normally.


Microsoft has confirmed this to be a problem in Microsoft Windows 2000.


NOTE: The use of NetBIOS scopes as described in this article is included only as a convenience for limited situations in which they absolutely must be used, and no other alternatives exist (such as VLANs, IPSec, more restrictive use of NTFS and share security, and so on). The use of NetBIOS scopes is discouraged, and there are no guarantees that NetBIOS scopes will be supported in future releases of Microsoft products.

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

204279 Direct Hosting of SMB Over TCP/IP

254542 Windows 2000-Based Computers Can Communicate with Different NetBIOS Scope IDs

Keywords: kbbug kbenv kbnetwork kbpending kbsmb KB255195