I have a refurbed PowerEdge 2900 that has four network connections. Two connections are megabit (on one NIC) and two are gigabit (on another NIC). Thefollowing is what shows for these NICs in the device manager.

The megabit NIC is an Intel Pro 1000/MT Dual Port Netwotk Connection.
The gigabit NIC is a Broadcom BCM5708C NetXtreme GigaE (NDIS VBD Client).
Please see the image below:


I am using Hyper-V on this host with six virtual machines defined. Apparently for each of these four physical network connections, there is a corresponding virtual network connection. I have named these Gigabit Connection 1, Gigabit Connection
2, Megabit Connection 1, and Megabit Connection 2. You will notice that these also show up in the list of network adapters in the device manage above.
My question/problem is when I look at the network connections from the Control Panel, they toggle between, "Enabled" and "Unidentified Network" and sometimes it says "(unauthenticated) as seen in the screenshot below. What might be
causing this and what can I do to resolve it? If from this post it appears that I am confused about this whole issue of physical connections and virtual connections, please set me straight. Thanks for any help.

Doug Pruiett Good News Jail & Prison Ministry Richmond, Virginia
www.goodnewsjail.org


Need to support users over the internet? click here try our remote control online beta

MORE INFORMATION:
I noticed when I looked at the network connections in "details" view, some of them said "Domain network" and others said "Public network." How can I set them all to "Domain network"?



When I go into the Network Sharing Center, this is what I see. The list under "Unidentified network" expands and contracts. What can I do to make sure ALL connections show up under the "Domain network"? Thanmk for any help.

Doug Pruiett Good News Jail & Prison Ministry Richmond, Virginia
www.goodnewsjail.org


Need to support users over the internet? click here try our remote control online beta

THE SOLUTION:
I believe that my problems stemmed from me defining my virtual network connections (in Hyper-V Manager>Virtual Network Manager) before the NICs were actually physically connected to the network, and compounding it by assigning
these virtual connections to my virtual machines before physical connections were made.
I was able to clear the problem by going into Hyper-V Manager>Virtual Network Manager, deleting all the virtual network connections (which set all my virtual machines to "No connection" under the Network Adapter setting).
I then ensured that all NICs were physically connected to my network (which they already were). I then went back into Hyper-V Manager>Virtual Network Manager, adding back the four virtual network adapters associated with my four actual physical connections.
The network connections (under Control Panel\Network and Internet\Network Connections) now look as follows, which is what I expect. Looks like problem solved.
Doug Pruiett Good News Jail & Prison Ministry Richmond, Virginia
www.goodnewsjail.org


Need to support users over the internet? click here try our remote control online beta