3.2.5.1 Receiving Any Message

Upon receiving any SMB message, the client MUST associate the message received with the correct client process and thread, as identified by the PID and MID values in the Client.Connection.PIDMIDList. If the MID value is the reserved value 0xFFFF ((USHORT)(-1)), the message can be an OpLock break sent by the server. Otherwise, if the PID and MID values of the received message are not found in the Client.Connection.PIDMIDList, the message MUST be discarded.

If an SMB_COM_READ_RAW is in progress and the message is a raw data transfer, the message MUST be handled as described in section 3.2.5.16.

Unless otherwise noted, the client MUST return the status received in the SMB_Header.Status field of a response message to the application that issued the corresponding request.

For the response messages of the following commands, there are no other processing rules required on the client:

• SMB_COM_CREATE_DIRECTORY (section 2.2.4.1)

• SMB_COM_DELETE_DIRECTORY (section 2.2.4.2)

• SMB_COM_FLUSH (section 2.2.4.6)

• SMB_COM_DELETE (section 2.2.4.7)

• SMB_COM_RENAME (section 2.2.4.8)

• SMB_COM_SET_INFORMATION (section 2.2.4.10)

• SMB_COM_LOCK_BYTE_RANGE (section 2.2.4.13)

• SMB_COM_UNLOCK_BYTE_RANGE (section 2.2.4.14)

• SMB_COM_CHECK_DIRECTORY (section 2.2.4.17)

• SMB_COM_PROCESS_EXIT (section 2.2.4.18)

• SMB_COM_SET_INFORMATION2 (section 2.2.4.30)

• SMB_COM_LOCKING_ANDX (section 2.2.4.32)

• SMB_COM_TREE_DISCONNECT (section 2.2.4.51)

• SMB_COM_FIND_CLOSE (section 2.2.4.61)

• SMB_COM_NT_RENAME (section 2.2.4.66)

• SMB_COM_WRITE_PRINT_FILE (section 2.2.4.68)

• SMB_COM_CLOSE_PRINT_FILE (section 2.2.4.69)

• Transaction Subcommands (section 2.2.5)

  • TRANS_SET_NMPIPE_STATE (section 2.2.5.1)

  • TRANS_WAIT_NMPIPE (section 2.2.5.10)

• Transaction2 Subcommands (section 2.2.6)

  • TRANS2_SET_PATH_INFORMATION (section 2.2.6.7)

  • TRANS2_SET_FILE_INFORMATION (section 2.2.6.9)

• NT Transact Subcommands (section 2.2.7)

  • NT_TRANSACT_SET_SECURITY_DESC (section 2.2.7.3)

A client that has outstanding OpLocks can receive an OpLock Break Notification at any time from the server. This is the only unsolicited message that the server is permitted to send.