From bc10e5039a9056474f0cab03a798d85d62d47254 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Tue, 23 Jun 2020 17:39:10 +0200 Subject: [PATCH] docs-xml/smbdotconf: add "smb2 disable oplock break retry" MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Stefan Metzmacher Reviewed-by: Günther Deschner --- .../smb2_disable_oplock_break_retry.xml | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs-xml/smbdotconf/protocol/smb2_disable_oplock_break_retry.xml diff --git a/docs-xml/smbdotconf/protocol/smb2_disable_oplock_break_retry.xml b/docs-xml/smbdotconf/protocol/smb2_disable_oplock_break_retry.xml new file mode 100644 index 00000000000..1b67100b7eb --- /dev/null +++ b/docs-xml/smbdotconf/protocol/smb2_disable_oplock_break_retry.xml @@ -0,0 +1,39 @@ + + + This boolean parameter controls whether + smbd + 8 will trigger + smb2 oplock break notification retries when using + yes. + + + The [MS-SMB2] specification documents that a server should + send smb2 oplock break notification retries on all available channel + to the given client. + + But Windows Server versions (at least up to 2019) do not send + smb2 oplock break notification retries on channel failures. + That means they do not implement the behavior specified + in [MS-SMB2]. + + By default Samba behaves according to the specification + and send smb2 oplock break notification retries. + + Warning: Only enable this option if existing clients can't + handle possible retries and it turns out that the Windows Server + behavior is required. + + Note: it's likely that this option gets removed again + if future Windows versions change their behavior. + + Note: this only applies to oplocks and not SMB2 leases. + + +server multi channel support + +no +yes + -- 2.47.3