Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Hyper-V Problems Installing a VM. RDP Error?

Answered Hyper-V Problems Installing a VM. RDP Error?

  • Tuesday, January 15, 2013 3:31 PM
     
     
    Sign In to Vote
    0

    I'm new to Hyper-V, but not virtualisation and I'm tasked with setting up a virtual application server under Hyper-V.

    All seems pretty straight forward, set up VM, pointed at an ISO to install 2008 R2 server and powered it up. I can see the server booting in the preview window so I double click on the preview to try to connect so I can run through its installation;

    Remote Desktop Connection;

    An authentication error has occurred (Code: 0x507)

    Remote Computer: <fqdn of host server>

    OK, what does the event log say;

    Event ID: 12480 '<virtual machine>' failure in machine remoting system. Error: 'The client and server cannot communicate, because they do not possess a common algorithm.' (0x80090331). (Virtual machine<VM MAC>)

    So this seems to be an issue with RDP not communicating with Hyper-V, even though the VM isn't installed yet?

    Any suggestions/ ideas on how to progress?

     

All Replies

  • Tuesday, January 15, 2013 4:09 PM
    Moderator
     
     
    Sign In to Vote
    0

    How are you managing the Hyper-V Server?  

    Are you both domain joined?

    are you running the Free Hyper-V Server or a Windows Core or Full install with Hyper-V?

    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

     
  • Tuesday, January 15, 2013 4:19 PM
     
     
    Sign In to Vote
    0

    How are you managing the Hyper-V Server?  

    I'm logged onto the server directly, using Hyper-V Manager

    Are you both domain joined?

    The Hyper-V server is a DC, the VM hasn't even been installed yet; I can start the VM and see it boot in the preview window, but can't run through it's installation procedure as I can't connect to it.

    are you running the Free Hyper-V Server or a Windows Core or Full install with Hyper-V?

    It's a full install of Server 2008 (64-bit) Service Pack 2

     
  • Wednesday, January 16, 2013 6:40 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Is this a test environment? It’s never recommended but allowed to install Hyper-V role on a Domain Controller. It’s recommended to run Hyper-V on a domain member server or standalone server.

    If this is a test environment, it’s better to deploy the DC in a guest VM within the Hyper-V host server.

    > I can start the VM and see it boot in the preview window, but can't run through it's installation procedure as I can't connect to it.

    Did you mean you can’t connect to the VM through vmconnect.exe?

    You may try below article to fix such issue:

    Hyper-V Virtual Machine Connection and Direct Access
    http://blogs.msdn.com/b/thompal/archive/2009/11/06/hyper-v-virtual-machine-connection-and-direct-access.aspx

    For more information please refer to following MS articles:

    The Domain Controller Dilemma
    http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/11/24/the-domain-controller-dilemma.aspx

    Lawrence

    TechNet Community Support

     
  • Wednesday, January 16, 2013 9:16 AM
     
     
    Sign In to Vote
    0

    Thanks for getting back to me Lawrence,

    Hyper-V is installed on a DC as it's the only server in the environment (small network).

    >Did you mean you can’t connect to the VM through vmconnect.exe?

    Exactly, when I try to connect via vmconnect.exe it gives me 0x507 and generates Event ID: 12480 in the event log.

    I've read through your articles and don't think the problem is with DNS policy. The event log states 'The client and server cannot communicate, because they do not possess a common algorithm.' which looks like a certificate issue. When I look at the Hyper-V Virtual Machine Management Certificates mmc, the vmms/Personal certificate appears to be self signed with the fqdn of the host.

    Is it possible to reduce the security of RDP to negate certificates in Hyper-V (or across the entire system), purely as a troubleshooting step?

     
  • Wednesday, January 16, 2013 3:35 PM
     
     Answered
    Sign In to Vote
    1

    Hello

    May you check what version of rdp protocol is installed on your host first ?

    then eventually check if credssp is enabled.

    http://support.microsoft.com/kb/975943/en

    Regards

    ------------------------------------------------------- I understand a little computers.

     
  • Wednesday, January 16, 2013 4:19 PM
     
     
    Sign In to Vote
    0

    Hi Ales75,

    My RDP version is 6.1 and RDC version is 6.0.6002.18356

    I'll have to wait until tomorrow to run the hotfix in your comment as it will require a reboot of a live server.

    Is there a simple way to determine if credssp is enabled?

     
  • Wednesday, January 16, 2013 4:38 PM
     
     Answered
    Sign In to Vote
    1

    ok..

    except credssp, 

    cany go trough this link and see if helps you..

    http://virtualisationandmanagement.wordpress.com/2010/11/19/how-to-fix-the-unspecified-error-0x80004005-could-not-find-a-usable-certificate-windows-2008r2/

    then for credssp

    i am not sure but see if you can find these registry :

    HKEY_LOCAL MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\LSA

    AND SEE IF FIND A TSPKG VALUE.

    THEN GO TO :

    HKEY_LOCAL MACHINE\SYSTEM\CURRENTCONTROLSET\SECURITYPROVIDERS

    AND SEE if find a value like CREDSSP.DLL

    dont touch anything just check if you see them.

    Regards

    ------------------------------------------------------- I understand a little computers.

     
  • Wednesday, January 16, 2013 4:40 PM
     
     
    Sign In to Vote
    1

    before what i told you before..

    are you able to rdp from remote computer to the virtual machine ? not trough console. test it.

    Regards

    ------------------------------------------------------- I understand a little computers.

     
  • Thursday, January 17, 2013 11:09 AM
     
     
    Sign In to Vote
    0

    Thanks again for looking at this with me.

    I can't log into the virtual machine as it's not even installed yet. I can see it booting off the iso in the preview window, so when I invoke vmconnect.exe via the hyper-v manager to run through its installation, I get the error messages.

    I've looked at the registry ans the TSPKG value isn't there. So I need to enable CREDSSP. I'll run through that asap (any pointers?)

    Also, I  checked the certificate store for Hyper-V and they're good for another 6 months; this is a fresh install.

    I'll update the thread as soon as I know more.

     
  • Thursday, January 17, 2013 3:26 PM
     
     
    Sign In to Vote
    0

    OK, no good news as yet.

    Firstly, Certificates. I've checked the expiration dates of the certificates for Hyper-V under the Hyper-V Machine Management section of the Certificates mmc and the self signed certificate expires on 03/06/2013, so that doesn't seem to be the issue

    Secondly, CREDSSP, I do not have the registry keys you outlined

    HKEY_LOCAL MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\LSA

    TSPKG


    HKEY_LOCAL MACHINE\SYSTEM\CURRENTCONTROLSET\SECURITYPROVIDERS

    CREDSSP.DLL

    So, how do I enable credssp and will it have an impact on anything else (this server is a DC)?

    Thanks

     
  • Thursday, January 17, 2013 3:47 PM
     
     
    Sign In to Vote
    1

    Did you check if updates as told by me are presents ?


    http://support.microsoft.com/kb/975943/en

    http://support.microsoft.com/kb/955805

    then

    do you have any host file configured in the network adapter ?

    ------------------------------------------------------- I understand a little computers.

     
  • Thursday, January 17, 2013 4:13 PM
     
     
    Sign In to Vote
    0

    I've just installed the first hotfix, which does sound very promising, but unfortunately it has made no difference.

    The second hotfix gave "not for your system"

    The servers hosts file is standard, but as the VM doesn't even have an IP address yet...

    I'm interested in the credssp route, but cant find a decent resource that explains how to enable it

    I'll try reinstalling Hyper-V altogether to see if there is a corruption there tonight and let you know if it makes any difference.

    If you have any other ideas in the meantime... 

     
  • Thursday, January 17, 2013 4:18 PM
     
     
    Sign In to Vote
    1

    put this kb in google and the result is a fix for me

    9758284

    i really hope it is that..

    ------------------------------------------------------- I understand a little computers.

     
  • Thursday, January 17, 2013 4:19 PM
     
     
    Sign In to Vote
    1

    have you tried to reboot the server after update etc ?

    ------------------------------------------------------- I understand a little computers.

     
  • Thursday, January 17, 2013 4:28 PM
     
     
    Sign In to Vote
    1

    Tri if you can apply this too

    http://support.microsoft.com/kb/2665347/en

    are you sure your server is fully updated ?

    ------------------------------------------------------- I understand a little computers.

     
  • Thursday, January 17, 2013 4:31 PM
     
     
    Sign In to Vote
    1

    do you have a virtual switch ?

    did you choose to share it with the management os ?

    Regards

    ------------------------------------------------------- I understand a little computers.

     
  • Thursday, January 17, 2013 4:57 PM
     
     
    Sign In to Vote
    0

    Wow, there's a lot to do here. I'll feedback my results.

    FYI, there's no virtual switch, we're not at that level yet

     
  • Tuesday, January 22, 2013 11:53 AM
     
     
    Sign In to Vote
    0

    Hi Again Ales75, sorry for the late response but it's been a while since I've been able to get downtime on this server.

    Unfortunately the hotfixes you mentioned have either not worked or are are "not for your system"

    I'm stood at the server now. Contrary to a previous comment, this is NOT Server 2008, but SBS 2008 (Server FE?) which I assume will have an impact on the issue?

     
  • Tuesday, January 22, 2013 2:35 PM
     
     
    Sign In to Vote
    1

    Hello

    the hotfixes were for the hyper host server.. not for the virtual machine you cant connect too.. 

    what do you mean this is not 2008 but sbs 2008 ?

    can you tell me exactly the host and the vm what os run ?

    sbs 2008 it is like windows 2008 server, ok little different but this is not the case, for the issue..

    Regards

    ------------------------------------------------------- I understand a little computers.

     
  • Tuesday, January 22, 2013 9:47 PM
     
     
    Sign In to Vote
    0
    The host server is SBS 2008 Standard 64 bit (SP2), the VM I'm trying to install in Hyper-V is 2008 R2. I thought I'd confirm due to so many hot fixes give the hotfix error; does not apply to your system.
     
  • Tuesday, January 22, 2013 10:14 PM
     
     
    Sign In to Vote
    0
    DO YOU MEAN YOU INSTALLED HYPER V ROLE INTO SMALL B SERVER STANDARD 2008 ????????!!!!!!!!!!!!

    ------------------------------------------------------- I understand a little computers.

     
  • Wednesday, January 23, 2013 8:33 AM
     
     
    Sign In to Vote
    0
    Yes. Is that a problem?