2.2.24.2 Lease Break Acknowledgment

  • Article

The SMB2 Lease Break Acknowledgment packet is sent by the client in response to an SMB2 Lease Break Notification packet sent by the server. This acknowledgment is not valid for the SMB 2.0.2 dialect. The server responds to a lease break acknowledgment with an SMB2 Lease Break Response. This message is composed of an SMB2 header, as specified in section 2.2.1, followed by this acknowledgement structure.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

StructureSize

Reserved

Flags

LeaseKey

...

...

...

LeaseState

LeaseDuration

...

StructureSize (2 bytes): The client MUST set this to 36, indicating the size of the request structure, not including the header.

Reserved (2 bytes): This field MUST NOT be used and MUST be reserved. The client MUST set this to 0, and the server MUST ignore it on receipt.

Flags (4 bytes): This field MUST NOT be used and MUST be reserved. The client MUST set this to 0, and the server MUST ignore it on receipt.

LeaseKey (16 bytes): The client-generated key that identifies the owner of the lease.

LeaseState (4 bytes): The lease state in the Lease Break Acknowledgment message MUST be a subset of the lease state granted by the server via the preceding Lease Break Notification message.<63> This field MUST be constructed using the following values:

Value

Meaning

SMB2_LEASE_NONE

0x00

No lease is granted.

SMB2_LEASE_READ_CACHING

0x01

A read caching lease is accepted.

SMB2_LEASE_HANDLE_CACHING

0x02

A handle caching lease is accepted.

SMB2_LEASE_WRITE_CACHING

0x04

A write caching lease is accepted.

LeaseDuration (8 bytes):  This field MUST NOT be used and MUST be reserved. The client MUST set this to 0, and the server MUST ignore it on receipt.