|
I suppose you see the same behavior with windump. Right?
Do you have any sort of
- personal firewall
- VPN software
- antivirus
- tunneling protocol
installed on the failing machines?
If windump causes the same behavior, can you please file a bug
report as explained at
Have a nice day
GV
----- Original Message -----
Sent: Thursday, March 15, 2007 6:31
AM
Subject: Re: [Wireshark-users] TCP
capture problem,
Hi.
Thank you for answering.
Now I'm using the latest
versions, just downloaded them, before I had Ethereal with winpcap 3.1. There
is not any difference in their behaviour though.
There is one thing
more to mention about TCP. Sessions opened before capturing stay open, for
example SSH. Opening a new one during capturing is not possible.
br.
JN
2007/3/15, Anders Broman (AL/EAB) <anders.broman@xxxxxxxxxxxx>:
Hi,
What
version of Wireshark and WinPcap are you using?
Wiresark 0.99.5 and
WinPcap 4.0 are the latest versions.
Best
regards
Anders
________________________________
From: wireshark-users-bounces@xxxxxxxxxxxxx
on behalf of Jarkko Nevala
Sent: Thu 3/15/2007 1:23 PM
To: wireshark-users@xxxxxxxxxxxxx
Subject:
[Wireshark-users] TCP capture problem,
Hi, I'm having problems
with packet capturing. When I turn it on, no TCP-traffic gets through. Web
browser, SSH-client and all the other applications using TCP just freeze. No
such problems with UDP though, for example SIP-clients can register and make
calls without any difficulties. I guess this could be a problem of Winpcap,
but I do not have any idea how to fix it.
Does anyone else have this
kind of trouble. There is at least 7 computers at my work with Win XP SP2,
that has this problem.
Thank you in
advance.
_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users
_______________________________________________
Wireshark-users
mailing
list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users
|
