<div>
Hi LongFist, let's start it over.<br />
In hyperv, you can dedicate or share a nic to be connected to a virtual switch<br />
<br />
Let's choose the dedicated methode. First make sure there is no NIC teaming or trunk configured on the switch.<br />
<br />
Let's say Nic1 is for physical host and management purpose<br />
Nic2 should be used to create a Virtual External Network called 'Virtual Switch' for example. You want to <b>uncheck </b>'Interact with os' checkbox when creating this switch. No vlan configuration so far.<br />
Then, once applied, you browse you vm network settings and under Network configuration, you choose Virtual Switch in the dropdown list. Vlan should not be set as well.<br />
<br />
On the host side, in NIC2 property, IPv4 and other protocol should be automatically unchecked.<br />
<br />
The VM starts, and if VMBus drivers are correctly installed on the guest, you should have a plugged and activated network connection. <br />
<br />
Once you're there we can go on trying to fix your problem.
</div>


<div>
Okay. &nbsp;Starting from scratch. &nbsp;I like this. &nbsp;This way I can figure out what I'm missing - and I'm pretty sure it's something <i>I'm</i> missing.<br />
<br />
Host machine has 2 NICs.<br />
<br />
<b><u>Network Connections:</u></b><br />

<div class="indent">
<b>NIC1:</b> Client for Networks, File and Printer Sharing, IPV6, IPV4, Link-Layer Topo Discovery Mapper, and Link-Layer Topo Discovery Responder have been checked/selected.<br />
<b>NIC2:</b> Microsoft Virtual Network Switch Protocol has been checked/selected.
</div>
<br />
<br />
<b><u>Virtual Networks:</u></b><br />
Created a single network [VirConn], selecting [External] and binding it to NIC2. &nbsp;Nothing else selected, no VLANs enabled/in use.<br />
<br />
You mentioned &quot;Interact with os&quot; - this is an option have not yet encountered. &nbsp;Is there another place where this gets set up?<br />
<br />
Thanks!
</div>


<div>
Or have I mis-configured things yet again? &nbsp;So far, I've only looked at Network Connections, HyperV Manager, and HyperV Virtual Network Manager on the Host machine, and File--&gt;Settings--&gt;Network Adapter on the Virtual Machine. &nbsp;Is there another utility/application/interf<wbr />ace that I should pay attention to?<br />
<br />
Or am I as hopelessly lost as I think I am?<br />
<br />
Thanks again!
</div>


<div>
Interact with os, I meant &quot;allow management operating system to share this network adapter&quot; (see image)<br />
&nbsp;<a href="https://filedb.experts-exchange.com/incoming/2011/10_w42/510871/Screen-shot-2011-02-01-at-13.15..png" target="_blank" class="file-inline" title="share network (32 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Screen-shot-2011-02-01-at-13.15..png</a><br />
<br />
you should not check/uncheck protocols and services bound to the interface, Hyperv will do it for you automatically.<br />
<br />
Are we working on 2008 or 2008r2 version of Hyperv ?<br />
<br />
There is no other utility, its :<br />
1- create a switch<br />
2- set vm settings to be connected on this switch<br />
3- configure host with good parameters.<br />
<br />
<br />
You might have an issue with vmbus drivers and your hardware. Now we will add a Legacy emulated NIC in your VM<br />
Shut the VM down, click ADD Driver and select 3rd choice : legacy adapter if my memory is correct.<br />
Connect this adapter to VirConn switch.<br />
<br />
Windows Hosted VM will show 2 nics, disable the 1st one and configure the second one. Try to use it and give us feedback if it works better.<br />
<br />

</div>


Screen-shot-2011-02-01-at-13.15..png

<div>
I'm going to assume that I've got 2008 [Hyper-V Manager Ver, 6.0.6002.18005] based on the fact that I don't have the &quot;Allow management operating system to share this network adapter&quot; checkbox on my HyperV Virtual Network Manager.<br />
<br />
<br />
Okay, I shut down the VM. &nbsp;In the Network Manager, I added the Legacy Network Adapter, connected it to my [VirConn] connection, then Removed the prior Network Adapter. &nbsp;Restarted the VM.<br />
<br />
Everything seems to start up all right. &nbsp;Log into the VM. &nbsp;At the bottom right (SysTray) the Network icon pops up, gives me the &quot;Status: Acquiring network address&quot; mouseover message (and animation), then just continues to &quot;acquire network address&quot; in perpetuity.<br />
<br />
So, it would seem that creating a Legacy Network Adapter wasn't the answer.<br />
<br />
<br />
I realize that this should be pretty straightforward. &nbsp;I'm not sure what to think, because I was only informed of this issue after it occurred. &nbsp;Of note: this only started after a disaster recovery operation - this machine was recovered from backup. &nbsp;Would that cause some issues? &nbsp;Does Hyper-V networking &quot;break&quot; when restored from a backup? &nbsp;I mean, it sounds possible, but not very probable. &nbsp;It's been ten minutes now, and that machine is still fishing for an IP address. &nbsp;Dunno what to think about this.<br />
<br />
The host machine can see the 'net just fine - it recognizes all of the (other) connected machines, and can even access the internet.
</div>


<div>
Afaik, Hyperv doesnt break anything after a restore. There can still be hidden old devices in the registry, and some might already have an IP configuration<br />
To see these devices and clean the system check here :<br />
<a href="http://support.microsoft.com/kb/315539/en-us" rel="ugc">http://support.microsoft.c<wbr />om/kb/3155<wbr />39/en-us</a><br />
<br />
There are 2 *obvious* possibilities:<br />
<br />
Your physical network isnt registering any mac address to the switch, so your mainboard / nic has a problem.<br />
Your 2008 is an old one and is refusing to acquire an ip from a public network, or there is a firewall policy that blocks dhcp request... anyway turn it down this way:<br />
netsh firewall set opmode disable<br />
netsh firewall set opmode mode=disable profile=all<br />
<br />
At last, if you wanna deep farther, you can install wireshark on the Hosted VM and analyze the incoming and outgoing packets. there might be a clue hidden there<br />
<br />

</div>


<div>
Okay, the problem with the first obvious possibility is that if the NIC had a problem, it wouldn't connect to the network for the host machine. &nbsp;Since we see that it does, that's right out. &nbsp;The firewall has never been set up - this particular server doesn't use it <i>because</i> it gets in the way: if we really feel the need, we'll install ZoneAlarm to protect the server, but later.<br />
<br />
I have also opted to change the Virtual Switch definition from the second NIC to the first, just to see if it was a hardware issue. &nbsp;Since each NIC behaved in the same manner as the other - and both serve the host machine perfectly - I can only assume that the hardware is functional. &nbsp;And I have even performed the Legacy NIC test, with no success. &nbsp;Bound to either NIC. &nbsp;So, I'm going to check for hidden old devices in registry, that sort of thing, in accordance with &lt;<a href="http://support.microsoft.com/kb/315539/en-us" rel="ugc">http://support.microsoft.com/kb/315539/en-us</a>&gt;&nbsp;to see if there might be some cruft hiding out in the registry.<br />
<br />
The scary thing about this is that the interfaces are really simple, and yet I seem to have managed to mess something up - I'm not exactly sure how or why - and now my Hyper-V system is deaf/mute.<br />
<br />
Thanks for your time and attention: I'm going to go give this a look: I'll report back (either way) with results.
</div>


<div>
All right, I'm back, and nothing appears to have changed.<br />
<br />
When I go to device manager, as per &lt;<a href="http://support.microsoft.com/kb/315539/en-us" rel="ugc">http://support.microsoft.com/kb/315539/en-us</a>&gt;, I see nothing that isn't already there. &nbsp;Maybe this problem lies somewhere outside the Hyper-V strata: I'm not sure what to think.<br />
<br />
I gave this machine a thorough once-over, to make sure that everything appeared functional. &nbsp;And it does, it does. &nbsp;But - for reasons beyond my explanation, I note that (in the &quot;Network and Sharing Center&quot;, the second link appears broken:<br />
<br />
&nbsp; &nbsp; &nbsp;[SERVER] -----&gt; [Network] --X--&gt; [Internet]<br />
<br />
...when I click on the red X that appears in the second pathway to diagnose the possible issue, Windows tells me there is nothing wrong. &nbsp;The machine can see the network, the various and sundry other machines connected to the network, and even the Internet itself, although browsing from a server is totally against Microsoft's best practices. &nbsp;Windows Firewall is not running, so that's not an issue in this case.<br />
<br />
But that's about as far as I can see with this aberrant behavior: The apparent &quot;X&quot; in the link between [Network] and [Internet], and the fact that my VMs cannot see/hear/taste the network at all! &nbsp;Is there a link between the problems? &nbsp;I have no idea. &nbsp;The host machine interfaces to the network without a flaw, so I'm really puzzled, here.<br />
<br />
Sharing and Discovery:<br />
&nbsp; &nbsp; &nbsp;Network Discovery &nbsp; &nbsp; &nbsp; [GREEN LIGHT] Custom<br />
&nbsp; &nbsp; &nbsp;File Sharing &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [GREEN LIGHT] On<br />
&nbsp; &nbsp; &nbsp;Public Folder Sharing &nbsp; &nbsp;[GREY LIGHT] &nbsp;Off<br />
&nbsp; &nbsp; &nbsp;Printer Sharing &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[GREY LIGHT] Off (No printers installed)<br />
<br />
----- I always thought Network Discovery was either &quot;On&quot; or &quot;Off&quot;. &nbsp;What is this &quot;Custom&quot;, and why is there no radio button for such when the drop-down is activated? &nbsp;Come to think of it, I've never seen this type of behavior before. &nbsp;In the drop-down, it tells me that &quot;when network discovery is on, this computer can see other network computers and devices and is visible to other network computers&quot;, and the radio button to &quot;Turn on network discovery&quot; is un-greyed and available, while the radio button to &quot;Turn off network discovery&quot; is greyed out, with an attention triangle explaining that &quot;To turn off network discovery, you must first enable the Windows Firewall Service&quot;.<br />
<br />
<br />
Could this be the culprit? &nbsp;Or am I spinning my wheels here? &nbsp;It just seems that - by Occam's Razor - while my problem may manifest at the Hyper-V/VM/Network Connectivity layer, that the problem may actually exist/persist in a layer &quot;outside&quot; where the actual problem 'becomes' visible.<br />
<br />
What do you think?
</div>


<div>
Endgame: Updated the hardware drivers to the latest version, and re-defined virtual network settings (because when we removed and replaced the drivers our existing virtual bindings were removed). &nbsp;The DHCP still failed, but assigning the VM an IP address allowed it to connect properly - so we're not sure if DHCP wouldn't have worked had we given it the DHCP server IP. &nbsp;But for sure it wasn't performing DHCP IP acquisition correctly.<br />
<br />
Technically this was like peeling an onion from the inside. &nbsp;We started with the VM, reached out to the Virtual Network, then ended up looking at the actual (hardware) NIC for possible solutions. &nbsp;Now all is resolved, even though it introduces a little more network maintenance down the road (that's why we're trying to keep it all running DHCP).<br />
<br />
Well, the CRM server is back up and running, and now we know a lot more than we did before. &nbsp;Thanks for your help!
</div>


<div>
Before troubleshooting Hyperv Network issues, Upgrade Drivers, NIC firmwares and network teaming utility. &nbsp;It'll save a lot of time and headaches.
</div>


<div>
<div class="content wysiwyg-content">
Hi Experts! &nbsp;I have a Hyper-V machine with one VM that - regardless of what I try - cannot seem to see the physical network. &nbsp;I have installed (and re-installed) Hyper-V Tools, to no avail. &nbsp;I have created a second Network entity, bound to the first (instead of the second) NIC, also to no avail. &nbsp;I think I've covered most of the obvious bases, yet the machine still fails to &quot;reach out&quot; to the physical network: DHCP doesn't work, and I have only a few clues as to what <i>might</i> be happening. &nbsp;It seems to show a Local Connection 8, DCHP-Enabled, Autoconfig Enabled, no IP or Subnet Mask, and then a &quot;stub&quot; for the VPN tunnel, which we're not using yet (anyway). &nbsp;I think it has somehow - mo matter how I configure the Hyper V Network Settings - set upon the unused IP tunnel (or some other fictitious interface) as its Net Source, instead of NIC2 (Local Area Connection 5) to which it should be connecting.<br />
<br />
Both NICs are connected to the switch, so we're not bound to an inactive NIC. &nbsp;<br />
<br />
I'm confused, and getting a little frustrated. &nbsp;Is there some way to simplify this mess and make it work?<br />
<br />
Thanks in Advance,<br />
<br />
- LongFist
</div>
</div>


Hi Experts!  I have a Hyper-V machine with one VM that - regardless of what I try - cannot seem to see the physical network.  I have installed (and re-installed) Hyper-V Tools, to no avail.  I have created a second Network entity, bound to the first (instead of the second) NIC, also to no avail.  I think I've covered most of the obvious bases, yet the machine still fails to "reach out" to the physical network: DHCP doesn't work, and I have only a few clues as to what might be happening.  It seems to show a Local Connection 8, DCHP-Enabled, Autoconfig Enabled, no IP or Subnet Mask, and then a "stub" for the VPN tunnel, which we're not using yet (anyway).  I think it has somehow - mo matter how I configure the Hyper V Network Settings - set upon the unused IP tunnel (or some other fictitious interface) as its Net Source, instead of NIC2 (Local Area Connection 5) to which it should be connecting.

Both NICs are connected to the switch, so we're not bound to an inactive NIC.  

I'm confused, and getting a little frustrated.  Is there some way to simplify this mess and make it work?

Thanks in Advance,

- LongFist

Hyper V Network Issue

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.

Microsoft Virtual Server

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.