Wireshark mailing list archives

Re: tds


From: M K <gedropi () gmail com>
Date: Tue, 18 May 2010 09:39:22 -0700

I believe that the problem is the first because it appears to be
related to an application issue on only one server.  Connecting to the
app on another server in the cluster does not produce those errors.

On 5/10/10, Martin Visser <martinvisser99 () gmail com> wrote:
I'm not sure I understand. Are you saying that when packets have len==1460
you actually have application errors with real clients, or that you don't
seem to have any real errors but only that Wireshark report Unknown type?

If it is the first then there is an issue with your application.

If it is the second then there is problem with Wireshark decoding the valid
packets.

If it is the second then file a bug on the Wireshark bugzilla.


Regards, Martin

MartinVisser99 () gmail com


On Tue, May 11, 2010 at 1:09 AM, M K <gedropi () gmail com> wrote:

Thank you.  Actually any traffic with LEN== 1460 despite a variety of
'types' appear to produce the error.  But, reconnecting using
different servers does not produce the error.  Therefore not a WS
issue?  Thanks for helping to troubleshoot.

On 5/10/10, Martin Visser <martinvisser99 () gmail com> wrote:
Unknown Packet Types will just more likely mean that your the data has
type
identifiers that haven't been coded for in Wireshark. It could be that
you
are using a newer version of MS SQL server than has been coded for. This
is
often the case with proprietary protocols that may not have had
well-documented  specfications.
Regards, Martin

MartinVisser99 () gmail com


On Sun, May 9, 2010 at 3:44 AM, M K <gedropi () gmail com> wrote:

Perhaps I have figured out part of the Unreassembled Packet issue.  It
appears that the conversations between two servers are filled with
Unknown Packet Types.  I believe that the issue becomes clearer
because the Packet Types are many!  Can I take that to mean that the
databases are mismatched?  Or?

Thanks

___________________________________________________________________________
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


___________________________________________________________________________
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


___________________________________________________________________________
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


Current thread: