About the SMB error codes.
Tayade, Nilesh
Nilesh.Tayade at netscout.com
Tue May 21 10:13:19 MDT 2013
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?
--
Thanks,
Nilesh
-----Original Message-----
From: Christopher R. Hertel [mailto:crh at ubiqx.mn.org]
Sent: Tuesday, May 21, 2013 6:14 PM
To: Tayade, Nilesh
Cc: samba-technical at lists.samba.org
Subject: Re: About the SMB error codes.
Nilesh,
The severity of the error code is dependent upon the context...the situation in which the error code was returned. There is a full document listing the NT error codes:
http://msdn.microsoft.com/en-us/library/cc231196.aspx
...but [MS-CIFS] provides the best explanation of SMB error code handling (including maping from NT to DOS codes).
Chris -)-----
On Tue, May 21, 2013 at 06:04:52AM +0000, Tayade, Nilesh wrote:
> Hi,
>
> I am looking at the error codes for SMB/CIFS (both DOS and NT-STATUS errors). There is a description related to each error code in documentation.
> But there is no information related to severity of error codes (e.g. Fatal/Critical/Warning/Information only etc.).
>
> Could someone please point to any reference that shows such categorization?
>
> --
> Thanks,
> Nilesh
More information about the samba-technical
mailing list