Understanding Networking with Hyper-V

re: Understanding Networking with Hyper-V

Michael Dragone — Wed, 09 Jan 2008 18:51:58 GMT

Ben, shots 2 & 3 look the same to me. Did I miss something?

re: Understanding Networking with Hyper-V

Alan — Thu, 10 Jan 2008 00:31:18 GMT

I think image 2 & 3 are the same? is this right?

re: Understanding Networking with Hyper-V

BrentP — Fri, 11 Jan 2008 17:23:41 GMT

I have an issue that I'd be delighted to see you cover in the near future or throw some help at..

I'm trying use a virtual machine as a web server. Now the only way I'v emanaged to get my VM's to connect to the internet is follow these directions (http://blogs.sqlxml.org/bryantlikes/archive/2008/01/09/setting-up-hyper-v-virtual-networking.aspx).

All well and good, but neither my router or other physical machines on my network know how to get to the 192.168.0.x stack.

How can I create a VM that is exposed and accessible to the internet (web server, remote desktop) and other machines in my physical network?

re: Understanding Networking with Hyper-V

Mike Baz — Sun, 13 Jan 2008 02:40:40 GMT

There appears to be an odd bug wrt to networking in the current beta (it will be in Connect when I have the chance)... when creating a new VM you must have something, not sure what yet (TCP/IP?) bound to the real physical NIC for the new installation wizard to offer the card as a NIC for making a new network. If you unbind everything it's not in the list... but afterwards, if you unbind and make a new network in the management console, you can do it.

Thanks Mike

BrentP — Mon, 14 Jan 2008 03:37:35 GMT

That got it, was able to create the external network fine after unbinding.

Much appreciated!

re: Understanding Networking with Hyper-V

Daniel — Tue, 15 Jan 2008 17:42:17 GMT

I have the same 192 issue; what do you mean by unbind? In the VM's network setup or in the Hyper-V setup of the VM? Or in the host's Network setup? Or somewhere else?

re: Understanding Networking with Hyper-V

BrentP — Mon, 21 Jan 2008 05:08:13 GMT

Daniel -

the unbinding is done on the host computer's physical network connection.

On the properties dialog for the network connection there's a section in the middle 'This connection uses the following items' (Client for Microsoft Networks, TCP/IP, etc).

In there you want to uncheck all the items and click OK.

If you now go back into the Hyper-V network settings on the host computer, you can create an external network bound to the network adapter WITHOUT getting the 'this adapater is already bound' error. Once it creates the new network adapter, change the settings of your virtual machine to use the new external adapter and go back into the propterties of your host computer and re-tick all the boxes as they were before.

You should then be good to go.

re: Understanding Networking with Hyper-V

Robert — Wed, 06 Feb 2008 21:21:43 GMT

Ugh. I'm sure there are good reason for this, but people experienced with VS2005 are going to be very very very very confused by this and probably assume it is an error!