<div>
Hi!<br />
Thanks a lot for your help.<br />
Best regards,<br />
Kaspar
</div>


Hi!
Thanks a lot for your help.
Best regards,
Kaspar

<div>
<div class="content wysiwyg-content">
I've got one physical NIC.<br />
I installed Hyper-V-Server and the driver for the NIC.<br />
I connected via MMC-Snapin and configured an external virtual network bound to the physical NIC.<br />
Now this NIC is bound to the Virtual Switch Protocol and I'can't access the Server anymore.<br />
<br />
As far as I understand it, there should be something as a driver for the host to create also a virtual NIC to connect to this virtual network.<br />
<br />
Is there such a thing or is there another solution?<br />
<br />
(Yes I know, that I can solve the problem with a second NIC, but I would like to know if there is a 'one-NIC-solution')<br />
<br />
<br />

</div>
</div>


I've got one physical NIC.
I installed Hyper-V-Server and the driver for the NIC.
I connected via MMC-Snapin and configured an external virtual network bound to the physical NIC.
Now this NIC is bound to the Virtual Switch Protocol and I'can't access the Server anymore.

As far as I understand it, there should be something as a driver for the host to create also a virtual NIC to connect to this virtual network.

Is there such a thing or is there another solution?

(Yes I know, that I can solve the problem with a second NIC, but I would like to know if there is a 'one-NIC-solution')




Hyper-V: Virtual extern network with only one physical NIC

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.