Good morning Tim. Bill Wesse from the Documentation Support team here. I will
be your contact for this issue. We have created the following case to track our
investigation:
SRX091124600335 [MS-SMB] Trans2SetPathInfo() not enforcing share mode
I will begin work this morning, and will update you
Hello Tim. I think the difference in the response between the standard versus
pass-through level lies in how the file handle is obtained during the call
(given that TRANS2_SET_PATH_INFORMATION passes the path, and not the handle).
The logical conclusion from the trace is that pass-through gets
On Wed, Nov 25, 2009 at 05:14:26PM +, Bill Wesse wrote:
Hello Tim. I think the difference in the response between the standard versus
pass-through level lies in how the file handle is obtained during the call
(given that TRANS2_SET_PATH_INFORMATION passes the path, and not the handle).
Jeremy, I agree with you concerning Windows behavior needing to be documented;
but I felt it necessary to mention the possibilities concerning further
elaboration - since I am not the one to make that decision (nor do I wish to
second guess those who do).
My next step is to finish tracking
Question:
Which existing handle would the pass-through be using? The handle
opened in packet #28 is a separate tcp connection and a separte
session from the Trans2SetPathInfo in packet #33. I'm not aware of
any situation where the server is expected to share file handles
across multiple
Hi Steven,
Thanks for your question regarding SMBv1 LockAndX. One of the Open
Specification Documentation team will be in touch with you soon.
Best regards,
Tom Jebo
Open Specification Documentation Support
From: Steven Danneman [mailto:steven.danne...@isilon.com]
Sent: Wednesday, November
