networkingtcpwindows server 2012
I am wrestling with deploying an application on Windows Server 2012. The problem is that after accepting about ~2000 TCP connections it fails to accept more. And I need much more. We have 8 cores, 16 GB RAM, 3GH CPU, pretty strong box. But not capable of holding more than 2000 socket connections..
The questions:
A tcp session is defined by all four parts of the address, and only all four parts in combination need to be unique.
So
client ip : source port -> server ip : destination port
Provided these are different from the next session, the next session is valid, even if it uses the same source port and client ip.
Whether this is possible in reality is dependent on implementation of both the networking stack of the OS and the TCP library being used.
Clearly for incoming connections, the incoming count can be far greater than 65535 - a busy website could easily have far more concurrency than 65000 connections.
After some extra trial-and-error, using the Adapter Settings/Advanced/Advanced Settings dialog was the right approach, and led to the result I needed. All that was missing was a reboot after changing the settings.
For all those with the same problem:
You'll see this dialog:
Use the arrows next to the first list to sort your adapters. The first adapter in the list has the highest priority. These settings do not change the way incoming connections are handled.
There's no need to touch the metric settings of the interfaces. They work in automatic mode perfectly.
You might need to reboot to get the settings applied.
Best Answer
I hate replying to questions with links however I read through this very recently and found it hugely interesting so thought you might appreciate the read:
http://www.serverframework.com/asynchronousevents/2010/12/one-million-tcp-connections.html
Charles