On Fri, 2015-07-03 at 15:21 +0200, Martin Pauly wrote:
> On 03.07.2015 10:24, Martin Pauly wrote:
> > > But looking at your registry files, it definitely looks like
> > > that's
> > > what it's called. Does OpenVPN fare any better? If you run
> > > 'openvpn --show-adapters' what name does it give?
>
>
> > > But looking at your registry files, it definitely looks like
> > > that's
> > > what it's called. Does OpenVPN fare any better? If you run
> > > 'openvpn --show-adapters' what name does it give?
>
> I played around a bit:
> 1.deleted all TUN/TAP adapters with openvpn's batch file.
> 2. installed openVPN 2.3.7
> 3. Then I get:
>
> C:\Program Files\OpenVPN\bin>openvpn --show-adapters
> Available TAP-WIN32 adapters [name, GUID]:
> 'LAN-Verbindung 3' {488B1FC7-0D49-427D-BCDA-F67447C78380}
Was OpenConnect *not* working correctly at this point? Despite using
the name 'LAN-Verbindung 3' as it should?
> 4. Renamed Adapter to "TAP"
> 5. Can connect fine with openconnect an vpnc-script.js,
> with the interface coming from the openconnect install this time.
>
> > > What if you take the working one and rename it *back* to 'LAN
> > > -Verbindung 3' (or 4)? Does it work then?
> 6. did that, and now it works.
OK... if it's working now and not in answer to my previous question...
what's *different*? Can you take the same registry dumps and compare?
--
dwmw2
