I am creating a Windows Service in .NET to which N number of client can connect. The service starts a TCP listener and accepts the client connections. The problem I am facing is that I can only open 10 connections to this service. The listener::AcceptTcpClient() method accepts only 10 connection and throws an exception for 11th one. The client application uses the System.Net.Sockets.TcpClient class and the service is using System.Net.Sockets.TcpListener class.
This is the exception that I am getting when I try to make a number of connections in a for loop to this service (after the 10th connection is made):
"Unable to read data from Transport connection: An exsting connection was forcibly closed by remote host"
This sounds like you're running into the well-known 10-connection limit of half-open TCP connections on Windows XP. This limit is hard-coded as of XP SP 2, and there is no way to override it short of patching your system, which may technically violate your end-user license agreement (IANAL). XP is, alas, not intended to be a server system.
For Windows XP Professional, the maximum number of other computers that are permitted to simultaneously connect over the network is ten. This limit includes all transports and resource sharing protocols combined. For Windows XP Home Edition, the maximum number of other computers that are permitted to simultaneously connect over the network is five. This limit is the number of simultaneous sessions from other computers the system is permitted to host. This limit does not apply to the use of administrative tools that attach from a remote computer.
I don't think the answer that was given before is valid. I did some research and there doesn't appear to be a reason that TcpClient has any strict limit imposed. The other answer suggested a limit of 10 active TCP connections in Windows XP for a server service, but this is only true for specific application protocols (such as sharing, mail) provided by Microsoft.
I did find though that Microsoft added some restrictions in XP SP2 and continued through Vista SP1 to limit half-open TCP connections to 10. They also limited the number of new connections to 10 within a single second. These were both attempts to reduce the impact of virus software. Apparently these have not been very successful so Microsoft has finally decided to remove these in Vista SP2 and later.
This may have been the OP's actual issue - perhaps you are trying to create those connections too quickly in the client?
As I mentioned in my comments on the previously accepted answer, I personally write client/server software and have not had problems with a limit of 10. When I do tests, using Windows XP in the past and now with Windows 7 (the application limit is now at 20 connections), I am able to easily exceed this limit. I just retested and was able to create >140 active/established connections between one host (Windows 7 Home Premium) and another host (Windows 7 Enterprise); both client operating systems. This is using Java but there really should be no difference with .NET (which I've also tested in the past).
来源：https://stackoverflow.com/questions/657874/max-tcp-connections-to-a-machine