none
created a hyper-v then imported a VMDX provided by the vendor

    Question

  • Created a hyper-v then imported a VMDX provided by the vendor.  When this VM is started up, the NIC was configured. The vendor application installed as well.

    The vendor provided a VMDX which goes online as a linux machine.  It starts up then we add a IP in the same subnet as the hyper-v host.   The IP added was pinged and nslookup to confirm no other devices are using this IP.  We added valid DNS servers.  The vmdx was imported as a COPY (create new ID for virtual machine).   Virtual switch is set as External and no other options are chosen.

    The hyperv host can ping other network servers however this linux VM cannot ping or nslookup anything.  This Linux VM cannot even ping the default gateway.

    This hyper-v host is in Azure and we have confirmed the network security group (NSG) is configured identical to other working NSGs.

    Please recommend how to get this server to communicate.  Is there something wrong with the virtual network switch??


    dsk

    Friday, August 10, 2018 2:59 AM

All replies

  • Hi ,

    Ping is blocked by default for Azure VMs for security reasons。

    Please try to allow ICMP by configuring appropriate firewall rules or use port pings instead of ICMP to test Azure VM connectivity.

    For your reference:

    HOW TO ALLOW PING FUNCTIONALITY TO WINDOWS AZURE MACHINES?

    https://blogs.msdn.microsoft.com/microsoft_azure_guide/2014/12/13/how-to-allow-ping-functionality-to-windows-azure-machines/

    Use port pings instead of ICMP to test Azure VM connectivity

    https://blogs.msdn.microsoft.com/mast/2014/06/22/use-port-pings-instead-of-icmp-to-test-azure-vm-connectivity/

    Regarding Azure based issue, I suggest you refer to experts from the following forum to get professional support:

    https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=WAVirtualMachinesforWindows

    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Friday, August 10, 2018 8:49 AM
  • Hi ,

    Just want to confirm the current situations.
    Please feel free to let us know if you need further assistance.
     
    Best Regards,
    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Tuesday, August 14, 2018 9:10 AM
  • Hi KimDav,

    I would look at this from inside the VM and outside the VM on the Hypervisor.

    Inside the VM is standard Linux questions ... run ifconfig and check that the addressing is correct and that the address is valid for the VLAN that this is to run in.

    Outside the VM, check that the VLAN is correct on the VM within Hyper-V and that the vSwitch you are using is configured for that VLAN.

    Lastly, check the Physical Switch port that the Hypervisor connects into (that the vSwitch goes over) and check that the Switchport is configured to permit that VLAN.


    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Tuesday, August 14, 2018 9:40 AM
  • Hi ,

    Was your issue resolved?
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Wednesday, August 15, 2018 7:58 AM