Thanks to bcastner... I have worked out Apache can handle as many concerrent connections as you system and line can handle.... in other words, Apache will not be the bottle neck when it comes to running a web server...
Thought I'd post an anwser I got elsewhere in case it benefits some one else.
danielhozac, just confirming what you already told me
Wullie have you got a link to that info... you are the first source out of about 25 that has said that. My understanding is that the limits for concurrent connection to file and print sharing and IIS 5.1 (XP) are hard coded into Windows by MS, as nobody at MS got their mits on Apache it is free of those limitations...
An advantage of using a 3rd party software package (apache for example)is that you will not be limited by the 10 concurrent connection restriction built into PWS and IIS if you are not using the Server Editions of Windows.
Yes, Windows 2000 Professional and Windows XP Professional only have a 10-concurrent *incoming* user limit (AFAIK, it is an OS restriction, not an application restriction). They can make unlimited outgoing connections. Port 80 is not an exception to this, I'm sure. I am running Apache on Windows 2000 Professional, and I frequently get "10061 - Connection refused" errors (I access it from the LAN as well as on the internet).
I am thinking of upgrading to linux to get rid of the concurrent user limit.
I would think that if it was possible to run Apache on a 2K Pro machine, that a lot of people would use 2K Pro/XP Pro to run production webservers as it's cheaper than the 2K Server version.
um guys just to let you know I run apache on an xp pro machine with only 256 megs of ram and a xp2000 cpu. I have had a test with a few of my friends at the local college and all 79 were able to connect to the server with no problems. When they all downloaded the same file at the same time via a predetermined time the server did slow down a bit but not enough to affect realtime performance. On a dsl line 1.5 up/down not bad for 59.95 per month. No concurrent connection problems.
So Im not sure where the 10 concurrent limit comes into play.
"So Im not sure where the 10 concurrent limit comes into play. "
Then they were not all connected at the same time - the requests were all handled quickly. Try getting more than 10 people to download a 10mb+ file at once via dialup, and I bet some will be refused. Wullie is right - Apache has no limit, but Windows XP Home is limited to 5 simultaneous connections, XP Pro, NT and 2000 Pro are all 10. If this were not true, MS wouldn't sell too many copies of Windows Server OS'.
Switch to linux to get more than 10 connections free.
Newposter
"Good judgment comes from experience. Experience comes from bad judgment."
It would be easier and cheaper to run Linux. If it isn't an emergency, I would spend a couple days getting comfortable with Linux and go that route. Webmin helps with configuring the server nicely.
flyingwolf23: My test was having about 1400 people connect to Apache at the same time. There was definitely collisions on mine... I was getting connection refused errors while trying to access Apache on the LAN.
However, I have wondered if Apache listened on a different port (a higher one, like maybe 6000?) if the connection limit applies. The limit may only apply to service ports or ports <1024.
I haven't had the time to test that theory, though.
Unfortunatly I dont know that many people so getting that type of test done is going to be rather hard. However I'm happy with my current setup and have been getting my hands dirty with linux (Rh9) and am most likely goint to be switching over to a dedicated box in the next few months.
I'm running two Windows workstations:
1) Windows XP Pro Workstation (Set up with Apache Tomcat server running on port 80.)
2) Windows 2000 Workstation.
I created a simple command file on the W2K workstation that opens 30 sessions to the Apache Tomcat server on the WinXP workstation (by using telnet)
The command line simply contained thirty of the following lines (Ip address obviously the WinXP machine):
start telnet 192.168.2.100 80
All connections were opened, none were refused.
On the WinXP machine, I entered the command netstat -a and I saw that all connections were Established.
TCP ram:http 192.168.2.123:3013 ESTABLISHED
This convinces me that 10 is not the limit for TCP connections in the WinXP Pro OS.
How To Increase Your Connections Up to 40 which normally equates to 20 users . . .
(tested on Windows 2000 and worked fine, did not test on Windows XP but should work fine)
1. Download Microsoft's Metabase Editor (MetaEdit) at
I'd have to say, prove it. First of all, limit is 10 connections, not 20. Second, it assumes use of IIS. For anyone running Apache, this is useless for that reason alone.
Newposter
"Good judgment comes from experience. Experience comes from bad judgment."
MFPRICE--thanks for the metaedit tip...worked like a charm...I can now simultaneoulsy host 39 connections from different users/machines/ip addresses...without hitting my head on the Win2k Pro 10 user limit.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.