search for: status_not_support

...sending data>65k Fail | sending data<65k Passes Max Write/Read Size[65535] *From Packet Captures*: 1. For FSCTL_VALIDATE_NEGOTIATE_INFO message: NAS returned STATUS_NOT_SUPPORTED & RHEL client drops the transaction. Though these are filters on NAS Server: NAS_Server::*> vserver cifs options show ... Max Buffer Size for SMB1 Message: 65535 SMB2 Enabled: true SMB3 Enabled: true WINS Se...

I noticed there was Bug 12808 against 4.6.3 ( if I read it right ) about smblcient doesn't handle STATUS_NOT_SUPPORTED gracefully for FSCTL_VALIDATE_NEGOTIATE_INFO. We are currently updating to 4.6.6 and I do not see it in smbXcli_base.c. I see the fix was done in 5/30/2017. Is this something that is still needed, and will be added in future releases ? I would like to know whether I should update 4.6.6 or not. R...

...gt; store information are listed in section 2.2.39. Documentation for these > is provided [MS-FSCC] section 2.5. Requests for information classes not > listed in section 2.2.39 but documented in section 2.5 of [MS-FSCC] for > Uses of "Set" or "LOCAL" MUST be failed with STATUS_NOT_SUPPORTED. Requests > for information classes not documented in section 2.5 of [MS-FSCC] or > documented in section 2.5 of [MS-FSCC] for Uses of only "Query" MUST be > failed with STATUS_INVALID_INFO_CLASS. > > If the object store supports security and the information class is >...

...> > is > > > > provided [MS-FSCC] section 2.5. Requests for information classes not > > > listed > > > > in section 2.2.39 but documented in section 2.5 of [MS-FSCC] for > Uses of > > > > "Set" or "LOCAL" MUST be failed with STATUS_NOT_SUPPORTED. Requests > for > > > > information classes not documented in section 2.5 of [MS-FSCC] or > > > > documented in section 2.5 of [MS-FSCC] for Uses of only "Query" MUST > be > > > > failed with STATUS_INVALID_INFO_CLASS. > > > > > &...