WireShark side effects

["Thompson, Howard K (Howard)" <howard () motive com>]

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

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