3.2.1.1 Success Case Example
The following diagram shows the steps required to connect to and open the shared virtual SCSI disk.

Figure 8: Connecting and opening a shared virtual SCSI disk
The RSVD client requests opening a shared virtual SCSI disk as described in [MS-RSVD] section 3.1.4.2. The RSVD client requests that the file client open the share as described in [MS-SMB2] section 3.2.4.2.
The file client processes the request and sends an SMB2 NEGOTIATE Request ([MS-SMB2] section 2.2.3) to the file server to notify the server about the dialects of the SMB2 protocol that the file client understands.
The file server processes the SMB2 NEGOTIATE Request, as described in [MS-SMB2] section 3.3.5.3. The file server responds to the file client with an SMB2 NEGOTIATE Response ([MS-SMB2] section 2.2.4) to notify the client of the preferred common dialect. The preferred common dialect has to be version 3.0.2 or later.
The file client processes the SMB2 NEGOTIATE Request as described in [MS-SMB2] section 3.2.5.2. The file client attempts to establish a session with the file server, as described in [MS-SMB2] section 3.2.4.2.3, by using the SMB2 SESSION_SETUP Request ([MS-SMB2] section 2.2.5).
The file server processes the SMB2 SESSION_SETUP Request, as described in [MS-SMB2] section 3.3.5.5. The file server responds with an SMB2 SESSION_SETUP Response ([MS-SMB2] section 2.2.6).
The file client processes the SMB2 SESSION_SETUP Response, as described in [MS-SMB2] section 3.2.5.3. The file client attempts to establish a tree connection to the file server, as described in [MS-SMB2] section 3.2.4.2.4, using an SMB2 TREE_CONNECT Request ([MS-SMB2] section 2.2.9).
The file server processes the SMB2 TREE_CONNECT Request, as described in [MS-SMB2] section 3.3.5.7. The file server responds with an SMB2 TREE_CONNECT Response, as described in [MS-SMB2] section 2.2.10.
The file client processes the SMB2 TREE_CONNECT Response, as described in [MS-SMB2] section 3.2.5.5, and returns STATUS_SUCCESS to the RSVD client.
Upon success, the RSVD client requests opening the shared virtual SCSI disk by sending the file name of the shared virtual SCSI disk, and an SVHDX_OPEN_DEVICE_CONTEXT structure ([MS-RSVD] section 2.2.4.12), and requests that the CreateOptions field of the SMB2 CREATE Request be set to FILE_NO_INTERMEDIATE_BUFFERING. The values for the SVHDX_OPEN_DEVICE_CONTEXT structure are described in [MS-RSVD] section 3.1.4.2.
The file client processes the request, as described in [MS-SMB2] section 3.2.4.3. The file client constructs an SMB2 CREATE Request that contains an SMB2_CREATE_CONTEXT Request ([MS-SMB2] section 2.2.13.2). The Buffer field of the SMB2_CREATE_CONTEXT will contain the SVHDX_OPEN_DEVICE_CONTEXT structure that was passed in from the RSVD client ([MS-SMB2] section 2.2.13.2.14).
The file server processes the SMB2 CREATE Request, as described in [MS-SMB2] sections 3.3.5.9 and 3.3.5.9.14. If successful, the file server passes the SVHDX_OPEN_DEVICE_CONTEXT structure that is contained in the SMB2_CREATE_CONTEXT Request to the RSVD server.
The RSVD server processes the open request, as described in [MS-RSVD] section 3.2.5.1. If successful, the RSVD server returns STATUS_SUCCESS to the file server.
The file server constructs an SMB2 CREATE Response, as described in [MS-SMB2] section 3.3.5.9, starting at the “Response Construction” phase.
The file client processes the SMB2 CREATE Response, as described in [MS-SMB2] section 3.2.5.7, and returns STATUS_SUCCESS to the RSVD client.
The RSVD client returns a handle for the opened shared virtual SCSI disk to the calling application.