FreeTDS Development Group

["Jackson, Craig (Gale)" <Craig.Jackson AT cengage.com>]

The Wireshark TDS decode is not up to date.

It does not recognize a number of packet formats which are new.

Craig 

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org 
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Steve Fischer
Sent: Thursday, July 30, 2009 11:30 AM
To: freetds AT lists.ibiblio.org
Subject: [freetds] Malformed Packets

I am a network engineer investigating a complaint of slow application
performance.  In doing a capture (using Wireshark), I noticed a fair
number (about 125 in a 10 minute window) of responses coming from a host
on 1433/TCP (Response Packet) with a Malformed Packet:TDS label on the
payload.  I know that 1433/TCP is the port Microsoft SQL Server uses,
and until today, had never heard of TDS as a protocol.  Can anyone here
shed some light on this?  The research I've done regarding "Malformed
Packet" and Wireshark indicates that something in the response the
server is crafting is amiss, but as to what, I'd have not even the
slightest clue.  I'd be happy to forward the capture file to anyone who
could help me get to the bottom of this mystery.  Whatever this is, it
can't be helping performance any I'd assume.  Thanks in advance for any
assistance that anyone can provide.

Steve Fischer
Sr. Network Engineer.

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds