Network adapter for Hyper-V

Can anyone help me to three different options to setup the network adapter ? From the article :

•External      : creates a connection from physical adapter and the virtual machine.
•Internal       : allows communications between virtualization servers and the virtual machine.
•Private : provides communication only among the virtual machines and allows the virtual machines to talk to each other only.

So, does it mean "External" means only the Hyper-V machine could communicate with the network card, but not the VM machine ? So, should I normally setup "Private" in order for Hyper-V server to comunicate with all these VM ? What is the actual use for these 3 settings ? Any examples to illustrate further ?

Thanks
AXISHKAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
maco008Commented:
Just a thing,

Hyper-V is a hypervisor and it doesn't really need to communicate with the VM through the network.  If the word "communication on hyper-v" you're referring to heartbeat, time synchronization, and other extra stuffs Hyper-V do, then you just need to install the Hyper-V Addition - Integration Services.

External is more likely a "gateway" for your VMs to communicate on the network where the "External NIC" is connected.  The NIC can be connected to your perimeter physical network or your internal physical network. "Gateway" meaning, it's like connecting the Virtual Machine directly to the switch where the "External NIC" is connected.  It can communicate to your virtualization server - host, all guests connected to this network, and all "Physical" devices (routers, machines, servers) connected to the same network and switch where the "External" interface is connected.

Internal - It can communicate to all Guest Virtual Machines connected to the same "Internal" network and can communicate to the host virtual machine server if the host has the same subnet/network like the guests.  Best if you need to use your Hyper-V Host to communicate to the Guests machines connected to this network.  Rarely used

Private - ONLY guests virtual machines connected to this network can communicate to each other.  It's like creating a single switch and connecting guest machines directly to this isolated switch.  Best for isolating the virtual machine's network to the rest of the system.  Usually used for isolated testing environment

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.