With increasingly more complex web pages, I found myself running into a limit in the number of IIS connections allowed for the constrained web server on Windows XP. By default Microsoft has limited the connections to 10. Even when I changed the time to release connections down to 5 minutes, I was still running into problems. With a little Google searching, I found a solution (
here,
here, and
here).
Apparently the hard-coded limitation Microsoft has set is 40 connections. The trick is determining how to raise the level from 10 to 40. There's a script, adsutil, that can do this for you.
- Go to the Command Prompt and navigate to C:\Inetpub\AdminScripts.
- Enter "adsutil set w3svc/MaxConnections 40".
- If you get an error message, "This script does not work with WScript," click OK and click Yes to make Cscript as the default script for VBscript.
- When this completes, go back to the Command Prompt and press F3 (repeats last command) and Enter.
- If you were successful, the command should return "MaxConnections: 40".
- Stop and start IIS. You can do this as the same Command Prompt by entering "iisreset".
I suspect there may be a Registery equivalent setting, but this did the trick for me. If you don't need IIS to begin with, perhaps a better solution would be to load Apache. Microsoft Visual Web Developer may also be a solution, though I haven't spent much time with it myself.