When you try to connect to a DNS server by using the DNS snap-in (Dnsmgmt.msc) on a Windows Server 2003-based computer, the connection fails

When you try to connect to a Domain Name System (DNS) server by using the DNS snap-in (Dnsmgmt.msc) on a Microsoft Windows Server 2003-based computer, the connection fails. In the console tree, you see a red "X" next to the DNS server connection node. This problem occurs if the following conditions are true:

• The DNS remote procedure call (RPC) interface is configured to use only local procedure calls.
• You connect to the DNS server by using a NetBIOS name.
• The DNS server has a computer name of 15 characters.

Note This problem also occurs when you use other DNS management tools that are based on DNS RPC. For example, this problem also occurs when you use the Dnscmd.exe tool.

This problem occurs because the DNS management tool incorrectly allocates a buffer.

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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

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 Server 2003 with SP1, x86-based versions

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003 with SP2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with SP2, x64-based versions

To work around this problem, follow these steps:

1. Click Start, click Run, type dnsmgmt.msc, and then click OK.
2. Right-click the problematic DNS server connection node, and then click Delete.
3. Click Yes to confirm the deletion.
4. Right-click DNS, and then click Connect to DNS Server.
5. Click The following computer, enter one of the following items, and then click OK:
   • A dot (.)
   • The fully qualified domain name (FQDN) of the DNS server
   • 127.0.0.1
   Note We recommend that you type a dot or the FQDN. "127.0.0.1" may not work in some cases.

Note After you follow these steps, the problem is resolved only for the administrator who is currently logged on to the computer.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

As an example, you would configure DNS RPC to use only local procedure calls after you have followed Microsoft Security Advisory 935964. This security advisory discusses how to remove a vulnerability in RPC. For more information about Microsoft Security Advisory 935964, visit the following Microsoft TechNet Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: