A Windows network bridge is the old-school, highly useful way to let a PC join two network segments at Layer 2—the same basic neighborhood, not two neighborhoods connected by a toll road. In practical terms, it can pass an Ethernet connection through a Windows 10 or Windows 11 PC to another wired device that needs access to the same router, DHCP server, and local network.

This is not the same thing as Internet Connection Sharing (ICS). A bridge passes network traffic through as though the downstream device were directly connected to the upstream LAN. ICS, by contrast, uses the PC as a small NAT router and creates a separate private network. Choose the bridge when the attached device must receive an address from the existing router and remain discoverable on that LAN.

Microsoft’s current Windows networking documentation still supports Network Bridge on Windows 10 and Windows 11, describing it as a Layer 2 MAC bridge between network segments. Microsoft also cautions that not every adapter can participate—a detail worth remembering before blaming the nearest innocent Ethernet cable.

A desktop computer, router, and network storage device are connected by Ethernet cables, with glowing graphics linking devices. Before you create a bridge​

The most dependable arrangement is:

  • Adapter 1: Ethernet connection to the router, switch, or wall jack with network access.
  • Adapter 2: A second Ethernet port connected directly to the device that needs access.
  • Downstream device: Set to obtain its IP address and DNS server automatically, unless your network administrator has assigned it a static configuration.

You need an account with administrative rights. The PC must remain powered on and connected for the downstream device to stay online; this is a bridge, not a magical cable replacement.

Before changing anything, note any static IP addresses, DNS entries, or specialized adapter settings already in use. A bridge changes where Windows keeps the active IP configuration.

Do not bridge these unless you have a very specific, tested reason​

Avoid including:

  • VPN adapters
  • Hyper-V, VMware, VirtualBox, or other virtual adapters
  • Cellular adapters
  • Bluetooth network adapters
  • Corporate-managed adapters subject to network policy
  • An adapter already used by Internet Connection Sharing

A bridge merges networks. If one of those networks is a corporate VPN or a virtual-switch environment, “merge” can become “Monday-morning incident report” surprisingly quickly.

Create the Network Bridge in Control Panel​

Windows Settings is convenient for everyday networking, but the classic Network Connections window remains the practical place for bridge management.

  1. Press Windows + R.
  2. Type:
    ncpa.cpl
  3. Press Enter to open Network Connections.
  4. Identify the two adapters to join. For a typical pass-through setup, select:
    • the Ethernet adapter connected to the existing network; and
    • the second Ethernet adapter connected to the downstream device.
  5. Hold Ctrl and click both adapters.
  6. Right-click either selected adapter and select Bridge Connections.
  7. Approve the administrative prompt if Windows displays one.
  8. Wait while Windows creates a new item named Network Bridge.

The individual member adapters may temporarily disconnect and then show that they are bridged. Windows can briefly renegotiate network access while it rearranges the furniture, so expect a short interruption.

What success looks like​

After creation, Network Bridge should appear in Network Connections. That bridge—not the individual member Ethernet adapters—is now the connection Windows uses for IP networking.

To check the resulting configuration:

  1. Open Command Prompt.
  2. Run:
    ipconfig /all
  3. Look for the Network Bridge section.

On a DHCP-based home or small-office network, the bridge should show an IPv4 address, subnet mask, default gateway, and DNS servers supplied by the upstream router. The downstream wired device should receive its own address from that same network.

For example, if the router uses the 192.168.1.x network, both the Windows bridge and the attached device should normally receive addresses in that range, with the same default gateway. The router sees the downstream device as another LAN client—not as a device hiding behind Windows.

If the bridge must use a static IP address, configure it on Network Bridge:

  1. Right-click Network Bridge.
  2. Select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4).
  4. Select Properties.
  5. Enter the approved static IP, subnet mask, gateway, and DNS values.

Do not assign competing IP settings to the individual bridged adapters. Once they are bridge members, their separate TCP/IP settings are no longer the place to manage the connection.

Test the wired device​

On the downstream device, confirm that it has:

  • An IP address from the expected subnet
  • The correct default gateway
  • DNS servers appropriate for the network
  • Access to the router and required LAN resources

A quick test sequence is:

  1. Ping the default gateway.
  2. Ping another known device on the LAN, if permitted.
  3. Test name resolution by opening a known website or resolving a hostname.
  4. Test the specific service you actually need—file share, printer, console management page, update server, and so on.

Internet access alone is not proof that the bridge is doing the right job. If the goal is LAN discovery or access to a local management interface, test that too.

Wi-Fi bridging: possible, but not a promise​

Bridging an Ethernet adapter to Wi-Fi sounds like the perfect “laptop as a tiny wired access point” trick. Sometimes it works. Sometimes it produces a connection that is technically alive but practically as useful as a screen door on a submarine.

The limitation is not merely Windows. Wireless adapters, drivers, and access points may not support the forwarding behavior required to carry traffic for another device’s MAC address over a normal Wi-Fi client connection. Microsoft explicitly notes that not all adapters can be bridged.

If the Bridge Connections option is missing, fails, or produces unreliable connectivity:

  • Update the Wi-Fi and Ethernet drivers from the PC or adapter manufacturer.
  • Test with two wired Ethernet adapters first.
  • Check whether corporate management policy blocks bridge creation.
  • Use Mobile hotspot or Internet Connection Sharing if the real requirement is only downstream internet access rather than membership in the same LAN.

For dependable bridge behavior, Ethernet-to-Ethernet remains the grown-up choice.

Why VPN adapters should stay out of the bridge​

Do not bridge a work or privacy VPN adapter to Ethernet. VPNs are point-to-point tunnels with routing, traffic-filtering, and security-policy behavior that may be incompatible with Layer 2 forwarding. A managed VPN can also enforce forced tunneling or lockdown rules that intentionally restrict where traffic may travel.

On corporate PCs, an administrator can prohibit users from installing or configuring Network Bridge through Windows policy. That restriction is not a bug to outwit; it is generally there to prevent an unmanaged device from becoming a back door between protected and unprotected networks.

If a device needs access through a VPN, use the organization’s approved routing, remote-access, or network-sharing design. A Windows bridge is not a substitute for an IT-approved gateway.

Remove the bridge and restore the adapters​

When the temporary setup is no longer needed:

  1. Open Network Connections with ncpa.cpl.
  2. Right-click Network Bridge.
  3. Select Delete.
  4. Confirm the prompt.

Windows removes the bridge and returns the member adapters to separate connections. Recheck their original IP settings afterward—particularly if they were previously configured with static addresses or a special DNS setup.

Common problems and fixes​

The Bridge Connections option is unavailable​

Confirm that exactly two eligible adapters are selected. Disconnect or disable VPN, virtual-machine, and cellular adapters while troubleshooting. If the adapters are managed by an organization, Group Policy may block bridge configuration.

The downstream device has no IP address​

Check the physical Ethernet link first. Then verify that the upstream router’s DHCP service is active and that the downstream device is configured for automatic addressing. Review ipconfig /all on Windows to make sure the Network Bridge has a valid address and gateway.

Windows has internet access, but the attached device does not​

Make sure the downstream device is connected to the second member adapter—not accidentally back into the same switch or router path. Confirm that the bridge, rather than a member adapter, holds the active IP configuration. Also check for a network loop; connecting both sides of the bridge into the same LAN through another path can make a small network very unhappy, very fast.

The bridge works until a VPN connects​

That is a sign to stop treating the VPN as bridge-friendly. Disconnect the VPN and test again. If the bridge only fails with the VPN enabled, keep the VPN adapter out of the bridge and use a network design approved for that VPN.

A Network Bridge remains a handy Windows tool when a wired device needs to sit on the same LAN as the PC. Use it deliberately, favor two Ethernet adapters, keep VPN and virtual adapters out of the mix, and remember the central rule: the bridge belongs on the LAN, while the IP configuration belongs on Network Bridge itself.

 

Click to expand...
You must log in or register to reply here.