2

**Disclaimer. I'm a developer, largely ignorant on what actually happens with virtual directories and such.

A recent outage was explained away as too many connections to a Windows file share, and it didn't seem like a good enough answer to me, so I wanted to ask the experts here.

Say I have 30 machines running IIS, 8 & 8.5 mixed. All of them are running five sites. Each site has three virtual directories, \vdir1, \vdir2 and \vdir3 that point to \\fileserver\data\dir1, \\fileserver\data\dir2 and \\fileserver\data\dir3 respectively. Physical Path Credentials are all set to the same user and Physical Path Credentials Logon is set to ClearText.

  1. If my application doesn't make use of these virtual directories, meaning we never call Server.MapPath() to them anymore because we're using Azure BLOB storage now, and there is no traffic to the virtual dirs externally, does IIS itself maintain any active connections to the shared folders? If so how many?
  2. How many connections can a Windows file share handle at once? Even if IIS does have one connection per virtual directory, it doesn't seem likely to me that 30 x 5 x 3 = 450 connections would overwhelm a file share.

Also, is there anywhere you could point me on the web that documents at a lowish level what's going on in IIS with virtual directories or Windows file sharing in general and any other specifics related to number of connections allowed? This isn't super detailed.

4
  • 1
    I'm very dubious of the explanation "too many connections to a Windows file share". Oct 8, 2014 at 19:20
  • I agree, Evan. That's why I'd like to see if I can find a more specific answer here.
    – Dzejms
    Oct 8, 2014 at 19:45
  • Having similar problem. Did you ever get more details?
    – Dave
    Jan 28, 2016 at 14:33
  • Sadly, no more details.
    – Dzejms
    Jan 30, 2016 at 1:35

0

You must log in to answer this question.

Browse other questions tagged .