Is there a fix for Windows XP TCP/IP limit of 10 maximum connections: i.e. can there be more than 10 clients?
Question: I am using Windows XP professional and I have a network of 12 computers. I'm using one computer essentially as the "server" for a MSSQL database with other computers on the network accessing the data from it. Any computer past the initial 10 computers that tries to access a program (that uses the MSSQL database in question) gets rejected, bounced, with the error message: "\\server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. No more connections can be made to this remote computer at this time because there are already as many connections that the computer can accept." I have already looked at this supposed patch: http://www.lvllord.de/ (Update of TCPIP.SYS), but I can't get it to work, i.e. raise the number of computer connections allowable under Windows XP professional. Some chat sites seem to imply that this is a feasible item, please tell me if so. Thanks
Best Answers: Is there a fix for Windows XP TCP/IP limit of 10 maximum connections: i.e. can there be more than 10 clients?
The only fix is to install a server setup as a domain controller. This is by design by Microsoft. This is because sharing resources can get too complicated with more than 10 computers. And if you want all of the resources to be on 1 PC with all of the other computers accessing these resources, Microsoft wants it to be a server. You can get an entry level server with Windows 2003 server for about $2000. This would fix your problem.
Hello, Here's a table that shows memory limits for Windows 7: http://msdn.microsoft.com/en-us/library/... I recommend that you upgrade to 4GB. I hope this helps. Jason, Windows Outreach Team
Windows XP Professional allows a maximum of 10 other computers to connect to its shared resources simultaneously. Computers that aren't actively connected to a computer's shared resources don't count against the limit. When a computer disconnects from a shared resource, it no longer counts against the limit. For details, see the article Inbound Connections Limit in Windows XP in the Microsoft Knowledge Base. http://support.microsoft.com/?scid=kb;en... Have you thought of upgrading to Server 2003? There are NO limits to it.
Here is the Official Ubuntu Samba Documentation https://help.ubuntu.com/community/Settin... LUg.
MSSQL comes as a fixed licence install, you need to buy a licence pack to increase the number of client connections.
First, motherboards have their own limits on how much RAM they can support, both physically and logically. Physically, there are only going to be so many slots available for RAM. As for the "logical" limits, don't fully understand why this is still the case for x86-64 (the memory controller having long since been migrated into the CPU itself), but there it is. Presumably corners are being cut on address lines to save a few bucks in design and manufacturing. Second, an operating system may have internal limitations as to how much RAM it can efficiently support. In part, this is actually to prevent needing overly large data structures to keep track of usage for memory that isn't really there. Last I checked, Linux allows 128TB of virtual address space per process on x86-64, and can theoretically support 64TB of physical RAM. Third, some operating systems (e.g. Windows) will artificially limit how much RAM can be used as a tactic to make users upgrade to more expensive versions if they want more RAM (Windows 7 Starter is limited to 2GB, Home Basic to 8, Home Premium to 16, and Professional and above are 192GB, and Windows Server releases have far higher limits).
If you have your own answer to the question Is there a fix for Windows XP TCP/IP limit of 10 maximum connections: i.e. can there be more than 10 clients?, then you can write your own version, using the form below for an extended answer.