Hi,
with SMB 2.1 (and higher) it's possible to do a session
re-authentication without
getting a STATUS_NETWORK_SESSION_EXPIRED. With SMB 2.0
STATUS_REQUEST_NOT_ACCEPTED
is returned.
In what situations do clients do a (pro active) reauthentication without
getting
STATUS_NETWORK_SESSION_EXPIRED
Hello Stefan,
Thank you for your inquiry about file sharing protocols.
One of the Open specifications team member will contact you soon.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-Original Message-
From: Stefan (metze) Metzmacher
[Sreekanth and dochelp to Bcc, Casemail to Cc]
[Adding Case number in subject]
Hi Metz
I will be assisting you with this inquiry and the case number for follow up is
: 112042751520312.
As stated in our specification, doch...@microsoft.com should always be used
to engage our team. Any other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dochelp!
I'm hoping you can help clarify some points about proper SMB1 (and
maybe SMB2?) client behavior when it does not hold an oplock (at least
one that allows write caching).
My understanding has always been that when a client does not have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the duplicate emails, but I sent this to the wrong dochelp
address before. Let me try again...
Hi Dochelp!
I'm hoping you can help clarify some points about proper SMB1 (and
maybe SMB2?) client behavior when it does not hold an oplock (at
Hello Jeff,
Thank you for your inquiry about File sharing protocols. One of
the Open specifications team member will contact you soon.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-Original Message-
From: Jeff Layton [mailto:jlay...@poochiereds.net]
