This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We have a Windows Server Core 2019 Hyper-V server serving four Hyper-V Clients (two Windows Server 2019 GUI) and (two Windows Server Core 2019 Servers). The Hyper-V Server has full network connectivity and is a member of a domain. All 4 Virtual Machines are pingable from the Hyper-V host and each VM can ping the Hyper-V Server. They are on a 10.18.21.0-10.18.21.255 network with a gateway 10.18.21.1. The Hyper-V host and one VM has full network connectivity however the other three VMs cannot ping their default gateway 10-.18.21.1 or reach the rest of the network.
These three VMs are not reachable via connecting from Windows Server Admin also.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi, I'm David.
The Microsoft Community is a forum for home users.
Due to the scope of your question, I suggest that you access the link below, which will direct you to the Microsoft Q&A page.
https://docs.microsoft.com/en-us/answers/index....
Microsoft Q&A has IT professionals and system admins who can best help you with this type of question.
Best regards.
