Bridging: adapter does not belong to the bridge

Started by Angus Ma

Angus Ma

Bridging: adapter does not belong to the bridge   10 February 2017, 08:02

I want to enable bridging. I added a second NIC using a USB Ethernet adapter. In Connection Emulator, I selected the two LAN interfaces for bridging. However, when I click Start, it says "You have chosen an adapter that does not belong to the bridge". Do I have to define bridging in Windows too? How do I do that? Thanks.
SoftPerfect Support forum - Andrew avatar image

Re: Bridging: adapter does not belong to the bridge   10 February 2017, 12:47

It's not related to Windows bridging. The software is saying that the adapter you want to run it on is not one of these in the bridge.

For example, if you defined a bridge to be between Local Area Connection and Local Area Connection 2:

SoftPerfect support forum

Then either Local Area Connection or Local Area Connection 2 must be chosen here:

SoftPerfect support forum
Angus Ma

Re: Bridging: adapter does not belong to the bridge   16 February 2017, 05:09

Thanks. I finally got it to work. It was complicated by the fact that I had to disable Cisco AnyConnect Network Access Manager on the 2nd interface. Otherwise the NIC will not come up.

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 ********   ******    **     **  **    **  **    ** 
 **        **    **   **     **   **  **   **   **  
 **        **         **     **    ****    **  **   
 ******    **   ****  **     **     **     *****    
 **        **    **    **   **      **     **  **   
 **        **    **     ** **       **     **   **  
 ********   ******       ***        **     **    ** 

Message: