Hyper-V

[mofusjtf]

I have a w2k8 64-bit server running Hyper-V. I setup a Virtual install of 32-bit w2k8. The install went well and all hardware is recongnized. However, my network card will not obtain an address and even if I manualy assign one I cannot connect to any networks.

 

[kmcferrin]

Which network card? The physical NIC in your machine or the virtual NIC on your VM?

Technically you are supposed to have a second NIC dedicate to the VMs (which you specify during setup) and then a primary NIC which is used by the physical server. I'm guessing that is your issue. If you don't have two NICs or try to use the same NIC for both, the Hyper-V install will create a second instance of the NIC on your physical machine that handles the network traffic for the VMs, but your previous instance will go away. Because of that you will have to configure the new NIC with the same network settings that the previous instance had.

Also, you'll probably run into issues with the NICs in the VMs then as well unless you use a legacy NIC driver.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCSE:Security 2003
MCTS:Active Directory
MCTS:Network Infrastructure
MCTS:Applications Infrastructure

 

[mofusjtf]

Thanks. It was actually the configuration of networks in Hyper-V settings. You can set 3 different types: external, internal & private.

External allows the VM to communicate with the other VM's and the external physical network.

Internal allows the VM's to communicate with other VM's and the physical host.

Private allows the VM's to communicate with VM's only.

I was set to private so I changed that and it works now.

 

[dennydd]

There are a lot of cool things you can do with Server 2008 Hyper-V networking