For those of us who do demos on laptops, Hyper-V provides great performance but no wireless capability. You simply can’t bind a Hyper-V virtual machine to a wireless adapter, but you can implement a workaround in just a few minutes. There are three options. One option is to use Internet Connection Sharing (ICS, see Ben Armstrong’s blog http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/09/using-hyper-v-with-a-wireless-network-adapter.aspx). ICS imposes a restriction that seems too inconvenient to me. It requires an IP address of 192.168.0.1, which is also the default address for many NAT routers. Although it is possible to change the NAT router’s address, there are always networks you’re not allowed to reconfigure. A second option is to use Routing and Remote Access Service (RRAS, see Ken Schaefer’s blog http://www.adopenstatic.com/cs/blogs/ken/archive/2008/01/17/15530.aspx). RRAS offers the flexibility of being able to change the IP address it uses to avoid conflicts. It requires the most steps but it can still be configured in under 10 minutes. The third option, which was suggested by a reader, is to bridge network connections. It’s simple and quick to implement.
By Deepak Gupta Posted on
Share This Story, Choose Your Platform!
About the Author:
Deepak Gupta is a IT & Web Consultant. He is the founder and CEO of diTii.com & DIT Technologies, where he's engaged in providing Technology Consultancy, Design and Development of Desktop, Web and Mobile applications using various tools and softwares. Sign-up for the Email for daily updates. Google+ Profile.
@diTii Facebook Page
Recent News Topics