there is no communication between host and hyper-V VM via an internal hyper-v virtual switch

Michal Jan Gorol 0 Reputation points
2024-02-11T11:23:54.7733333+00:00

I run Windows10 on a host machine and setup just one hyper-V VM running also windows 10.

Now I want that those two mashines can communicate via network.

As I understand this shall be a fairly simple setup:

  • setup an internal virtual switch via hyper-v manager> virtual switch manager,
  • and then select that same virtual switch in the VM settings > Network adapter, to connect to
  • I set up the IP addresses to be in the same subnet (both on the eth adapter related to my new switch that is automatically created on the host, and in the VM

I disabled the windows firewalls on both host and VM.

As a test I run a ping command, but there is no reply - eihter way.

The above procedure is so simple that the problem must be somewhere else.

I would appreciate some tips as where to start the trouble shooting or another advice (maybe I don't need an internal switch , maybe I can use the default switch?)

(I did some more checking without success but it would be just a noise to post in the beginning here)

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-02-20T06:59:28.4033333+00:00

    Hi Michal Jan Gorol,

    Thanks for your post. You can't ping your VMs from your host by design. Using "Internal network" allows multiple VMs to communicate together on an internal network but this network is not open to the outside world, including the host. However, if you have configured the static Ips for VMs and host. You can run ipconfig /all to see if the Ips are already exist in the output. If so, please refer the following directions to troubleshooting the network issue.

    • Network adapter misconfiguration – An incorrectly configured network adapter is the most common cause of a missing IP address. If the network adapter in the VM is not configured correctly, it won’t be able to connect to the network and obtain an IP address
    • DHCP server issue – DHCP servers assign IP addresses to devices on the network. The VM won’t receive an IP address if the DHCP server is down or has issues
    • Network connectivity issues – If there are network connectivity issues between the VM and the host machine, the VM won’t be able to communicate with the network and obtain an IP address. Incorrect VLAN configurations, router misconfiguration, etc, can lead to a lack of connectivity
    • Firewall or antivirus software – Sometimes, firewall or antivirus software can block legitimate traffic, preventing the VM from connecting to the network and obtaining an IP address
    • Virtual switch configuration – If the virtual switch is misconfigured, the VM may not be able to communicate correctly or in a way that is expected

    Best Regards,

    Ian Xue


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.