"Adapter already in use ..."
Posted: Wed Sep 26, 2018 12:35 am
Background: win 10 home; connect to several VPN servers, but only one at a time, using viscositycc via scripts.
I'm running into the following issues related to network adapters, and here's what I've tried:
I started off using single-adapter-mode, waited for a connection's status to say "connected" before using, disconnected the connection and waited for its status to say "disconnected" before initiating another connection. This should have worked, but I consistently got "adapter already in use" dialogs.
To address that I issued a "taskkill -f openvpn.exe", wait 10 seconds before initiating a new connection, and that worked for a while, but recently I've again been seeing the "adapter already in use" message. So I added a 'netsh interface set interface "Viscosity" admin=disable' (with and without a subsequent "enable") after killing the openvpn process, but still get the "adapter in use" dialog.
So I went the adapter-per-connection route: uninstalled viscosity, reinstalled, checked "create adapter on import", and imported connections. Here's what I see:
a) even though I check create-adapter-on-import, no adapters are created when I import a folder of connections. Does this work only for per-connection-import?
b) when viscosity tries to create a new adapter at run-time, I get a dialog saying "you have an active connection. viscosity will need to close this connection bla bla to create a new adapter. do you wish to continue?" I don't see an option to say "do this always, and don't ask again". Am I missing something?
These dialogs are really hampering my being able to use viscositycc efficiently.
Please advise
Thank you
I'm running into the following issues related to network adapters, and here's what I've tried:
I started off using single-adapter-mode, waited for a connection's status to say "connected" before using, disconnected the connection and waited for its status to say "disconnected" before initiating another connection. This should have worked, but I consistently got "adapter already in use" dialogs.
To address that I issued a "taskkill -f openvpn.exe", wait 10 seconds before initiating a new connection, and that worked for a while, but recently I've again been seeing the "adapter already in use" message. So I added a 'netsh interface set interface "Viscosity" admin=disable' (with and without a subsequent "enable") after killing the openvpn process, but still get the "adapter in use" dialog.
So I went the adapter-per-connection route: uninstalled viscosity, reinstalled, checked "create adapter on import", and imported connections. Here's what I see:
a) even though I check create-adapter-on-import, no adapters are created when I import a folder of connections. Does this work only for per-connection-import?
b) when viscosity tries to create a new adapter at run-time, I get a dialog saying "you have an active connection. viscosity will need to close this connection bla bla to create a new adapter. do you wish to continue?" I don't see an option to say "do this always, and don't ask again". Am I missing something?
These dialogs are really hampering my being able to use viscositycc efficiently.
Please advise
Thank you