Re: Can I setup two separate networks on one server 2008 for use with Hyper-V?

Hello:

I haven't done this myself, but it seems possible. Once you have the second
NIC and network set up, you should be able to go into Hyper-V Mgr and create
a new virtual network of type external and connected to the second NIC. Note
that if you only want an isolated network for your VMs, you can create an
"internal only" virtual network without the need to install a second NIC on
the host. Search Hyper-V help for "virtual network" for more info.

--
Mel K.
MCSA: M

"asilcott" <> wrote in message
news:68897f03-69b8-486f-8752-...
>I am very confused with multihoming and was hoping somebody could
> help.
>
> What I am hoping to accomplish is to have two separate networks (one
> private, and one public) on separate NIC's, on the same Windows 2008
> server. And then I would like to assign in Hyper-V which network the
> virtual machine connects to.
>
> Is this a pipe dream? Thanks

Consider if someone hacks Hyper-V from the public network chances are they
will then have access to your private network.
It may be possible but do you really want to take that chance?

hth
DDS

"Mel K." <> wrote in message
news:%...
> Hello:
>
> I haven't done this myself, but it seems possible. Once you have the
> second NIC and network set up, you should be able to go into Hyper-V Mgr
> and create a new virtual network of type external and connected to the
> second NIC. Note that if you only want an isolated network for your VMs,
> you can create an "internal only" virtual network without the need to
> install a second NIC on the host. Search Hyper-V help for "virtual
> network" for more info.
>
> --
> Mel K.
> MCSA: M
>
> "asilcott" <> wrote in message
> news:68897f03-69b8-486f-8752-...
>>I am very confused with multihoming and was hoping somebody could
>> help.
>>
>> What I am hoping to accomplish is to have two separate networks (one
>> private, and one public) on separate NIC's, on the same Windows 2008
>> server. And then I would like to assign in Hyper-V which network the
>> virtual machine connects to.
>>
>> Is this a pipe dream? Thanks
>
>

If the hacker can take control of the Hyper-V host, then it doesn't matter
what type of network the VMs are on, they're compromised since the host is
compromised. It's not clear if the poster meant "public" as in
Internet-facing or as in production corporate LAN-facing.
--
Mel K.
MCSA: M

"Danny Sanders" <> wrote in message
news:...
> Consider if someone hacks Hyper-V from the public network chances are they
> will then have access to your private network.
> It may be possible but do you really want to take that chance?
>
> hth
> DDS
>
> "Mel K." <> wrote in message
> news:%...
>> Hello:
>>
>> I haven't done this myself, but it seems possible. Once you have the
>> second NIC and network set up, you should be able to go into Hyper-V Mgr
>> and create a new virtual network of type external and connected to the
>> second NIC. Note that if you only want an isolated network for your VMs,
>> you can create an "internal only" virtual network without the need to
>> install a second NIC on the host. Search Hyper-V help for "virtual
>> network" for more info.
>>
>> --
>> Mel K.
>> MCSA: M
>>
>> "asilcott" <> wrote in message
>> news:68897f03-69b8-486f-8752-...
>>>I am very confused with multihoming and was hoping somebody could
>>> help.
>>>
>>> What I am hoping to accomplish is to have two separate networks (one
>>> private, and one public) on separate NIC's, on the same Windows 2008
>>> server. And then I would like to assign in Hyper-V which network the
>>> virtual machine connects to.
>>>
>>> Is this a pipe dream? Thanks
>>
>>
>
>

Agreed, but in this case he would get 2 networks for the price of 1.

I took "public" to mean "Internet facing".

hth
DDS

"Mel K." <> wrote in message
news:...
> If the hacker can take control of the Hyper-V host, then it doesn't matter
> what type of network the VMs are on, they're compromised since the host is
> compromised. It's not clear if the poster meant "public" as in
> Internet-facing or as in production corporate LAN-facing.
> --
> Mel K.
> MCSA: M
>
> "Danny Sanders" <> wrote in message
> news:...
>> Consider if someone hacks Hyper-V from the public network chances are
>> they will then have access to your private network.
>> It may be possible but do you really want to take that chance?
>>
>> hth
>> DDS
>>
>> "Mel K." <> wrote in message
>> news:%...
>>> Hello:
>>>
>>> I haven't done this myself, but it seems possible. Once you have the
>>> second NIC and network set up, you should be able to go into Hyper-V Mgr
>>> and create a new virtual network of type external and connected to the
>>> second NIC. Note that if you only want an isolated network for your VMs,
>>> you can create an "internal only" virtual network without the need to
>>> install a second NIC on the host. Search Hyper-V help for "virtual
>>> network" for more info.
>>>
>>> --
>>> Mel K.
>>> MCSA: M
>>>
>>> "asilcott" <> wrote in message
>>> news:68897f03-69b8-486f-8752-...
>>>>I am very confused with multihoming and was hoping somebody could
>>>> help.
>>>>
>>>> What I am hoping to accomplish is to have two separate networks (one
>>>> private, and one public) on separate NIC's, on the same Windows 2008
>>>> server. And then I would like to assign in Hyper-V which network the
>>>> virtual machine connects to.
>>>>
>>>> Is this a pipe dream? Thanks
>>>
>>>
>>
>>
>
>

"Danny Sanders" <> wrote in message
news:#...
> Agreed, but in this case he would get 2 networks for the price of 1.
>
> I took "public" to mean "Internet facing".
>
> hth
> DDS
>
So did I.

The plan is certainly possible. I have had Hyper-V set up with two
virtual networks linked to two different physical NICs connected to two
different networks. An it is fairly easy to move a vm from on network to the
other.

Having said that, I would not recommend it, unless there was a
particular reason for it. And then only if there was a firewall in place
between the Internet and the public NIC.