Two Ethernet ports can improve reliability or increase total network throughput, but plugging in two cables does not automatically create one 2 Gbps connection. You must configure NIC teaming or bonding on the computer and, for link aggregation, configure a compatible LAG (link aggregation group) on the switch or other peer. A failover team keeps networking available when one link fails. An LACP/802.3ad team can distribute separate traffic flows across both links. A single ordinary TCP connection usually remains limited to one member link’s speed.
Start by identifying your goal, operating system, exact network adapters, switch capability, and whether your workload is one flow or many. The correct design for a file server serving several clients is different from the design for one workstation trying to accelerate one download.
As an Amazon Associate I earn from qualifying purchases.
What two Ethernet ports can actually do
Keep the connection working after a link failure
An active-backup team uses one Ethernet port as the active path and keeps the other ready. If the cable, adapter, or active switch port fails, the team moves traffic to the standby member. This improves availability, not the speed of one transfer. On Linux, the active-backup bonding mode described by the kernel can work without switch configuration in the stated topology. Windows Server NIC Teaming also supports adapter and link failover, with the exact protection depending on whether the team is switch-independent or switch-dependent.
Recommended Free Tools
Increase aggregate throughput for several flows
LACP (also called 802.3ad) and other load-balancing teams can spread traffic among links. The gain appears when there are multiple clients, simultaneous transfers, virtual machines, or other independent flows. The switch and endpoint must agree on the aggregation mode, and the member ports must be configured as one LAG. Traffic distribution is controlled by the peer’s load-balancing or hashing policy, so two links do not guarantee a perfectly even split.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Make one connection faster than one port
Common 802.3ad arrangements keep a given connection on one member link, so one file copy, stream, or TCP session generally cannot consume both ports at once. Linux documents balance-rr as an exception that can stripe packets from a stream, but it requires suitable switch configuration and can reorder packets; it is not a plug-and-play recommendation. If one flow is the bottleneck, investigate a faster single Ethernet link or an application that can create parallel connections instead of assuming LAG will double that flow’s rate.
Separate networks instead of combining them
Two adapters can also serve different networks, VLANs, or routes. That design isolates traffic rather than combining bandwidth. Routing tables, VLAN membership, and application interface selection determine which traffic uses which port.
| Goal | Approach | What it provides | Important limitation |
|---|---|---|---|
| Stay online when one cable or link fails | Active-backup or another supported failover team | A standby member takes over | It does not accelerate one transfer; protection from a switch failure depends on the topology and team mode. |
| Raise total throughput for many users or flows | LACP/802.3ad or another supported load-balancing team | Independent flows can be distributed over both links | Both endpoints must support and configure the same mode, and a single flow commonly remains on one link. |
| Exceed one port’s rate for one transfer | A faster single link or application-level parallel connections | Potentially higher per-flow speed when every device and service in the path supports it | LAG alone usually does not provide this; balance-rr has packet-ordering and switch-configuration trade-offs. |
| Keep traffic types apart | Separate interfaces, routes, or VLANs | Workload isolation and deliberate path selection | This is not bandwidth aggregation; routing and application binding still matter. |
Understand the terminology
Documentation uses several overlapping names: NIC teaming, bonding, link aggregation, LAG, port channel, Ethernet teaming, and, on many systems, 802.3ad. LACP is the negotiation protocol for a dynamic LAG. A static LAG is configured manually and does not negotiate in the same way. The names describe related designs, but the available modes depend on the operating system, adapter, driver, and switch.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteAggregation is a two-ended configuration. The computer’s team and the switch’s LAG must contain the intended ports and use compatible settings. NETGEAR’s support guidance states: “Unmanaged switches do not support link aggregation.” A router, firewall, server, or second switch used as the peer must likewise document LACP or a compatible static aggregation feature; two ordinary Ethernet sockets are not enough.
Check these requirements before connecting the second cable
- Define the outcome. Decide whether you need failover, more total throughput for multiple flows, a faster single flow, or traffic separation. This determines whether you need active-backup, LACP, a faster link, or separate routing.
- Identify the exact hardware. Record the computer’s NIC models, driver versions, switch or router model, and the ports you intend to use. Teaming modes are not universal across operating systems and adapters; Intel’s teaming documentation, for example, notes that available team types vary by operating system and adapter.
- Verify peer support. The switch or other peer must support LACP for a dynamic team or the exact static LAG mode you plan to use. An unmanaged switch cannot provide a LAG.
- Match member settings. Use compatible speed and duplex on every member. Where the equipment exposes them, also align flow-control settings, MTU, VLAN membership, and other port-level options. A mismatch can leave the LAG down or cause intermittent loss.
- Plan the topology. Decide whether both links terminate on one switch, on a switch stack or chassis that presents a single aggregation system, or on separate switches. Failover across separate switches requires a team and switch design that explicitly supports it; do not assume two unrelated switches form one LAG.
- Configure first, cable second. Build the team and the switch-side LAG before attaching both links. Connecting parallel cables before either side has aggregation or loop prevention can create a Layer 2 loop, producing broadcasts, severe slowdown, or an outage.
- Check the workload. Note whether your test is one TCP stream, several simultaneous transfers, multiple clients, virtual machines, or a service such as SMB. The traffic pattern determines whether aggregate capacity can be used.
Linux: choose the bonding mode for the job
Active-backup for straightforward resilience
Linux’s bonding driver includes active-backup. One interface carries traffic while the other waits. In the topology covered by the kernel guidance, this mode does not require switch aggregation configuration, which makes it useful when the switch is unmanaged or when your priority is link failover rather than combined throughput.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
- Confirm that both adapters are supported by your distribution, driver, and kernel.
- Create one bond using the distribution’s network configuration tool and select
active-backupas the mode. - Place the host’s address, gateway, DNS settings, and any required VLAN configuration on the bond rather than independently assigning the production address to both physical members.
- Connect and test one member first, then bring up the standby member and verify that the bond reports one active interface.
- Disconnect or disable the active link and confirm that the bond changes active members while the host remains reachable. Restore the link and verify the recovery behavior your policy expects.
Exact configuration files and commands differ among distributions and network managers, so use the network-management method shipped with your Linux release. The important choices are the bond mode, which interface owns the address, and a deliberate failover test.
802.3ad/LACP for aggregate capacity
Use the Linux bonding driver’s 802.3ad mode when the peer supports LACP. The kernel guidance requires the aggregate devices to use the same speed and duplex. Configure the switch’s LAG with the same member ports and VLANs, then configure the host bond and bring the links up as members of that bond.
- On the switch, create an LACP group containing only the intended ports and apply the correct VLAN or trunk settings.
- On Linux, create an 802.3ad bond and add the two physical interfaces as slaves or bond members using your distribution’s supported tool.
- Assign the host’s IP configuration to the bond interface, not to each member.
- Check the bond and switch status for negotiated members, matching speed and duplex, and the expected VLAN.
- Generate several independent flows—such as simultaneous copies from multiple clients—to measure aggregate behavior. A single-stream test cannot demonstrate the full capacity of a load-balanced team.
In a single-switch design, the best load-balancing behavior depends on the application and topology. The kernel notes that gatewayed and local traffic can distribute differently. A switch may hash on addresses, ports, or another policy, so the two links may not carry equal traffic during a particular test.
Why balance-rr is not a default answer
Linux also documents balance-rr, which can stripe packets and potentially let one stream use both interfaces. It requires appropriate switch configuration and can reorder packets. Reordering may reduce performance or cause instability for some traffic, so treat it as a specialized design that must be validated end to end, not as the normal way to turn two ports into one faster port.
Windows: distinguish ordinary adapters from NIC Teaming
Two adapters on one subnet are not a team
Assigning two IP addresses on the same Windows subnet does not, by itself, provide reliable load balancing or failover. Microsoft explains that the ordinary multiple-adapter arrangement is not a good redundancy method and that route selection may continue to use the first adapter. You can end up with one active path, asymmetric routing, or difficult-to-diagnose connectivity rather than a combined link.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Windows Server NIC Teaming (LBFO)
Windows Server provides NIC Teaming, also called Load Balancing/Failover (LBFO), with switch-dependent and switch-independent modes. Both modes can provide adapter or link failover and bandwidth aggregation, but the switch behavior differs.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Switch-dependent teaming: the switch participates in the team, normally through a static aggregation configuration or LACP. The switch ports must be configured as one compatible group.
- Switch-independent teaming: the switch does not need to form one LAG for the team. Microsoft describes this mode as often providing failover when a switch fails, provided the physical topology and team configuration actually place members on independent switch paths.
Use the Windows Server NIC Teaming controls for the exact server build, select the intended physical adapters, choose the teaming mode and load-balancing method exposed by that build, and then put the server’s IP configuration on the team interface. Confirm that the switch side matches whenever you choose a switch-dependent or LACP design. Labels and available options can vary with the Windows Server release and adapter drivers.
Hyper-V and RDMA caveat
In the cited Hyper-V guidance, teaming disables RDMA capability. If your design depends on SMB Direct or another RDMA workload, follow Microsoft’s specific RDMA and Hyper-V guidance instead of assuming that a conventional LBFO team is suitable. A configuration that is correct for ordinary TCP traffic may not preserve RDMA features.
SMB Multichannel is a separate Windows feature
Microsoft’s Windows Server and SMB 3.0 guidance also describes SMB Multichannel, which can use multiple network connections for supported SMB traffic. Do not generalize that server feature to every Windows client, application, or file-transfer protocol. Check the Windows edition, SMB scenario, and adapter capabilities before treating it as an alternative to NIC Teaming.
Configure the switch-side LAG safely
The switch configuration is where many two-port experiments fail. Use the switch’s documentation for the exact interface names and syntax, but follow this order:
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
- Confirm that the switch is managed and supports LACP or the static aggregation mode required by the endpoint.
- Choose two compatible ports and verify that they have matching speed, duplex, MTU, flow-control behavior where applicable, and VLAN or trunk membership.
- Create the LAG or port channel before connecting the second physical cable. For LACP, set the ports to the same dynamic group. For a static LAG, configure the identical manual group on both devices.
- Configure the endpoint’s bond or team with the corresponding mode.
- Connect the cables and check that both members show as active in the switch and on the host.
- Keep unused ports out of the group. A port accidentally added to the LAG with different VLANs or speed can prevent negotiation or create a forwarding problem.
Do not connect two parallel cables between devices that have not been prepared for aggregation or loop prevention. If neither side recognizes the group, the links can form an accidental Layer 2 loop.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the result instead of assuming it worked
Verify membership and link health
- Check that the host reports one bond or team with both physical members present.
- Check the switch’s LAG or port-channel status for both intended ports, negotiated LACP state when applicable, and matching VLANs.
- Confirm that each physical member has the expected speed and duplex and that neither interface is reporting errors.
- Verify that the IP address, default route, and VLAN configuration live on the logical team or bond interface.
Test failover separately
For an active-backup or failover design, start a continuous ping or an application session, then unplug or disable the active member. The host should move to the remaining member without requiring a new address. Repeat the test in the reverse direction and record how long the transition takes. If connectivity does not return, inspect team state, switch port state, VLAN consistency, and any upstream topology assumptions.
Test aggregate throughput with multiple flows
Use several independent transfers or clients rather than one copy operation. For example, run concurrent transfers from different local hosts to the teamed server while observing per-port counters on the switch. If traffic remains near one link’s rate, check whether the test is actually one flow, whether the switch’s hash policy maps all flows to one member, and whether the destination is a single gateway or a set of local hosts. Linux documentation notes that gatewayed and local topologies can distribute traffic differently.
When the LAG is down
- Confirm that both endpoints support the selected mode. A switch that supports only static aggregation cannot negotiate LACP.
- Check that the same physical ports are selected on both sides and that no port is administratively disabled.
- Compare speed, duplex, MTU, flow control, VLAN membership, and trunk or access settings.
- Remove and recreate a mismatched group rather than adding cables repeatedly while the state is uncertain.
- Review switch logs and host team status for negotiation, driver, or link errors.
When the network slows or stops
Disconnect one of the parallel cables immediately if you suspect a loop, then restore service before troubleshooting the configuration. A loop can flood the segment and make normal traffic appear broken. Rebuild the LAG with loop prevention and the correct member ports before reconnecting both links.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Know what aggregation cannot change
It does not raise the Internet service rate
Link aggregation combines paths between the devices where it is configured. It does not change the capacity of an ISP subscription, an upstream router, or a remote service. Two local ports connected to a switch cannot make an Internet plan deliver twice its subscribed rate. Aggregate benefit is possible only where the traffic path beyond the team has enough capacity and the remote endpoints can use multiple flows.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
A faster single link may be the better answer
If one workstation, one client, or one transfer is consistently limited by a single member link, evaluate a multi-gigabit Ethernet adapter and matching switch port instead. This is conditional, not a universal purchase recommendation: the computer’s bus and NIC, switch or router, cabling, remote endpoint, service, and every intervening link must support the faster rate. Otherwise, a faster adapter merely moves the bottleneck elsewhere.
Aggregation does not guarantee a perfectly even split
Load balancing normally assigns each flow according to a hash or policy. A small number of flows can coincidentally land on one member, while many flows or many clients are more likely to use both. Measure with the same traffic pattern that matters to you; a synthetic test with one stream answers a different question from a server handling many clients.
Practical designs for common situations
One computer with two 1 Gbps ports and a managed switch
For several local clients, configure an LACP team on the computer and a matching LAG on the switch. Expect higher total capacity across concurrent flows, not a guaranteed 2 Gbps single copy. For simple cable or adapter resilience, choose active-backup instead and leave the switch unaggregated if the topology and operating system support that mode.
A file server serving many users
LACP or another supported load-balancing team can be appropriate when multiple users or services generate independent flows. Validate the switch’s hash policy and observe both member counters under realistic concurrent use. If the server uses Hyper-V with RDMA requirements, investigate the RDMA-specific design before selecting conventional Windows teaming.
A workstation downloading one large file
Ordinary LACP is unlikely to make that one connection exceed one member’s speed. Look for a faster single link or an application and service that intentionally use parallel connections, and verify that the entire path supports the chosen rate.
A device connected to an unmanaged switch
Use active-backup only if the host and physical topology support failover without switch aggregation, or replace the switch with a managed model that documents compatible LACP or static LAG support. Do not connect both cables and expect automatic balancing.
Quick Recap
Decision checklist
- If losing one cable must not interrupt service, select a supported failover team and test it physically.
- If many independent flows need more total capacity, select LACP/802.3ad or another mode supported by both endpoint and switch.
- If one flow needs more than one port’s rate, investigate a faster single link or application-level parallelism.
- If the switch is unmanaged, do not attempt LAG; use a failover mode that requires no switch configuration or upgrade the switch.
- Match port settings and VLANs, configure both ends before cabling, and verify status under the real workload.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
