All TAP-Win32 adapters on this system are currently in use.
-
The .msi is for connecting to OpenVPN's commercial "Access Server", and others have said that it specifically did not work.
The "Community Software" link at the top has the one you really need - http://openvpn.net/release/openvpn-2.1.2-install.exe
That client works fine on Windows 7, you just need to make sure you run it as Admin when it is launched.
-
Well when I use that .exe instead of the .msi install, when attempting to connect I get the above error. Any idea on why that is?
-
Did you try the steps in the first Google hit on that error + windows 7?
http://www.surfbouncer.com/TAP_adapter.htm
-
Yes I found that page, but no luck. Here is what is going on:
When I look in Control Panel > Network Connections, no TAP32 devices are listed. I only see my two physical ethernet connections, a couple VMWare interfaces, and a Sonicwall VPN Interface.
When I look under Device Manager, I DO see "TAP-Win32 Adapter V9". However it has a yellow exclamation point on the icon. The device manager says that it could not verify the digital signature of the drivers, etc…
What is strange, is if I disable the TAP in Device Manager, now it shows up back under Control Panel > Network Connections (as a disabled device). If I enable it again (in either Window), it disappears from the Network Connections window.
So apparently the only way I can get the TAP device to show up for me is to disable it in Device Manager, but then its disabled and I can't use it.
Also, I have used the OpenVPN "Add/Remove TAP devices" links in the start menu. They correctly add/remove the TAP devices but again, they only show up in Device Manager, not in Network Connections.
Also, let me get this straight: If I visit http://openvpn.net, goto Client Software > Downloads, the Windows Download link is NOT the correct client to use? Can you explain to me the difference between them? Because when I installed and tried that client, I was able to use it to successfully connect to my pfSense box. And I can verify that it did in-fact create the TAP Win32 device that showed up under Network Connections.
-
If that did work, then you might be OK. But others have reported that the very same program did not work for them.
-
I'll investigate the Access Client some more, but I still want to try to get the Community version working.
So what I think is the problem is that Windows 7 Ultimate x64 only allows digitally signed drivers to be installed (by default). And because the TAP-Win32 Adapter V9 drivers are not digitally signed, they aren't going to work for Win7.
There are some work arounds though to make Windows 7 accept unsigned drivers and I'm going that route right now. I'll post results soon.
-
Okay I have solved the problem. My assumptions about driver signatures was correct.
An important note: The following installer: http://openvpn.net/release/openvpn-2.1.2-install.exe did NOT work on Windows 7 Ultimate x64. During the installation, the installer does NOT ask you if its okay to install an non-digitally signed driver from OpenVPN. Therefore the TAP-Win32 Adapter does not get installed properly. That's why it would not show up under Network Connections. No TAP adapter means that OpenVPN will not be able to connect.
The solution: I reverted back to a previous version (2.1.0): http://openvpn.net/release/openvpn-2.1.0-install.exe
Version 2.1.0 worked just fine. As expected, during the installation, it asks if you want to accept the non-digitally signed driver. Something that 2.1.2 does NOT do. I'm not sure if the OpenVPN community knows of this problem or not. I believe this is the root of the problem though.
Thanks for the help guys.
Also, for the record, as I said, that Access Server OpenVPN client was working for me at one point. I was able to successfully connect to my pfSense box with it.
-
Just wanted to state that the reversion back to the older client worked for me as well….digital signature was not allowing newer version to install TAP device properly.
thanks for the help! -
What versions of windows 7 are you using?
The install worked fine for me here with Professional. Install asked if I wanted to install the unsigned drivers and worked fine connecting. -
Generally people with signed vs unsigned trouble are running Windows 7 on amd64 (x64, 64-bit, whatever you want to call it)
-
But that's exactly what I am running
AMD Athlon
64 X2 Dual-Core Processor TK-53 1.7GHz
4.00GB RAM
Running the 64 bit version of windows 7I am just wondering what the cause might be, because I am looking at a new laptop (since this one is older and I need something that can handle VMWare workstation better).
-
Perhaps your current system shipped with driver integrity checking disabled. Google for it, there are ways to turn it off.
