Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 446
  • Last Modified:

Hyper V networking problem

Hello

this past weekend i configured a server 2012 Hyper V environment; my first ever.  I am pretty green on on this and hope someone can assist.

i have my host configured and setup a VM; the VM cannot talk to the public netowork.

here is what i have setup.

public, internal and private networks configured on the host.  the VM is set to use the Public NIC.  the Physical Nic is configured with an ip of 172.x.20.x; the VM resides on the same network as the host and has an IP of 172.x.20.x

where am i going wrong? please help
0
johnkesoglou
Asked:
johnkesoglou
  • 5
  • 3
  • 2
2 Solutions
 
Svet PaperovIT ManagerCommented:
By public, you mean external, right? External virtual switch is the one you need.

Several questions that could help find the issue:
What OS the VM runs?

Did you install the integration services?

Does the external virtual NIC is shared with the host?

Can you ping the default gateway from the VM or the host?
0
 
johnkesoglouAuthor Commented:
Hi and thank you for your response.  answers to your questions

The Guest OS is running server 2012


1.  Yes - integration services are all checked on the Virtual machine.
2.  i dont know if it is shared, i have on the vswitch a public, private and internal network configured.  the VM is connected to the PUBLIC (External)
3.  I cannot ping the default gateway
0
 
johnkesoglouAuthor Commented:
this is a photo of my PUBLIC (External) Switch settingsPublic vswitch settings
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Rob WilliamsCommented:
Try unchecking "Enable virtual LAN identification" if you have not set up VLAN's
0
 
Svet PaperovIT ManagerCommented:
If you need the virtual machine to be on the same subnet as the host you need to clear the VLAN setting.
0
 
johnkesoglouAuthor Commented:
We have Vlans configured but i tried it by removing the check box for VLAN tagging on the VM and on the VSWTICH.  im sorry to say that didnt work.
0
 
johnkesoglouAuthor Commented:
Here is my networking setup.

from the physical switch (VLAN 20) to the physical NIC on my VMHOST server.  the Virtual machine is connected to the PUBLIC (External) with no VLAN tagging.  i look at the Virtual machine settings and confirm that VLAN tagging is off at the VM; the VM resides on the same  subnet of the HOST.
0
 
Rob WilliamsCommented:
If using VLAN's the VM NIC will need to be tagged, but the virtual switch on the host should not need to be to access the Internet.  I don't suppose the results of a tracert help?
0
 
Svet PaperovIT ManagerCommented:
Is this a production server or a test server? If it’s a production one I suppose it has more than one network adapters. In such case it’s considered best practice to separate Hyper-V host management traffic and the virtual machines’ traffic. To do it, you need to clear out the check box “Allow management OS to share this adapter”. Then plug and configure another physical adapter on the host with the host IP address (actually, if you want to reuse the same IP address, you have to switch the host shared adapter to DHCP before clearing out the checkbox). In such configuration, you will have one adapter that is used by the parent OS only (Hyper-V host) and one or more (may be teamed) by the virtual machines. You don’t need to configure VLAN on the host or on the virtual machines since all physical adapters are plugged to untagged ports of the physical switch.
0
 
johnkesoglouAuthor Commented:
thank you for the effort; the trial and error and your lending a hand; i found my solution.


thank you
0
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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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