Server Availability Affected By Maximum Simultaneous Connections

With Windows XP, you are subject to a limitation on the number of simultaneous connections that a server can provide. If you have more than 5 connections to a server running XP Home, or 10 connections to a server running XP Pro, you may observe various symptoms:

  • The error “No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.”
  • As connections time out from disuse, they will become disconnected. Attempts to reconnect will either result in the above error, or will force the disconnection of another, less active computer.
  • The error “Server is not accessible…”.

The good news is, you can’t use up all of your connections on any server from any one client with multiple sessions on that server. Generally, one account on one client with multiple sessions = 1 connection. A session started by a user, and another session started by the system account, from one client, will count as 2 connections, though.

If you ever need to know how many connections are active on your server, look in Control Panel – Adminstrative Tools – Computer Management. Under System Tools – Shared Folders, you will find the current Sessions inventory.

As a client becomes inactive on a server, its connection will timeout, and become available to another client. The default period for inactivity to trigger a disconnection is 15 minutes.

If you need many more client connections than the server can provide, you can lower the timeout period, by tuning the server. Inbound connections limit in Windows XP tells us how to change the timeout period to 10 minutes, for instance. Into a command window, enter:

net config server /autodisconnect:10

But beware. Changing the timeout period, by using “net config”, may affect server functionality, permanently.

The Windows Server service is self-tuning; normally the server configuration parameters are autoconfigured (calculated and set) each time you start Windows XP. If you run net config server in conjunction with the /autodisconnect, /servcomment or /hidden options, the current values for the automatically tuned parameters are displayed and written to the registry. After these parameters are written to the registry, you cannot tune the Server service by using the Networks tool in Control Panel. If you change any of the Server service settings, Windows XP can no longer automatically tune the Server service for your new configuration. To avoid losing the Server service’s automatic self-tuning capability, make the change through Registry Editor instead from a command line or Control Panel Network.

You may want to use the Local Security Policy Editor (for XP Pro only) instead. Under Security Options, you should find “Microsoft network server: Amount of idle time required before suspending session”. Or, you may prefer to edit the registry directly, and change Registry Value [HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\autodisconnect]. Change either the LSP entry (for XP Pro), or the registry value, to an appropriate setting.

You may find additional information of interest in Server Service Configuration and Tuning, or Troubleshooting Server Message Block inbound connection limit…

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: