On Friday, 27 October 2017 21:10:22 CET Sreekanth Nadendla wrote:
> Hello Andreas, Windows SMB1 clients use SMB_COM_RENAME as Uri Simchoni
> mentioned below. I'm confirming that part.
> Perhaps your samba 'smbclient' test used the same as Uri pointed out and
> that's why it worked. If that’s the
ifs-protocol@lists.samba.org; MSSolve
Case Email <casem...@microsoft.com>
Subject: RE: [cifs-protocol] [REG:117102016529426] SMB2 File Rename
Hello Andreas, Windows SMB1 clients use SMB_COM_RENAME as Uri Simchoni
mentioned below. I'm confirming that part.
Perhaps your samba 'smbclient' test used the s
otocol@lists.samba.org; MSSolve Case Email <casem...@microsoft.com>
Subject: Re: [cifs-protocol] [REG:117102016529426] SMB2 File Rename
Chiming in because I also had rename-related investigations (I don't think this
answers the original question but it is relevant to the
response):
- smbclient
Chiming in because I also had rename-related investigations (I don't
think this answers the original question but it is relevant to the
response):
- smbclient does SMB1 rename using cifs rename, not using FILE_RENAME_INFO
- so does Windows (or so it seems)
- smbclient can be made to use
Hello Andreas, in the sample traces you've sent us, I can see the setInfo
request with SMB2_FILE_RENAME_INFO for SMB2 case. However I don't see similar
rename structure from your first trace rename_nt1. Let me know if I'm missing
something.
On windows OS, rename command does not allow you to
Hello Andreas, I will be assisting you with your issue. I am currently
researching the problem and will provide you with an update soon. Thank you for
your patience.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-Original Message-
From: Andreas Schneider
[DocHelp to BCC, casemail on CC, SR ID on Subject]
Hi Andreas,
Thank you for your protocols question. We have created SR 117102016529426 to
track this issue. One of our engineers will respond soon.
Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open
