About the SMB error codes.

[Tayade, Nilesh]

> -----Original Message-----
> From: Christopher R. Hertel [mailto:crh at ubiqx.mn.org]
> Sent: Tuesday, May 21, 2013 10:22 PM
> To: Tayade, Nilesh
> Cc: Christopher R. Hertel; samba-technical at lists.samba.org
> Subject: Re: About the SMB error codes.
> 
> On Tue, May 21, 2013 at 04:13:19PM +0000, Tayade, Nilesh wrote:
> > Thanks Chris.
> > In my case, I received STATUS_INVALID_DEVICE_REQUEST error. The
> communication still goes on the same socket after the error is
> reported.
> > So can I treat this as non-FATAL error? How do I evaluate the context
> where errors will be treated as FALAL/Critical ones?
> 
> This is where it becomes necessary to study the Microsoft
> documentation.
> You may have gotten that error because you were trying to do more than
> one thing (lots of the SMB calls do more than one thing).  Find out
> which message returned the error, and then look at the documentation
> for that call (both in section 2 and section 3).  Start with [MS-CIFS]
> and/or [MS-SMB] if you are working with SMBv1.  SMBv2 and V3 are
> documented in [MS-SMB2].

Thanks Chris. 
I looked into the MS-CIFS documentation. In my case the STATUS_INVALID_DEVICE_REQUEST error is generated for NT-TRANS request with IOCTL subcommand.
But in MS-CIFS documentation, the error codes list for NT-TRANS command with IOCTL subcommand doesn't show the STATUS_INVALID_DEVICE_REQUEST error.
What's wrong?

Please refer the attached pcap file with 2 SMB packets. The IOCTL is being performed on some file system resource.
And the IOCTL parameters show 'Unknown' function. Could this be the reason of error? Could this happen because of incompatibility of Windows versions?
> 
> Chris -)-----
[...]

--
Thanks,
Nilesh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smb_packets.pcap
Type: application/octet-stream
Size: 301 bytes
Desc: smb_packets.pcap
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20130522/d5e65644/attachment.obj>