ok - as you have 3 networks cards that would be for now enough and cover
your current needs - 1xManagement, 1x Internal LAN (Switch), 1x External WAN
I would not add the management adapter to Hyper-V networks and let it
dedicated for management OS. Then you need to configure 2 "external"
networks which you name like where the physical adapter is connected
(Internal/External) and uncheck "Allow management OS to share this
adapter...". With that you configure the physical NICs dedicated for Hyper-V
and all well known protocols (TCP/IP, Client for MS Networks...) will be
removed from this adapter and an "Microsoft Virtual Network Switch" Protocol
installed. Do not change this configuration ! Then you only need to add 2
vNICs within your VMs and connect them to each network via the Hyper-V
Manager -> VM Settings -> Network.
I addition i would also recommend to you the following 2 links :
Understand Hyper-V Networking http://www.microsoft.com/downloads/d...4-62b925ed7eea
Understanding Networking in Hyper-V http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
PS : This design does rely on Windows 2008 R2 Hyper-V, where you can
dedicate an adapter to Hyper-V via the GUI -> Hyper-V Manager -> Network
If you have any further questions please let me know.
"Nime" <eminakbulut@newsgroup> wrote in message
> Hi all
> I will move servers into Hyper-V environment and I need to ask a question
> about virtual network configuration. Below are the current and projected
> network schemas:
> In Hyper-V, I've got 3 network cards. Can you advice any configuration,
> where should I begin then what would be the next steps.
> Thanks in advance.