Re: [Openvpn-users] Windows XP SP2: TAP-Win32 non-functional after boot

[Anssi Kolehmainen <akolehma@xxxxxxxxxxxxx>]

On Mon, 1 Nov 2004, Richard Atterer wrote:
> On Mon, Nov 01, 2004 at 03:07:15PM +0200, Anssi Kolehmainen wrote:
> > This is the old unexplained mystery of SP2.
> > With me this was caused by Kerio Personal Firewall. After I removed it
> > everything started working again. Disabling firewall wasn't enough.
>
> Thank you for this tip! I had to deinstall both Kerio PF and Sophos to make
> things work.
I'm glad that it worked.

> Unfortunately, running the machine without a firewall and antivirus
> software is not an option. :-(
Strange thing is that other firewalls work!
I tried about four different firewalls and they I've had no problems with 
them. Bad thing is that Kerio is the best firewall (in my opinion).

> How about this workaround: Let the installer install new TAP-Win32
> interfaces in the "deactivated" state. Then make OpenVPN activate the
> interface just prior to using it.
This is "same thing" as below.

> Or as a more short-term workaround: Is there a command which allows me to
> (de)activate an interface? Then I could have a small batch script
> auto-executed on boot which de- and re-activates the interface.
Only problem is that I'm not sure if there even is a "correct" possible 
way to do it. Short googling and msdn-browsing didn't produce any results.

BTW, another workaround is to deactivate TCP/IP in adapter settings and 
then reactivate it... I wonder if this could be done with windows API.

Anssi Kolehmainen

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users