• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 465
  • Last Modified:

Hyper-V Networking

I'm not sure I have my network adapters configured properly, and would like some help!

I have two physical network adapters on my motherboard, and am running 3 virtual machines.  

Network Adapters


Marvell Yukon 10/100/1000 Adapter - Connected directly to my internet modem


Marvell Yukon 10/100/1000 Adapter - Connected directly to my network switch

Virtual Machines


pfSense 2.0(firewall/router)


Server 2008 Enterprise (application server)


Server 2012 Essentials (domain controller/file server)
I have created 3 virtual networks within the Virtual Network Manager


Internal Only (no network connection)


WAN Connection (Marvell Yukon #1)


LAN Connection (Marvell Yukon #2)
I have allowed the operating system to share the LAN, but have unchecked to allow the operating system to share the WAN.

I have configured my two Windows Server VMs to utilize the LAN virtual network adapter, and pfSense is configured to use the WAN virtual network adapter.

In the Network Connections control panel applet on my HOST, I see 4 network adapters - Local Area Connection (Marvell Yukon - Enabled), Local Area Connection 2 (Marvell Yukon - Unidentified Network), Local Area Connection 4 (Internal Only - Unidentified Network), Local Area Connection 6 (LAN Connection - <internal domain name.local>)

I have assigned LAN 4 and 6 to be DHCP (v4).  I have assigned LAN 2 to have a static IP (, and LAN 1 (the WAN) has all networking protocols unchecked except for the Microsoft Virtual Network Switch Protocol

When I ping the HOST DNS name, it comes back with  When I try to RDP to the HOST it fails.  The 184 IP is the DHCP address assigned to the LAN virtual network adapter.  I have to RDP to the IP address of LAN 2, since ping and RDP are pointing to the LAN virtual network adapter.

I feel like I don't have my networking configured properly.  While everything is connecting and working just fine, I'd like to understand if I should be configuring this differently.

I also am considering migrating to Server 2012 Standard for my VM host, but am unsure if it's needed or will provide any benefits.
  • 2
1 Solution
Gajendra RathodSr. System AdministratorCommented:
Firewall-- Switch-- Hyper V server

Both interface should be connected to switch with two different private IP address.

One interface should be configuration for the management of Hyper V .

Second interface should be used as local area network. Configure DHCP and DNS on local area network.
Set firewall local IP address as DNS forwarder in domain control .
ITworksAuthor Commented:
My firewall is a virtual machine on the server - I can't physically wire it the way you're suggesting...

your pfSense firewall should have two virtual network adapters assigned. One network adapter should be in the WAN network and one network adapter in the LAN network.
Thus the pfSense firewall should be routing between the WAN and LAN.

Why you are having a third (internal only) network? Do you want to use is as DMZ? If so you need to assign the pfSense a third virtual network adapter which is connected to the internal only network.
ITworksAuthor Commented:

The third (internal only) adapter is not an actual network adapter.  It's so I can transfer files between the virtual machines quickly.  It's just a virtual adapter.
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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now