This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

NT Status: STATUS_UNSUCCESSFUL (0xc0000001)

0

trying to save a scanned file from a Canon copier running MEAP (Multifunctional Embedded Application Platform) to an SMB share on NetApp 2240 (C-Mode) generates a meaningless error on the copier.

Wireshark capture from the scanner side shows a successful 3 way handshake, then SMB protocol negotiation request which gets an error response from NetApp "NT Status: STATUS_UNSUCCESSFUL (0xc0000001)"

What would be an indication that the SMB request from the copier is non-Unicode ?

Thanks

asked 05 Sep '13, 10:55

net_tech's gravatar image

net_tech
116●30●33●37
accept rate: 13%

One Answer:

1

What would be an indication that the SMB request from the copier is non-Unicode ?

That depends on what you mean by "non-Unicode".

I'm looking at one SMB trace that I have; the Negotiate Protocol request has the "Strings are Unicode" flag set in the Flags2 field, but the protocol names are non-Unicode, as Microsoft's MS-CIFS specification says they should be:

String fields that restrict character encoding to OEM characters only, even if Unicode support has been negotiated, are labeled as OEM_STRING. Some examples of strings that are never passed in Unicode are:

  • The dialect strings in the SMB_COM_NEGOTIATE (section 2.2.4.52) command.

answered 05 Sep '13, 11:54

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k●3●35●196
accept rate: 19%

In the SMB request packet, under Flags2 I see Unicode Strings: Strings are ASCII

I am running in to a BUG described in the article below.

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=617674

The CIFS-enabled Vserver disallows any SMB 1 requests that do not have the Unicode bit set. This happens even if there are not any Unicode strings sent in the request.

(05 Sep '13, 12:08) net_tech