none
hyper v 2012 VM Cannot connect to external network.

    Question

  • Hi

    We have recently done a P2V conversion of an existing Window 2008 server and have it running on Hyper V on a Windows 2012 server.   However the Guest VM will only connect to the external network through the Legacy Adapter.  I have added the Integrated Services disk to update the VM - but when we add a Network Adapter the device Manager on the guest show an HP n373i Gigabit adapter (virtual) all working but there is no communication to the network.

    The legacy driver is an Intel 21140 working at 100MB but is to slow for the network - any help gratefully received.

    Thanks in Advance

    KEvin


    Kevin Sait

    Wednesday, May 15, 2013 1:09 PM

Answers

  • For both host and guest, it appears like you are attempting to have both NICs assigned to the same IP subnet.  That is generally not a good idea with Windows.  If you are trying to build in redundancy, use NIC teaming instead.  This could also be why only the one NIC is working.  Windows will tend to recognize only one of the NICs if multiple are defined on the same subnet.  Which one gets selected is non-deterministic for everything that I have seen.

    Regarding your statement "The legacy driver is an Intel 21140 working at 100MB ".  True, the emulated NIC is the Intel/DEC 21140, but the 100Mbps you see is simply a number that is reported.  Hyper-V does not go out to the network and perform any sort of speed test.  The legacy NIC will operate at the speed of the physical port.  Even if the legacy NIC is assigned to a virtual switch defined on a 10 Gbps NIC, it will still report 100Mbps.  The slowness comes in because the legacy NIC is emulated in software, so it is executing thousands of software instructions to accomplish what is being handled in hardware on the synthetic NICs.  That's why you see a performance difference.

    Replication of the VM... You say your VM is a DC and that you want to (eventually) replicate to another host.  A much better idea is to simply create another VM on the second host and make it another domain controller.  AD replication is tried, proven, and well understood.  Hyper-V replication is asynchronous.  It should work, but you are not gaining anything by implementing it to replicate a DC.  Because it is asynchronous, and a manual process to get up and running, you have additional management overhead.  Putting in another DC automates everything.  If one DC goes down, the other is there automatically, 100% up to date.  And there is no savings in regards to storage or network bandwidth.  So I have not seen any good reason yet to implement a Hyper-V replica of a DC instead of just installing another DC.


    .:|:.:|:. tim

    Thursday, May 16, 2013 12:39 PM

All replies

  • We need more infomation to help you. Post the results of both host and guest ipconfig /all may help.


    Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

    http://www.ChicagoTech.net

    How to Setup Windows, Network, VPN & Remote Access on

    http://www.howtonetworking.com

    Wednesday, May 15, 2013 2:50 PM
  • Hi Bob   these are the details from the Host running Windows Server 2012 Hyper V


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : blackwidow
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter vEthernet (live 2):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-1B-78-30-31-18
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f8bd:79d7:35e7:1588%21(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.104(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.246
       DHCPv6 IAID . . . . . . . . . . . : 352328568
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-DF-4A-1C-00-1B-78-30-31-18
       DNS Servers . . . . . . . . . . . : 192.168.1.104
                                           192.168.1.246
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter vEthernet (live):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
       Physical Address. . . . . . . . . : 00-18-71-4D-5B-FF
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::8588:55a:7a5e:5256%26(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.82.86(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 192.168.1.246
       DHCPv6 IAID . . . . . . . . . . . : 436213873
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-DF-4A-1C-00-1B-78-30-31-18
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{E3ADE40B-EE6B-495A-A8CD-BC79E440D1CB}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{0B3E0D37-8A54-4407-8F6B-55B58FE31503}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:c01:3199:5601:ada9(Preferred)
       Link-local IPv6 Address . . . . . : fe80::c01:3199:5601:ada9%18(Preferred)
       Default Gateway . . . . . . . . . : ::
       DHCPv6 IAID . . . . . . . . . . . : 553648128
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-DF-4A-1C-00-1B-78-30-31-18
       NetBIOS over Tcpip. . . . . . . . : Disabled

    and these from the guest OS which is Windows 2008


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : ML350KMS
       Primary Dns Suffix  . . . . . . . : speeddeck-stramit.co.uk
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : speeddeck-stramit.co.uk
                                           co.uk

    Ethernet adapter Local Area Connection 4:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)
       Physical Address. . . . . . . . . : 00-15-5D-31-C3-11
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.248
       DNS Servers . . . . . . . . . . . : 192.168.1.100
       NetBIOS over Tcpip. . . . . . . . : Enabled

    PPP adapter RAS (Dial In) Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : RAS (Dial In) Interface
       Physical Address. . . . . . . . . :
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.170(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.255
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 8:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{6E06F030-7526-11D2-BAF4-00600815A4BD}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{F508D420-8CD8-4391-BD4F-5CFF5002E74F}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 12:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    as mentioned before I am getting connectivity through the legacy driver but nothing through the HP n373i network card (virtual)    - i have also found noticed the one of the VM Bus adapter has an exclamation mark on it

    It comes up with Error 29 the firmware did not give it enough resources

    I am taking it this could be my problem?


    Kevin Sait

    Wednesday, May 15, 2013 3:27 PM
  • Hi Kevin,

    We have some issues with the network settings.

    1. On the host - Ethernet adapter vEthernet (live) has this IP:
       Autoconfiguration IPv4 Address. . : 169.254.82.86(Preferred)

    Suggestion: create NIC teaming or disbale this conenction and use only one connection on th ehost.

    2. On the VM - Default Gateway . . . . . . . . . : 192.168.1.248
       DNS Servers . . . . . . . . . . . : 192.168.1.100

    The default gateway and DNS are different from the Host. Why? What is the 192.168.1.248?


    Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

    http://www.ChicagoTech.net

    How to Setup Windows, Network, VPN & Remote Access on

    http://www.howtonetworking.com

    Wednesday, May 15, 2013 10:03 PM
  • Hi Bob

    1. I will disable the NIC this afternoon.

    2.  We have two broadband routers in the factory 192.168.1.246 & 192.168.1.248 .  The idea with the virtualization is two have two (eventually ) Windows 2012 server running Hyper- V and the VM replicated between the two. The VM is the AD machine.     We didn't want the host(s) to be part of the AD domain simply to host the VM.

    Hope that makes sense.

    Thanks for your help so far

    Kevin

    Thursday, May 16, 2013 10:31 AM
  • For both host and guest, it appears like you are attempting to have both NICs assigned to the same IP subnet.  That is generally not a good idea with Windows.  If you are trying to build in redundancy, use NIC teaming instead.  This could also be why only the one NIC is working.  Windows will tend to recognize only one of the NICs if multiple are defined on the same subnet.  Which one gets selected is non-deterministic for everything that I have seen.

    Regarding your statement "The legacy driver is an Intel 21140 working at 100MB ".  True, the emulated NIC is the Intel/DEC 21140, but the 100Mbps you see is simply a number that is reported.  Hyper-V does not go out to the network and perform any sort of speed test.  The legacy NIC will operate at the speed of the physical port.  Even if the legacy NIC is assigned to a virtual switch defined on a 10 Gbps NIC, it will still report 100Mbps.  The slowness comes in because the legacy NIC is emulated in software, so it is executing thousands of software instructions to accomplish what is being handled in hardware on the synthetic NICs.  That's why you see a performance difference.

    Replication of the VM... You say your VM is a DC and that you want to (eventually) replicate to another host.  A much better idea is to simply create another VM on the second host and make it another domain controller.  AD replication is tried, proven, and well understood.  Hyper-V replication is asynchronous.  It should work, but you are not gaining anything by implementing it to replicate a DC.  Because it is asynchronous, and a manual process to get up and running, you have additional management overhead.  Putting in another DC automates everything.  If one DC goes down, the other is there automatically, 100% up to date.  And there is no savings in regards to storage or network bandwidth.  So I have not seen any good reason yet to implement a Hyper-V replica of a DC instead of just installing another DC.


    .:|:.:|:. tim

    Thursday, May 16, 2013 12:39 PM
    1. As mentioned, if you have two NICs in the same subnet, create NIC teaming.
    2. If for some reasons you want to have two gateways in your network, one for host and another one for VM, you may want to create two subnets.

    Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on

    http://www.ChicagoTech.net

    How to Setup Windows, Network, VPN & Remote Access on

    http://www.howtonetworking.com

    Thursday, May 16, 2013 4:26 PM
  • Hi,

    I would like to confirm what is the current situation? Have you resolved the problem or do you have any further progress?

    If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.


    Lawrence

    TechNet Community Support

    Tuesday, May 21, 2013 6:28 AM
    Moderator