[case number in subject] [dochelp to bcc] Michael,
The case number 112091915263549 has been created to track this inquiry. I will assist you in resolving this issue. In the SMB2_CREATE_APP_INSTANCE_ID Create Context: DataOffset: 36 (0x24) should be DataOffset: 32 (0x20) and no padding is required. You have 4 extra bytes of zeros padding after the SMB2_CREATE_APP_INSTANCE_ID context name. 00 00 00 00 10 00 10 00 00 00 24 00 14 00 00 00 45 BC A6 6A EF A7 F7 4A 90 08 FA 46 2E 14 4D 74 00 00 00 00 14 00 00 00 67 5F D4 1E 7C E4 55 42 88 1D E6 9F C3 9E 0A F6 Here is an example of working create context: 00 00 00 00 10 00 10 00 00 00 20 00 14 00 00 00 45 BC A6 6A EF A7 F7 4A 90 08 FA 46 2E 14 4D 74 14 00 00 00 65 E3 26 E0 E7 03 50 44 9B B9 E5 A5 45 FF C0 4C Thanks, Edgar -----Original Message----- From: Michael Adam [mailto:ob...@samba.org] Sent: Tuesday, September 18, 2012 5:11 PM To: Interoperability Documentation Help Cc: p...@tridgell.net; cifs-proto...@samba.org Subject: clarification for application instance ID We are having problems in testing the AppInstanceID behaviour of Windows Server 2012. (In order to implement it correctly in Samba.) We have written a test case that sends a smb2_create request with the AppInstanceId create blob filled as specified by the [MS-SMB2] doc. At least we believe we have correclty created the context. But the server returns INVALID_PARAMETER. What are we possibly doing wrong here? Network capture attached. Thanks, Michael _______________________________________________ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
