AnyConnect INT gets disabled by wireless supplicant

Unanswered Question
Jul 6th, 2009

Our Wireless Software disables wireless connections upon wired connect. For some reason the AnyConnect virtual adapter gets identified as a wired adapter. When the vpn connection is enabled, our wireless supplicant disables itself, which (if the user is using wireless) disconnects the session.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
jickfoo Tue, 07/07/2009 - 04:46

This is a known issue with the Juniper Odyssey client. In order to resolve the issue you just need to add the Cisco AnyConnect adapter to a OAC Blacklist.

Steps are described in the below article

http://kb.juniper.net/index?page=content&id=KB10522&actp=search&searchid=1246909105418

Here is a synopsis on what to do:

1. In Network Connections, copy the name of the adapter as it appears in its connection properties. In the event of virtual adapters, copy the name of the adapter as it appears in Odyssey.

2. Open your registry and go to...

HKEY_LOCAL_MACHINE\SOFTWARE\Funk Software, Inc.\odyssey\client\configuration\options\adapterTypes\virtual

3. Under "virtual" create a new string value. As there may be other entries you will have to name the value appropriately. As shown in the screen shot below there were 5 previous entries, so a 6th entry was created called v6. For the value data just paste in the name of the adapter you copied from Network properties.

Note: Any registry settings you put into a machine will be ported over when you create a custom MSI.

Once you have made the change and make sure the setting works for you. You can create a custom MSI on that machine and install the custom MSI on all machines that would be using the virtual adapter.

Actions

This Discussion