IIS on Win2K

Off the top of anyone's head, what is the maximum number of concurrent IIS connections to a win2K Pro box, as in, not server?

IIS has the following limitations:

* Limited to 10 connections
* Limited to one Web and one FTP server. In other words, you cannot create additional virtual Web or FTP servers.

In the past I have managed to get both more than 10 connections and more that one website on a Win2k Pro box. I did it by hacking around with the metabase to make it look more like a Win2k Server box.

I did it because while I had the Win2k Server licences I wasn't being allowed to reinstall the OS on the box it was intended for. Office politics...

Last time I tried it though it failed. I think Microsoft must have got wise to it and "fixed" it in a service pack/hotfix.

I can't say I've tried it myself, but there's a script called "mkw3site.vbs" that can be used to create a new virtual web server. It should be located in your /inetpub/AdminScripts directory.

Who knows - it might even work.

Thanks guys... It looks like the geniuses a our contract company put our taxbill payments website on Win2K Pro. People have a month to pay, 60,000 citizens. People are getting server busy messages left and right. Well, at least it wasn't MY fault. Now to migrate it to server...

Wait!

I have run across this before, and it was easily solved by unchecking the "HTTP Keep-Alives Enabled" on the "Web Server" tab of the properties window. ISTR that that box is checked by default as it decreases response time for small numbers of connections.

In my experience, the 10 simultanious connections goes way further than most people expect, as they are each servered in fractions of a second. If you have that checked, this will likely fix your issue so that you don't have to do an OS reinstall. (Unless you really do have a massive, massive amount of people hitting your box.)

Something to try, at least.

John

Aha..... I will certainly give it a shot.... Thank you!

You could also mitgate the problem by moving the IIS site to something other than port 80 and running proxy on port 80 to cache requests to real IIS webserver. I expect you could set Apache up to do this (it might not be easy if you were new to Apache though).

It looks like there is at least one "free" Windows http proxy that you could use instead of Apache:

http://www.delegate.org/delegate/

Thanks for all the suggestions guys. It appears that this has fixed my particular problem. Without migration.