Windows Vista-based client computers do not use the node type that you specify for name resolution on the DHCP server

You use a Dynamic Host Configuration Protocol (DHCP) server to assign TCP/IP configurations to client computers. You set the WINS/NBT Node Type scope option to a specific node type. However, one or more Windows Vista-based client computers do not use the node type that you specify for name resolution.

For example, you set the WINS/NBT Node Type scope option to P-node (0x2) to configure client computers to use P-node name resolution. However, some Windows Vista-based client computers do not use P-node name resolution. Instead, if these computers cannot resolve the host name by using a NetBIOS name server, they broadcast requests. This behavior causes unexpected traffic in the network environment.

Note In the P-node configuration, client computers should not broadcast requests even if the computers cannot resolve the host name by using a NetBIOS name server.

This problem occurs if the DHCP Client service on a Windows Vista-based client computer does not have permission to write the following registry subkey:This registry subkey controls the client node type. If a computer cannot write this registry subkey, the computer uses a default configuration that is based on the following principles:

• If no NetBIOS name server is configured for the client computer, the computer uses B-node.
• If one or more NetBIOS name servers are configured for the client computer, the computer uses H-node.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.After you apply this hotfix, the DHCP Client service has permission to write the registry subkey.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you can obtain new TCP/IP configurations from the DHCP server by restarting the computer. Or, you can type the following commands to obtain the new configurations. Press ENTER after each command.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, 32-bit versions

Windows Vista, 64-bit versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

To work around this problem, manually set the node type in the client computer's registry. To do this, follow these steps:

1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netbt\Parameters
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type NodeType, and then press ENTER.
5. Right-click NodeType, and then click Modify.
6. In the Value data box, type the desired value, and then click OK.
   
   Note To use P-node name resolution, set this value to 2.
7. Exit Registry Editor.

For more information about name resolution in NetBIOS over TCP/IP, click the following article number to view the article in the Microsoft Knowledge Base: For more information about DHCP, visit the following Microsoft TechNet Web site:For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: