how to setup virtual lan in hyper-v

[Luca]

Hello,
i've a hp ml370 g6 with 4port gigabit adapter.
I install 2008 r2 with hyper- v role.
When i create virtual lan I see a new adapter appear in my host, then i'll
connect my guest machine to it.
I have to assign an ip to the new adapter in the host or I can only assign
in the virtual guest?
If I create more virtual adapter, can i use different class of ip?
In case i must put an ip to them i have to ignore the warning rguarding the
multiple gateway?

Thanks

Luca

[Bill Grant]

"Luca" <Lu...@discussions.microsoft.com> wrote in message
news:6E8E26C4-F8A4-48D7...@microsoft.com...

If you are getting new adapters appearing in the OS running on the host
you must be creating internal virtual networks. If you want them to see the
physical network you need to create external virtual networks linked to your
physical NIC(s). If you don't need them to actually see the host OS, use
private virtual networks.

If you want to use a different IP subnet for your virtual machines, do
not create a virtual network linked to a NIC in the physical machine. Create
a private virtual network (which is a virtual switch available to vms only).

You only need an IP address for an interface in the host OS if you want
the host OS to connect to the physical network (eg so that it can receive
updates for the host OS or so that you can administer this OS remotely).

[Luca]

Thanks Bill,
I have the host e 2 virtual guest.
The host and 1 virtual guest are in the same ipsubnet. So, if i've
understood right I must connect a virtrual networks to the phisical nic cause
the two server are visible each other and my guest server is visible in the
lan and can browse the internet.

The second server , which is in another ipsubnet, only needs to see its
network lan but not the first guest and host. I've to use a private network
without connects to another phisical nic?
I think I don't understand this point.

Thanks for your precious help.

Luca

"Bill Grant" wrote:

> .
>

[Bill Grant]

There are three different types of virtual network in Hyper-V.

An external network is a virtual switch which is linked to a physical NIC
(and therefore to the physical network which that NIC uses). vms in this
network need to be in the same IP subnet as the physical machines in that
physical network. The virtual network is just an extension of the physical
LAN, like an extra switch added to an existing network.

An internal virtual network is a virtual switch which also has an
interface in the host OS (not a physical NIC). It can be used by virtual
machines and the host. If you want the host to communicate with vms in this
network, this interface in the host OS needs an IP address in the same IP
subnet as the vms in this network.

A private virtual network is a virtual switch with no connection to the
host OS or to a physical NIC. It is like a physical switch which has no
connection to any other devices. vms in this network can communicate with
each other but cannot connect to any physical network without a router. I
use a private network like this to run a test lab of virtual machines in a
domain. They are isolated from the physical network and run in their own IP
subnet. They connect to the physical network and the Internet through
another virtual machine running as a NAT router (one NIC in the private
network, one connected to the external virtual network).

"Luca" <Lu...@discussions.microsoft.com> wrote in message

news:8BD088C6-58A1-4FFC...@microsoft.com...