["M. Giertzsch" <mgiertzsch@xxxxxxxxxxx>]

Hello Howard,

maybe you should try to not capture on the client itself but using a different machine which you tapped in just before the client.
This is a little more passive and may help you out.

--- On Thu, 6/2/11, Thompson, Howard K (Howard) <howard@xxxxxxxxxx> wrote:

From: Thompson, Howard K (Howard) <howard@xxxxxxxxxx>
Subject: [Wireshark-users] WireShark side effects
To: "wireshark-users@xxxxxxxxxxxxx" <wireshark-users@xxxxxxxxxxxxx>
Date: Thursday, June 2, 2011, 5:07 PM

Hello

 

I am having a strange problem that I was wondering if anyone may have seen before.

 

In short, I am troubleshooting an offline management client.  A particular test case involves disconnecting and reconnecting the DSL line.  After reconnecting the DSL line, the client should be able to detect that it has been reconnected, and this works fine general but it is not working in a particular configuration.  It seems to be related to some combination of network and modem.

 

For further analysis. I was gathering packet captures using Wireshark and … this is the fun part … the problem went away.  Disabling Wireshark caused the problem to happen again.  Fiddler has the same effect. While running, the issue doesn’t happen.

 

Has anyone seen a situation similar to this, where running a packet capture caused a problem to go away?  Any ideas as to how or why this might happen?

 

Thanks

Howard Thompson

 

-----Inline Attachment Follows-----

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

-- 
Best regards,
   M. Giertzsch