Connection to a Virtual Machine running in Hyper-V fails

Article ID: 961723 – Last Review: January 5, 2009 – Revision: 1.0

Connection to a Virtual Machine running in Hyper-V fails

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptom

In Windows 2008, when you use VMConnect  and Remote Desktop Connection to connect a Hyper-V Guest, after you enter your logon credentials, you may receive the following error:

No authority could be contacted for authentication. For assistance, contact your system administrator or technical support.

Cause

This problem occurs because the version number of the KRBTGT account increases when you perform an authoritative restoration. The KRBTGT account is a service account that is used by the Kerberos Key Distribution Center (KDC) service.

Resolution

To resolve this problem, apply the Hotfix mentioned in this section to all the Windows Server 2003-based domain controllers in the domain. This Hotfix prevents the problem before you perform an authoritative restoration. This Hotfix also fixes the problem when you have already performed an authoritative restoration

 

939820 Error message when you try to use Remote Desktop Connection to connect to another Windows Vista-based computer in Windows Vista: No authority could be contacted for authentication

/939820 (http://support.microsoft.com/default.aspx?scid=kb;en-us;939820)

More Information

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 (http://vkbexternal/VKBWebService/ViewContent.aspx?scid=kb;EN-US;889100&PortalId=1) How to obtain the latest service pack for Windows Server 2003

You must restart the computer after you apply this Hotfix.

This Hotfix does not replace any other hot fixes.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.


APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
Keywords: 
kbnomt kbrapidpub KB961723

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image