none
RDP to VM connects only to Hyper-v server RRS feed

  • Question

  • Hyper-v server with one VM (for now).  VM is running WHS 2011.  Hyper-v remote manager is working from Vista, but I cannot RDP into the VM... RDP to either NIC results in connection to the Hyper-v server.  Console in remote manager is working.  Also, with Hyper-v Server firewall enabled, I cannot ping either of the two NICs (on board and PCI card).  I have the onboard NIC is configured as "external" for the VM.  Both adapters are on same subnet.  Remote desktop is enabled in WHS.
    Saturday, April 21, 2012 3:34 AM

Answers

  • Answered my own question...

    As I'm new to hyper-v, I didn't get the distinction between the physical nic and the virtual world.  so my WHS 2011 VM was getting it's own IP from DHCP.  Assigned a static IP, updated hosts, and now I'm happy RDP without issues.

    Sorry for the noob question, and thank you all for offering the help.

    • Marked as answer by jtnorman Sunday, April 22, 2012 6:03 PM
    Sunday, April 22, 2012 6:03 PM

All replies

  • First try to ping that virtual machine; if the ping works check the VM firewall, event tought when you enable RD the firewall is automatically configured to let the RDP traffic, but you can still check it and isable it for troubleshooting. Now try to make a RD connection using the VM IP address, if that works you have name resolution problems, but we'll take care of that after you confirm that is working using the VM IP address.

    Adrian Costea - MCP, MCTS, MCSA 2003, MCITP: Windows 7

    My Blog: www.vkernel.ro/blog

    Saturday, April 21, 2012 9:36 AM
  • Hi,

    Did you remote desktop into the virtual machine with computer name or IP address? If you use the correct computer name or IP address, you will be able to remote desktop into the virtual machine properly.

    By the way, please try to disable the firewall and then try to ping the Hyper-V host machine again.



    Vincent Hu

    TechNet Community Support

    Saturday, April 21, 2012 1:08 PM
    Moderator
  • try to telnet to that vm using port 3389

    ex

    telnet 192.168.1.1 3389

    also as vincent said if you using computer name check your dns severs functionality.


    Darshana Jayathilake

    Saturday, April 21, 2012 4:54 PM
  • Hi,

    you wrote that you can connect with the remote manager. So I would sugest that you check these two things:

    1. Has the VM an IP Address that you can reach from the client where you try to establish a RDP session?
    2. Is RDP Enabled on the VM. In most new Windows OSes you have to enable it first.


    Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa | www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

    Saturday, April 21, 2012 7:19 PM
  • With Hyper-v host firewall enabled, I cannot ping either NIC.  Disabling firewall on hyper-v host allows me to ping both.  I can sucessfully RD to both NICs, however the resulting connection to ether card is to the hyper-v host (this works with hyper-v host firewall enabled or disabled)....very strange, since in other respects, the VM running WHS 2011 appears to be using the onboard NIC properly.

    I am in a home network environment, so I do not have an internally configured DNS server.  I am using hosts to resolve IPs.  Resolution is working correctly....I can use machine name or IP, with the same result....connection to the hyper-v host.

    In short, I cannot connect to the VM using RDP using either IP or machine name.

    I look forward to your response.

    Sunday, April 22, 2012 5:08 PM
  • I cannot RDP to the VM. I can get to the VM via the hyper-v remote manager.

    With Hyper-v host firewall enabled, I cannot ping either NIC.  With the host firewall disabled, I can ping both NICs.

    As stated in response to adrian.costea, I'm using "hosts" file for name resolution, which is working properly.  I do not have a DNS server configured for name resolution on my 192. network.

    I'm experienced enough to get myself in trouble, but this seems to me to be an issue of the intended NIC for the VM not being properly "bound" to the VM, so RDP traffic is going to the hyper-v host, rather than the VM....just exposed my noob status...oh well...

    Sunday, April 22, 2012 5:18 PM
  • telnet to either nic results in blank screen connectivity...ie it does not return a error.
    Sunday, April 22, 2012 5:19 PM
  • Question1 - The NIC for the VM is on the same subnet, with only the switch in between.  With the hyper-v host firewall disabled, I can ping both the nic intended to be used for the VM and the nic intended to be used for the hyper-v host.

    Question 2 - I have remote desktop enabled in the WHS 2011 control panel, and the whs 2011 VM firewall rules for RDP are active.  I also have my non-administrator account added as a RD user.

    Thanks for your response.

    Sunday, April 22, 2012 5:23 PM
  • Answered my own question...

    As I'm new to hyper-v, I didn't get the distinction between the physical nic and the virtual world.  so my WHS 2011 VM was getting it's own IP from DHCP.  Assigned a static IP, updated hosts, and now I'm happy RDP without issues.

    Sorry for the noob question, and thank you all for offering the help.

    • Marked as answer by jtnorman Sunday, April 22, 2012 6:03 PM
    Sunday, April 22, 2012 6:03 PM