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

Hyperv Error

Have Windows 2008 R2 teamed network card, setup windows 2008 R2 hyperv to external teamed network nic and created virtual nic for the hyperv, however, only thing unable to do is get internet access on the hyperv which has its own static ip address and dns pointing to main server. Have setup numerous times on other servers no probs but this one is proving a battle !
0
discoveranother
Asked:
discoveranother
  • 6
  • 4
1 Solution
 
Svet PaperovIT ManagerCommented:
Did you check the cabling? Can you ping the dafault gateway IP?
0
 
discoveranotherAuthor Commented:
No, but did wonder about the cabling actually, can't ping the gateway from the hyperv but I can from the server. The hyperv is installed on the server.
0
 
Svet PaperovIT ManagerCommented:
Could you, please be more specific: you have network access from the Hyper-V host (can ping the DG) but you don’t have access from a guest virtual machine?

You will have to check the Virtual NIC configuration. If you wish you could share some screen shots of the NIC config: on the host, in the virtual network manager and on the guest.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
discoveranotherAuthor Commented:
Ok, attached are screenshots
HyperV-issue-screenshots.doc
0
 
Svet PaperovIT ManagerCommented:
For me, there is something wrong with the way the network cards are teamed. But I am not familiar with the HP Teaming software, so I would explain how it is done in general (for example with Broadcom driver on a Dell server) and how the team should appear in the Hyper-V Manager:

Let say there are 3 NICs on the server:
We will keep 1 NIC (not in a team) for the Hyper-V server (the host) only
We will team 2 NICs that will be made available in the Hyper-V manager for virtual machines (guests)

1.

We configure the NIC 1 as Local Area Connection with its IP Address v4 (of the host) and all other services, except for the Microsoft Virtual Network Switch Protocol

2.

We create a Teamed NIC from NIC 2 and 3. When the team is created all bindings of the team members, except for the advanced driver/utility (HP Network Configuration Utility) and the File and Print Sharing, become disabled

3.

We do not configure IP address on the Teamed NIC

4.

In Virtual Network Manager, we create a new Virtual Adapter from the Teamed NIC and we disable the “Allow management operating system to share… “. If we verify the binding protocols on the Teamed NIC (on the host), they all except for the advanced driver/utility (HP Network Configuration Utility) and the Microsoft Virtual Network Switch Protocol should be disabled

5.

Then that Virtual Adapter is used in one or more virtual machines (guests)
To summarize, on the host:
There should be only one NIC with IP address configured, NIC 1
Microsoft Virtual Network Switch Protocol should be configured on the Teamed NIC only

 I hope this will help you. Unfortunately, I cannot provide you with screenshot examples
0
 
discoveranotherAuthor Commented:
Hi

We normally set all servers the same and every other has worked fine. I did try the above and disabled “Allow management operating system to share… “, but now I have lost remote connectivity to the main server !
0
 
Svet PaperovIT ManagerCommented:
That means you were using the same NIC for the virtual machines and the host. There is nothing wrong if there is limited number of adapters, example a small server in a lab environment but generally it is not a good practice.  

Dell has a very good (general) networking guide that might help you (again, I am not familiar with HP servers but it provides general information, not Dell specific): http://support.dell.com/support/edocs/software/HyperV/en/nsg/nsga00.pdf
0
 
discoveranotherAuthor Commented:
Ok thanks.

Yes, the nic is teamed, an external nic within hyperv is created from the host server teamed nic. We have always set these up this week and it appears to have worked ok !
0
 
discoveranotherAuthor Commented:
No solution
0
 
discoveranotherAuthor Commented:
Unfortunately, solution doesn't appear to have worked, but thanks for the info
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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