http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1744
Summary: TDS Packet Decode ?
Product: Wireshark
Version: 0.99.6
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: dennis.hollarn@xxxxxxxxxxxxxxxxx
Build Information:
wireshark 0.99.6a (SVN Rev 22276)
Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 1.3.0, with GLib 2.12.12, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.
Running on Windows 2000 Service Pack 4, build 2195, with WinPcap version 4.0.1
(packet.dll version 4.0.0.901), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
--
When running a trace between a Solaris client and Solaris Server using backup
software, the decode contains TDS decodes with 'unknown packet type' and
'unreassembled packet' in the 'info' field.
Just curious.. How does Wireshark determine the packet is a TDS packet ?
TCP Port # ? Or other TCP options ? When I run Sniffer 4.9, it does not
decode same packet as a TDS packet..
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
