Problem with Window 7 Pro computer not accepting more than 20 concurrent connections
Hi - We have an access database running on a Windows 7 Pro desktop. When we have more than 20 people/sessions connected to the computer, NO ONE ELSE can connect, I did read something on a registry key that limits the amount of connections, but this computer didn't even have the key. (HKEY_LOCAL_MACHINE\SYSTEM
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the problem is we have about 40 users accessing it. The mdb file is on the win 7 computer, and a front end is on each of their computers
ASKER
There are no registry tweaks to change this?
Not that I know of as they would break the EULA. You need a Operating System designed for connections over that 20 limit - a server based OS.
It would be against EE rules to advise you on how to Break the license conditions of a software product. You have accepted the terms of the license by using it and have to abide by them
If you need more users then as already stated, you need a server OS not a desktop OS
If you need more users then as already stated, you need a server OS not a desktop OS
Here is what I do in similar circumstances:
First, as a tutorial, if you don't already know, you can see the number of connections by going to:
Computer / Manage (from right click menu)
Shared Folders
Sessions
The number of Sessions should be what's limited to 20.
OK.
The challenge is to reduce the number of simultaneous connections.
- Do users have folders on this computer mapped? Unmap them. That will get rid of nearly-permanent connections.
- As an alternate, create shortcuts on the desktop that will open the needed folder. Since most people close unused windows, this could help constrain the number of simultaneous connections.
You can monitor your progress as above.
First, as a tutorial, if you don't already know, you can see the number of connections by going to:
Computer / Manage (from right click menu)
Shared Folders
Sessions
The number of Sessions should be what's limited to 20.
OK.
The challenge is to reduce the number of simultaneous connections.
- Do users have folders on this computer mapped? Unmap them. That will get rid of nearly-permanent connections.
- As an alternate, create shortcuts on the desktop that will open the needed folder. Since most people close unused windows, this could help constrain the number of simultaneous connections.
You can monitor your progress as above.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need to accept the fact your asking something of Windows 7 that it was not designed to do, technically and legally. There is no magic fix.
Qlemo's comment re: Access is something I didn't know.
It *is* clear now that there's a 20 connection limit, yes? That *is* what it's designed to do. That seems water under the bridge then.
If all the users are Access users then it sounds like there's not a technical solution.
And, I've not seen a suggestion for an "illegal" solution = ;-o
There are times when a Server is the right solution. It would be silly to try to modify your usage profile as I suggested if there are lots more than 20-50 "users" with an actual need for >20 connections. My point, which is underscored by Qlemo's observation, is that there are more or less "greedy" approaches where this is concerned. And *some* of those can be ameliorated. Case in point, some people and some groups just *love* to map drives when they don't really need to. But that's a different situation than yours it seems.
It *is* clear now that there's a 20 connection limit, yes? That *is* what it's designed to do. That seems water under the bridge then.
If all the users are Access users then it sounds like there's not a technical solution.
And, I've not seen a suggestion for an "illegal" solution = ;-o
There are times when a Server is the right solution. It would be silly to try to modify your usage profile as I suggested if there are lots more than 20-50 "users" with an actual need for >20 connections. My point, which is underscored by Qlemo's observation, is that there are more or less "greedy" approaches where this is concerned. And *some* of those can be ameliorated. Case in point, some people and some groups just *love* to map drives when they don't really need to. But that's a different situation than yours it seems.
I've requested that this question be deleted for the following reason:
Not enough information to confirm an answer.
Not enough information to confirm an answer.
This is a "You can't do that" type of question, so I suggest to split points:
http:#a40545194 300 pts - "you can't do that"
http:#a40545601 200 pts - confirming above, and showing alternatives (probably out of scope)
http:#a40545194 300 pts - "you can't do that"
http:#a40545601 200 pts - confirming above, and showing alternatives (probably out of scope)
OM Gang