[MAC Lion] smbclient "Open AndX Request->STATUS_NOT_SUPPORTED"

George K Colley gcolley at apple.com
Tue Aug 2 10:36:31 MDT 2011


On Aug 1, 2011, at 9:02 PM, Christopher R. Hertel wrote:

> George K Colley wrote:
>> On Aug 1, 2011, at 8:43 AM, Christopher R. Hertel wrote:
>> 
>>> In theory, theory and practice are the same.  In practice, they're not.
>>> 
>>> Volker:  You're right to be cautious here, but I think that counting
>>>        on a broken CIFS server to send back a correct error code is
>>>        just as risky as counting on the CAP_NT_SMBS bit to be correct.
>>> 
>>> Sending the NT_STATUS_NOT_SUPPORTED error is correct behavior if the command
>>> is recognized but not supported.  We made that clear in [MS-CIFS], but I
>>> don't believe that it was clearly specified in any earlier documentation.
>>> The use of CAP_NT_SMBS was documented earlier.
>>> 
>>> I'm not sure why CAP_NT_SMBS is there.  It's fairly silly to negotiate NT LM
>>> 0.12 and then not support the full set of NT SMB commands.
>> 
>> Window 95/98 support the NT LM 0.12 dialect but did not set the CAP_NT_SMBS bit. This meant the some calls were not supported. This include any "NT_". I could get you a list of the ones I know if anyone is interested. 
> 
> I will have to get that testing copy of 98 running.
> 
> [MS-CIFS] only considers Windows 98SE clients, and not servers.  The
> question I want to check is whether W98SE sends NTCreate&X or Open&X.
I believe the Client supports the NTCreate&X but not the server. 
> 
> Thanks!
> 
> Chris -)-----
> 
> -- 
> "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
> Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
> jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
> ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
> OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org



More information about the samba-technical mailing list