I tried to connect 40 clients to a webservice that is on Windows XP and I get no connection.
Are the inbound TCP/IP connections on Windows XP limited to 10 at any one time?
The TCP connection limit is not enforced, but it may be bound by legal agreement to not permit more than 10 clients.
See this from Microsoft: Inbound connections limit in Windows XP
In a command prompt type:
net config server
This shows max allowed logged on users, and max open files per session
Technically it is sessions. And it has nothing to do with TCP/IP.
This is to prevent the Home and Professional edition Windows from being used as Servers.
I don't blame them. If they supported more concurrent sessions, that would mean they would have to test that limit. Then fix whatever bugs that show up. And then more testing. All for a Home edition. . .
That's less time for features that the rest of us use. BTW, that limit was removed in Vista SP2.
The default connection limit for IIS on Windows XP is 10 connections. This can be increased to 40 connections, but not higher than that.
Find the adsutil.vbs script (should be in c:\inetpub\AdminScripts or similar) and run the following command:
adsutil set w3svc/MaxConnections 40
You can also disable "allow keepalives" in IIS which should allow you to serve connections faster, though it is still limited to the number of concurrent connections above. If it is a simple webservice, you shouldn't really need keepalives anyway.
Besides the obvious answer of purchasing a Server OS, or to use Apache for Windows (if you aren't running ASP.net apps), since it does not have the same limit that IIS has.
is Windows XP only allows 10 inbound TCP/IP connections at any one time ?
No, it definitely allows many more than that. Else how could people do things like run torrents?
Edit: According to Nicu's answer, I'm probably mistaken. I'm amazed by the link he provided. What complete (#profanity#).
i try to connect 40 client to my webservice that on Windows-XP and i get no connection
I'm not entirely sure what you really mean here. Are you running a local web server?
You can use various tools to help you see what's going on with your network. Task Manager gives a very basic view. "perfmon.exe" gives a lot more. And Wireshark gives tons of information. You can also try Event Viewer for hints.
Maybe you have some strange firewall setting that's causing this behavior? Do you have other network interfaces in your machine you can use to see if it's a hardware or interface-specific effect?
More detail about your particular situation may be helpful in providing meaningful answers. Take care
While your question is in regards strictly to inbound connections, I put this here just for a FYI.
Outbound connections are limited by Windows XP to help prevent viruses and malware from rapidly spreading and infecting a network (this was only patched after SP2).
Before SP2, the maximum number of connections was virtually unlimited (technically, the maximum value of a 16-bit integer). LvlLord believes that 50 is a (sane) value that is good enough for most people. You can go higher if you wish, but do note that if you happen to get a virus, you'll also spread it much faster.
As an aside, I also believe nLite can perform this patch before creating an ISO (so you don't have to each time you format).