9 or 10 user connection limit?

  • Thread starter Thread starter Jack \(MVP-Networking\).
  • Start date Start date
J

Jack \(MVP-Networking\).

Hi
10 Concurrent Connections.
Connection are not just users. When a WinXP computer prints to a network
printer it is a Connection that counts.
Jack (MVP-Networking).
 
Does XP have a 9 or a 10 user connection limit for file sharing stuff?

I've only seen references to there being a 10 user limit, but I've always
seen XP reject the 10th connection thereby limiting to only 9 users.

I'm verifying the connected sessions by opening Computer Manager and under
"Shared Folders / Sessions"...it only shows nine user sessions (refusing the
10th).

Any ideas?

- anthonyx26
 
Does XP have a 9 or a 10 user connection limit for file sharing stuff?

I've only seen references to there being a 10 user limit, but I've always
seen XP reject the 10th connection thereby limiting to only 9 users.

I'm verifying the connected sessions by opening Computer Manager and under
"Shared Folders / Sessions"...it only shows nine user sessions (refusing the
10th).

Any ideas?

- anthonyx26
Click to expand...

Anthony,

Windows XP Home is 5 connections, and Pro is 10. Connections won't always equal
number of client computers!
<http://networking.nitecruzr.net/2005/07/server-availability-affected-by.html>
http://networking.nitecruzr.net/2005/07/server-availability-affected-by.html
 
Yes, I've seen this issue (of multiple connection-licences being taken-up by
one computer) many times when mappings are being created manually in
Explorer, or from 'Network Places.'

The solution is to create all connections from a batch file, with NET USE
commands. (Or use system-calls from within a program) I think the reason this
avoids the problem is that it ensures the same credentials are used each
time.
 
I didn't think Windows would permit multiple connections with different
credentials from the same computer? At least, I've seen that when
attempting to do so when using "net use" combined with /user:xxx. It throws
back an error claiming it can't connect using multiple different
credentials.

So how is one supposed to accurately monitor the number of connected
users/sessions on the "server" (XP pro in this case) if Microsoft's own
"computer manager" doesn't show an accurate count? While i haven't verified
it, I suspect "net session" would display the same info as "computer
manager".

How does Windows determine when to reject another connected network
connection?

- anthonyx26
 
Back
Top