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@xxxxxxxxx> 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@xxxxxxxxx
>
>
> On Sun, May 9, 2010 at 3:44 AM, M K <gedropi@xxxxxxxxx> 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@xxxxxxxxxxxxx>
>> Archives: http://www.wireshark.org/lists/wireshark-users
>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>> mailto:wireshark-users-request@xxxxxxxxxxxxx
>> ?subject=unsubscribe
>>
>
