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

We have an application that makes request to a UNC path for files and serves them via IIS.

How many concurrent connections can a process on Windows 2008 r2 make to a UNC file share?

Are there any specific limitations on this, or is it purely a based on physical resource constraints (and number of available ports for TCP/IP connections).

share|improve this question
up vote 4 down vote accepted

Assuming your UNC file share is also a Windows server, then the max is really only limited by CAL licenses owned (but not actually set anywhere but on paper).

Since this is asking concurrent connections, you can check it here (on the server with the share):


Look at the share and there is a REG_MULTI_SZ that should say "MaxUses"

the default is some crazy high number like 4294967295 (65536 times 65536 minus 1) based on ports like you say (no it's not a reference to Excel :) )

share|improve this answer
Thanks, this is useful, though I need to check with our ops guys to see if the share is Windows or a Linux share masquerading as a windows share. :-) – Andrew Theken Dec 5 '12 at 21:34

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.