Hyper-V Host and Guest cannot access Internet at the same time

I'm running Windows 8 Enterprise (RTM) and have 1 VM (Windows Server 2008 R2) running in Hyper-V. Both host and guest are connected to my wireless NIC via a Virtual Switch (external network). The Virtual Switch has the check box "Allow management operating system to share this network adapter" checked.

Both host and guest can access internet but not at the same time. The internet access jumps back and forth between host and guest. This can be visually verified by runing the command "ping www.bing.com -t" on both host and guest and only one of the ping commands will succeed at any one time while the other ping command will  time out. After a couple of seconds the access is switched and the one that timed out will succeed while the one that previously succeeded will time out.

Why can't my host and guest use the shared internet connection (pNIC) at the same time? Any ideas?

Wireless NIC is an "Intel(R) Centrino(R) Ultimate-N 6300 AGN".

August 20th, 2012 6:03pm

I am assuming that both have a unique IP and MAC address?

Since it is wireless you should not be hitting a port filtering issue.

Free Windows Admin Tool Kit Click here and download it now
August 20th, 2012 6:34pm

Yes, both are set to retrieve IP automatically and both seem have a valid IP/MAC on the network. My host uses the same IP as the Virtual Switch and my guest uses its own IP.
  • Edited by Fann Monday, August 20, 2012 3:39 PM
August 20th, 2012 6:38pm

FYI - the Virtual Switch does not get an IP.  Only the management OS does, and then any VMs that you attach.

The only thing that I can think of is that it has something to do with your wireless router / AP that is causing the issue.

It almost sounds as if it is port filtering, but I have not heard of this (yet) with wireless routers.

Free Windows Admin Tool Kit Click here and download it now
August 20th, 2012 6:56pm

Thanks for your input. 

The main problem remains but to work around it I updated the configuration to use Internet Connection Sharing instead.

I updated the virtual switch to be internal instead of external and then I enabled Internet Connection Sharing on my wireless NIC in my host and chose the virtual switch as "Home networking connection" and checked the checkbox "Allow other network users to control or disable the shared Internet Connection". The guest is still configured to automatically retrieve an IP.

  • Marked as answer by Fann Monday, August 20, 2012 4:04 PM
August 20th, 2012 7:03pm

Hi,

I have the same issue with exact the same Wireless NIC. As it seems the wireless network at my office is causing these issues because back home I don't have the issue. Both the guest and the parent can access the Internet at the same time when I'm at home. It definitely has something to do with the wireless router/ DHCP combo at my work.

Not sure how and why yet but I'll try to find out!

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2012 10:32pm

Hi Fann..

I tried to setup the virtual switch to be internal and enabled Internet Sharing. However, my guest OS still cannot connect to the internet though it can resolve Internet Address. This is the capture from my Windows 7 guest OS:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\SPH>ipconfig -all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LVVIRTUAL702
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : mshome.net
   Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
   Physical Address. . . . . . . . . : 00-15-5D-06-FB-01
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::cd70:aef:7935:c873%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.137.28(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, December 06, 2013 9:25:08 AM
   Lease Expires . . . . . . . . . . : Friday, December 13, 2013 9:25:08 AM
   Default Gateway . . . . . . . . . : 192.168.137.1
   DHCP Server . . . . . . . . . . . : 192.168.137.1
   DHCPv6 IAID . . . . . . . . . . . : 301995357
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-E6-BD-4E-00-03-FF-18-D9-D8

   DNS Servers . . . . . . . . . . . : 192.168.137.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.mshome.net:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : mshome.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   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:6abd:3077:28c:3f57:76e3(Prefe
rred)
   Link-local IPv6 Address . . . . . : fe80::3077:28c:3f57:76e3%14(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\SPH>ping 192.168.137.1

Pinging 192.168.137.1 with 32 bytes of data:
Reply from 192.168.137.1: bytes=32 time<1ms TTL=128
Reply from 192.168.137.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.137.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\SPH>nslookup
Default Server:  Hendhy.mshome.net
Address:  192.168.137.1

> www.google.com
Server:  Hendhy.mshome.net
Address:  192.168.137.1

Non-authoritative answer:
Name:    www.google.com
Addresses:  2404:6800:4003:808::1012
          173.194.117.49
          173.194.117.52
          173.194.117.48
          173.194.117.51
          173.194.117.50

> exit

C:\Users\SPH>ping www.google.com

Pinging www.google.com [173.194.117.48] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.194.117.48:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\SPH>tracert www.google.com

Tracing route to www.google.com [173.194.117.48]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *     ^C
C:\Users\SPH>

Can you help me..?

Regards,

HENDHY

December 5th, 2013 10:15pm

I remembered having some issue's when trying setting up my HyperV over WIFI. In the end I followed these instructions ; and they seem to work for me: http://blog.credera.com/technology-insights/microsoft-solutions/using-your-windows-8-wireless-connection-inside-hyper-v/

Free Windows Admin Tool Kit Click here and download it now
December 6th, 2013 2:56am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics