Microsoft KB Archive/936243

= 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 =

Article ID: 936243

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems

-



SYMPTOMS
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 &quot;X&quot; 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.



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



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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:

889100 How to obtain the latest service pack for Windows Server 2003

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 SP2, x64-based versions


WORKAROUND
To work around this problem, follow these steps:  Click Start, click Run, type dnsmgmt.msc, and then click OK. Right-click the problematic DNS server connection node, and then click Delete. Click Yes to confirm the deletion. Right-click DNS, and then click Connect to DNS Server. Click The following computer, enter one of the following items, and then click OK:  A dot (.)</li> The fully qualified domain name (FQDN) of the DNS server</li> 127.0.0.1</li></ul>

Note We recommend that you type a dot or the FQDN. &quot;127.0.0.1&quot; may not work in some cases.</li></ol>

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

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
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:

http://www.microsoft.com/technet/security/advisory/935964.mspx

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: dns mmc rpc connection for LPC fails 15 char computer name

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB936243

-

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

© Microsoft Corporation. All rights reserved.