Home / server / Questions / 274802
Accepted
ChrisA
Asked: 2011-05-29 03:19:39 +0800 CST

Cannot connect to a Hyper-V Virtual Machine

  • 772

I've been setting up a Windows Server 2008 R2 locally - all went well, and I added the Hyper-V role. Then I created a new VM using the Hyper-V Manager, and added a dynamic VHD.

I could start the VM and connect to it, within Hyper-V Manager. I did not, at that point, install an OS on it.

Up to that point, the host computer had been running on my local network. Then, it was shipped to a colocation company, and now has a new IP address.

It has an IPSEC policy assigned, that allows IP traffic from my local IP address, so I can remote into it via RDP, and my userid, which is in the Administrators group for the host server.

However, I can no longer connect to the VM within Hyper-V Manager. I can see that it's running from the thumbnail, but connecting to it seems to time out.

Would appreciate any suggestions. I've tried deleting and recreating the VM, but the result is the same.

Edit:

In case I wasn't clear:

  • There is no OS on the VM
  • I could connect to the VM from the Hyper-V manager before the host machine was shipped to the colo, now I can't

(Yet) another edit!

This is what my IPSEC filter looks like now:

enter image description here

But I still can't connect.

Final edit:

It doesn't let you create a rule where the source and destination IPs are the same, but reasoning that any traffic from 'My IP address' must be Ok, I added the following rule, and it seems to do the trick:

enter image description here

Still not really sure why the more complicated one isn't allowing the local traffic, but I seem to be Ok now. My thanks for the suggestions.

hyper-v

2 Answers

  1. Best Answer

    I would suggest looking at the IPSEC policy.

    It has an IPSEC policy assigned, that allows IP traffic from my local IP address

    What about the localhost address? and it's own external address?

    The Hyper-V connection tool must connect to it, too, and it does not come from your home address. The IpSec policy possibly filters that traffic out.

    • 1

  2. If you have locked yourself out of the VM with its guest OS level configuration(s), then one possible approach may be to:

    • create another VM without the guest OS misconfiguration and with a NIC assigned to the internal VM-Net
    • configure the new VM as a DHCP server for the internal VM-Net with a similar configuration to your local IP net (e.g. the mis-configured limitation of your subject VM)
    • add an additional NIC to the problematic VM assigned the internal VM-Net

    The result will be where the new VM should be able to access your subject VM based upon it now being able to mimic your local net across the internal VM-Net - which is the mis-configuration of your subject VM.

    • -1