Volker,
The following is the information you requested regarding DataOffset in
WRITE_ANDX request.
Each request is self-describing, so the offset is always from the start of
the SMB Header for the current message. In this case, the DataOffset is
relative to the SMB_HEADER of the current request (not just the first request).
The only offset in either protocol that spans multiple requests is the
"AndXOffset/NextCommand" that links the requests.
Please let us know if you have further questions.
Thanks !
----------------------------------------------------------
Hongwei Sun - Sr. Support Escalation Engineer DSC Protocol Team, Microsoft
[EMAIL PROTECTED]
Tel: 469-7757027 x 57027
-----------------------------------------------------------
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Volker Lendecke
Sent: Saturday, November 08, 2008 12:44 PM
To: Richard Guthrie
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [cifs-protocol] Re: [Pfif] Correction Assistance Request: DataOffset
in WRITE_ANDX request
Hi, Richard!
On Wed, Nov 05, 2008 at 10:40:38AM -0800, Richard Guthrie wrote:
> Your issue has been logged as a bug in the documentation and will be
> taken into consideration as part of our efforts to update the document
> you reference. You should expect to find your issue addressed in that
> document.
> Thank you for your feedback.
Well, this is actually a question I need an answer on, as right now I am in the
process of rewriting our chained SMB engine, and it is a bit difficult for me
to trigger a Windows client doing that kind of request.
It is a bit unsatisfactory that the CAR process right now only covers the newer
protocols and for the old protocols we are deferred to some unknown point in
the future. I think this is not what the CAR process was installed for.
What do I have to do to get an answer on my question?
Volker
_______________________________________________
cifs-protocol mailing list
[email protected]
https://lists.samba.org/mailman/listinfo/cifs-protocol