Problem with network connectvity with Windows Hyper-V?

Discussion in 'Windows Virtual Machine' started by GarethP1, Sep 12, 2016.

  1. GarethP1

    GarethP1 Bit poster

    Messages:
    8
    Hi,
    I've got a problem connecting Hyper-V guest VMs to the internet.

    I created a Parallels (Desk 12 Pro) VM of Win10Pro, with 2 network cards - in bridged mode. This Win10Pro guest OS works well, both MACs are seen by the router and the correct local IP addresses are given to them.

    In the Win10Pro VM I added Hyper-V. Then created a single Win10 Hyper-V guest VM. To connect this Hyper-V guest I created an External Virtual Switch to one of the network cards.
    And that only partially works. The router can see the MAC address of the Hyper-V guest, and it gives it an IP address. From the Hyper-V guest I can ping the host.

    But when I try to connect to any other ip address (local and internet) I get either "Destination host unreachable" or "Request timed out".

    Can anyone help?

    (If I make the network connection "Shared" mode in the outer Parallels VM, then both the Win10Pro VM and the Hyper-V guest can connect to the internet. But I cannot reach them to connect via Remote Desktop - which is what I need to do...)

    Many Thanks!
     
  2. Dinesh@Parallels

    Dinesh@Parallels Guest

    Messages:
    300
    Hello @GarethP1
    Set the virtual machine networks settings to Bridged network and change DNS to settings to manual. Enter the preferred DNS IP address same as your host and check if you're able to ping. Please update us with the results. If the issue persists, please share the screenshot of the IP configuration on the host and as well as on the Hyper guest OS.
     
  3. GarethP1

    GarethP1 Bit poster

    Messages:
    8
    Hi Dinesh - thanks for getting back to me.
    I changed the DNS to manual in the HyperV guest and set the preferred DNS to match the (working) HyperV host - 10.0.1.1
    Afraid it didn't work.
    Here's the screen shot of the HyperV guest's ipconfig /all output
    upload_2016-9-13_22-12-32.png upload_2016-9-13_22-12-32.png

    And here's the same for the HyperV host
    upload_2016-9-13_22-8-45.png upload_2016-9-13_22-8-45.png
     

    Attached Files:

  4. GarethP1

    GarethP1 Bit poster

    Messages:
    8
    Sorry the host ip config didn't paste correctly.
    Here it is
    upload_2016-9-15_9-3-40.png upload_2016-9-15_9-3-40.png
     
  5. Dinesh@Parallels

    Dinesh@Parallels Guest

    Messages:
    300
    Hello @GarethP1
    Are you able to ping any website inside the Hyper-V virtual machine? Did you created virtual switch as "external" ?
     
  6. GarethP1

    GarethP1 Bit poster

    Messages:
    8
    Yes the virtual switch is external. (I can ping the virtual switch from another physical machine)
    Afraid that I cannot ping any website from inside the Hyper-V virtual machine. (The only thing I can ping from the Hyper-V VM is the Hyper-V Host.)
     
  7. Dinesh@Parallels

    Dinesh@Parallels Guest

    Messages:
    300
    Hello @GarethP1
    Please check your private message and reply us!
     
  8. Elric

    Elric Parallels Team

    Messages:
    1,712
    Hi,
    Generally speaking, if VM without HyperV works sucessfully in bridge mode, then Hyper-V VMs should also work in bridge to wired ethernet.

    But HyperV-VMs will not ever work on bridge to WiFi. It is internal limitation of current version of Parallels Desktop, since things become too complicated while WiFi: it requires rather complex substitution of MAC-addresses..
     
  9. Elric

    Elric Parallels Team

    Messages:
    1,712
    May be setup of PortForwarding in Shared Neworking will help?
     
    CarlW6 likes this.
  10. GarethP1

    GarethP1 Bit poster

    Messages:
    8
    Thanks Elric. You've solved my problem!
    Just as you said - by using wired not wireless connection.
    I can now see the HyperV inner VM from across my network.
     

Share This Page