Hyper-V Program Manager
Some people have noticed that our support for virtual networking when using a physical wireless network adapter is a bit hit and miss.
The reason for this is because in order to perform our virtual networking - we implement an OSI layer 2 filter driver that creates network packets with the MAC address of the appropriate virtual machine. Unfortunately the wireless networking standard explicitly forbids the creation of network packets with different MAC addresses to that of the physical computer (for security reasons). To handle this - when we detect that we are using a wireless network adapter we create packets where some of the MAC addresses in the packet match that of the virtual machine - while the other MAC addresses match that of the physical computer.
Given this approach we find that some wireless networking hardware works, but other hardware doesn't. When it doesn't work it will either:
If you are seeing either of these symptoms your options are:
Try http://wlancontroller.com to turn windows 7 into hotspot
Probably this is problem with router configuration -> option Bind IP to MAC. After switch OFF this option connection working OK at VPC over Wifi card :-)
Yes, I tested. Options Bind IP to MAC + Strict bind (even without added IP-MAC pair to bind list) will disable connection on VPC over Wifi.
its nice idea for using internet but not for using wirless card options itself and using software
>>Max 20 May 2012 6:49 AM
>>Probably this is problem with router configuration -> option Bind IP to MAC. After switch OFF this option >>connection working OK at VPC over Wifi card :-)
>>Max 20 May 2012 7:33 AM
>>Yes, I tested. Options Bind IP to MAC + Strict bind (even without added IP-MAC pair to bind list) will disable >>connection on VPC over Wifi.
Thankyou very much to Max who solved my problem.
I setup Bridged Networks on VirtualBox. They did not work until i removed ALL MAC/IP bindings on my Netgear 834 router. After that, everything works like a charm.