Wireshark mailing list archives
Re: MS SQL 2000
From: Martin Visser <martinvisser99 () gmail com>
Date: Thu, 22 Apr 2010 09:52:54 +1000
The protocol Microsoft SQL uses is called Tabular Data Stream (TDS). Your traffic might be using a non-standard TCP port. Find the TCP stream that you think is between server and client, select a packet, right-click and select Decode As.. and choose TDS for the protocol (using the server side TCP port as the reference). If that doesn't work it probably is because your TDS traffic is wrapped inside of SSL, for encryption security. In that case you will first need to provide to wireshark the server's private key - as per http://wiki.wireshark.org/SSL Regards, Martin MartinVisser99 () gmail com On Wed, Apr 21, 2010 at 8:33 AM, false <jctx09 () yahoo com> wrote:
I am unable to decode MS SQL 2000 traffic? Can wireshark do this? If not, does anyone know of a tool that can? 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
Current thread:
- MS SQL 2000 false (Apr 20)
- Re: MS SQL 2000 Martin Visser (Apr 21)
- Re: MS SQL 2000 Bill Meier (Apr 21)
- Re: MS SQL 2000 Martin Visser (Apr 21)