search for: smb2_file_rename_info

...ows Server 2012 R2 (haven't checked with other versions). IMHO it is caused by: - Not setting SMB2_HDR_FLAG_DFS when calling smb2cli_req_send() from smb2cli_set_info_send() - cli_resolve_path() returning a full dfs path for the destination, which is then passed to cli_rename() to be used in SMB2_FILE_RENAME_INFO After some patching and testing, I came to this conclusion: Setting SMB2_HDR_FLAG_DFS solves the issue for smbd, but not for Windows Server and not for NetApp. It seems that the file name in SMB2_FILE_RENAME_INFO must always be a non-dfs path and the header flag is ignored: - A windows client u...

...> checked with other versions). > > IMHO it is caused by: > - Not setting SMB2_HDR_FLAG_DFS when calling smb2cli_req_send() from > smb2cli_set_info_send() > - cli_resolve_path() returning a full dfs path for the destination, which is > then passed to cli_rename() to be used in SMB2_FILE_RENAME_INFO > > After some patching and testing, I came to this conclusion: > > Setting SMB2_HDR_FLAG_DFS solves the issue for smbd, but not for Windows > Server and not for NetApp. > It seems that the file name in SMB2_FILE_RENAME_INFO must always be a > non-dfs path and the header flag...

..."client max protocol = NT1" in the smb.conf of my cluster members but the Win 7 clients continue to use the SMB2 protocol. Looking more closely at the communication between the Win 7 client and the Samba Servers when i attempt a file save in Excel i see that the Client issues a FILE_INFO/SMB2_FILE_RENAME_INFO request and the samba server returns a STATUS_ACCESS_DENIED response. I suspect disabling ACL's would resolve the issue but unfortunately these are necessary for the project . Ideally i would be able to use SMB2 but it is not a show stopper if i could force Win 7 clients to use SMB1. I'm...