[cifs-protocol] [REG:113041210363439] RE: [MS-CIFS] Windows Note 246.

Tue Apr 30 09:23:30 MDT 2013

Hi Chris,

Future versions of the document will look similar to this:

3.3.5.6   Receiving an SMB_COM_CREATE Request
If the Create operation fails, the server MUST return an error response with a Status code from the list provided in section 2.2.4.4.2. Otherwise, the server MUST allocate a new FID, format an SMB_COM_CREATE response message as defined in section 2.2.4.4.2, and set SMB_Header.Status to indicate success. Server.Statistics.sts0_fopens MUST be increased by 1, and an Open containing the new FID MUST be created, initialized, and entered into the Server.Connection.FileOpenTable.<246> If Server.EnableOplock is TRUE and a requested OpLock was granted, the type of OpLock MUST be set in Server.Open.OpLock and Server.Open.OplockState MUST be set to Held;
<246> Section 3.3.5.6: When opening, overwriting, deleting, or renaming a file, Windows NT Server checks for sharing violations. If a sharing violation would be generated by the operation, the server delays for 200 ms, as default sharing violation delay time, and then tests again for a sharing violation. The server retries five times as default, for a total delay of approximately one second, before giving up and returning the sharing violation error.
The sharing violation delay time and number of retires can be configured through the registry settings.
More details about these values modification can be found in the following KB article http://support.microsoft.com/kb/150384

Please let me know if this addresses your concern.

Thanks and regards,

Sebastian

Sebastian Canevari | Escalation Engineer | US-CSS Developer Support Core (DSC) Protocol Team
[Description: Description: Description: Description: Description: Description: Description: cid:2A481EA8-2691-4873-8A80-F8CFF3297746 at domain.actdsltmp]
P +1 469 775 7849
One Microsoft Way, 98052, Redmond, WA, USA http://support.microsoft.com<http://support.microsoft.com/>

From: Sebastian Canevari
Sent: Monday, April 29, 2013 4:35 PM
To: Christopher R. Hertel
Cc: Obaid Farooqi; MSSolve Case Email; cifs-protocol at samba.org
Subject: RE: [cifs-protocol] [REG:113041210363439] RE: [MS-CIFS] Windows Note 246.

Hi Chris,

Yes indeed.
I am just waiting on a final confirmation from the PG.

Thanks,

Sebastian

Sent from my Windows Phone
________________________________
From: Christopher R. Hertel<mailto:crh at ubiqx.mn.org>
Sent: ‎4/‎29/‎2013 4:31 PM
To: Sebastian Canevari<mailto:Sebastian.Canevari at microsoft.com>
Cc: Obaid Farooqi<mailto:obaidf at microsoft.com>; MSSolve Case Email<mailto:casemail at microsoft.com>; cifs-protocol at samba.org<mailto:cifs-protocol at samba.org>
Subject: Re: [cifs-protocol] [REG:113041210363439] RE: [MS-CIFS] Windows Note 246.
Sebastian,

Just checking on the status of this ticket.  Were my suggestions of any use
to the documentation team?

Chris -)-----

On 04/12/2013 03:47 PM, Obaid Farooqi wrote:
> Hi Chris:
> I have created a case to track this issue. 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 nkang at Microsoft dot com
>
>
> -----Original Message-----
> From: Christopher R. Hertel [mailto:crh at ubiqx.mn.org]
> Sent: Friday, April 12, 2013 1:43 PM
> To: Interoperability Documentation Help
> Cc: cifs-protocol at samba.org<mailto:cifs-protocol at samba.org>
> Subject: [MS-CIFS] Windows Note 246.
>
> Dochelp,
>
> Me again.
>
> Document: [MS-CIFS] v20130118
>       Page: 726
>        WBN: 246
>
> Windows behavior note 246 SHOULD reference the following KB article, to indicate that the timeout value of 200 ms and the repeat count of 5 are tunable parameters, and to provide the registry keys.
>
>     http://support.microsoft.com/kb/150384
>
> Oh... and there's a typo in the first sentence of the note.  The word "check" should be "checks".
>
> 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/     -)-----   crh at ubiqx.mn.org<mailto:crh at ubiqx.mn.org>
> OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org<mailto:crh at ubiqx.org>
> _______________________________________________
> cifs-protocol mailing list
> cifs-protocol at cifs.org<mailto:cifs-protocol at cifs.org>
> https://lists.samba.org/mailman/listinfo/cifs-protocol
>

--
"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/     -)-----   crh at ubiqx.mn.org<mailto:crh at ubiqx.mn.org>
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org<mailto:crh at ubiqx.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20130430/4c1bf84b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2118 bytes
Desc: image001.gif
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20130430/4c1bf84b/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1705 bytes
Desc: image002.jpg
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20130430/4c1bf84b/attachment-0001.jpg>