Information About Active Sessions on the Computer That Is Running the Server Service
To receive information about active sessions on the computer that is running the server service, type the following command:
Count the number of open sessions to see if the session limit of 10, or 5 in the case of Windows XP Home Edition, is already reached. Typically there is only one session per remote client.
If there is more than one session from a remote client, view the User name context on the remote client that has set up more than one session:
| • | View all the services that are running, and find out if one is running under the user context of the username shown in the session table. |
| • | Look for scheduled tasks that are running in a logon script and are using a different user account then the one logging in. |
| • | Look for rows where the User name column is empty and examine the idle time. |
A session that has an empty user context is a null session.
Temporary null sessions are usually caused by IPC$ connections as the first step in establishing a connection. They stay active for 30 seconds to 90 seconds.
Note To disconnect client computer sessions, use the following command:
This command disconnects all sessions from that computer and closes all open files. This command may cause data loss if open files that have not been saved are closed.
