IIS: how to work around limitation of 10 users on XP?
Vladimir Petter
May be somebody knows if there is a product that may be addressing following
issue:
- On Windows 2000 Professional/XP Professional IIS (version 6.0) is
limited by 10 simultaneous TCP connections.
If 11'th connection comes it going to get HTTP error.
- IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS
(and keep-alive is on) then IE will keep this connection
up to ~30 sec (even if does not have any requests to send).
- Each IE client makes up to 2 connections to the IIS and keeps them in
cash.
So 10 simultaneous IE clients will eat up to 10 connections and 11'th
user may get an error. This becomes a limitation for my WEB application.
What I am looking for is a Proxy that would not have limitation on number of
incoming TCP connections (IE to Proxy), but would be aware of IIS limitation
(10 connections on Professional platform) and put client's request on hold
until IIS connection would become available.
I've already considered possibility of turning off keep-alive on the server
side and now interested only in discussion of the option described above
(Proxy).
Regards,
Vladimir.
-=bina
few sites setup using same time zone setting - the addition of another
website requires a separate time zone -- is there a registry fix or anything
to handle a unique time zone for a particular website??
be helpful in handling recon files, etc...
-=bina
Cari MS-MVP
and not a server operating system. For unlimited connections, use either
one of the (now discotninued) Windows 2000 Server family or the new Windows
2003 Server family.
"Vladimir Petter" <vla...@hotmail.com> wrote in message
news:uTbTPg0...@TK2MSFTNGP09.phx.gbl...
Vladimir Petter
Thanks for your answer.
I know that. I am looking for possibility to "work-around" this limitation
without making customer upgrade to Server.
Any suggestions?
Vladimir.
"Cari MS-MVP" <Newsg...@coribright.comn> wrote in message
news:uEA6lw0v...@TK2MSFTNGP10.phx.gbl...
DUH
----- Vladimir Petter wrote: -----
Vladimir Petter
answers?
Once again:
- I know that it is impossible to have more than 10 connections to IIS
on Professional.
- I am looking for a Proxy that can accept unlimited number of IE
connections and serialize them
to use only 10 IIS connections (client's request will be in a queue until
connection to IIS would not succeed).
If you do not have answer please do not waste bandwidth.
Vladimir.
"DUH" <anon...@discussions.microsoft.com> wrote in message
news:065925D4-7EF8-4189...@microsoft.com...
Phil Frisbie, Jr.
> Cari,
>
> Thanks for your answer.
> I know that. I am looking for possibility to "work-around" this limitation
> without making customer upgrade to Server.
> Any suggestions?
Use Apache. The 10 connection limit is coded into IIS, not XP. However, there
are other limitations (such as the accept connection backlog) you will run into
if the site becomes popular that can only be fixed by upgrading to a server
version of Windows or another OS like Linux.
> Vladimir.
--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com
Paul Lynch
<vla...@hotmail.com> wrote:
>Cari,
>
>Thanks for your answer.
>I know that. I am looking for possibility to "work-around" this limitation
>without making customer upgrade to Server.
>Any suggestions?
>
>Vladimir.
Vladimir,
The best you can hope for is to do this :
"If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on
Microsoft Windows XP Professional, disable HTTP keep-alives in the
properties of the Web site. When you do this, a limit of 10 concurrent
connections still exists, but IIS does not maintain connections for
inactive users."
but you cannot get away from the 10 concurrent connection limit - its
hard-coded in the 'desktop' versions of Windows 2000 and XP
Error Message: HTTP 403.9 - Access Forbidden: Too Many Users Are
Connected
http://support.microsoft.com/?id=262635
Regards,
Paul Lynch
MCSE
Vladimir Petter
Thanks for answer.
The specific of my application is that it is not actually a public WEB site.
It is an internal company's site that may have about 10-15 clients. Because
of WinINet limitations (we are using WinInet on client extensively) we
increased max number of HTTP requests to 4 so now even 2 clients eating up 8
IIS connections.
Well I think I will try to write a kind of proxy I've described.
Regards,
Vladimir.
"Paul Lynch" <paul....@nospam.com> wrote in message
news:c7setvs8qdoj02ola...@4ax.com...
Vladimir Petter
Thanks for response.
Could you please point me to any resources telling about "connection
backlog"?
All though I think the trick with proxy could work. The question is if such
a product already exists or I have to write it.
Thanks,
Vladimir.
"Phil Frisbie, Jr." <ph...@hawksoft.com> wrote in message
news:%23FpHwH1...@TK2MSFTNGP12.phx.gbl...
Tom Miller
folder accross a LAN?
Tom
"Vladimir Petter" <vla...@hotmail.com> wrote in message
news:%232n$2y0vDH...@TK2MSFTNGP11.phx.gbl...
Vladimir Petter
Thanks for reply.
Good idea, but would not do in my case :(. WEB application implemented with
ASPs and have to collaborate with a set of DCOM servers. Having DCOM servers
on another machine may become a pain in the but especially with coming XP
SP2.
Thanks,
Vladimir.
"Tom Miller" <tlgal...@chatnfiles.com> wrote in message
news:vtf0ure...@corp.supernews.com...
Jeff Cochran
<vla...@hotmail.com> wrote:
>Dear All,
>
>May be somebody knows if there is a product that may be addressing following
>issue:
>
> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is
>limited by 10 simultaneous TCP connections.
>If 11'th connection comes it going to get HTTP error.
> - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS
>(and keep-alive is on) then IE will keep this connection
>up to ~30 sec (even if does not have any requests to send).
> - Each IE client makes up to 2 connections to the IIS and keeps them in
>cash.
>
> So 10 simultaneous IE clients will eat up to 10 connections and 11'th
>user may get an error. This becomes a limitation for my WEB application.
>
>What I am looking for is a Proxy that would not have limitation on number of
>incoming TCP connections (IE to Proxy), but would be aware of IIS limitation
>(10 connections on Professional platform) and put client's request on hold
>until IIS connection would become available.
You won't find that, and it may not even be possible to write your
own. The limit is inherent to the operating system, not IIS itself.
>I've already considered possibility of turning off keep-alive on the server
>side and now interested only in discussion of the option described above
>(Proxy).
Then I'll honor your request and not tell you the options available
that would work for you.
Jeff
Vladimir Petter
Thanks for reply.
From my current study it seams to me that proxy solution should work. The
limit of connections on Professional OS has nothing to do with IIS limit (10
connections). So proxy should be able handle high number of incoming
connections and make sure that it does not go above 10 on IIS.
Well if there is other possibilities (except upgrade to Server) that I
overlooked then I really would like to hear it out :-).
Thanks,
Vladimir.
"Jeff Cochran" <jcochra...@naplesgov.com> wrote in message
news:3fdd8ffa...@msnews.microsoft.com...
Phil Frisbie, Jr.
> Vladimir,
>
> The best you can hope for is to do this :
>
> "If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on
> Microsoft Windows XP Professional, disable HTTP keep-alives in the
> properties of the Web site. When you do this, a limit of 10 concurrent
> connections still exists, but IIS does not maintain connections for
> inactive users."
>
> but you cannot get away from the 10 concurrent connection limit - its
> hard-coded in the 'desktop' versions of Windows 2000 and XP
Just to clarify this statement... The 10 concurrent connection limit is 'hard
coded' into IIS, not into XP. Even Windows 95 can have over 200 active TCP
connections with other server software.
> Error Message: HTTP 403.9 - Access Forbidden: Too Many Users Are
> Connected
> http://support.microsoft.com/?id=262635
>
>
>
> Regards,
>
> Paul Lynch
> MCSE
--
Phil Frisbie, Jr.
> Hello Phil,
>
> Thanks for response.
> Could you please point me to any resources telling about "connection
> backlog"?
Basically, the connection backlog determines how fast clients can connect. In
other words, if too many clients request a connect at about the same time, the
connection backlog fills up and some will be rejected. You would need to see
more than a few hundred connections per second before this would become a problem.
Phil Frisbie, Jr.
> On Wed, 10 Dec 2003 10:01:44 -0800, "Vladimir Petter"
> <vla...@hotmail.com> wrote:
>
>
>>Dear All,
>>
>>May be somebody knows if there is a product that may be addressing following
>>issue:
>>
>> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is
>>limited by 10 simultaneous TCP connections.
>>If 11'th connection comes it going to get HTTP error.
>> - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS
>>(and keep-alive is on) then IE will keep this connection
>>up to ~30 sec (even if does not have any requests to send).
>> - Each IE client makes up to 2 connections to the IIS and keeps them in
>>cash.
>>
>> So 10 simultaneous IE clients will eat up to 10 connections and 11'th
>>user may get an error. This becomes a limitation for my WEB application.
>>
>>What I am looking for is a Proxy that would not have limitation on number of
>>incoming TCP connections (IE to Proxy), but would be aware of IIS limitation
>>(10 connections on Professional platform) and put client's request on hold
>>until IIS connection would become available.
>
>
> You won't find that, and it may not even be possible to write your
> own. The limit is inherent to the operating system, not IIS itself.
That is false. The limit is coded into IIS. I have accepted more than 8000
simultaneous TCP connections on Windows 2000 and XP Pro.
>>I've already considered possibility of turning off keep-alive on the server
>>side and now interested only in discussion of the option described above
>>(Proxy).
>
>
> Then I'll honor your request and not tell you the options available
> that would work for you.
>
> Jeff
--
Bernard
tcp connection is no limit, but it may not be legal -
"Per development: The connection limit refers to the number of
redirector-based connections and is enforced for any file, print, named
pipe, or mail slot session. The TCP connection limit is not enforced, but it
may be bound by legal agreement to not permit more than 10 clients. "
--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...
"Phil Frisbie, Jr." <ph...@hawksoft.com> wrote in message
news:utq$zG3vDH...@TK2MSFTNGP09.phx.gbl...
Sami Korhonen
they were using HTTP1.0. However, both IIS and IE are using HTTP1.1 and
persistent connections by default. And that's where things get much more
complicated. Writing universal proxy for the purpose simply isn't worth the
trouble.
- Sami
Ken Schaefer
it would be cheaper than spending time/dev resources trying to write such a
specialised proxy application that you are considering.
Cheers
Ken
"Vladimir Petter" <vla...@hotmail.com> wrote in message
news:uTbTPg0...@TK2MSFTNGP09.phx.gbl...
: Dear All,
:
:
:
Jerry III
restriction given in the HTTP standard (RFC 2616)?
Jerry
"Vladimir Petter" <vla...@hotmail.com> wrote in message
news:#wxxjR1v...@TK2MSFTNGP12.phx.gbl...
Jeff Cochran
<ph...@hawksoft.com> wrote:
>Paul Lynch wrote:
>
>> Vladimir,
>>
>> The best you can hope for is to do this :
>>
>> "If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on
>> Microsoft Windows XP Professional, disable HTTP keep-alives in the
>> properties of the Web site. When you do this, a limit of 10 concurrent
>> connections still exists, but IIS does not maintain connections for
>> inactive users."
>>
>> but you cannot get away from the 10 concurrent connection limit - its
>> hard-coded in the 'desktop' versions of Windows 2000 and XP
>
>Just to clarify this statement... The 10 concurrent connection limit is 'hard
>coded' into IIS, not into XP. Even Windows 95 can have over 200 active TCP
>connections with other server software.
To clarify a bit further...
The 10 connection limit *is* the result of the operating system and
not IIS. The fact that other web server software, such as Apache,
doesn't use the operating system as tightly doesn't change that fact.
You only get ten network connections with a workstation OS.
Jeff
Jeff Cochran
>> own. The limit is inherent to the operating system, not IIS itself.
>
>That is false. The limit is coded into IIS. I have accepted more than 8000
>simultaneous TCP connections on Windows 2000 and XP Pro.
TCP/IP connections, sure. But you're not dealing with strictly a
TCP/IP connection when using IIS on a workstation operating system.
TCP/IP connections aren't limited the same way file, print, pipes,
etc. are limited. Unfortunately, IIS uses the Windows OS to handle
the connection limits. You'll find that some other products, such as
Apache, do not.
Jeff
Jeff Cochran
>limit of connections on Professional OS has nothing to do with IIS limit (10
>connections). So proxy should be able handle high number of incoming
>connections and make sure that it does not go above 10 on IIS.
So since it's simple, write one. :)
Seriously, you said you only had 15 systems or something connecting,
so the number of requests likely isn't terribly high. A caching proxy
might get you part way, and writing a proxy (well, it's not really a
proxy...) that simply submitted requests until the request got
fulfilled might work. 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.
>Well if there is other possibilities (except upgrade to Server) that I
>overlooked then I really would like to hear it out :-).
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,000 miles to
the gallon and does 0-60 in 1.2 seconds, but unless I'm willing to
design and build it myself I'm pretty unlikely to get it.
You know, if you converted to Linux, Apache and PHP, all things would
be free and there would be world peace within the decade...
Jeff
Phil Frisbie, Jr.
Sigh! You still do not understand... This has been hashed out MANY times here
and on the IIS group. Even Microsoft says the 10 connection limit is coded into
IIS, not the OS. 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 2000 or 2003
Server.
Jerry III
(even though I do believe that IIS has its own limit and the NetBIOS
protocol has its own).
Jerry
"Phil Frisbie, Jr." <ph...@hawksoft.com> wrote in message
news:eoUXhJAw...@TK2MSFTNGP11.phx.gbl...
Vladimir Petter
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. Unfortunately if
there is limit of 2 connections (default recommended by RFC) a thread
establishing 3'rd connection is going to hang for ~5 minute no meter how
soon the connection will be released. The only acceptable solution we found
so far was increasing this limit up to 4.
Vladimir.
"Jerry III" <jerr...@hotmail.com> wrote in message
news:OEaeaq8v...@TK2MSFTNGP12.phx.gbl...
Vladimir Petter
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.
Vladimir.
"Jeff Cochran" <jcochra...@naplesgov.com> wrote in message
news:3fdc8039...@msnews.microsoft.com...
Vladimir Petter
Thanks everyone for responses. The discussion went much further then I
expected :-) so let me put down what I've got so far.
1. The kind of proxy I was asking about does not exist.
2. 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?). Unfortunately with IIS/IE pair I can
handle only 1 user reliably.
3. Why I am not migrating on Apache?
Because of historical reasons and there is nothing I can do about it right
now. I am not expert in Apache and can not estimate how is it difficult to
migrate IIS/ASP/COM application to use APACHE/ASP/COM, but this would be a
different discussion anyways.
4. 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. I bet you would not expect that $50 bucks product you bought
requires from you to by Server :-(.
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.
- I am simply not interested in the OS authentication.
Regards,
Vladimir.
Paul Lynch
<ph...@hawksoft.com> wrote:
>Just to clarify this statement... The 10 concurrent connection limit is 'hard
>coded' into IIS, not into XP. Even Windows 95 can have over 200 active TCP
>connections with other server software.
Sorry Phil, but you're wrong. The 10 user connection limit in Windows
2000 and Xp Professional versions is imposed by the underlying OS not
IIS.
This limit applies to all Windows based networking, not just IIS
running on the desktop OS.
Regards,
Paul Lynch
MCSE
Jeff Cochran
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... :)
>May be you can clarify yourself on that.
>At least that contradicts to what I know so far.
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...),
is thus free to have unlimited connections. Apache (and other TCP/IP
software) doesn't make use of the underlying redirector, which is one
reason its performance is poor on Microsoft OS's, but rather uses
TCP/IP connection limits, which aren't limited on a workstation (and
rightly so, it'd be way too easy to formulate a DOS attack on a
workstation OS...).
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...)
runme.vbs
------------------------
Set site1 = GetObject("IIS://LocalHost/W3SVC/1")
if site1.MaxConnections < 40 Then
' Set connections to 40
site1.MaxConnections = 40
site1.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 40. This *may* work, it hasn't in all cases and depends
on what you're doing. It appears to expand the connection limitation
for IIS, allowing four connections per redirector connection, for a
total of 40. 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.
Jeff
Paul Lynch
<ph...@hawksoft.com> wrote:
>Sigh! You still do not understand... This has been hashed out MANY times here
>and on the IIS group. Even Microsoft says the 10 connection limit is coded into
>IIS, not the OS. To be specific, when IIS starts up, it determines if it is
>running on a desktop or server OS, and sets functional limits accordingly.
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 ?
>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.
You can sigh all you want but you are still wrong. The limit is
hard-coded to 10 concurrent connections. This KB article is quite
explicit about that fact :
"The maximum number of other computers that are permitted to
simultaneously connect over the network to Windows NT Workstation 3.5,
3.51, 4.0, and Windows 2000 Professional is ten. This limit includes
all transports and resource sharing protocols combined. This limit is
the number of simultaneous sessions from other computers the system is
permitted to host. This limit does not apply to the use of
administrative tools that attach to the system from a remote
computer."
Inbound Connections Limit in Windows
http://support.microsoft.com/?id=122920
Regards,
Paul Lynch
MCSE
Tom Kaminski [MVP]
> >I really not sure where from comes you confidence that it is OS
limitation.
>
> 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... :)
... and we haven't even begun to talk about how it's a licensing violation.
--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserver2003/community/centers/iis/
Vladimir Petter
That is a great news! Believe me I have no intentions to violate any
Licenses.
That what I am going to do:
- Apply your the script on my own risk.
- Limit number of connections on my Application Server by 5 users.
As I said the only thing I care about is to have 5 users from 5 computers be
able work reliably on Professional.
Thanks,
Vladimir.
"Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message
news:bralcv$q0...@kcweb01.netnews.att.com...
Phil Frisbie, Jr.
> On Thu, 11 Dec 2003 08:18:04 -0800, "Phil Frisbie, Jr."
> <ph...@hawksoft.com> wrote:
>
>
>>Sigh! You still do not understand... This has been hashed out MANY times here
>>and on the IIS group. Even Microsoft says the 10 connection limit is coded into
>>IIS, not the OS. To be specific, when IIS starts up, it determines if it is
>>running on a desktop or server OS, and sets functional limits accordingly.
>
> 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 ?
I am going by a dissuasion from about two years ago when someone discovered that
the core files for IIS were byte for byte exact between Windows 2000 Pro and
Server. A Microsoft rep stated that IIS checked on startup to see if it was
running on a desktop OS and made the following changes:
Limit incoming TCP connections to 10.
Disable host headers.
Use less aggressive caching.
And I am sure others I have forgotten.
>>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.
>
> You can sigh all you want but you are still wrong. The limit is
> hard-coded to 10 concurrent connections. This KB article is quite
> explicit about that fact :
>
> "The maximum number of other computers that are permitted to
> simultaneously connect over the network to Windows NT Workstation 3.5,
> 3.51, 4.0, and Windows 2000 Professional is ten. This limit includes
> all transports and resource sharing protocols combined. This limit is
> the number of simultaneous sessions from other computers the system is
> permitted to host. This limit does not apply to the use of
> administrative tools that attach to the system from a remote
> computer."
Yes, that is referring to AUTHENTICATED connections. It does not apply to any
application that simply opens up a TCP port to accept connections.
> Inbound Connections Limit in Windows
> http://support.microsoft.com/?id=122920
The very last line makes my position perfectly clear:
"Each logon session that uses the Server service counts against the connection
limit."
> Regards,
>
> Paul Lynch
> MCSE
Vladimir Petter
<quote form http://support.microsoft.com/?id=122920>
The maximum number of other computers that are permitted to simultaneously
connect over the network to Windows NT Workstation 3.5, 3.51, 4.0, and
Windows 2000 Professional is ten
<quote>
Talks about maximum computers not users. I assume MS just was not able to
trace it on computer base so the limitation is "overenforced".
Lets say how is it illegal to have 20 IEs on professional machine to work
with IIS on the same machine?
Vladimir.
"Phil Frisbie, Jr." <ph...@hawksoft.com> wrote in message
news:eUK%23AoDwD...@TK2MSFTNGP11.phx.gbl...
Jerry III
a Workstation currently) does not cost over 1 grand.
How about a solution 5: Host the application on your server and charge
clients monthly fees. Sell it to them as on-demand computing, where they
won't have to manage their own servers, since your company would take care
of it. That way you can easily do things such as fail-over which is
something the clients would never get if they host their own local server,
that would just sit idly most of the time.
Jerry
"Vladimir Petter" <vla...@hotmail.com> wrote in message
news:ekW9c#AwDHA...@TK2MSFTNGP09.phx.gbl...
Bernard
Now, I would say is hardcode in OS and some minor checking in application
and its GUI. say - when you try to increase the connection in IIS 5.1 MMC -
you get error saying you can't increase it, but if you change the metabase
number as Jeff mentionend - some claims work, some are not. in my case it
didn't work. so no sure how true for those that claims it work.
in this kb -
Inbound Connections Limit in Windows XP
http://support.microsoft.com/?id=314882
it said "The TCP connection limit is not enforced" .. which puzzle me.
http is tcp connection, right ? but you will get this error -
Error Message: Access Forbidden: Too Many Users Are Connected 403.9
http://support.microsoft.com/?id=248074
NOTE: Microsoft Windows 2000 Professional and Microsoft Windows XP
Professional automatically impose a 10-connection limit on IIS. You cannot
change this limit.
but if you install apache, and use WAS to load 100 connection,
it will run happily.
so based on the above you tell me where is the 'limit' enforced ???
IIS level ? yes - and you get 403.9
OS level ? yes - for other print sharing / smb connection and etc
the best people to answer this question, is the ms developer....
--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...
"Vladimir Petter" <vla...@hotmail.com> ????
news:eIwt1tDw...@TK2MSFTNGP11.phx.gbl...
Chris P.
> >I really not sure where from comes you confidence that it is OS
limitation.
>
> 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... :)
>
> >May be you can clarify yourself on that.
> >At least that contradicts to what I know so far.
>
> 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.
Yes workstation does have a 10 connection limit on the redirector, however
IIS (or any web server) does not use the redirector. The connection
limitation here is in IIS itself which can be proven by installing a
replacement web server. You can see the redirector connections in Computer
Management, you will notice that you have no connections displayed for web
clients.
> 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...),
> is thus free to have unlimited connections. Apache (and other TCP/IP
> software) doesn't make use of the underlying redirector, which is one
> reason its performance is poor on Microsoft OS's, but rather uses
> TCP/IP connection limits, which aren't limited on a workstation (and
> rightly so, it'd be way too easy to formulate a DOS attack on a
> workstation OS...).
>
> 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...)
It is a licensing violation of the Workstation version of IIS to try and
exceed it's spec through proxying. Best bet is to install a 3rd party web
server. Only limitation you will run into is the connection backlog as Phil
described.
Cheers,
Chris
Chris P.
> <ph...@hawksoft.com> wrote:
>
>
> >Just to clarify this statement... The 10 concurrent connection limit is
'hard
> >coded' into IIS, not into XP. Even Windows 95 can have over 200 active
TCP
> >connections with other server software.
>
> Sorry Phil, but you're wrong. The 10 user connection limit in Windows
> 2000 and Xp Professional versions is imposed by the underlying OS not
> IIS.
>
> This limit applies to all Windows based networking, not just IIS
> running on the desktop OS.
No Phil is right, you are wrong.
That limit is for the redirector only! IIS does not use the redirector but
co-incidentally also has a 10 connection limitation in the workstation
build.
TCP has no such limitation, it only has a backlog limitation and a memory
limitation. Install a 3rd party web server and you will not have the 10
connection limitation only a problem connecting many clients in quick
succession.
Paul Lynch
wrote:
>No Phil is right, you are wrong.
>
>That limit is for the redirector only! IIS does not use the redirector but
>co-incidentally also has a 10 connection limitation in the workstation
>build.
>
>TCP has no such limitation, it only has a backlog limitation and a memory
>limitation. Install a 3rd party web server and you will not have the 10
>connection limitation only a problem connecting many clients in quick
>succession.
>
Well somebody is definitely wrong here, that's for sure ;-)
You are now suggesting that IIS is a different build on desktop OS's.
However Phil originally suggested that IIS is identical on both
desktop and server and that it performs some form of check when
starting and then sets limits based on the results of that check.
I've never heard of any such check, but I have read a few KB articles
which suggest that the TCP connection limit is hard-coded in the OS
and that this limit also affects IIS.
Regards,
Paul Lynch
MCSE
Chris P.
My bad, it's the same build it just does an OS check to see if your running
server or workstation.
There is no TCP connection limit, I just ran FTP with 30 connections - not
IIS mind you.
Cheers,
Chris
Douglas Cohn
Wrtten by Cari
www.coribright.com
For unlimited connections, use either
> one of the (now discotninued) Windows 2000 Server family or the new
Windows
> 2003 Server family.