"Tim" said:
What are the ip socket connection limitations in Windows
2000 server. I believe it should be 2 to the 32nd power
because its a 32 bit ip socket stack but I am not sure.
Every socket that you have open requires a certain amount of memory to be
reserved for its use. And I'm not talking swap space, this is physical
memory - real, non-paged memory. [For performance reasons, you understand]
That's the usual limit on the number of sockets you can open.
Now, as for the range of ports allowed, remember that each TCP or UDP socket
has a local address, a remote address, a local port, a remote port, and a
protocol ( TCP or UDP ). The local address is restricted by what addresses
your system has been assigned. The remote address is 0 if the socket is
listening for input from 'anywhere', or it's set to the address of the
connected client. Each end defines its own port value, and chooses from
between 1 and 65535 (0 is generally not available for use). Servers listen
on fixed ports, usually in the range of 1 to 1023 - the "well-known ports".
Clients connect from ephemeral ports, by default in the range of 1024 to
5000 (for no really good reason other than it's a convenient number). All
ports from 1 to 65535 can be used by applications that wish to do so.
Hope that answers your question.
Alun.
~~~~
[Please don't email posters, if a Usenet response is appropriate.]
