I'm running Windows 7 Professional; it's probably an obscure bug, even though I've see this exact error on the forums. So I'm not alone. But you're right, Microsoft's code is not worth debugging. I can just just rename it to 'My-TAP' and that should do it. I'll probably play with the Java Script tonight; I'll let you know. One last thing. Is there a way to pass an option to reply 'yes' to the certificate mismatch? -----Original Message----- From: David Woodhouse Sent: Thursday, January 29, 2015 1:21 PM To: Steven Petraglia Cc: Niels Peen ; openconnect-devel at lists.infradead.org Subject: Re: W7 Cannot Set IP on Network TAP Adapter On Thu, 2015-01-29 at 12:43 -0500, Steven Petraglia wrote: > I tried to escape it, but no luck. > "Local Area Connection 2" > Local^ Area^ Connection^ 2 > Local\ Area\ Connection\ 2 I'm confused by this. Even OpenVPN works by spawning netsh to do the configuration it needs ??? the default adapter names with spaces in seem to work for *everyone* but you. Unless it's a more widespread issue, the best option is just for you to rename the device. Windows is just too painful to debug this kind of thing. -- dwmw2
