I just installed a second guest OS (Windows Server 2008) on a Windows Server
Hyper-V parent. I used Hyper-V manager to set up the processors, disks, and
network adapter. But after installing the second guest OS it says no network
adapter is installed. Did I miss a basic step?

The parent has two network adapters, I left one unplugged for management of
the parent OS if necessary, the second physical adapter is connected to the
small test network and that physical adapter is the one I want both guest
OS's to use (for now). I set up the virtual network as an "external" network
to the appropriate physical network adapter, and the first guest OS (which is
Small Business Server 2008) can access the network and see the other physical
machine which currently connected to the network via a physical switch.

Any suggestions on how to get the network adapter to be recognized in the
second guest OS.
--
Gary S.

Hi gs-nj,

host side :
check the following link to confirm your current virtual network
configuration :
How to configure Hyper-V R2 networking ?
http://tekktips.spaces.live.com/blog...04D7!494.entry

guest side :
What OS (SP) version are u running here ?
Did you had installed the ICs (integration components) already ?
Are u using "synthetic" network adapter (normal) or an "legacy" adapter ?

Regards
Ramazan

"gs-nj" <gsnj@newsgroup> wrote in message
news:AF888128-AC3F-40EF-B88C-9DB6AC411573@newsgroup

> I just installed a second guest OS (Windows Server 2008) on a Windows
> Server
> Hyper-V parent. I used Hyper-V manager to set up the processors, disks,
> and
> network adapter. But after installing the second guest OS it says no
> network
> adapter is installed. Did I miss a basic step?
>
> The parent has two network adapters, I left one unplugged for management
> of
> the parent OS if necessary, the second physical adapter is connected to
> the
> small test network and that physical adapter is the one I want both guest
> OS's to use (for now). I set up the virtual network as an "external"
> network
> to the appropriate physical network adapter, and the first guest OS (which
> is
> Small Business Server 2008) can access the network and see the other
> physical
> machine which currently connected to the network via a physical switch.
>
> Any suggestions on how to get the network adapter to be recognized in the
> second guest OS.
> --
> Gary S.

I have it partially figured out. Host side is Windows Server 2008 with
Hyper-V. Guest is Windows Server 2008 x64. Originally after installing the
second guest OS I did not add the Integration Services (Hyper-V said it was
running on the guest OS), but after I added the Integration Services for the
2nd guest, I could connect to the network adapter (using synthetic adapter).

I still have a bungled up network, cannot ping from second guest to first
guest (which is Small Business Server 2008) or from either first guest or
second guest to the physically separate ISA server which works as my
firewall. The setup was working yesteday before I added the second guest OS.

I'm baffled for now, any suggestions would be appreciated.
--
Gary S.


"RCan" wrote:

> Hi gs-nj,
>
> host side :
> check the following link to confirm your current virtual network
> configuration :
> How to configure Hyper-V R2 networking ?
> http://tekktips.spaces.live.com/blog...04D7!494.entry
>
> guest side :
> What OS (SP) version are u running here ?
> Did you had installed the ICs (integration components) already ?
> Are u using "synthetic" network adapter (normal) or an "legacy" adapter ?
>
> Regards
> Ramazan
>
> "gs-nj" <gsnj@newsgroup> wrote in message
> news:AF888128-AC3F-40EF-B88C-9DB6AC411573@newsgroup

> > I just installed a second guest OS (Windows Server 2008) on a Windows
> > Server
> > Hyper-V parent. I used Hyper-V manager to set up the processors, disks,
> > and
> > network adapter. But after installing the second guest OS it says no
> > network
> > adapter is installed. Did I miss a basic step?
> >
> > The parent has two network adapters, I left one unplugged for management
> > of
> > the parent OS if necessary, the second physical adapter is connected to
> > the
> > small test network and that physical adapter is the one I want both guest
> > OS's to use (for now). I set up the virtual network as an "external"
> > network
> > to the appropriate physical network adapter, and the first guest OS (which
> > is
> > Small Business Server 2008) can access the network and see the other
> > physical
> > machine which currently connected to the network via a physical switch.
> >
> > Any suggestions on how to get the network adapter to be recognized in the
> > second guest OS.
> > --
> > Gary S.

>
> .
>

Hi gs-nj,

"gs-nj" <gsnj@newsgroup> wrote

> I have it partially figured out. Host side is Windows Server 2008 with
> Hyper-V. Guest is Windows Server 2008 x64. Originally after installing the
> second guest OS I did not add the Integration Services (Hyper-V said it
> was
> running on the guest OS), but after I added the Integration Services for
> the
> 2nd guest, I could connect to the network adapter (using synthetic
> adapter).

perfect

> I still have a bungled up network, cannot ping from second guest to first
> guest (which is Small Business Server 2008) or from either first guest or
> second guest to the physically separate ISA server which works as my
> firewall. The setup was working yesteday before I added the second guest
> OS.

The setup had worked before and after adding an guest to Hyper-V the VMs
network communication is gone ?
If this is correct, there is definitely something missconfigured during the
installation of the new VM. Check your external network settings again.

for crosscheck (assume your virtual switch is working here) :
when both VMs are connected to the same virtual network switch ....
+ have set correct IP address
+ if synthetic adapter are in use - no issues detected in device manager
(ICs are installed)
+ firewalls from OS of VMs are not blocking "ping" (turn off for testing)

you MUST be able to communicate with each other and or external
clients/servers :-)

> I'm baffled for now, any suggestions would be appreciated.

PS : ISA server, you could check the firewall rules if the "ping" protocol
is allowed (destination -> local host) which is disabled per default .

Let me know when you face any further issues.

Regards
Ramazan

Well, I solved it, but only by experimentation. Probably my ignorance, but my
overall impression is that guidance on the use of guest OS's and networking
in a virtual environment could be improved. Here's what I had to do to get my
two guest OS's to connect to each other:

In the parent partition (the Windows Server2008 Hyper-V server), the two
network adapters, the ones which Hyper-V manager added, one for each guest OS
in my case, (these adapters are the ones with TCP/IP properties enabled), had
to be set to "obtain IP addresses automatically", and then in the guest OS I
had to set the IP addresses of the network adapters to the fixed IP addresses
I wanted.

That was it. Doesn't seem to have any problems after that. For the life of
me I could not find any guidance in either of two Hyper-V books I bought, or
on the MS technet sites, or on the SBS2008 sites (for how to set up SBS2008
in a virtual environment).

Maybe this is not the correct way to do it, but it seems to be working now.
--
Gary S.


"RCan" wrote:

> Hi gs-nj,
>
> "gs-nj" <gsnj@newsgroup> wrote

> > I have it partially figured out. Host side is Windows Server 2008 with
> > Hyper-V. Guest is Windows Server 2008 x64. Originally after installing the
> > second guest OS I did not add the Integration Services (Hyper-V said it
> > was
> > running on the guest OS), but after I added the Integration Services for
> > the
> > 2nd guest, I could connect to the network adapter (using synthetic
> > adapter).

>
> perfect
>

> > I still have a bungled up network, cannot ping from second guest to first
> > guest (which is Small Business Server 2008) or from either first guest or
> > second guest to the physically separate ISA server which works as my
> > firewall. The setup was working yesteday before I added the second guest
> > OS.

>
> The setup had worked before and after adding an guest to Hyper-V the VMs
> network communication is gone ?
> If this is correct, there is definitely something missconfigured during the
> installation of the new VM. Check your external network settings again.
>
> for crosscheck (assume your virtual switch is working here) :
> when both VMs are connected to the same virtual network switch ....
> + have set correct IP address
> + if synthetic adapter are in use - no issues detected in device manager
> (ICs are installed)
> + firewalls from OS of VMs are not blocking "ping" (turn off for testing)
>
> you MUST be able to communicate with each other and or external
> clients/servers :-)
>

> > I'm baffled for now, any suggestions would be appreciated.

>
> PS : ISA server, you could check the firewall rules if the "ping" protocol
> is allowed (destination -> local host) which is disabled per default .
>
> Let me know when you face any further issues.
>
> Regards
> Ramazan
>
> .
>

Hi gs-nj,

"gs-nj" <gsnj@newsgroup> wrote

> In the parent partition (the Windows Server2008 Hyper-V server), the two
> network adapters, the ones which Hyper-V manager added, one for each guest
> OS
> in my case, (these adapters are the ones with TCP/IP properties enabled),
> had
> to be set to "obtain IP addresses automatically", and then in the guest OS
> I
> had to set the IP addresses of the network adapters to the fixed IP
> addresses
> I wanted.

this can be implemented depending on your needs. Now you had assigned
dedicated pNICs to each VM.
assume you are using Hyper-V 2008 RTM (SP2) here and when you select your
NICs you don't need to configure any IPs (host side) before as the protocols
will be uninstalled and and a new virtual switch will be installed. TCP/IP
configuration for host need to be done after the pNICs are added to Hyper-V.

+ You can also use 1 pNIC for both VMs at the same time, 1 x management OS,
1 x VM ONLY. Hyper-V creates here (virtual) network switches where many VMs
can be attached as a physical one. See the VM and Host from networking
perspective as totally seperate "clients".

+ If you have teaming capabilities that would be also an option here.

> That was it. Doesn't seem to have any problems after that. For the life of
> me I could not find any guidance in either of two Hyper-V books I bought,
> or
> on the MS technet sites, or on the SBS2008 sites (for how to set up
> SBS2008
> in a virtual environment).

Look at the best practices for SBS 2008 in virtualized environments
published from MS:
Best Practices for Using Hyper-V with Windows Small Business Server 2008
http://technet.microsoft.com/en-us/l...99(WS.10).aspx

Hope that helps

Regards
Ramazan