Hyper-V problem

I am using Windows Server 2008 64-bit. I have two Hyper-V machines and when
I setup the Hyper-V network adapters within the Hyper-V mmc, after selecting
to use the physical adapters for external connectivity, I go back into the
console and notice that they keep reverting back to the Private Virtual
Machine Network option versus the External. What could be causing this as
the physical NICs are connected. I now have a ton of additional local area
network icons in my network manager that show disconnected and the physical
NICs do not show the option of using the Microsoft Virtual Network Switch
Protocol. This was working fine before I had my servers placed out in a
hosted environment.

Thanks!

On Apr 8, 6:26*pm, Joe <J...@discussions.microsoft.com> wrote:
> I am using Windows Server 2008 64-bit. *I have twoHyper-Vmachines and when
> I setup theHyper-Vnetworkadapters within theHyper-Vmmc, after selecting
> to use the physical adapters for external connectivity, I go back into the
> console and notice that they keep reverting back to the Private Virtual
> MachineNetworkoption versus the External. *What could be causing this as
> the physical NICs are connected. *I now have a ton of additional local areanetworkicons in mynetworkmanager that show disconnected and the physical
> NICs do not show the option of using the Microsoft VirtualNetworkSwitch
> Protocol. *This was working fine before I had my servers placed out in a
> hosted environment.
>
> Thanks!

I wish I could help you. I'm having similar network config problems
though. I'm running 64 bit guests as well. I have had the Hyper-V
network adapter dissapear altogether - just sort of on a spontaneous
whim. Whenever I edit the Hyper-V network adapter, it trashes my
physical adapter and sets it back to DHCP. Kind of tough when I'm
trying to work this server via RDP.

> I wish I could help you. I'm having similar network config problems
> though. I'm running 64 bit guests as well. I have had the Hyper-V
> network adapter dissapear altogether - just sort of on a spontaneous
> whim. Whenever I edit the Hyper-V network adapter, it trashes my
> physical adapter and sets it back to DHCP. Kind of tough when I'm
> trying to work this server via RDP.

That sounds like a completely different problem. Have a look at this
article.

http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx