Inactive Sessions Don't Occupy Any Memory on the Server
ID: Q59940
|
The information in this article applies to:
-
Microsoft LAN Manager, versions 2.0, 2.1, 2.1a, 2.2
SUMMARY
An auto-disconnected session uses no memory on the server.
MORE INFORMATION
Information regarding disconnected sessions isn't kept on the server;
it is kept on the workstation. This can be proven by tracing the flow
of server message blocks (SMBs) that the workstation reconnects. A
simple test is as follows:
- Connect to a disk share on a server.
- Change several directory levels down, so that you can see exactly
how the path information related to the session is passed to the
server.
- Let the server auto-disconnect the session.
- Start a trace utility on the server, to track the flow of SMBs.
- Request a directory of the subdirectory on the server.
As the session is reconnected, you will see the server receive a
SESSETUPX SMB (establish the session), a TCONNX SMB (make the
connection), and several CHKPATH SMBs (change directory). If the
session information were actually maintained on the server, it would
not be necessary for the client to send the CHKPATH SMBs back to the
server; this information would be held internally on the server.
Additional query words:
2.00 2.10 2.10a 2.20 sessions memory
Keywords :
Version : :2.0,2.1,2.1a,2.2
Platform :
Issue type :
|