Chris, I will be looking into this for you. Do you have network traces you can share?
Regards, Edgar -----Original Message----- From: Obaid Farooqi Sent: Wednesday, May 18, 2011 10:58 AM To: [email protected] Cc: [email protected]; MSSolve Case Email Subject: RE:[REG:111051857287367] BranchCache and SMB2: Questions specific to BranchCache. Hi Chris: Thank you for contacting Microsoft regarding your query on branch cache. A member of the protocol documentation team will be in touch soon. Regards, Obaid Farooqi Escalation Engineer | Microsoft Exceeding your expectations is my highest priority. If you would like to provide feedback on your case you may contact my manager at [email protected] -----Original Message----- From: Christopher R. Hertel [mailto:[email protected]] Sent: Tuesday, May 17, 2011 9:12 PM To: Interoperability Documentation Help Subject: BranchCache and SMB2: Questions specific to BranchCache. I have a couple of questions regarding BranchCache and [MS-PCCRC]. As you know, BranchCache--particularly the Content Information format specified in [MS-PCCRC]--can be used as an extension to SMB2. 1) In the Content Information structure ([MS-PCCRC:2.3]), there is the following field definition: dwOffsetInFirstSegment (4 bytes): Number of bytes into the first segment within the Content Information data structure at which the content range begins. I can't make heads nor tails of that description, and the captures I have done on the wire typically show that field set to zero. Similarly, the examples in section 3 of [MS-PCCRC] show the value of this field to be zero. The field is 4 bytes in length, so it cannot be an offset into the content itself, since content offsets are (should be) 8 bytes (64-bit). Please clarify: What does dwOffsetInFirstSegment actually represent? 2) I am not getting what I expect in the dwReadBytesInLastSegment field. This field is defined in [MS-PCCRC:2.3], as follows: dwReadBytesInLastSegment (4 bytes): Total number of bytes of the content range which lie within the final segment in the Content Information data structure. It seems to me that this value represents the number of bytes of actual content included in the calculation of the final Segment block of the Content Information. That interpretation is supported by the examples in section 3. In actual captures, however, Windows IIS server returns zero (0x00000000) in the dwReadBytesInLastSegment field. Is this a documentation bug or is the IIS server returning the wrong value? This is IIS running on W2K8r2 with fairly up-to-date patches applied. Looking forward to the replies. Thanks. Chris -)----- -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- [email protected] OnLineBook -- http://ubiqx.org/cifs/ -)----- [email protected] -- Christopher R. Hertel -)----- Storage Architect & CIFS Geek http://www.ubiqx.com/ Data Storage and Systems Consulting "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Microsoft is committed to protecting your privacy. Please read the Microsoft Privacy Statement for more information.The above is an email for a support case from Microsoft Corp.REPLY ALL TO THIS MESSAGE or INCLUDE [email protected] IN YOUR REPLY if you want your response added to the case automatically. For technical assistance, please include the Support Engineer on the TO: line. Thank you. _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
