22.214.171.124 Request Expiration Timer Event
When the Request Expiration Timer (section 126.96.36.199) expires, the client MUST walk the outstanding commands in Client.Connection.PIDMIDList for any pending commands that have exceeded Client.SessionTimeoutValue. If a command has exceeded Client.SessionTimeoutValue,<210> the client SHOULD<211> close the connection to the server, and all resources associated with the connection MUST be freed, as specified in section 188.8.131.52.
The NT_TRANSACT_NOTIFY_CHANGE (section 184.108.40.206) subcommand MUST be exempt.
The following commands are exempt from the Request Expiration Timer:
The NT_TRANSACT_NOTIFY_CHANGE (section 220.127.116.11) subcommand
Read and write commands issued on an Open to a named pipe via the following commands:
TRANS_READ_NMPIPE (section 18.104.22.168) subcommand
TRANS_WRITE_NMPIPE (section 22.214.171.124) subcommand
TRANS_RAW_READ_NMPIPE (section 126.96.36.199) subcommand
TRANS_TRANSACT_NMPIPE (section 188.8.131.52) subcommand
TRANS_RAW_WRITE_NMPIPE (section 184.108.40.206) subcommand
TRANS_CALL_NMPIPE (section 220.127.116.11) subcommand
TRANS_WAIT_NMPIPE (section 18.104.22.168) subcommand
SMB_COM_LOCKING_ANDX Request (section 22.214.171.124.1) with the Timeout field set to a nonzero value