<div>
Not sure. It may increase bandwidth, but not sure if it will decrease latency.<br />
<br />
<br />
I would test different configurations and see what works best for you.<br />
I hope this helps ! <br />

</div>


Not sure. It may increase bandwidth, but not sure if it will decrease latency.


I would test different configurations and see what works best for you.
I hope this helps !


<div>
Bandwidth won't increase as the switch will not send traffic to both NICs at the same time. &nbsp;Bridging at best will be effective for failover only.
</div>


Bandwidth won't increase as the switch will not send traffic to both NICs at the same time.  Bridging at best will be effective for failover only.

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I have a vm on hyper-v. The hyper-v host has two physical nics. I have created two external networks in hyper-v network management, external1 and external2. <br />
<br />
My vm has two virtual nics, vnic1 and vnic2. If I connect vnic1 to external1, and vnic2 to external2 and then bridge vnic1 and vnic2 within the guest OS (win2003), will this reduce latency and double the &nbsp;bandwidth?<br />
<br />
I realize the above scenario isn't the same as teaming, and in my case teaming on the hyper-v host isn't an option for various reasons. Basically I am just looking for a way to give more bandwidth to a vm and reduce latency. 
</div>
</div>


Hi,

I have a vm on hyper-v. The hyper-v host has two physical nics. I have created two external networks in hyper-v network management, external1 and external2. 

My vm has two virtual nics, vnic1 and vnic2. If I connect vnic1 to external1, and vnic2 to external2 and then bridge vnic1 and vnic2 within the guest OS (win2003), will this reduce latency and double the  bandwidth?

I realize the above scenario isn't the same as teaming, and in my case teaming on the hyper-v host isn't an option for various reasons. Basically I am just looking for a way to give more bandwidth to a vm and reduce latency. 

bridge virtual NICs to reduce latency and increase speed?

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

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.