A History of Changes to SESSTIMEOUT from LM 2.0 to 2.2 (97876)


The information in this article applies to:

  • Microsoft LAN Manager 2.0
  • Microsoft LAN Manager 2.1
  • Microsoft LAN Manager 2.1a
  • Microsoft LAN Manager 2.2
This article was previously published under Q97876

SUMMARY

Some problems that occur after upgrading from LAN Manager 2.1 to LAN Manager 2.1a (for instance, SQL application processes dying) can be solved by increasing sesstimeout on the workstation. The sesstimeout settings have changed from LAN Manager 2.0 to 2.2. This article lists the changes.

MORE INFORMATION

The sesstimeout parameter has the following effect on the LAN Manager versions listed:

LAN Manager 2.0

OS/2 workstations:

  • Set the value of the CALL/LISTEN NCB Send TimeOut (STO).
  • Set the redirector multiplex table "wait for SMB response" time-out.
MS-DOS workstations:

  • No effect (STO was set to 0 [no time-out], non-configurable. Redirector multiplex table "wait for SMB response" unlimited, non-configurable.

LAN Manager 2.1

OS/2 workstations:

  • Same as LAN Manager 2.0.
MS-DOS workstations:

  • Set the value of the CALL/LISTEN NCB Send TimeOut (STO) "wait for SMB response" unlimited, (non-configurable).

LAN Manager 2.1a

OS/2 workstations:

  • Same as LAN Manager 2.1.
MS-DOS workstations:

  • Set the value of the CALL/LISTEN NCB Send TimeOut (STO).
  • Set the redirector multiplex table "wait for SMB response" time-out.

LAN Manager 2.2

Same as LAN Manager 2.1a.
Modification Type:MajorLast Reviewed:9/30/2003
Keywords:kbnetwork KB97876
©2003 Microsoft Corporation. All rights reserved.