Windows xp professional iis limitations

So since it's simple, write one. A caching proxy might get you part way, and writing a proxy well, it's not really a proxy You may need to do some client-side work to enable it, but as long as your time has no value you'll save the expense of a server license.

How about Apache? It doesn't use the OS in the same integrated manner, and has no trouble with more than ten connections. You've already investigated the keep-alive issues, which is the only simple alternative. The problem isn't your concept, the problem is you're unwilling to work within the limitations of a given product on a given operating system. I'd like a car that runs on tap water, gets 1, miles to the gallon and does in 1. You know, if you converted to Linux, Apache and PHP, all things would be free and there would be world peace within the decade You still do not understand To be specific, when IIS starts up, it determines if it is running on a desktop or server OS, and sets functional limits accordingly.

But let me clarify even more: I am referring to anonymous connections, NOT Windows authenticated connections. Even Apache will have a 10 user limit if using Windows authentication since that is controlled by the OS. However, non-authenticated connections are simply normal TCP connections and hence there is no limit.

Let me also be clear that I would never tell anyone that it is proper to use a desktop Windows OS as a web server for other than a test or personal site. I agree that the original poster should simply invest in a copy of or Server. Jerry "Phil Frisbie, Jr. Yes I do. I am sorry if I was not clear on that.

The problem is not this limitation the problem is the way WinInet implements it. The only acceptable solution we found so far was increasing this limit up to 4. I really not sure where from comes you confidence that it is OS limitation. May be you can clarify yourself on that.

At least that contradicts to what I know so far. Thanks everyone for responses. The discussion went much further then I expected :- so let me put down what I've got so far. The kind of proxy I was asking about does not exist. Why I am not simply using server OS? Well I am investigating possibility of using OS that costs couple hundred dollars rather than one that costs over 1 thousand.

What I need is just a intranet website that could handle 3 to 5 clients reliably does not sound like an enterprise level does it? Why I am not migrating on Apache? Because of historical reasons and there is nothing I can do about it right now. What if I got to write this damn proxy? Well if I would not find another solution except using Server I may end up doing that.

From technical stand point of view I do not see why this proxy would not work. All though I do realize that time to finish it may be comparable to "migrate to apache" project. As well the functionality may be limited like no SSL for the first version, and no OS authentication.

From licensing stand point of view I am not violating anything. Sorry Phil, but you're wrong. I've been called a pompous ass and a know-it-all, but in this particular case I'm on solid ground.

At least according to the folks at Microsoft who write the code Microsoft workstation operating systems have a 10 connection limit for the redirector. Even if you don't use IIS, you can't have more than ten connections technically twelve if you have printer connections from a client. IIS uses the redirector for much of its connectivity, and thus inherits that limit.

This has been true for every version of IIS and hasn't changed. Whether it's an OS or an IIS limitiation isn't really the core of your problem though, the problem is that due to this limit IIS will not accept more than 10 concurrent connections. Disabling keep-alives doesn't change that, though IIS will stop holding connections open and you may get by with it.

Server OS's don't have the limit, and IIS which is identical code in either workstation or server setting Okay, since we've beaten this to death, let me offer you one more undocumented option to try.

If you'd actually done a bit of Googling you'd have found this SetInfo ' Save info msgbox site1. MaxConnections else msgbox "Servers has already 40 connections" end if Save the above script, run it from a command prompt or Windows Explorer or whatever.

This resets the MaxConnections for the default web site to It appears to expand the connection limitation for IIS, allowing four connections per redirector connection, for a total of Some users claim it works, some get a partial increase, some don't get any increase and I believe it has to do with what constitutes a connection.

You can't get above 40, and in my own personal testing I get 10 clients max, even if they only make 1 connection each. Note that this is undocumented, unsupported and if your system crashes, your web site stops working, your wife leaves you or frogs rain from the sky, it's your own danged fault for trying it.

In otherwords, you're entirely on your own for this. Can you provide any documentary evidence to back this claim up Phil? I've never heard of any such check being carried out by IIS. Is the result recorded in the Metabase? If not, then where? Please note: Do not post advertisements, offensive material, profanity, or personal attacks.

Please remember to be considerate of other members. All submitted content is subject to our Terms Of Use. General discussion. The problem is when I try to add a second web site the option is unavailable, there isn?

I have been perusing through Microsoft references but I found nothing? Thanks for your time, Tyler. Share Flag. All Comments. Collapse -. This can be bumped up to 40 but not higher 40 is the hardcoded limit.

To do this, find the adsutil. You can also try to prevent individuals from hogging a bunch of connections and thereby blocking out other users. IE will normally use 2 connections to a web site. Lowering the timeout default is 5 min will cause idle connections to get dropped quicker. Disabling keep alives will cause connections to disconnect immediately after the request is handled instead of waiting for new requests on the same connection.

Or Just use apache, or just about anything else How passe Send a message to MS. Tell them to stop harrassing their customers with crap like this.