Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Please tell me:

Are there some limitations on connection/socket/http in Windows Server 2008 R2 editions family? For example i am pretty sure that some of servers will have 100+ connections (by sockets and http requests) at the same time (simultaneously) from other servers in network. In this comparison i found some limitations on "Network Access Connections (IAS)" and "Network Access Connections (RRAS)" but i do not how these limitations will influence on socket/http connections. If these limitations will block for example more then 50+ local network connections from other servers, so i must choose Enterprise edition. Am i right?

Thank you for any advice!!!

share|improve this question
up vote 3 down vote accepted

None of those figures you link to are relevant to your use case and your use case won't even slightly bother the maximum connections per server, we have some with several thousand constant connections with no problem whatsoever.

share|improve this answer
thank you for answer! Could you tell me please what editions do you use for so many connections? is it standard edition? – Edward83 Nov 21 '10 at 11:34
We happen to use EE as we use clustering but most services have limits in the multiple thousand even with the cheapest versions. – Chopper3 Nov 21 '10 at 12:05

These figures are not for "connections" they are for the number of windows users making connections.

Windows 2003 had a limitation of 64,000 connections per IP Address.

This has been fixed in Windows 2008, see:

share|improve this answer
thank you! Cool! – Edward83 Nov 21 '10 at 12:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.