Browse Prior Art Database

A method for optimal SMB connection re-use including the cases of protocol version fallback

IP.com Disclosure Number: IPCOM000236374D
Publication Date: 2014-Apr-23
Document File: 8 page(s) / 83K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method for optimal SMB connection re-use including the cases of protocol version fallback

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 29% of the total text.

Page 01 of 8

A method for optimal SMB connection re -use including the cases of protocol version fallback

Problem Statement:

    An SMB client system provides access to remote files and allows various operations on them to the requesting applications by interacting with SMB server as per the protocol specification (using required protocol version negotiated).

    Access to remote share is made available to requesting application by the SMB client system after performing following three sequential SMB operations in given order i. SMB Protocol Negotiation: This takes care of negotiating protocol version and capabilities between client and server.

ii. SMB Session Setup: This is responsible for user authentication between client / server and establishing associated Session identified by a unique session identifier.

iii. SMB Tree Connect: This is responsible to render the remote share on the server accessible to the client over established SMB session.

    Given the provision, an application could input highest version of the protocol desired to be used by the SMB client system for SMB connection. Best attempt is made to use the requested highest version of SMB protocol during protocol negotiation. However if the application seeks usage of higher version protocol to the SMB client during fresh connection to remote SMB share and the server supports only lower versions of the protocol, the connection shall fall back to use prior version of the protocol during protocol negotiation.

    The problem is to establish minimum possible SMB connections with the SMB server by re-using SMB connections for new mount requests whenever there is a similar SMB session connection already existing, including the scenarios of protocol fall back based on user input mentioned above. This in turn also means, the SMB connection table should contain minimum

possible entries, with one entry per unique SMB connection.

Use Case:

platform which accepts the user input the highest version of SMB protocol to be used.

    It is especially more useful in cases where there multiple different applications requesting an SMB client to establish SMB session with same SMB server.

References: SMB protocol specifications

    A direct solution to the problem does not seem to be available as the case of accepting input desired protocol version to be used by the client is not addressed by any SMB client implementations. The protocol specifications also do not discuss managing the data structures, connection table, session table in case of protocol version fall back.

However there seems to be an implied solution that is to have separate

1

This problem is applicable to SMB client file system implementation on any Unix


Page 02 of 8

ConnectionTables maintained by the SMB client for different SMB protocol versions that it supports which would typically work as follows, with two cases.

Case 1: Search in the ConnectionTable is performed only at the beginning, which is before protocol negotiation.

SMB client maintains one...