Fwd: [REG: 113020410191647] Windows Server 2012 seems to behave differently than Product Note #196 in [MS-SMB2].pdf states

[Richard Sharpe]

Hi folks,

This is for those who might be interested in behavior differences
between W2K08 and W2K12 on the wire.

---------- Forwarded message ----------
From: Edgar Olougouna <edgaro at microsoft.com>
Date: Tue, Feb 5, 2013 at 8:04 AM
Subject: RE: [REG: 113020410191647] Windows Server 2012 seems to
behave differently than Product Note #196 in [MS-SMB2].pdf states
To: Richard Sharpe <realrichardsharpe at gmail.com>
Cc: MSSolve Case Email <casemail at microsoft.com>


Richard,

I have taken ownership of this issue and will follow-up once we have the answer.



Thanks,

Edgar



From: Tarun Chopra
Sent: Monday, February 04, 2013 5:01 PM
To: Richard Sharpe
Cc: MSSolve Case Email
Subject: [REG: 113020410191647] Windows Server 2012 seems to behave
differently than Product Note #196 in [MS-SMB2].pdf states



Hi Richard



Thanks for contacting Microsoft Support. We have created a case,
113020410191647, to track your inquiry and a support engineer will
contact you to assist further. It would be helpful if you can please
share frame numbers in both the traces exhibiting working and
non-working behavior.



Thanks

Tarun Chopra



As an additional information, we have made some modification to this
section 3.3.5.2.7.2 and windows note <198> but still it *DOES NOT*
address the issue you reported. I am sharing updated content as it
might be helpful.



Section 3.3.5.2.7.2 : Handling Compounded Related Requests



Changed from:



The server MUST handle each individual request that is described in
the chain in order. For the first request, the identifiers for FileId,
SessionId, and TreeId MUST be taken from the received request. For
every subsequent request, the values used for FileId, SessionId, and
TreeId MUST be the ones used in processing the previous request or
generated for the previous resulting response. When all operations are
complete, the responses SHOULD<198> be compounded into a single
response to return to the client.



Changed to:



The server MUST handle each individual request that is described in
the chain in order. For the first request, the identifiers for FileId,
SessionId, and TreeId MUST be taken from the received request. For
every subsequent request, the values used for FileId, SessionId, and
TreeId MUST be the ones used in processing the previous request or
generated for the previous resulting response. If the previous request
failed to create SessionId or TreeId, or the compounded request does
not contain a SessionId or TreeId, the server MUST fail the compounded
request with STATUS_INVALID_PARAMETER. If the parent request in the
compounded chain failed to create FileId or the compounded request
does not contain a FileId, the server SHOULD<198> fail the compounded
request with the same error code returned by the parent request. When
all operations are complete, the responses SHOULD be compounded into a
single response to return to the client.



Section 6 Appendix A: Product Behavior



Changed from:



<198> Section 3.3.5.2.7.2: Windows Vista, Windows Server 2008, Windows
7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 fail the
compounded request with STATUS_INVALID_PARAMETER if the previous
request failed to create the FileId or the compounded request does not
contain a FileId, SessionId, or TreeId. If the previous session
expired, Windows Vista, Windows Server 2008, Windows 7, Windows Server
2008 R2, Windows 8, and Windows Server 2012 fail the next request in
the compound request with STATUS_NETWORK_SESSION_EXPIRED, and the
subsequent requests in the compounded request will be failed with
STATUS_ INVALID_PARAMETER.



Changed to:



<198> Section 3.3.5.2.7.2: If the parent request failed to create
FileId or the compounded request does not contain a FileId, Windows
Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 fail
the compounded request with STATUS_INVALID_PARAMETER. If the previous
session expired, Windows Vista, Windows Server 2008, Windows 7,
Windows Server 2008 R2, Windows 8, and Windows Server 2012 servers
fail the next request in the compounded chain with
STATUS_NETWORK_SESSION_EXPIRED, and the subsequent requests in the
compounded chain will be failed with STATUS_INVALID_PARAMETER.





-----Original Message-----
From: Richard Sharpe [mailto:realrichardsharpe at gmail.com]
Sent: Monday, February 04, 2013 1:44 PM
To: Interoperability Documentation Help
Subject: Windows Server 2012 seems to behave differently than Product
Note #196 in [MS-SMB2].pdf states



Hi folks,



I was looking at [MS-SMB2] — v20120705 and in particular, Product Note
195, which says:



-------------------------------------------------

<195> Section 3.3.5.2.7.2: Windows Vista, Windows Server 2008, Windows
7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 fail the
compounded request with STATUS_INVALID_PARAMETER if the previous
request failed to create the FileId or the compounded request does not
contain a FileId, SessionId, or TreeId. If the previous session
expired, Windows Vista, Windows Server 2008, Windows 7, Windows Server

2008 R2, Windows 8, and Windows Server 2012 fail the next request in
the compound request with STATUS_NETWORK_SESSION_EXPIRED, and the
subsequent requests in the compounded request will be failed with
STATUS_ INVALID_PARAMETER.

-------------------------------------------------



The [MS-SMB2] — v20121017 version has similar wording but it is in
product note 197.



However, an SMBTORTURE test I added to the Samba master branch seems
to show that W2K12 responds with something different

(STATUS_OBJECT_NAME_NOT_FOUND) while W2K08 seems to conform to the
product note I mentioned.



Attached is a capture of the W2K0 behavior and the W2K12 behavior.



Could you clarify whether I have simply misinterpreted the product
note or some other part of the spec or whether W2K12 behavior does
indeed differ from the latest version of the spec I have?



--

Regards,

Richard Sharpe

(何以解憂？唯有杜康。--曹操)


-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)