Home All Groups Group Topic Archive Search About

10th user unable to connect to XP Pro machine

Author
16 Jun 2005 7:32 PM
kazer98
We are having the following problem:

The 10th user is unable to log into an XP Pro machine running as a server.
The user list shows 9 users connected and the 10th user receives this message:

"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"

When all ten systems are connected, both netstat and net session show only 9
users connected, with the 10th unable to connect. Netstat shows the 9 IP
addresses of the connected users. Net session does not show any local user
connected (logged in as Administrator). This system is not used by anyone, so
there aren't mappings to any shares on it.

Also tried logging out of the system and leaving it at the login screen -
this made no difference; still only 9 users allowed.

Author
16 Jun 2005 9:58 PM
JS
kazer98 wrote:
Show quoteHide quote
> We are having the following problem:
>
> The 10th user is unable to log into an XP Pro machine running as a server.
> The user list shows 9 users connected and the 10th user receives this message:
>
> "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"
>
> When all ten systems are connected, both netstat and net session show only 9
> users connected, with the 10th unable to connect. Netstat shows the 9 IP
> addresses of the connected users. Net session does not show any local user
> connected (logged in as Administrator). This system is not used by anyone, so
> there aren't mappings to any shares on it.
>
> Also tried logging out of the system and leaving it at the login screen -
> this made no difference; still only 9 users allowed.

XP Pro is hard-coded to enable only 10 concurrent connections, just like
Windows 2000 and NT WS before it. See:

http://support.microsoft.com/kb/122920/
Author
16 Jun 2005 11:51 PM
Scott M.
And how does this reply help the OP since his question is asking why he
can't get the 10th user connected.  He already knows about the 10 user
limit.  He's having a problem at 9.


Show quoteHide quote
"JS" <u***@example.net> wrote in message
news:3heb07FglecoU1@individual.net...
> kazer98 wrote:
>> We are having the following problem:
>>
>> The 10th user is unable to log into an XP Pro machine running as a
>> server. The user list shows 9 users connected and the 10th user receives
>> this message:
>>
>> "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"
>>
>> When all ten systems are connected, both netstat and net session show
>> only 9 users connected, with the 10th unable to connect. Netstat shows
>> the 9 IP addresses of the connected users. Net session does not show any
>> local user connected (logged in as Administrator). This system is not
>> used by anyone, so there aren't mappings to any shares on it.
>>
>> Also tried logging out of the system and leaving it at the login screen -
>> this made no difference; still only 9 users allowed.
>
> XP Pro is hard-coded to enable only 10 concurrent connections, just like
> Windows 2000 and NT WS before it. See:
>
> http://support.microsoft.com/kb/122920/
Author
17 Jun 2005 5:43 AM
Malke
Scott M. wrote:
Show quoteHide quote
> And how does this reply help the OP since his question is asking why he
> can't get the 10th user connected.  He already knows about the 10 user
> limit.  He's having a problem at 9.
>
>
> "JS" <u***@example.net> wrote in message
> news:3heb07FglecoU1@individual.net...
>
>>kazer98 wrote:
>>
>>>We are having the following problem:
>>>
>>>The 10th user is unable to log into an XP Pro machine running as a
>>>server. The user list shows 9 users connected and the 10th user receives
>>>this message:
>>>
>>>"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"


(some snippage)

>>XP Pro is hard-coded to enable only 10 concurrent connections, just like
>>Windows 2000 and NT WS before it. See:
>>
>>http://support.microsoft.com/kb/122920/
>

The OP is having the trouble at 9 because the concurrent limit does not
apply to *computers* but to *connections*. One computer can make more
than one connection to a server. You will usually start to run into the
concurrent connections problem with 8 or 9 computers; sometimes even
with 7 depending on what the server is being used for. So it is now time
for the OP to get a real server operating system. JS gave a good link
and here is more info:

Concurrent connection limits:

10 for XP Pro/Tablet/MCE
5 for XP Home
49 for SBS 2000
74 for SBS 2003
Unlimited for full Server O/Ses

Hope that clarified things,

Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"
Author
17 Jun 2005 10:54 PM
Scott M.
Yes, thank you.  I was really trying to illustrate that the last reply was
useless.


Show quoteHide quote
"Malke" <notrealem***@invalid.com> wrote in message
news:%236WQs3tcFHA.3048@TK2MSFTNGP12.phx.gbl...
> Scott M. wrote:
>> And how does this reply help the OP since his question is asking why he
>> can't get the 10th user connected.  He already knows about the 10 user
>> limit.  He's having a problem at 9.
>>
>>
>> "JS" <u***@example.net> wrote in message
>> news:3heb07FglecoU1@individual.net...
>>
>>>kazer98 wrote:
>>>
>>>>We are having the following problem:
>>>>
>>>>The 10th user is unable to log into an XP Pro machine running as a
>>>>server. The user list shows 9 users connected and the 10th user receives
>>>>this message:
>>>>
>>>>"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"
>
>
> (some snippage)
>
>>>XP Pro is hard-coded to enable only 10 concurrent connections, just like
>>>Windows 2000 and NT WS before it. See:
>>>
>>>http://support.microsoft.com/kb/122920/
>>
>
> The OP is having the trouble at 9 because the concurrent limit does not
> apply to *computers* but to *connections*. One computer can make more than
> one connection to a server. You will usually start to run into the
> concurrent connections problem with 8 or 9 computers; sometimes even with
> 7 depending on what the server is being used for. So it is now time for
> the OP to get a real server operating system. JS gave a good link and here
> is more info:
>
> Concurrent connection limits:
>
> 10 for XP Pro/Tablet/MCE
> 5 for XP Home
> 49 for SBS 2000
> 74 for SBS 2003
> Unlimited for full Server O/Ses
>
> Hope that clarified things,
>
> Malke
> --
> MS-MVP Windows User/Shell
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic"
Author
26 Jun 2005 3:44 PM
Mark Fineman
On Thu, 16 Jun 2005 22:58:29 +0100, JS <u***@example.net> wrote:

Show quoteHide quote
> kazer98 wrote:
> > We are having the following problem:
> >
> > The 10th user is unable to log into an XP Pro machine running as a server.
> > The user list shows 9 users connected and the 10th user receives this message:
> >
> > "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"
> >
> > When all ten systems are connected, both netstat and net session show only 9
> > users connected, with the 10th unable to connect. Netstat shows the 9 IP
> > addresses of the connected users. Net session does not show any local user
> > connected (logged in as Administrator). This system is not used by anyone, so
> > there aren't mappings to any shares on it.
> >
> > Also tried logging out of the system and leaving it at the login screen -
> > this made no difference; still only 9 users allowed.
>
> XP Pro is hard-coded to enable only 10 concurrent connections, just like
> Windows 2000 and NT WS before it. See:
>
> http://support.microsoft.com/kb/122920/
Also, in Windows 2000, at least, if a connection isn't closed to the
satisfaction of the operating system the connection still counts even
though it can't be used.

For example, a telnet connection that is was broken due to network
problems and which cannot be reconnected to counts as a connection
until the system reboots. (I don't think killing the process on the
server reduces the count - at least it didn't for me when I tried on
Windows 2000 Professional some years ago.)

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Author
16 Jun 2005 11:30 PM
Dave
If I remember correctly one of the 10 users is the system.

Show quoteHide quote
"kazer98" wrote:

> We are having the following problem:
>
> The 10th user is unable to log into an XP Pro machine running as a server.
> The user list shows 9 users connected and the 10th user receives this message:
>
> "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"
>
> When all ten systems are connected, both netstat and net session show only 9
> users connected, with the 10th unable to connect. Netstat shows the 9 IP
> addresses of the connected users. Net session does not show any local user
> connected (logged in as Administrator). This system is not used by anyone, so
> there aren't mappings to any shares on it.
>
> Also tried logging out of the system and leaving it at the login screen -
> this made no difference; still only 9 users allowed.