[Winpcap-users] WinPcap_3_1_beta4: bugreport
Gianluca Varenni
gianluca.varenni at cacetech.com
Tue Aug 2 17:59:03 GMT 2005
Hi Franz.
I think this is due to some "unclear" (maybe interaction) between your VPN software and the Windows NDIS networking stack. As explained in FAQ6 (https://www.winpcap.org/misc/faq.htm#Q-6), the standard Microsoft VPN client works ok with WinPcap, but we cannot grant that WinPcap will work (or badly interact) with third party VPN client software.
Regarding the problem of WinPcap 3.0 vs. 3.1beta4, I'm almost sure that the cause of the it is that in WinPcap 3.1beta we have added support for PPP/dialup sniffing through the Microsoft NetMon COM component, i.e. their (not so stable) capture component. I suspect that their COM component breaks your VPN software.
Have a nice day
GV
----- Original Message -----
From: fredler at ycn.com
To: winpcap-users at winpcap.org
Sent: Monday, August 01, 2005 10:38 PM
Subject: [Winpcap-users] WinPcap_3_1_beta4: bugreport
Hello,
just to inform you about a problem I had with WinPcap_3_1_beta4.
WinPcap_3_1_beta4 blocked my VPN-client from NetScreen Technolgies which is SafeNet SoftRemote 10.3.3 (build 4).
After using WinPcap_3_1_beta4 I was unable to connect to the VPN of my company.
I have downgraded to WinPcap_3_0 and now it works again.
regards
Franz Edler
------------------------------------------------------------------------------
_______________________________________________
Winpcap-users mailing list
Winpcap-users at winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20050802/6bcd1661/attachment.html
More information about the Winpcap-users
mailing list