This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

I notice that the decode for an SMB2 Negotiate Protocol Request is fairly sparse compared to the decode used for the equivalent SMB1 Request

SMB1 Dialect: PC Network Program 1.0 Dialect: LANMAN1.0 Dialect: Windows for Workgroups 3.1a Dialect: LM1.2x002 Dialect: LANMAN2.1 Dialect: NT LM 0.12 Dialect: SMB 2.002 Dialect: SMB 2.???

SMB2 Dialect: 0x0202 Dialect: 0x0210

In the SMB2 decode, I would prefer to see something like: Dialect: SMB 2.02 (Vista/Win2003) Dialect: SMB 2.10 (Win7/Win2008)

I would be happy to submit a feature request ... but before I do that, would anyone like to push back and either defend the current approach or offer a third path?

--sk

asked 09 Oct '13, 02:10

skendric's gravatar image

skendric
11111113
accept rate: 0%

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×27
×1

question asked: 09 Oct '13, 02:10

question was seen: 2,694 times

last updated: 09 Oct '13, 02:10

p​o​w​e​r​e​d by O​S​Q​A