Created attachment 17872 [details]
Different TreeConnect responses for different malformed Tree fields
When I used TreeConnection request with different malformed Tree fields, the response is different.
For the Tree field in the form "\\server\share", the server responds with STATUS_SUCCESS for a malformed "server" while STATUS_BAD_NETWORK_NAME for a malformed "share", as shown in the attached file. Is it normal?
Try the same request against Windows and report back on what is returned please.
I don't believe anything looks at the '\\server' field (it's really not relevant to anything in SMB3). The share of course has to match a real exported share.
My first inclination is that this is not a bug, but if you can show Windows behaving differently I'm willing to reconsider.
(In reply to Jeremy Allison from comment #1)
Could you please give me an overview of the internal workflow of parsing the Tree field? Thanks for your time!
(In reply to fouzhe from comment #2)
No, sorry. That's why we give you the source code, so you can do these things yourself :-).