[cifs-protocol] [REG:111052652308584] [ttalpey at microsoft.com: Reminder -- share secdesc and smb2 echo?]
obaidf at microsoft.com
Fri Jun 17 14:22:05 MDT 2011
It looks like we need the trace to properly answer this question.
I appreciate your help and understanding in this matter.
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 allisong at microsoft.com
From: Volker Lendecke [mailto:Volker.Lendecke at SerNet.DE]
Sent: Tuesday, June 14, 2011 8:34 AM
To: Obaid Farooqi
Cc: cifs-protocol at samba.org; pfif at tridgell.net; MSSolve Case Email
Subject: Re: [REG:111052652308584] [ttalpey at microsoft.com: Reminder -- share secdesc and smb2 echo?]
On Mon, Jun 13, 2011 at 03:42:05PM +0000, Obaid Farooqi wrote:
> Hi Volker:
> Thanks for your reply.
> I'll look into the questions raised by you and will be in touch as
> soon as I have an answer.
> I did not find a trace attached to this email. Please send me the
> trace you mentioned.
Hmmm. I'm sorry, but I can't reproduce the behaviour anymore at this moment. Can you find out how I can trigger Windows XP to use the NT_TRANSACT_CREATE call according to
including a security descriptor instead of a normal SMB_COM_NT_CREATE_ANDX call according to
? I have seen that where the reply to NT_TRANSACT_CREATE said it has successfully created the file, probably including setting the security descriptor.
If you really need the trace to work on these questions, I could write a special test program and create it.
With best regards,
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
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 casemail at microsoft.com 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.
More information about the cifs-protocol