[Winpcap-bugs] Using WinPcap with Sunbelt Kerio Personal Firewall prohibits new outbound TCP connection

[Nathan J. Yoder]

I've tried running WireShark, Ethereal (older version of WireShark), and
Windump and after running them, I can no longer establish outbound TCP
connections.  Based on a WireShark bug report linked below, it seems that
the checksums are incorrect.  ICMP pings and DNS seem to work fine.  Already
established TCP connections continue to work well.  It's only new TCP
connections that fail.  I don't know if this includes inbound TCP
connections.

For me, the problem persists even after the packet capture program has
terminated, but at least one WireShark bug report states that they have the
problem only while it's active.

This seems related to KPF (Kerio Personal Firewall), as the problem is
resolved when I exit KPF after having run the packet capture program.  When
I restart KPF, TCP connections work just fine.

Computer:

Dell Inspiron 8500
Windows XP SP2
Broadcom 440x 10/100 Integrated Controller
Sunbelt Kerio Personal Firewall 4
PeerGuardian 2.0 Beta 6b
WinPcap 4.0.2
Ethereal 0.99 (earlier version of WireShark)
WireShark 1.0
Windump 3.9.5

WireShark Bug Reports on Similar Issues:
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1855
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1302
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-bugs/attachments/20080422/6a43a859/attachment.htm